jwenting

PSS uses their own autopilot, not the default one.

Start the APU or ground power. I think that will prevent the battery from draining (not sure though).

If you register FSUIPC you don't have to register anything else.

Cheers, was a bit worried about addons possibly installing customised dlls which would delete my licensed version.

If the person making the program takes the trouble to ask Pete for a key and sends out an update for their program it will work. If the program maintainer can't be bothered you're out of luck. And is $20 for the years of commitment Pete has shown to the community really so much? Or do you think Pete has unlimited funding to spend on supporting our hobby indefinitely?

OK, thought you were the spider in your web :) Yes, Miguel is quite human and does enjoy a good beer once in a while.

Simmarket sends your details to Pete who will send you the key. Depending on where Pete is and what he's doing this may take a few hours but normally you will get it within 24 hours.

you get the address for the pointer into the FSUIPC data set correctly? The offset is nothing more or less than the number of bytes after that address that you start reading. It often helps to set up a struct with all the fields you want programmed as datatypes of the correct length and the rest as arrays of bytes of appropriate length. You can then simply read the member of that struct after filling it using the appropriate function in the SDK (the struct is effectively a mapping over the FSUIPC memory).

The Delphi examples in the SDK doc are quite helpful in fact. Did a bit of testing last year but I seem to have deleted that code (was more a getting to know the API than anything useful anyway). You will need to dive into bits and bytes, and especially pointers. They're indispensible.

Simmarket sends the registration details to Pete who generates the keys by hand. As Pete is a human being who needs to go out from time to time (food, sleep, etc) it can take a while.

Read a 32 bit value and discard the upper (?) 16 bits.

File on Enrico's server is dated 27/07/2003 19:25 That's version 3.01

did you click the correct link? Maybe a stupid question but it has been known to happen :? Or maybe you're behind a caching proxy and they have an old version in cache. If so try turning off proxyservers in your browsersettings.

Remember reading in the FSUIPC installation instructions some time ago that is was recommended to delete the inifile when installing a new version :?

All those who have no trouble have nothing to complain about so they're just having a blast flying around :lol:

Got my key within 5 minutes. Probably beat the rush of requests, seeing I was one of the first ones... Also remember that friday evening for you would be the middle of the night for Pete.

Your post does not belong in this thread... Both Simmarket and Pete are located in timezones where it is the middle of the night by the time you registered and posted your complaint. As your code is generated by Pete personally and he is not a robot sitting there 24/7 waiting for people to request a key (he needs to sleep, eat, program the next version of FSUIPC, etc.) you'd better WAIT a while. It does say it can take a while. Now with the initial rush it might be a day or more. Rest assured I got mine within 5 minutes (but then I mailed Pete during businesshours his timezone...).

You can expect it to take a bit longer if you're asking for a key at 2AM in the morning UK time, Pete's likely to be asleep :shock:

I think Frolov's Dash8 needs FS2002 Professional installed to work correctly. If you have FS2002 Std. you will indeed be missing some gauges.

If more people had made meaningful donations it probably would have. It's because of people like you who only want freebies without ever considering the effort (in both time and money) that goes into it that Pete had to decide to charge for it. But then you're probably using a pirated version of FS as well because it should be free right?

troll alert! Roger Wilco (though despicable in it's silent installation of spyware on your computer) has nothing at all to do with FS and needs no interaction with it either. FSUIPC commercial version isn't released, I don't know if Pete even started work on it yet. This is just another person wanting to make Pete look bad it seems...

In other words Gosta, you want Pete to hand you the source so you can take his work and run with it? Because that's what frequently happens with GPL code, as I've experienced myself. I've become quite disgusted with most of you people here screaming bloody murder when someone whose work you've used for years and years asks you to put a value to that work and you say that value is NIL, then complaining when that work is removed from your free use. If you think it so useless that it's not worth the money, don't use it. If you think it is, help with your money to keep it alive. I think most if not all of you will be working overtime to find a means to crack FSUIPC once it's commercial so you can use it without paying.

Emile, have you read Pete's original statement? Seems clear to me, if you donated more than a token amount you should get a free license.

C++ Builder generates pure ANSI C++ code (plus any libraries you use of course) and all Borland libraries are also pure ANSI compliant. In that it's currently the ONLY commercial C++ environment that is fully ANSI compliant. The problem lies in the DLL entry code. Borlands code is correct but different from Microsoft code. On 99% of machines it works, but not on all. Or rather, it works together with programs and other DLLs compiled in Microsoft C++/Visual C++ almost always but there are exceptions which are almost impossible to predict. This was in fact one cause for the delay of one commercial aircraft package. The gauges were written and compiled using Borland C++ and worked fine on everyone's machines until they entered a largescale beta. Suddenly someone reported that the gauges wouldn't load and crash FS with an error that could be tracked to the fact that a Borland compiler was used. The entire codebase had to be recompiled in VC++ (and partially rewritten because VC++ has some minor differences as it's not fully ANSI compliant) and retested. Lesson learned from this: for DLLs that need to run in a program compiled with one brand compiler stick to that brand compiler only. Another advantage is that getting the DirectX import libraries and headerfiles to work with Borland C++ can be a major pain since Microsoft stopped shipping Borland import libs and headers (Borland uses a slightly different entry point definition into the implib, and needs a small change to some header definitions affecting some of the constants).

All FSUIPC versions should be/are fully backwards compatible with older versions (up to a point, 2.972 might not be fully compatible with 1.0 but Peter would know that).