Pete Dowson

Do you think a thread merely entitled "Help" will get the folks who might know about your problem actually looking? Please always use a descriptive thread title. Did you read at lease some of the WideFS documentation, especially the part about configuring your Network and pointed out with a red plea to read at least the first few paragraphs? If there is a genuine problem much more information is needed. Like which Sim are you talking about, which version of the Sim and which version of FSUIP? And please show the WideServer and WideClient logs. Pete

66494 and 66495 are FS controls, not PMDG controls. And they operate Fuel Valves. FSUIPC's idle/cutoff switches are operated by the Mixture Full Rich / Lean controls. PMDG have their own controls for almost everything. Look in the aircraft's SDK folder for the .h file which lists them all near the end. Pete

If you have no key assignments in FSUIPC and you hsave no HotKey assignments in FSUIPC, and no applications or Lua plug-ins running which use the keyboard, then FSUIPC simply ignores the keyboard. It just cannot interfere. Therefore you must look in all those areas -- Keys, Hot Keys, FSUUIPC-using add-ons, and Lua plug-ins. If you have problems with some keypresses in other program, outside of the sim, then Hotkeys must be involved. Pete

Please explain the exact problem, because you posted a completely different problem where there is no black screen in a different post. I need more details in any case -- FSUIPC version 9if not 5.113, use that first), FSUIPC5.LOg, details of oyther add=ons, Windows Event viewers if any entries there correspond. Depending where in the load sequence P3D reached, it could be any one of a number of corrupt files being loaded by SimConnect. Pete

You assigned everything "direct to FSUIPC calibration". So where is the calibration section for the INI? For the Throttles, if you didn't calibrate at all, or calibrated without checking "no reverse zone" then up to the lower half of the axis movement will be reverse. Generally the PMDG aircraft doen't work well with FSUIPC calibration. most folks assign to the normal FS axis controls (Axis_Throttle ...) and don't calibrate. Other ways will sometimes induce conflicts in the aircraft because they also read the axis imputs independenty. Pete

event.control is triggered by FSUIPC detecting a control event being passed via the Sim's Windows message queue -- or, in some cases by using a Simconnect intercept function. Whilst I cannot implement this in WideClient, it would be possible for a Sim-based plug-in the use the events to set flags orwhatever in user offsets so that the WideClient plug-in can use event.offset or event.offsetmask. On the Lua sockets code, I'm afraid I really have no idea how to fix it. I need assistance on that. Any network experts out there who can also get to grips with rather convoluted Lua code? Pete

I don't think any Sim FSUIPC supports can simulate these as such. Can you not simulate the reaults of such an event, whatever they are? Pete

Sorry, the limit on Lua names is 16 characters, and it is table related. It has provided sufficient for the whole time FSUIPC and WideFs has supported Lua. Just try using more succinct or abbreviated names. You won't run out. Pete

I think it should work, if it worked okay in with 32-bit and FSUIPC4. But make sure to use the latest version of FSUIPC5. I'm afraid i don't have any VRI devices. I'm just going by confirmation from others. Pete

I need more information, please. But first please download and install the interim update FSUIPC 5.113. Then, I need the crash details from Windows Event Viewer, and the FSUIPC5.LOG from the P3D modules folder. Pete

This is normally due to a SimConnect trust checking error, which is intermittent but sometimes more persistent on some systems. Persisting by saying "Run" each time should eventually succeed. If not, please see if an FSUIPC4.LOG file is produced in the FSX modules folder. If so, please show it to me. Please also make sure you are using the latest version of FSUIPC (4.971), as I cannot support older versions. Pete

This was reported before I went on holiday and fixed by a fresh upload. So all you need to do is re-download it. Pete

I wonder if the screen and client positions are getting mixed up. I'll check this. But tell me, are you by any change running in Windowed mode? I use full screen more and it appears to work perfectly then (ALT+ENTER swaps between them). I notice that the x, y position of the top left if changing by 118, 922 (119, 922 in the last case). Could that be the screen position of the top left corner of the P3D Window? Pete

There are some add-on aircraft which operate many aspects of their relationship with the base simulation facilities in the simulator using the SimConnect EVENT system. It can seem very inefficient (and does to me), especially when the repeated events are for the same values. It's as it it is trying to prevent external interference with thse values. PMDG aircraft were always very heavy indeed with the numbers of events generated, which flooded the log so much as to make it unusable to find odd events more related to external programsor devices. That is why I added INI parameters to allow sepcific Events to be ignored. No one has notified me of this -- neither Mathijs nor L-M!!! I've no idea how it is possible for FSUIPC to cause an add-on aircraft to CTD. I've written to Mathijs asking for an explanation. Pete

I think they overhauled the joystick reading, so it is probably different. Whether that parameter would do anything or not I don't know, but it won't do any harm. If you assign in FSUIPC instead of P3D, it isn't relevant in any case. It was only relevant for FSUIPC calibration of axes asigned in P3D. Pete

This post seems to be a more elaborate version of a post I already answered. Where are these Global variables being set? Please also see my other reply. Please stick to one thread per subject in furture to avoid extra work and confusion. Pete

Sorry, I don't know what HID device you are using, but isn't "WriteFeature" used to set feature options in HID devices? if you are simply trying to communicate data to be used by code running in the device, shouldn't you be using the normal com.write? I'm afraid I've no idea what "mikroc" is. You also need to state which version of FSUIPC you are using, and which Flight Simulator. Pete

UT2 and FSUIPC4 are completely unrelated. FSUIPC cannot possibly make UT2 lose its registration. You have some other unrelated problem. I've been using UT2 and FSUIPC continuusly with FSX, FSX-SE and P3D ever since UT2 was first released, with no problems. UT2 is a separate program, not even running inside the Sim like FSUIPC, and connects directly to SimConnect, not to FSUIPC. Pete

What is "magnetometer data of a plane"? I don't think any value simulated by any flight simulator supported by FSUIPC provides detail of magnetism around or in the aircraft. Pete

Hmm. That's strange. The code is no different. I wonder if it is something to do with 64-bit versus 32-bit programs -- though that would be rather odd. I'll do some more testing here when I've caught up with the support backlog. Pete

You don't need to buy FSUIPC for an application client! They connect free with no purchase needed! You only ever buy FSUIPCC to use the User facilities. Its interface for other programs has NEVER needed a purchase! Pete

No, I dount you are missing anything. Sounds like there is no provision for operating that switch by anything else but mouse. There have always been a few like that in default cockpits, and a LOT in add-on aircraft cockpits! That's what Mouse Macros were invented to deal with. Try that method. Pete

NO, I'm not! I have no idea WHEN it will be released. It is never decided till it is ready, and even then it goes out for Beta testing before user release. I was only repeating the joke about new releases always appearing when I'm on holiday! Pete

Even when I have only one disc, I tend to partition it, so I have C: and D:. But it doesn't matter. BUT don't let the installer decide the folder name. Change it so it installs in, say, "C:\Prepar3D v4". Did you not bother to try suggestion 1 above, simply running P3D "as administrator" (you can set that as normal in the Prepar3D.exe Properties, in Compatibility? You never bothered to tell me if you tried any of my other suggestions either. I am not really getting any information from you which would help me to help you! :-( Pete

I posted in the private Developer's forum, and identified the precise variable which is lacking: "AI Traffic Assigned Runway". If they fix it in the next update, I probably won't be able to test it then, though. I'm away this Thursday till September 12th, so it's inevitable they'll do a release whilst I'm away! ;-) Pete