John Dowson

Yes, paid/licensed version is required to run lua scripts.

Hi Ray, of course - just add to the [Auto] section of your ini (or the [Auto.<profile>] section if profile specific. See p40 of the Advanced User manual. ...ah, but just noticed that you are referring to P3Dv3 not v4, so presume for FSUIPC4, no? Not 100% sure when this was implemented so this feature may or may not be available - check your FSUIPC4 user manual.

Hi Gundars, that is a long time ago! I'm afraid I can't help much with your question - Pete will be back in 2 weeks or so and may possible remember the problem to which you are referring. However, you should just go to the download links page and download the latest FSUIPC3 version (for FS9 and earlier): If you are now using a different sim and require FSUIPC4 or FSUIPC5 then you will require a new license. Cheers, John

Hi Stephanev, glad its working for you - and wow - that is a great set-up you have there!

Hi Dave, could you post your FSUIPC5 log, ini and JoyScan files please. Which Goflight modules are you running, and are you sure that they are being loaded? Cheers, John

As Ray says, this is going to take some time, especially with Pete being away. Its not an LM issue, it seems to be a timing issue in FSUIPC and I can't replicate in a debug version, so its tricky to track down. Just reduce AI traffic for the time being. I will post when I find more info. John

Hi Scott, 'DIRECT' means you selected the action 'Send direct FSUIPC Calibration'. The calibration you have set for the Ailerons is as follows: Aileron=-16103,-1152,-1090,16249 Your 'null' zone (around neutral) is -1152,-1090, which is very small (62). Try re-calibrating this in the 'Joystick Calibration' tab. John

oh, and the FSUIPC5.JoyScan.csv after a successful start please.

Could you also provide the FSUIPC5.log file for this as well please. John

Hi, looks like you have some serious USB problems...! If you run without FSUIPC, can you assign your joystick axis/buttons in P3D (or in any other program)? Can you try the HidScanner utility, available from Unplug your devices and reboot first before reconnecting them, then try the HidScanner to see if that recognises your devices correctly. I'm pretty sure you've done this already, but also check the device manager on your usb hubs/devices to see if any errors or conflicts are reported. Cheers, John

Hi Ray, I started with RC4 to try and reproduce the crash but didn't get too far and switched to trying with FSAIS instead, but still no joy. I can go back to trying with RC4 - can you provide more details on how to re-create the crash you get with this? Thanks, John

Which one? The rudder? Your image shows you have the centre/null zone set at 331. This should be a range (usually something like -512, 512). You also have no calibration for your throttle. Which axis again? If the axis is reversed, you need to check the 'Rev' box for that axis in the calibration page. Please read the calibration section of the User Guide for details on how to assign and calibrate your axis. If you requite any further help, please give more information (axis? aircraft?) and post your ini and log files, not screen shots - these don't tell me much. Thanks, John

Hi Luke, this is next on my list, after we have got to the bottom of the current problems with AI Traffic/Radar Contact crashing P3d/FSUIPC. I'll get back to you on this once I've had some time to look into it in detail. Cheers, John

What sim are you using? What version of FSUIPC? Can you also check that you have your controllers disabled in your sim. Then if you are still having issues, please provide more details (which axis, sim, aircraft, etc) and also post both your ini and log files (from your FSUIPC installation directory).

Hi Ray, ok, thanks for the added info. I'll ramp-up the AI once I've installed. I'll report back if/when I find something, though it might take me a few days to get around to this, unfortunately.

Now I'm back, I'm going to install both AIM (I've been meaning to do this for a while now anyway) and RC4, one at a time and together, and see if I can reproduce. Once I can do that, I can see if the exception can be handled in FSUIPC.

Hi Bill, this is not really the correct forum for such requests. However, for the Saiteck/Logitech multi and switch panels, you could either use maxx's free SPAD: Saitek Panels Advanced Driver (Go to http://fstools.weebly.com) or the payware Spad.next advanced driver package (https://www.spadnext.com/home.html), which works with or without FSUIPC. Cheers, John

Hi Alan, could you try the 5.151b version posted in this thread (in second to last comment): Its a dll file but named as a .txt - just download it, rename to FSUIPC5.dll and use it to replace the existing one in your modules folder. Thee are only some minor changes in this version, but I would be interested to know if you still get the .NET framework error with this version (was it a COM error?) Thanks, John

FSUIPC5 requires a new license - it is a different product (a near complete rewrite) to FSUIPC4 due to the change from 32-bit to 64-bit. Your WideFS license is still valid. Note that WideServer is now part of FSUIPC5 and so the WideServer application is not needed with FSUIPC5. John P.S. You posted in the FAQ section. I have moved it for you, but please post all support requests here in the support forum.

Hi Alan, does it also crash if you disable Radar Contact? John

If there are key commands, you can assign buttons directly to those. However, reading your earlier post it seems that this works for other aircraft for you, but not the PMDG ones, no? You could also try mouse macros. You will probably need to play around with the mouse control codes - I have had success for left/right knob turns with the mouse-wheel up/down codes, but you will need to try them. I don't have any PMDG aircraft, sorry.

Have you tried activating your lua on the button release as well?

Hi Onno, first, you are using an old unsupported version of FSUIPC5 - can you update to the latest supported version, 5.151. If you still get error 1332, you can manually edit the Modules folder permissions yourself to allow full access, by right clicking on the folder properties: select Security-->Edit-> Add, enter Everyone as the object name, then 'Check Names' and 'OK'. Then give 'Full Control' to the 'Everyone' group just added. Alternatively, as your P3D installation is under the 'Program Files' folder (which is why you are having this issue), you could run P3D as administrator, which would then allow FSUIPC to write to the modules folder. Regards, John

Hi Pietro, your dll looks fine. Enabling logging in SimConnect is defined (for FSX) here (yes, from 2006 and for FSX, but still valid!): For P3D its the same - create the SimConnect.ini file in your P3D documents folder. I will be away from my sim/dev PCs (travelling/working) for the next 8 days so it may take me longer to respond during this period. Cheers, John

The versions are the same, its just that some features are disabled in the unregistered version. If its crashing with the unregistered version, it will also crash in the registered version. Also no point upgrading unless you are going to use some of the features it brings - check the user manual for this. Let me know how it goes with the NoWeatherAtAll flag set. Cheers, John