Pete Dowson

Yes. By ICAO of Wx Station, or by Lat/Lon. Yes. You didn't look? Wouldn't it be best addressed to them, in that case? I doubt they visit here. Pete

The key file would have been generated in the FSX Modules folder then copied over for P3D. I don't know why yours didn't get copied, but you can easily do it yourself -- just copy the FSUIPC4.KEY file from your FSX modules folder to your Prepar3D modules folder. BTW please, next time you have a problem, do not append it to a thread which is about an entirely different matter. It makes it much more awkward for others trying to search for solutions! Thank you. Pete

There are quite a lot of 32-bit floating point values in the interface, so I'm surprised that this "PYUIPC" program (which is new to me) hasn't encompassed those. The underlying Intel architecture supports both 32- and 64-bit floating point values directly, as do all of the Microsoft programming language family. Anyway, there is a 64-bit version (relating to the HSI) at offset 2F88. I guess that should be the same value if VOR1 is selected -- you may need to check offset 2FAA as well, though, for validity. If you don't need such accuracy (for instance, if it is only for display on a gauge) then the 8-bit (single byte) integer version at offset 0C48 should be used. Regards Pete

What is your question? I see none. If you need to write a program to interface to FSUIPC please download the FSUIPC SDK which contains all the information you need. Regards Pete

But what about button assignments in FSX? You say you deleted all axes, but you don't mention buttons. If you don't actually diable controllers completely in FS it will sometimes automatically reassign buttons as it sees fit, according to its references files for different devices. If that is all your FSUIPC button assignments then it mostr certainly is NOT dual assignment in FSUIPC. You must look at FS assignments, or just disable controllers in FSX! Give up if you like, but why not just remove the duplicate assignments in FS, or, better, disable controllers in FS? Pete

If the wrong axis is detected first, simply use the Ignore Axis option, and Rescan. Refer to the User Guide, page 41. It's all there -- about two paragraphs after the 2nd picture on that page! Pete

If you can assign in FSX, I don't understand what the problem is in FSUIPC's normal axis assignments tab. Can you explain please? Pete

Best then to use 0D0C for them all. Don't mix them. How are you wanting to program it? Through notmal button/switch assignment? Or via a Lua plug in? Or are you writing a program interfacing through the FSUIPC application interface? Also, please read the thread about bits and numbers in the FAQ subforum. You need to know about bits in bytes and AND and OR logical operations. Pete

If FSUIPC is not producing a run-time log, then it is not being run as that is the first thing it does. Earlier you said which is completely different to what you say now. Which is it? Pete

If buttons or switches have more than one effect it is because you have them assigned to do so. If they are not because of dual assignments in FSUIPC, then check FSX -- it is most likely that you still have them assigned there. I don't see how this is at all related to mouse macros specifically. It is just plain and simple double assignment. Regards Pete

What an odd question. I'm not sure how to answer. Is it working? if so it is there. If not we need to delve deeper. Why should that specifically have disappeared if FSX hasn't? Pete

Gradually? Pete

As Paul says, the Delta is set to 32767. The Delta is the value below which changes seen in the input will be ignored. It shouldn't normally be changed -- it's only normal purpose is to eliminate small scale jitter which has no bearing on the result but wastes a lot of processing time. Check that the input value ("In") varies correctly between some large negative number, like -16383, and a similar positive number, like +16383. If not, if the axis input changes directly between such numbers, then it is defined as a digital one, not analogue, in your driver. Pete

I'm afraid I need more information. Don't try "uploading" stuff here. All the information I'd need is textual -- just paste it into a message. Info needed: * Windows error information for the "fatal error" from the Windows event viewer. * FSUIPC4 log, as far as it went (from the FS Modules folder * List of other add-ons being used. Pete

No, sorry, I didn't know that. No, it cannot do that. Joystick scanning, like all USB stuff, allows multiple users and there's nothing FSUIPC can do, without hooking into Windows drivers, to prevent it reading axes itself. No. Best just to initially do axis assignments for your general case, in FSUIPC, non-specific, then add the Profile-specific needs afterwards. Pete

They are just text, so just paste them into a message. Note that if FSUIPC is actually generating a run-time log file (FSUIPC4.LOG), then it IS getting loaded and is running. You said: which I don't fully understand. What is "the same old routine"? I recall you saying: FSX freezes to the point that I have to cancel my FS session. How do you "cancel" it? What exactly is this "freeze"? A hang, or just a slow-down? And when, exactly, does it occur? For instqance, this suggestion of mne: should certainly have changed the timing of events. Pete

I didn't find anything much about Europe, though, which is where I fly. I used to use Jeppesen FlightMap on a PC, linked to FSUIPC's GPSout facility. Very nice, but too expensive to keep updated. I'd love to have the Jeppesen stuff on my iPad, but that's silly money, obviously aimed at airlines not to ordinary hobbyists. Regards Pete

No. It is one of the main advantages of purchasing FSUIPC. Sorry, I don't understand this question. Pete

FSUIPC uses a Windows interface for joysticks which only gives access to 32 buttons on up to 16 joysticks. This is stated clearly somewhere in the documentation. There are other ways of accessing more, but only via Lua plug-in methods. The expansion of the Windows facilities to allow up to 64 buttons per device was much later than the design of FSUIPC, and I really cannot justify the complex changes which would be needed to accommodate this in FSUIPC, not at this stage after 16 years. It would be too precarious. Sorry. Pete

There's no other components that I know of which will cause these crashes -- maybe it's your WEATHER.DLL which is actually corpt, so you could try repairing that. You can stop FSUIPC reading or writing any weather. Of course any applications you may be using which relies on FSUIPC weather information won't then get it, but if you want to resort to such methods instead of getting FSX working correctly the way to do this is to set the WeatherReadFactor value in FSUIPC4.INI to zero. Pete

Assuming you mean the FS controls, Aileron trim left and right do a fixed increment left or right, whilst aileron trim set, like all "set" controls, take a parameter between -16384 and +16383 and use that to set a specific trim value. Similar to aileron left, aileron right and airleron set for the ailerons themselves, and, in fact, all the other control surfaces. Pete

Except for the GPSout facility in the Registered install, which sends standard NMEA sentences out on a serial port, FSUIPC does not "send out data" (it's up to interfacing applications to read it across a defined interface). And there is no networking code at all in FSUIPC itself, only in the WideFS purchasable option, which in any case only talks to the WideClient program on Networked PCs, not to iPads and the like. You mention a Lua script. I'm not sure whose or what that is, and I have never heard of "AVplan" so I don't know what it uses, but Lua plug-ins for FSUIPC only work with a Registered install in any case. So, sorry, I cannot advise you. Best to seek help from AVplan's author's or support. [LATER] I googled AVplan and FSX and found out what it is you needed. I think you just need to purchase and register FSUIPC, because the Lua script from Jason Beringer does the rest. You just need to edit the FSUIPC INI file to get the main Lua plug-in loaded, eg, from an [Auto] section. AVPlan looks interesting, but am I right in guessing that it doesn't really provide much for those not flying in North America? Pete

There is no such message in FSUIPC. You've got something else doing that. And autosaves are based on a timer, not on when you crash. Look in the Documents Flight Simulator X Files folder for FSUIPC autosaves, if in fact you've even enabled them. Pete

As Ian says, there's a "Cancel" or "Not now" button which you can press (depending on version of installer. Didn't you see this? Perhaps you ought to consider reading the Installation document which is enclosed in the ZIP which explains your options amongst other useful things? Pete

No, it is certainly not an "FSUIPC problem". You either have a corrupted wxstationlist.bin file, or the WX file being loaded with your default flight is corrupted. The only reason it only crashes with FSUIPC running is that FSUIPC is probably the only application on your system which is reading FSX weather via SimConnect. It starts doing that immediately after the last line you see in its log. The files I mentioned are binary, not text, and are read by FSX without adequate checking. Best to just delete them. If you are using a weather program such as ASN you don't need the saved weather files (.WX) in your documents "Flight Simulator X Files" folder in any case. The wxstationlist file in in the same folder as your FSX.CFG file. If gets updated by FSX fairly often and can get corrupted just like any other file being written. If you delete it a default one will be copied there from the FSX Weather folder. Regards Pete