Pete Dowson

You do NOT buy a specific version! The current version is 4.962, not 4.96, so please go get the current version. Additionally, if/when you ARE using 4.962 I need more information, because so far yours in the only report. I need 1. The Windows crash details. You can use the Event Viewer you get this. 2. The FSUIPC4.LOG file from the sim's Modules folder. 3. A list of what add-ons you are running. 4. A note of the Windows version -- Win7, Win8 or Win10? Pete

Yes, I changed the default so had to rename it, deleting the old one. It is documented properly in the Advanced users guide, but I see I didn't update it in the Lua libray document. I'll see to that before the next full release. No, it won't be SimConnect. It's a direct hook by FSUIPC into the sim, as confirmed by this, in your log: 1453 --- SimConnect intercept for texts and menus installed ok What are you using which does this Why remove the first lines of the Log? Those contain essential information I need. Are you not using version 4.962? That last message will tend to crash the sim in 4.962. For more information about this in the log, add the following lines to the [General] section of your FSUIPC4.INI file. Then show me the Log after your attempt: Debug=Please LogExtra=x20 Pete

Well, error 87 is documented as ERROR_INVALID_PARAMETER 87 (0x57) The parameter is incorrect. Looking up the facility to set the affinity I see: If the thread affinity mask requests a processor that is not selected for the process affinity mask, the last error code is ERROR_INVALID_PARAMETER. So, effectively, you can only select cores already selected for the Process (i.e. for P3D). All you can do is keep my stuff off whichever P3D uses most of. I didn't notice that before, but I'll put it into the documentation for the facility. Pete

You have to enable the SimConnect Text intercept facility in the FSUIPC INI file. The parameter is "InterceptTextMenu" and is described in the Advanced User manual and in the Lua library document in the section about the event.textmenu function. The default setting is with it disabled. The RC display is using a different facility altogether, not using SimConnect. Pete

If you can implement the interface correctly, I don't see why not. Do you have access through it to Windows APIs? Study the C/C++ source provided for the interface in the SDK. Well, there's no WideClient implemented for Unix, and there's no documentation for the WideFS TCP or UDP data formats used. You'd need to write a Windows-based server program to run on the FS PC (or a WideClient networked PC), which interfaces to FSUIPC (or SimConnect), and then talk to it over the Network from your "pie" using whatever protocol you need. Pete

Please install version 4.962.

FSUIPC 4.962, now released, allows you to set two affinity masks for FSUIPC. One for all of its own little threads -- probably the more demanding of which would be those associated with WideServer -- and another for all lua plug-ins. See the Changes document included. Pete

The Monitor won't start operating until FSUIPC is sure it is safe to "start everything". There's a delay incorporated, as mentioned in the Changes document in the ZIP (please take a look). The delay is 20 seconds from the signal from P3D that is is not longer displaying its progress window, but in my experience it signals this long before, usually at the 80% or so mark. If FSUIPC starts too early it can suffer SimConnect timeouts, waiting for data which is held up because things are still loading. That makes things much worse because it closes SimConnect and starts it over again. 20 seconds might be erring on the long side, so i may reduce it a bit. 10 seconds it definitely too short. I'll see how things turn out. I'd rather stay on the safe side, and after all a few seconds at the srtart of a session isn't really that long. Yes, PLEASE always read the changes document supplied with every update. That's what it is for. Pete

Could you pls indicate where exactly this option should be placed? INI file?, where?. Er, it's there, shown on the very picture you just posted, to the left of "FS Window" which you ticked, it is (obscurely?) named "normal log file" as I surely said? Try also ticking the "title bar" option, and see if it appears in the title bar. You'd need to switch to Windowed mode, of course. It isn't a "VAS utilty". You'd find the VAS monitor lua plug-in, supplied in the FSUIPC Documents folder, in the Example Lua plug-ins ZIP, much more informative and meaningful. being in megabytes, and also showing frame rate and maximum free VAS block. Pete

So nothing in title bar and nothing if you select "FS display" in the Monitor options? I assume you have checked the setting for Minot on the Logging options tab? Let me see the [Monitor] section of your INI file. Does the Monitor not monitor anything at all, any old offset? Also try sstting "normal log" option to see if it logs to the fSUIPC4.LOG file. This is not making any sense. There's certainly no change in the Monitor facilities, which is what you are using. Even if the VAS measure was turned off it would still show something -- zero in fact. Pete

Well try increasing the Delta. You can do that in Axis Assifgnments, or easier by changing the 256 (or whatever) in the assignment in the INI file. You can change it whilst FS is running, then just go to the axis assignments tab and click the reload button. Pete

No. It hasn't been changed at all. and the offset monitoring facility works fine here. Where are you trying to display it? Is there no display, or an incorrect one? Check that you haven't turned the OOMcheck off in the INI file. Pete

Steering Set, unlike my built-in tiller, is only an FS control. For every change more than the Delta (as shown on the FSUIPC axis assignments tab) it has to send a message to FS's window. That message goes through to the simulation system and, if you calibrated in FSUIPC, gets trapped by FSUIPC for calibration. Then the calibrated value gets sent on. The delay will be due to the large queue of messages awaiting attention, along with all of the others (and if you are using an add-on like PMDG planes, there are a lot!). Check that your Delta has not been set low. 256 is the normal default -- don't set it less than that. 512 would give half the messages and still give enough resolution. The full range is something like 32768, so 512 still gives it 64 distinct positions. The FSUIPC tiller would be more efficient. Pete

Version 4.962 is released. Pete

For explanations and cures coming soon please read the pinned thread at the top of the forum. Pete

I'll be releasing FSUIPC 4.962 later today, which should fix the only remaining "crash on exit" problem I know of and therefore stop the P3D crash on startup -- at least any actually caused by FSUIPC induced crash on exit. I'm sure it also happens with other add-ons sometimes, as perhaps the FSL A320 example above shows. Pete

Other LINDA users will need to answer this for you. Why not also check their website? Pete

Yes, but FSUIPC is NOT a process. It runs inside FSX or P3D. THAT's the Process, and can already be assigned affinity. That's a bit different. A lot of FSUIPC's interfacing to FS cannot be in a separate thread, only in the main FS one. Separate threads are used for each Lua plug-in, and for some other things like button and axis scanning. I suppose, if I found out how, I could restrict all those threads to a given different AM. The standard ones, normal in FSUIPC without plug-ins, probably would make no difference, but I suppose badly written or heavy Lua plug-ins -- especially those using other external libraries -- might give a little benefit. BTW, I don't have VoxATC, but I thought it was a separate process, an EXE, not an internal FS DLL? Do you still have a link, Jabloomf1230? Ah, no. it's okay . I asume you meant "SetThreadAffinityMask". I already use "SetProcessAffinityMask", of course, for the AM= facilirt in the [Programs] section. For now I'll try allowing users to set two different masks -- one for the assorted odd-job threads FSUIPC creates, and one for all of the Lua plug-ins. I could, I suppose, allow Lua threads to set their own via a new function, but that seems a bit overboard. Pete

Okay, good. I'm still trying to work out what changed between 4.955 and now to make this act differently. It's strange. If it was a bug I fixed it most certainly should have been recorded, but I don't see it anywhere! Oh well. Perhaps I wasn't myself at the time! Pete

You could try using FSUIPC's steering tiller (in the ""direct to calibration" drop-down), which does use the rudder input but can be calibrated separately from the rudder axis to give more sensitivity, Also this, along with rudder assignment and calibration, lets FSUIPC gradually transfer rudder control between the two axes according to ground speed, making for quite a realistic feel. Pete

Case 9 is ESP (now defunct and unsupported), Case 10 is P3D If there is ever a 64-bit P3D and a 64-bit FSUIPC (hypothetical at present) then it would be 11.

Really? That's really stupid, when there's already a "Steering Set" control in FSX and P3D designed for the purpose. Sorry, but there's no way in FSUIPC to make a throttle assignment send a negative value more negative than -4096.if it is calibrated. You could try with no calibration, but no other way certainly. I'm sure the Aerosoft Airbus hasn't just been released. So why has no one else ever reported this problem? I think you should double check that so-called hard-coding, because it really makes no sense. Pete

The simulator yoke is a graphic trying to imitate the real aircraft, where most yokes turn at least, and sometimes beyond, 90 degrees. It is the Saitek which has a limited angle. Pete

There's no "Start" button. Where are you actually looking. Please tell me what you are actually assigning to. No, you don't really need to. Okay. And which selections there are you making? The calibrations section will receive changes for any method of assignment, including those "to FS controls" in FSUIPC, and using FS to assign. Most beginners start out just using FSUIPC calibration, not assignment. Is there a particular reason you are jumping in so deep so soon? Before proceeding to more questions, it would help if I can see what you've done so far. Find the FSUIPC4.INI file in the FS modules folder and post it here. It is an ordinary text file so you can cut and paste into a message. Pete

Well, I completely disagree with you there. The flight controls should always allow you the full range of deflection provided for in the engineering of the aircraft. Why else would they construct it that way otherwise? And you never know when you might need it. If you simply want more central range, pushing the more extreme angles to a small outer portion of the controls, then use one of the slopes available in the FSUIPC calibration tab to achieve this. If you really want to (UNREALISTICALLY) limit the effect of your controls there are two ways of doing it: 1. Edit the AIRCRAFT.CFG file of whatever aircraft you use to reduce the aileron effectiveness. 2. Edit the calibration values in FSUIPC4.INI to make the minimum and maximum figures recorded there a multiple of the ones now set (eg 2X to reduce effectiveness by 50%) Pete