Pete Dowson

As documented in the FSUIPC SDK, you can set LLAPBH (Latitude, Longitude, Altitude, Pitch, Bank, Heading). In FS2002 and before the PBH could only be set in Pause, Slew, or zero-simulation rate modes. In FS2004 all six aspects can be set even in flight mode. Whether this can result in a smoother and more "realistic" flight than the video method, I really have no idea. I don't know anyone who has done any comparisons. One this I know can't be done through FSUIPC, and that is controlling the airspeed directly. Maybe that's a deciding factor. There is a third way, of course, and that is using the multiplayer interface to feed in the flight of another aircraft, and have the user's FS set in MP "observer" mode rather than in his own aircraft. If it is the visual path you want, then the facilities available in FSUIPC will do all that. Whether you use Slew mode or not would need to be a choice based on what you find, but as documented in the FSUIPC SDK you can switch that on and off through the interface. I would not keep changing the time in FS, however. This could cause nasty pauses whilst things redraw. Best to set the start time (both Local and UTC or Zulu) then let FS update its time naturally with you keeping pace with the inputs. For smoothness you'll want to interpolate values between your GPS readouts which are probably rather infrequent. Aim at at least 10 frames per second, ideally around 20. (18 corresponds to Windows "tick" time of 55 mSecs, so would be useful). Interpolation of Lat/Lon/Alt would be easier if you have the Ground Speed and Track values as well, but you would not be using either of those directly in FS. Regards, Pete

Okay, I'll fix it and send you another Beta. Pete

Flaps have detentes, special positions where they stop, which is why INC/DEC type parameters suit them. Spoilers are continuous, so FS doesn't provide an INC/DEC for them. It would be easy enough for me to add a couple of "pseudo" FS commands to FSUIPC's Keys and Buttons pages. It isn't on my list at present because no one's ever asked for this, but I'll add it now. The only thing I'm not clear on is the increment value. How many steps would you think appropriate between Spoilers fully raised, and spoilers down, off? I can make it configurable in the INI but it is always best if there's a good default. Perhaps 32 steps, or maybe only 16? What do you think. Regards, Pete

Is this with FS2000, 2002 or 2004? Possibly the Menu ID's have changed. I'll check when I know what version of FS you've checked it with. Certainly it isn't anything changed in FSUIPC, so I assume it never operated on the World menu in FS2004? It should be easy enough to fix. Regards, Pete

There was the facility for moving fuel fore to aft or vice versa in the Concorde, to maintain the CofG in the correct range. I suppose that still works in FS2004, but certainly I know of no way to move fuel between left/right/centre tanks. I doubt if that feature exists on many if any real aircraft, does it? Regards, Pete

Not much more is "findable" in the old sense. FS2002 uses GLOBALS.DLL but a little and FS2004 even less. To provide offsets for such control someone would have to hack the sound subsystem. It isn't easy anymore, what with C++ and the convoluted code the Class system produces. Regards, Pete

Oh, right. Not sure why, but then I don't know VB, lrt along VB.NET. Er .. it isn't in my copy, it's declared as 4. Maybe it was in an old version of the SDK? I don't have one so I can't check I'm afraid. Well, from the sorts of questions I get on VB problems I think most are due to the language, not the user. I think it is ambiguous and imprecise, and the more I know about it the more I think it's a bad choice for beginners (or for anyone, for that matter). But maybe I'm just a little prejudiced! :D Regards, Pete

Not sure they ever worked really. Maybe with some aircraft models where there are separate fuel selector switches and cross-feed valves, if such is possible to implement in FS. You will find, however, that on the default 737, for example, the FUEL_SELECTOR_LEFT control selects crossfeed left-to-right, and so on. The X-Feed switch graphic is ambiguous, and I find it misleading, as it shows the destination of the fuel, not the source, so LEFT to RIGHT shows as "Right" on the switch. Regards, Pete

No, I've not catered for that. The 3 engined arrangement in FSUIPC is 1->12 and 2->3, as documented. I don't see any point in 1->13, 2->2 as the main use of two throttles is for asymmetric thrust -- either to aid in ground steering or to deal with engine troubles. Being able to control the centre engine separately seems to confer no benefits at all as far as I can see. Regards, Pete

Yes, it seems like the pumps are only boosters -- for low wing GA aircraft and for aerobatics. The fuel pressure should increase with them on. Regards, Pete

I have two, one with 256Mb RAM and an older one with 128. I would be too. Sorry. I've had some odd graphics glitches but the latest drivers (1.5.107 I think?) seem pretty well perfect with FS2004 so far. I use them at 2400 x 600, but with no FS panel (virtual or 2D) at all, just the forward view at 0.50x Zoom. I did try 3840 x 1024, but really for the outside view that resolution isn't needed and the lower gives me more frames per secwhich I then use up by having virtually all sliders at max. Have you thought it might be nothing to do with the video card and drivers, but the sound system instead? Try it with no sound, and with the sound acceleration turned down one or two notches (use DxDiag for that). It wouldn't surprise me if it were the sound drivers. Both my Parhelia's are on Pentium based PCs, though it shouldn't really make any difference, unless the Matrox drivers have some incompatibility with AMD stuff. Were both your systems AMD? Same chipset? Really? Mind you, if it is your sound system you can't really blame them for being puzzled too. Just to see if it's some problems with AGP you could try turning AGP off (in DxDiag too) -- there was a time when AMD-based mobos had AGP problems. I think you have to make sure you have the latest "minidrivers" or some such. Whether that applies to your mobo's chipset or not I wouldn't know, but it's worth checking. Sorry, I've really no other ideas. Regards, Pete

Sorry, so many things to do, not enough hours. And it's a separate utility with more dependence on releases of FliteStar and FliteMap than FS. If I had to update it specifically for FS2004 I would have changed the documentation and everything. But no such change was needed so I didn't. Regards, Pete

Yes. It could be done, as I said. I don't want to do it. I'm really not able to look for more things to do, I have enough to last years as it is. i would dearly love to find time to actually fly FS now and then too. :( If it is so desirable I'm sure someone will want to do it, just not I. Sorry. Of course, they don't need to use WideFS in any case. The interface to FSUIPC is published. I'm sure anyone could program an external program, or even another DLL, with a protocol of their own choosing. I know, for instance, that the 777 cockpit designed and nearly finished (?)some time back by Chris Brett has its own TCP/IP links between its components. Regards, Pete

Ah, right. Yes, I didn't notice that. Looks like the 32-bit result was being written to an 8-bit location and so spilling over into another value. Since it would normally be zero that would clear part of that value. You were lucky (or unlucky) that it didn't overwrite something more important and crash the program! :wink: I still think that you should either read all 4 bytes of Flaps or set your Flaps = 0 before reading, in case there's rubbish in the high part. Don't forget, when you start reading more stuff, it is much more efficient to do a list of "FSUIPC_Reads" and then one "FSUIPC_Process" for the lot. Only the "Process" call actually goes into FSUIPC. I still don't understand why there's that "FSUIPC_Get", though. Regards, Pete

What does "FSUIPC_Get" do? Surely after the Process call the Integer "Flaps" already contains the value, which should certainly be 16383 for full flaps. I don't know what "ToString" does either, but it's why you need a "Get" which is really puzzling me. I'm afraid you'll need to talk to someone who know something about VB or VB.NET (if they are different?). Incidentally, it is odd seeing "3036" for the flaps offset of 0BDC. Doesn't VB.NET have the hex facility either (&H0BDC I think?). Also, note that 0BDC is defined as 4 bytes (i.e. a full 32-bit integer) even though the value never exceeds the 2-byte capacity. However, you've defined "Flaps" as "Integer" which I assume is 32 bits (4 bytes). I don't know if VB clears the values to zero for you -- C/C++ certainly doesn't for dynamic (stack-based) variables -- so to be safe you should either read 4 bytes or set Flaps = 0 first. Regards, Pete

No, not from me. But it would be easy enough for anyone to write an external program to do that using the FSUIPC interface. It would be pretty jerky unless the program interpolated quite a bit between readings -- I think most GPS outputs are not frquent enough for reasonable fps without some crafty programming. This question, or similar, has arisen several times and I'm sure someone somewhere must either have done such a thing already, or be working on it now. Try doing a Google search. Regards, Pete

No to FSUIPC, it is an FS module. I don't think Microsoft provide a Linux version of FS do they? If you mean WideClient, then I suppose it would be possible, but it isn't going to be me doing it I'm afraid. Several years ago someone did start on something like that and I provided some details, but I never heard anything after. I'm afraid there's no written specifications of the protocol WideFS uses, but it can be deciphered using TCP/IP tools, and that's what they did. I just answered questions now and then. Regards, Pete

How would you use it? Are there now programs which receive NMEA 0183 signals on USB? I've got the offical NMEA specifications and they only lay down standards for RS232 and similar serial links. They may be out of date now, of course, so do you have revised details? The other problem which I don't really know how to deal with is a USB device driver. All USB thngs seem to have to either abide by certain global standards (HID, such a joysticks, keyboards, mice, and Disks or similar storage devices for instance), or need specifically-written drivers. So where would these come from? Do the makers of the software you've got which can read NMEA on USB supply drivers for writing it too? If you are looking to use USB simply because you have no serial ports available, then there are serial port adapters for USB which do the job. I think they are quite cheap too, now. Regards, Pete

Don't they already? I wasn't aware there was any change in the format. In fact I'm sure I've loaded them on FS2004 already. Can you elucidate please? Regards, Pete

Not a menu, I think there's far too many of those already. how about a HotKey, you could define it in the INI file? A toggle. All "aircraft settings" should be saved in the Flight file. that's what it's for. AutoSave doesn't save any files at all itself, it simply calls the same routine as FS's Flights-Save menu option. What's missing? Look in a FLT file and see all the stuff FS saves. I can only think these are 3rd party add-ons doing their own thing and not using FS values. There's really no way I'd have acces to those even if AutoSave was to get involved in file transfers. This is really something the aircraft/panel makers could take care of themselves, like the .FMS files saved by one well-known example. Really? That's an FS deficiency then, and should be reported to Micrsoft! Again, I'm not sure I can even get the data let alone restore it on reload. All that stuff is done by FS, not I. Sorry. Regards, Pete

Thanks for letting me know. Glad you sorted it! Pete

I don't know VB, but normally the result is merely an indication of success or failure. The FSUIPC_Read operation reads a block of memory, it isn't specifically an integer or anything else. It could be a whole batch of integers, or a string of characters, et cetera et cetera. What you then treat the data as will vary according to what you are reading and how you want to use it. In C/C++ "long" is the same as "int". Do you mean unsigned as opposed to signed? If VB cannot handle unsigned numbers then, I'm sorry, I don't know what to advise you. I've no idea how you get 255's for full flaps -- the Integer value is 16383, or hex 3FFF. If you only read one byte (character) you'll get 255 (the FF in the first byte), but that could equally refer to 63 other flap positions (00FF to 3EFF, hex 3F = 63 decimal). The pitch and bank values are easy, because they are simple signed 32-bit integers, which I'm sure is the default Integer value type in VB. But it is 4 bytes you need to tell the Read routine -- if you are getting 255 for full flaps it sounds very much like you are reading only 1 byte (8-bits) and so only getting a quaerter of the total data needed for a 32-bit integer. Regards, Pete

Just delete WideServer.DLL. FSUIPC doesn't know or care about it -- it's the other way round, WideServer needs FSUIPC. Regards, Pete

If you have the original email from SimMarket, just print it and save it, keep it safe as you would anything else you pay for. if you want to use the programs on a different PC just enter all the details again, exactly as before. Same if you need to re-format your disk or re-install Windows. If you've already lost the email notification but still have a registered installation, then make a safe copy of the FSUIPC.KEY file (it's in the FS modules folder, with FSUIPC), or even print it out for future reference. it is an ordinary text file and can be read and printed. If you've already lost the keys and overwritten the FSUIPC.KEY file, then you will have to explain the situation to customer services at http://www.simmarket.com. Provide the same name and details as you did originally and they should be able to find you on their database. Regards, Pete

AhI believe there was a problem originally with FSNav. I think you may need to go download the latest version. The first version issued for FS2004 did cause problems. Sorry, i did not remember that myself either. Regards, Pete