Stoney3K

Well, if it started with a -ve number it must finish with one, else the compiler is in error. Sounds like, if you don't have a bug, Microsoft does! Regards, Pete Not really. If you put them up like that (in integer numbers) VB will treat the values as INTS (32-bit!) and calculating 63336 squared times 360 will cause a huge overflow. I use these formulas in floating point (adding a .0 after every number) which doesn't cause the compiler to overflow in the calculations. Worked for me in C# where it didn't work if I typed the code as integers.

Either via FSUIPC's programmable interface (i.e. from a program) by writing to the Sim Rate offset (0C1A), or by using the FS control "SIM RATE SET" with a parameter of 0. The latter can be assigned to a keypress or joystick button in FSUIPC's user options. Regards, Pete Maybe here's the right place to post my Q's... I want to do the same, syncing multiple FS's, but mainly because I found a set of really good gauges (from RealityXP) which I want to run remotely on another computer. When you run WidevieW or FS Manager the position gets synchronised but no information regarding panel data (e.g. altimeter setting, indicated airspeed, engine information, etc...) is displayed. FS Manager claims to sync this data and its debug log shows it sending engine data packets. But the engine instruments are NOT updated. (the other instruments, dependent on position and orientation, like attitude, altimeter, DG etc are updated). Is this caused by the pausing of the simulation engine? Or does FS Manager have a problem synchronising? I reckon that when you set an engine's N1 value via FSUIPC directly (after receiving it through the network from a server program) that it should change on the screen. Edit: Success! When you put the simulation engine in its slowest speed through FSUIPC (write a 0 to 0x0C1A) you can basically fiddle around with every variable in FS as the engine runs too slow to ever touch it before you will. Worked for me on the engine N1 through offset 0x2000... does not seem to work through the 'classic' offsets though (in the 0x0896 range)... only the doubles work.

The user's aircraft, the one you are flying you mean? There are no such specific indications -- you have to deduce them from all the information you have. If you are flying it in person you will know in any case. Regards Pete And if you don't you shouldn't fly either because you have a serious issue with situational awareness. Having the parking brakes on and contacting ground when at 2500ft AGL is NOT wise. :) I think he's talking about the AI aircraft. That's all explained in the FSUIPC For Programmers" document, which can be found on Pete's page with the FSUIPC SDK.

No, i'm not new to C but i've never saw a void pointer, only void methods!!!!. Thank you for the answer!!! Mirko Just pull up your Kerninghan & Ritchie... should be in there. A void * is a pointer that could be made to point to ANY data type. Meaning the same variable coud be made to point to a character first (e.g. string), next to an int and even later to some struct containing data. But not simultaneously of course. You probably shouldn't declare some variable as a void * unles you really don't know what's going to end up in it in the first place. It's a common way of transferring blocks of data of any type (e.g. "raw bits") from one place to another. Later in the code will be decided what data it actually is (or, if you're writing a dumb copy, for example, you don't want to care about the data type and output a void * as well). The reason you see voids in front of a function a lot is because you don't want every function to return a value. In the case of a void function it will return a variable of no data type, e.g. no return value. You can make a function void * to let it return a raw memory address. Just to let you know: Pointers are pretty messy, and don't fiddle with them too much or you'll cause defintite memory leaks or hard crashes. C doesn't have a way of checking whether an application stays within its own memory space (C++, however, does have a mechanism and raises an EAccessViolation if you 'step out of bounds'.)

Shame my Zire31 doesn't have BT either... the GPS Pilot demo ran well on it. I just couldn't get it to talk with FS2004... The Palm has a native USB to RS232 chip built in. This may be a standard chip from a different manufacturer, but the Vendor and Product ID's have been changed. Palms (at least the older types) are only able to communicate through RS232 which gets converted into USB internally. Palm has kits available (at least for the Zire 31) to connect a GPS receiver to it, which obviously has the industry standard RS232 connector. If you hook that via a null modem cable to your PC's serial port (yes, you DO have a regular COM port, right?) and things should work like you connected a REAL GPS unit through the COM port. The Palm doesn't know it's talking to a PC and the PC doesn't know it's talking to a Palm. As long as they're speaking the same language... I haven't been able to make this work here because I couldn't find supplier for a GPS kit. Maybe it's available online.

Nice work... you got the panelwork from Schaeffer? Looks like their engraved metal panels... Any solutions already for the dual rotaries in the panel? If you use the PSOne screen , don't you have trouble with clearances around the switches? I'm a real RealityXP fan myself and I'm currently attempting to write a program that can link several copies of FS over a network. Kind of like WidevieW, but more specific to panels. So it doesn't focus on the outside visuals primarily, but syncing every bit of data that's in gauges, so engines, navigation, GPS, etc... Is there a way to transfer flight plans through FSUIPC? I know I can get the inbound FIX and DTK from the GPS values, but I'm not sure if it's possible to transfer a complete flight plan.

Hi people, I'm developing my own Glass Cockpit suite and was wondering if I could use a set of offsets in the user area of the FSUIPC memory. Things like EFIS values, FMS values and the like will be stored there, much like Project Magenta does. I just wanted to get confirmation before I start writing somewhere and may get in the way of other software when I publish my package, and the Programmer's Manual also says I should contact Pete on this. So here I am ;)