Pete Dowson

Ouch! That does indeed imply that Goflight are using FSUIPC for something. They haven't approached me about this, so there's no access key issued for their modules. Even if they were to get a key it wouldn't work because they are using an incorrect method to access FSUIPC in the first place -- one which will certainly cause problems with other modules or gauges in due course in any case. If you were to pay for and register FSUIPC then those modules may work, but if you ever have any other gauge or module using the same incorrect access method they could easily corrupt each other's data (as they would be forced to share the data interchange memory space), probably causing odd problems or even FS crashes. Please, when you've verified this, do report it to GoFlight support. Regards, Pete

Erwhy not just assign the button to the PTT controls in FSUIPC, which works fine with the current Squawkbox no matter whether it is on the same PC as FS or on another via WideClient. You don't have to do anything in any INI files. the keyboard method hasn't been used for ages and probably involves fiddling around with other parameters in any case. Just use the easy method provided for the purpse (and documented too, even!). please. Regards, Pete

The GoFlight modules don't use FSUIPC at all as far as I know. "offset 0238 size 3" is the FS local time (hours, minutes, seconds). In the FSUIPC log the "P1432" is a reference to a Process which will have been logged shortly before that line -- 1432 is the process "ID". See if that tells you. If it says it is "FS9.exe" then it is a gauge or DLL using FSUIPC incorrectly. Regards, Pete

That is NOT from the "latest" FSUIPC, but from one which is now many months old! Download the current release (which is 3.60) from http://www.schiratti.com/dowson, or get the very latest interim version from the Interim Versions announcement above. ALWAYS check the version number and report that, never just say "latest" as that is totally meaningless, as this proves! To find the version number simply right-click on the FSUIPC.DLL file itself and select "Properties" then "Version". The one you are trying dates from before the FS9.1 update Microsoft released for FS2004. Pete

Yes. did you check the documentation? If not why don't you simply download the ZIP and read the documentation, see what you think? Pete

A void pointer is one which can be cast into a pointer to anything. That's the whole point. Please check your C programming references. If the compiler doesn't do it automatically, try using an explicit case, but it does rather spoil the point of having void pointers in the first place. Regards, Pete

Well I just googled his name and came up with it in lots of places -- regarding airliner photographs. Try for instance http://www.airliners.net/message/index.main?id=1049029&photographer=Matthias%20Neusinger Regards, Pete

Not that I know about, sorry. It wasn't even me who found these values to map in the first place, but some other clever person. I wish I knew -- if I did I'd add it to FSUIPC, but I doubt if they'd want to release their secrets. Are you sure they are not simply editing the aircraft or flight file then loading it? Maybe the "reload aircraft" control would do it, but it seems unlikely. Regards, Pete

Isn't that where I referred you in the fist place? ("...the current view mode TYPE in offset 8320."). Remember? All I know is written in the documentation. And I only know that because Matthias told me. Regards, Pete

In what way? You can control the zoom at least. Probably other things using the discoveries by Matthias Neusinger which were added to FSUIPC recently. Have you checked? Pete

I don't have any pages anywhere outside this Forum. But equally I've never actually ordered any keys for my programs so I've never seen the order acknowledgment. If it is misleading you should raise a Problem Ticket about it so it gets amended, but I must say this is the very first time I've had such a query raised, and that is after 35 months of operation. I think that is automatic, whilst the key notification has to be generated by a human being. Hence the possibility of up to 24 hours delay, depending on workload, time-of-day etc. Regards Pete

Does it? I thought they only had names. However, I've no real way of getting information on which has focus other than the current view mode TYPE in offset 8320. Will that do? Pete

I think you must be misreading something. The keys will arrive in a separate email. If they don't within 24 hours, only then should you raise a problem ticket at SimMarket. I'm fairly sure it explains this on the site. Pete

Not sure how that can ever happen merely changing aircraft, but the throttle settings are saved in the FLT files, when you save a flight. Just set them to idle and save a flight, marking it as the one to be default so it loads automatically next time. Pete

Ah, Niko Kaan's program. Yes. I know of that. Sorry, there are so many programs that I do need context to identify them. I recall that he was, in an earlier version, using the same offsets as Project Magenta, but brought out a later one which uses offsets especially reserved for him. However, I am sorry, I do not know any more than the fact that the program has a set of offsets used to control his interface to the aircraft. As far as I knew everything was explained in his documentation. All FSUIPC is doing here is acting as a postbox -- one program (presumably your Phidgets software) will be writing values to offsets, and this FSConv program will be reading them and passing them on the the aircraft code -- and vice versa. You can, of course, enable IPC read and write logging in FSUIPC to see what data is being passed back and forth, but really, for this sort of application, that's about the limit of FSUIPC provisions. Regards, Pete

No, sorry. It is not something I have ever seen, nor heard reported. Mind you, I rarely run FS with the menu bar showing in any case. It is better without, and the menu comes back automatically if you press the ALT key to get into it. Sorry. I hope someone else may be able to help. Regards Pete

Are you sure you are asking in the right place? What is "fsconv"? Pete

The modules menu is not unique to FSUIPC or AdvDisp (my only two that use it). Have you checked to see what else is in there? Anyway, why not hide the menu bar (right click on the outside view and select Hide Menu) -- it only helps slow things down in any case. Regards, Pete

For FSUIPC delete the FSUIPC.INI file. For FS2004 delete the FS9.CFG file. No sorry. Regards, Pete

It sounds like they write directly to the FSUIPC offsets, rather than act like real joysticks or send Axis controls. This is the same as an external autopilot application would do, for instance. Yes, because if this is the case the control software is writing directly to the place where the end result of these goodies end up. In other words they bypass all manipulations and write direct to FS's simulation engine. Regards, Pete

Once calibrated correctly in FSUIPC (with a stable centre zone), just use the slope selection facilities. These allow you to flatten the central response (less sensitive) whilst maing the extremes more sensitive so you can still achieve full deflection. Slopes in the opposite direction do the reverse. Please check the documentation. There is even a picture showing a typical slope with a flattened centre. Pete

There are only two possibilities. Either there are two FSUIPC's installed, possible one with a different name, or you have had FS9 running before and it hung on termination (though the window disappeared), so that, in fact, it and FSUIPC are still running when you try to start FS9 again. To check the latter, do Ctrl + Alt + Del to bring up the Task Manager, and look in the Processes list for "FS9.exe". If it is there, delete it (select it and use the button bottom right). If this is the case then you have some add-in program (DLL or Gauge) which is misbehaving -- i.e. not termininating correctly when you close FS. You'll need to find out which it is (by trial and error) and either remove it or see if a fixed update is available. Early versions of ActiveCamera for FS9 did this, but that was fixed a long time ago. Only in the FS modules folder. Make sure you don't have one in the main FS folder. Delete FSUIPC.DLL. Then you don't have one. If you are merely updating it you don't need to delete, just copy the new one into the modules folder. If you have ever renamed it, you need to find the renamed copies and delete those. Never rename it. Regards Pete

Sounds like a faulty unit. You need a hardware repair I suspect. No way will the software make pot values drift all the time. Maybe it is something easy like the pot in the unit come adrift from its mounting and twisting. BTW version 3.53 of FSUIPC is very old now and is not supported. Regards, Pete

To be more precise, the Windows joystick API supports only 32 buttons, 6 axes and 1 POV, per joystick. devices like the EPIC get around this by simulating uo to 16 joysticks. No. It would need to be re-written to use DirectInput. Sorry, I'm not going there. I don't know. I will have enough on my plate with supporting the next version of FSX. Please ask again in a year or so. ;-) Regards, Pete

Sorry, now it is you misunderstanding me . I meant HOW are you measuring those forces? What information are you providing or expecting? There are force feedback facilities in FS, but I really don't know anything about those, and from what I've heard they don't do anything for you in this case. With typical sim controls (joysticks or yokes) the trimming merely allows you to remove your hands -- the pressure on these devices is provided by springs, trying to force the control back to centre. This is not "proper trimming" the way you mean -- so in the end it all comes down to the controls you are using. How are YOU providing the force? I cannot answer questions without understanding what you are asking. The way flight sim is with normal commercially available controls, the "in trim" setting is the one which allows you to fly in the attitude you want with the controls centred -- i.e. giving zero deflection. So, for such controls you can assume it is always out of trim when the deflection has to be held at any other point. the force needed to do so depends entirely on the springs in the controls you are using. Regards, Pete