Pete Dowson

There's no "axis calibration" in FSUIPC. There's axis assignment, but joystick calibration is a separate issue -- calibration works on FS controls and operates with axes assigned in FSX or in FSUIPC. You answer is therefore ambiguous. I'm afraid version 4.927a is out of date and unsupported. Please update to 4.928, released over a week ago now. The error you report from FSUIPC is merely an error reported by Windows to FSUIPC and passed on. I can do no more than suggest that something is wrong with your joystick and DirectX installation. FSUIPC cannot manufacture Windows DirectX errors like this one. Try reinstalling DirectX and also uninstalling and reinstalling your joysticks. Pete

Sorry, but I really have no idea what FDE does. I didn't even know it used any display options in FSUIPc. The only program I use which uses FSUIPC's display facilities, apart from my own Lua plug-ins, in Radar Contact, and its menu display is certainly okay. I'm afraid I would be totally reliant on Dave March explaining what it is he thinks might be wrong. Software doesn't deteriorate or change itself over time, so you have something else changing things. I'm afraid I really have no idea what could be wrong nor really what information might lead to a solution as I have no idea what FDE might be doing or trying to do. I'm sure Dave would be able to help you get the right information. No one else can. Regards Pete

The toggle action is just the same as a real switch. When pressed fromoff it goes on and when pressed from on it goes off. 0 = off, 1 = on. there's nothing mor complicated at all thatn that. You make it sound much more complex for no good reason. The confusion you are in is that some offsets work by sending toggle controls to FS. If they only do this when you write a 1 then nothing will happen when you write a 0. you should NOT be using the Button Screen toggle facility for such things, as I said originally. To see what is happening, log the events as well, not just the affected offsets. You don't need FSInterrogate for that -- the FSUIPC logging provides all the facilities you are using in FSInterrogate as it stands. see the Monitor facilities for instance! Pete

Axis calibration? In FSX? Or are you talking about FSUIPC? If so what actual version number? Where are you reading the error? Error 80040154 is a "class not registered" exception, which implies a DirectX error in your Windows installation. Download and install the latest DirectX from Microsoft. Pete

I think thee was (maybe still is?) a deal for those who purchased FSUIPC3 within recent months, maybe 6 or so? Pete

Not as such, no, but WideClient is small enough to occupy little disk space in any case, so just have separate folders containing Wideclient.EXE and the appropriate INI, and launch appropriately. What I do is place WideClient + INI in the actual application folder, so there's an obvios tie-up between which one loads what. Another way is to use RunKey instead of Run and use a button or key from your FS PC, via KeySend, to load whichever app you want. You could also close them with CloseKey. Regards Pete

Not easy. The ready-made failure options are not really failures so much as training aids, for flying without one or other instrument or subsystem. The better instructor stations (which are payware of course) simulate failures in a much more sophisticated manner, playing with the actual aircraft operation or performance in various ways.. Regards Pete

Folks generally only come here when they are in need of assistance in any case. ;-) Don't Thrustmaster and Saitek provide any instructions? Generally you don't need to "programme" such things, merely assign the various axes and buttons to functions in FS. FS also tends to make quite a few default assignments of its own accord, and these are often good enough as a start -- it is guided by files it has for each device type t recognises. Have you tried looking at the instructions -- there is a User Guide, a comprehensive document wth Chapters on these facilities. Many folks find the correct options pretty quickly in any case as they are evident in the FSUIPC options screen when you open the Add-Ons/FSUIPC Menu.. In case you don't know where to find the documentation, please look in the original ZIP file, the one from which you got the Installer, and you will findd an Installation and Registration guide which tells you exactly what is installed and where. Sorry, I can't help with that. I do not have or use any of their devices. But if and when you do assign in FSUIPC, be sure you don't also assign in FS too or you will get conflicts. Regards Pete

No you have not. This is a well-reported bug which was fixed in version 4.928 which was released a week ago and which is the only currently supported version of FSUIPC4. Regards Pete

With FS toggle controls you can't tell in any case. If you want specific on/off control you'd need to assign to offsets. Pete

Sorry, I'm still confused. If you define them as Toggles in the ButtonScreen definition then they will send a "press" on one push (and turn red) and a "release" on the next (and turn back green). You appear to be defining one toggle button and one momentary button to each control. Why? It makes no sense. Since the controls you are assigning to are not "on" and "off" controls, but simply toggles, your button screen programming should also just be simply momentary buttons, and only one for each. Only assign to "press" not to bother "press" and "release". There is absolutely no point in assigning the "T" toggle option for controls assigned the same for "press" and "release" -- and to have multiple buttons assigned to the same control with one set as a "toggle" will lead to the ultimate in confusion! Surely you can work this all out yourself using the logging in FSUIPC? That is what it is for, to help you understand what you are doing. Pete

Quite honstly I have no idea why you'd want to do all this in any case. But if you want to go ahead, I would most strongly advise programming it in a Lua plug-in, not trying to do complicated things with mere assignments in the INI file. It just doesn't suit such an approach, whereas Lua is made for it. Someone has already done almost all of the work for such a plug-in. See this thread in User Contributions: http://forum.simflight.com/topic/75409-setting-fsx-radios-obss-and-the-autopilot-using-the-keyboard-numberpad/ This was written for assigning the number keys on a keyboard, but there's no reason at all why the assignments can't be to buttons instead. Regards Pete

Should really be No, otherwise the values which any Lua might restore will be the patch values not the originals. Pete

No. Sorry. Pete

Since all you change when you install FSUIPC is the DLL, it makes no difference whatsoever what version it is replacing. On the other hand if you are deleting the INI file, so erasing all your settings, then obviously it is related to those, and nothing whatsoever to do with installing in any specific order. Version 4.927 etc isno longer supported -- 4.928 is the current version. It was released a week ago. If this INI file works for you as you say, why post it here? Please update to 4.928 before posting again. Regards Pete

I can't, really, having never done any. By "toggles" do you mean latching switches rather than buttons? Are all those controls toggling controls? Have you tried using FSUIPC button and event logging to see what is happening? Some of those are certainly listed in the Offsets list. You can assign switches to send or toggle values to offsets. Mostly they will by single bytes, so you'd use Offset Byte Set with parameter 0 for off 1 for on using a latching switch. Pete

Thanks for helping out here Paul! Pete

Might be quicker and easier to check just the [Keys] and [HotKeys] sections of the INI. It must be there somewhere. The left arrow key is number 37. Pete

Sorry, I don't know C# so there's no way what you show tells me you have it correct. Therefore please use FSUIPC logging and FSInterrogate to check exactly what the offset contains and what you are reading. I did suggest that, but I assume you've not bothered to do this? Additionally that same field is used to select Profiles ad Aircraft Specific assignments and settings, which obviously would not work with a corrupted string as you are implying. The aircraft name, again from that offset, is also written to the FSUIPC log file (in the line "Aircraft=" each time it is changed -- check that too. There are several ways to cross-check it which you should use. If you do find any of these showing the same as your code, by all means show it to me. Then we'll need to look for possible causes, some sort of corruption in your specific FS9 system. Pete

The INI file contains all the settings you've made in FSUIPC. If you remove it all those settings revert to default (in a newly generated INI file). If you don't actually use FSUIPC for anything this won't matter I suppose. All you've really proven is that something you've set assigns the arrow key to something and you've not remembered that. Pete

Well, you say that, but FSUIPC doesn't handle any keypresses at all unless you assign to them. Rename or delete your FSUIPC4 INI file to see what happens then. Pete

That's version 4.91, log since defunct! Something else is doing that -- FSUIPC is suffering too as SimConnect hanges and nees re-initialising. See: and I think you need to conduct a process of elimination to see what could be causing things to hang in SimConnect. Or maybe a SimConnect log will show -- there are instructions for making a Simcnnect log in the FAQ subforum. Also consider what you might have changed recently. Regards Pete

I have replied. You seem to have the wrong configuration. The log you sent shows no error whatsoever, the FSUIPC session finishes normally -- take a look! The parameter "NewInterceptTextMenu" defaults to "No" in FSUIPC 4.928. The testing period finished when I released 4.928. The original problem is fixed. The log you provide is not the one relating to whatever crash you had. Pete

None of the logs are finished. You need to close things down before copying the logs, otherwise essential information is lost. One strange thinge which doesn't make total sense is that when the message "Unable to serve (see logs)" is displayed, either it is preceded by a message box entitled "WideServer Error" which you have to "OK" to get out of, or, simultaneously, the explanatory message is written to the log -- yet in your case the server log shows nothing. However, maybe the error was so transient that this got overridden by subsequent events. Three questions rise: 1. Is the FSUIPC4.KEY file in the P3D Modules folder identical to that in the FSX Modules folder? 2. Are you possibly using anything else on P3D which might be taking the main port used by WideFS -- 8002? 3. Could your firewall be allowing FSX.EXE through but not Prepar3D.exe? That would explain it for sure. Regards Pete

No. It should be short. Paste it here along with the crash details from the Windows event viewer. Pete