FSUIPC and ESDG Citation X 2.0

[Capt. Walden]

Hey all,

My name is Josh and I am a BETA tester for Eaglesoft. I have been flying their Citation X 2.0 since its phases in January until now, working on correcting post release bugs and the beginning phases of other aircraft. Now here is the interesting part. I ve bought, purchased, whatever you want to call i t, and registered FSUIPC. The logs all concur, theres a key there, and it shows I ve made a legitmate purchase of the 3.9 module, which I bought for the sole purpose of this aircraft.

My boss, so to speak, Ed Wilson, the guage programmer at ESDG, also has a registered copy of 3.9. We have everything set up correctly, no issues, throttles calibrated and everything, right pages, etc...his bird works perfectly where my FSUIPC is not allowing my guage to connect, period. I ve purchased the bird and have great credibility with everyone and this is NOT pirated software, I repeat, NOTHING is pirated software. My system is a Vista 64 bit, 4 gigs of DDR3 RAm, an HD 3870 512 megs of ram, A sata 320 gig HD and an Intel P4 2 core processor.

Any suggestions?

[Pete Dowson]

... my FSUIPC is not allowing my guage to connect, period. I ve purchased the bird and have great credibility with everyone and this is NOT pirated software, I repeat, NOTHING is pirated software. My system is a Vista 64 bit, 4 gigs of DDR3 RAm, an HD 3870 512 megs of ram, A sata 320 gig HD and an Intel P4 2 core processor.

Does it connect if you remove the FSUIPC Key file from the modules folder? If so, then the key is being checked as invalid. Check your PC's system date. If that is wrong, set to some date BEFORE the key purchase date, then it will look invalid.

If it still fails to connect, then most likely you are somehow running with different privilege levels between FS and the program trying to access FSUIPC. This doesn't seem likely with an add-in aircraft, but maybe it has an outside part? Vista actively prevents programs of different privilege levels from sharing data. If you run FS "as administrator" you have to do the same with add-ons, and vice versa.

Finally, in none of this helps, please run FS, get the problem, close FS, find the FSUIPC.LOG file (you may need to run Explorer "as administrator" to get to the true Modules folder, if you've let FS9 install into Program Files, which is protected). Show me the log.

Regards

Pete