[Networking in Windows 7 - Impossible?]

Ok, so here's my issue:

I have two machines running Windows 7, one with FSX and the other, hopefully, running FSC Commander 8.6.

I have updated everything, FSC 8.6, FSUIPC 4.60, WIDEFS 6.78 and the whole thing.

Followed the tutorials regarding the mapping of network drives, I ended up correctly installing everything not using the Program Files drive, mapping the Z: letter,etc.

All went well, ran the Database Manager, found the virtual drive and compiled all files. FSC ran smoothly allowing me to create routes and everything. However, connecting to GPS I get the following error:

"unable to connect to flight simulator Msg# (no process response)"

Following several replies I reinstalled as Admin, used different folders for FSC and the whole thing. Nothing removed this error. Read this forum over and over, no situation actually pointed out to using FSC 8 in Networked Windows 7.

Then I got a fellow simmer saying I should run everything as Administrator, so I did. When I tried to run the database manager as admin, I do get a strange error: It doesn't show me my mapped network drives. So I cannot compile as admin, so the FSC8 doesn't run as admin saying my databases are incomplete or missing. Remember I can run all as non-admin, except connect to GPS.

I think you should assume that there may be issues regarding Networked FSC8 under Windows 7 not connecting to FSX GPS data...

[FSUIPC settings with S-76A]

Hello ohanmer

That oscilation is typical of an overspeed pattern. Check the IAS and see if you exceed the red tape.

If not, then there shouldn't be any situation when you could feel this, unless you are experiencing some noise on your controler.

Meaning that the null zone should be wider and the sensitivity trimmed.

FSUIPC can be used to correct this, but honestly the Saitek Calibration program is a much better tool.

Simply run the Axys null zone and limits and widen the null zone a few clicks.

Also make sure the FS9 settings for EVERY axys in "Options/Controls/Sensitivities" is set to MAXIMUM sensitivity (this will make sure you take advantage of those small inputs and makes sure the whirlybird is more responsive to controls, but you should run the tab a bit to the right if you prefer a more sluggish cyclic) and 1/3 null zone wide (note this is a redundancy that might interfere with the previous Saitek programming).

I have the very same controlers you do (Saitek X52+ rudder Pedals). The S-76 flies like a dream with me here...

Oh! and in FSuipc be careful with the slope... it might help you with the slower response but eventually you'll gain some desire to direct control the bird.

[S-76 panel/gauge problems]

Hi

I tried to read all these threads and found none that could solve my problem.

I have two gauges (OBS and what appears to be a engine situation panel) always present in the main panel blocking my view outside.

Furthermore the panel is poorly cut in its edges causing some "smudge" specially in the right side.

I can fly normally with the situation levers in "Ground Idle" mode? Bad bug!

Are there patches and/or repaints planned?

I got some trouble controlling this bird, is the SAS system operational or just "there to see"?

[FSUIPC and GFConfig error]

Thanks Peter

I sent the report to Microsoft, as for the logs, I found the FSUIPC.Log but where can I find the Simconnect one?

[FSUIPC and GFConfig error]

After I installed the FSUIPC 4.05 version into my FSX computer I noticed that GFConfig 1.71 had an error when leaving FSX, it won't close the program and an error report for "Program Not Responding" is made.

Now, this wouldn't be a FSUIPC problem if I hadn't found that what may be causing this is an error I discovered between GFConfig and FSUIPC.

IF I load the sim with no further edit or config changes to FSUIPC all goes well no problems whatsoever with the GoFlight modules.

BUT if I load FSUIPC menu, as soon as I do so, the modules halt and don't respond anymore. I must then exit FSX and that error log for the GoFlight program is created.

I upgraded FSUIPC to 4.06 and have the same issue.

Needless to say I removed FSUIPC and these halts and error logs no longer appear.

I tried to contact GoFlight on this, but I believe GoFlight product support are like UFO's: Some of us believe they exist, others have actually seen something like them, others simply don't believe they even exist...

Thank you.

[How can I program the arm spoilers function????]

Talk about multiple threads huh?

Use the axis assignment in FSUIPC, you can even program the "stages" or detents for "spoiler Arm".

[How can I program reverse in FSX?]

Hey,

Reverse thrust is more like a command using a button press than an axis in FS. Hard to explain. You activate them using the F2 key pressing it until the reversers deploy.

If you use the buttons built in the reverser levers in your TQ-6 you'll be able to program them in FSUIPC as Buttons Assignments using the "Throttle Decrease" (each for one engine) action.

Then again, GoFlight is about to launch the new programming software compatible with FSX due next week (Nov 3rd).

[Why is FSUIPC needed for FSX?]

Ah Ok.

I used PMDG as an example, of course. I was aware that its whole programming for FSX didn't exactly depend on FSUIPC integration.

I was just trying to understand when it was said that:

If developers write their software to use the FSUIPC interface, (...), then there (sic) software will be compatable (sic) with both FSX and FS9.

I thought that this meant those FS9 built software wouldn't require much updates to work in both FS9 and FSX.

But it has been clarified, thank you.

[Why is FSUIPC needed for FSX?]

I'm sorry, but I must interrupt the line of thought that you reached here.

webbm says:

If developers write their software to use the FSUIPC interface, and not the new MS SimConnect interface, then there software will be compatable with both FSX and FS9. If we chose to just use SimConnect, then our products will work with FSX only.

Does this mean that addons such as the PMDG 747 written to use the FSUIPC 3 interface for FS9, will work with FSX using FSUIPC 4?

If so, how's this accomplished?

I ask this because PMDG will charge for a new updated version of the 747 for FSX and if the above is entirely true then they should reconsider the update and just update the installer, right?

[The need of FSUIPC]

Mr. Dowson

Thank you for being honest. I rest my case.

Harm not taken, there's an old Portuguese proverd I like to quote in these situations: "He who sees faces, does not see harts", allow me to rephrase that with "He who reads replies, does not read feelings".

Once again thank you for your excellent work for the community. Keep up the good work.

[The need of FSUIPC]

Mr. Dowson.

There's a thin line between people who make criticism look like an arrow straight to the heart and the people who wish to make an educated and fact based point to justify an investment.

I know. But believe me I belong to the last group of people. 30 Euros is a lot of money for me. And I make my investments with my mind on it. And I really don't need the sarcastic reply.

I never faced anyone who just didn't care about his/her project after being so important to some community, so I don't buy your "why bother with FSUIPC?" type of reaction. I would expect you to defend your product, not having a "I couldn't care less" reaction and actually advising me NOT to buy your product.

I am a product manager myself and I would be backrupted in no time if I was to have the same reactions to my costumers. But from your words I can understand that you don't depend on FSUIPC sales to live, but that would raise some other questions about the payware products out there which aren't called for and I don't wish to take it there.

I never said that taking advantage of Simconnect's features would be easy to work around or that FSUIPC wasn't needed. In fact that was my question all the way. I admire your work in this field. This is not mere flattering.

So, I imagined that after hearing so many people saying what I said above I should get things straight and go to the source. And I expected you to defend this 30 Euros investment.

But the tables have turned and now my question is this: Do you really want to sell FSUIPC4? If so, why don't you clear things up?

I remember when FSUIPC was free and helper simmers so much. Then you made it payware and some of us still found the investment a nice one and in some cases necessary.

But now, and from your words, I get the feeling that you don't care if I or others buy FSUIPC4. So why make it payware? If you want to make some good to the community and still justify your wasted time, I can totally agree to pay for this. I do!

I asked a simple question: Where does FSUIPC Stand?.

You answered well, and I thank you, that would be enough.

You're not saying that MY investment isn't necessary, you're saying that to EVERYONE who bought FSUIPC4.

I really am disapointed with this. Not because of what happened here, you not "selling" the product, but from the misinterpretation of my words and the fact that you used them to almost withdraw yourself from the community.

I surely didn't expect this outcome. And I apologize if you believe I was attacking you.

But with all this, my mind is made. Thank you.

I hope you continue to work on FSUIPC4 and still be able to fly.

If I was to reach your beautiful age and still be able to do what I love I would be a blessed man.

[The need of FSUIPC]

Mr. Dowson.

I've been an active user of FSUIPC in the last editions. I purchased the FSUIPC 3 edition and was happy with it, specially regarding my need to have an interface with a second PC as well as the advanced joystick calibration and anys/keys assignments which I find extremely usefull.

With this, I want to say that I didn't believe I wasted money in vain with the FSUIPC3 for FS2004. In no way.

But, all of us who read your forum threads and others, must come up with the notion that FSUIPC4 not only fails to reach the level of features of the previous edition (regarding weather settings, etc), which I believe you will correct in future versions, but also that FSUIPC for FSX is somehow redundant with the new Simconnect feature.

According to my own readings in the Simconnect dedicated SDK files, I get the idea that the interface features are already there.

So where does FSUIPC comes in, now?

In my view, FSUIPC is just placing itself between the already established Simconnect network facilities. Therefore, when someone reads the SDK and takes advantage of this new feature, I predict FSUIPC to be completely redundant.

Now, correct me if I am wrong, but why should I buy FSUIPC if Simconnect already makes the connections between machines (TCP/IP), if it already has a SDK for future free aplications for Gauge control, etc?

Don't get me wrong, sir! I just want to justify the fact that I bought FSUIPC last year and now I would need to spend another 30 Euros in something I feel isn't THAT necessary.

To tell you the thruth I only need the excellent key/axys mapping and axys facilities, and even that is being passed by free software from the hardware developers like Saitek, CH or GoFlight.

I keep reading here that you expect patches or updates to simconnet because of Simconnect still having a hard time "talking to FSX".

If your program relies in Simconnect efficiency to make network connections, wouldn't Simconnect do the job by itself? We are led to believe so by the Beta Testers and the Developers who wrote the SDK files.

If I may, I just want you to justify me why should I buy FSUIPC4 and be sure that if I am totally wrong with the above and you garantee me that FSUIPC4 is as good as an investment as FSUIPC3 was for FS9, I WILL buy it ASAP.

Thank you, Mr. Dowson.