John Dowson

You don't need to put them anywhere, you just need to look at the header file if you want to use the PMDG custom controls as the numbers you need are defined there - see the following FAQ entry on how to use these: However, it is far easier to use the available PMDG presets, and if you update to the latest version of FSUIPC you will see a Find Preset... button which should help in finding available presets. John

I also need to see your FSUIPC7.log file with relevant logging - see my previous comment. You are als0 using a very old version of FSUIPC7 (7.3.10) - please update to the latest version, 7.3.24, before anything else. Your 737_Oprions.ini file is also strangely empty. You should re-install the PMDG just in case, and also check you are using the latest version, 3.0.72

I don't understand why you are getting these: Are those logged before or after you exit MSFS? Open the logging console window and check the messages before exiting. As you are in the main menu, FSUIPC should not be sending events... I will look further tomorrow, but for now can you update to the latest version of FSUIPC7, 7.3.24, which I released earlier, and try with that. John

I didn't....!

Ok, but no problem showing those here, they are only useful to me and SimMarket. I have checked your keys here and they validate just fine. Are you sure that you are using the correct WideFS7 key, the one starting with T?

Let me know your order numbers for FSUIPC6 and WideFS7 and I can check them here. Use the main support forum (one up from this): https://forum.simflight.com/forum/30-fsuipc-support-pete-dowson-modules/

Yes, it is the correct version - it works with FSUIPC4, 5, 6 & 7, and the simulators they support. You need all 3 parts - key, name and address/email, and they must all match the details specified in your simmarket purchase email or account. If the name or/and address/email differ from your FSUIPC6 details, you need to check the appropriate box and enter those details as well. Did you re-run the FSUIPC6 installer to register your WideFS7 license? Did your FSUIPC6 key validate ok? Btw, you posted in the FSUIPC7 / MSFS sub-forum for some reason. Please use the main support forum in future if your issue is related to FSUIPC6 / P3D, although I do accept WideFS7 questions in both forums.

Could you try changing these in your FSUIPC7.ini file's [General] section: TrafficStallTime=10 InitialStallTime=30 to TrafficStallTime=-5 InitialStallTime=-5 to see if that makes a difference. If you get the same issue, can you attach your FSUIPC7.ini file (again) together with your FSUIPC7,log file.

No, it is MSFS that starts FSUIPC7 anyway, via the EXE.xml file. It is strange - I can't see how they can be added back - how would FSYUPC know what to add back if it was removed? Something else must be going on....

It is better to keep the default profiles, and just create a new (and empty) profile for your devices for FSUIPC. What axis controls are you assigning to? There are several to choose from - if one doesn't work, try another. You can also try activating logging for Axes Controls (Log -> Axes Controls), open the logging console (Log -> Open Console), and see what is logged when you move the axis in the VC, and then use that. But I don't have the ProSim 737 fir MSFS, so it is difficult for me to advise. I think there is/was an 'FSUIPC compatibility' mode that you may need to activate in ProSim. You should consult the ProSim documentation or ask on the ProSim forums

There was a small change in the re-connection logic introduced in 7.3.22, but this should not have affected the shutdown process. I don't see a: 1920172 MSFS no longer running - exiting message in your 7.3.23 log, which is strange. Are you sure you haven't disabled 'Options -> Exit with FS'? Can you check that please. I will also revise that change to see if could cause this issue. I will be releasing a new version later today or tomorrow, so please also try with that once released. Can you show me/attach your FSUIPC7.ini file please. John

You should edit the FSUIPC7.ini file when FSUIPC7 is not running, otherwise entries can get written back, so please try that. However, they should still be started with the specified delay, so I am not sure why they are not starting. There has been no change to the functionality of the [Programs] section for many years, so i cannot understand why this isn't working for you. I will check this here later. There could be several reasons for this. First, try with: i.e. capitalise the first letter of Yes. This should'nt be case dependent, but I'm not sure (without checking the code), so please try that first. If it still doesn't work, try using Kill instead. See the WideFS technical guide on why close sometimes won't work, and what to try instead. Also note that you are using an old and unsupported version of FSUIPC7, v7.3.19. Please update to the latest and only supported version, v7.3.23. Also, when generating log files, do not log IPC Reads/Writes unless asked, as this can dd lots of useless messages for the issue at hand.

License sent. John

License sent. John

What version of FSUIPC are you using? If not using the latest version, 7.3.23. please update. In this version,. you assign an axis to a preset by selecting 'Send Preset to FS', not 'Send to FS as normal axis'. The Select for Preset checkbox is now for sending presets when entering an axis range., using the right-hand side of the axis assignment panel, which is not what you want. This is not correct either. You must use either $Param (short for parameter) or the @ symbol as a placeholder for the axis value. Try the following DuckWorks_DC3_ParkingBrake_On#1 (>L:DUCKWORKS_PARKING_BRAKE_SET) DuckWorks_DC3_ParkingBrake_Off#0 (>L:DUCKWORKS_PARKING_BRAKE_SET) DuckWorks_DC3_ParkingBrake#@ (>L:DUCKWORKS_PARKING_BRAKE_SET) The last one accepts a parameter, so you would have to provide the 1 (in) or 0 (off) as a parameter for the assignment. This is for adding lvars to offsets, and should be used when you want to read the lvar value as well as set it. You can also use this method, but then you would use one of the offset controls (e.g. Offset Byte Set) for your assignment. Unfortunately many aircraft. especially add-ons, don't respect or use the standard controls/events or simulator variables provided, and so you must use other variable types (lvars, hvars, etc) or complex calculator code yo achieve the same. FSUIPC just provides additional functionality to allow such assignments. Please see the Advanced User manual on using lvars, presets, etc. This is all described in the WASM section.

Also, I have noticed in the JF PA28 Arrow, if I set an ADF frequency (no decimal allowed when selecting) and keep the mouse over the frequency knob, the decimal part increments from 0 to 9 and then back again, changing approx every 4 seconds, and I see ADF Fract Inc/Dec Carry events being sent (9 inc events, followed by 9 dec events, then repeating). So it looks like the ADF for that aiircraft scans the decimal frequencies, although they are not displayed.

What aircraft allow a decimal part for the ADF frequency in the ADF panel? I have checked several aircraft and none I can find so far allow a decimal part to be set. Also please see this - it relates to x-Plane but is still relevant: https://forums.x-plane.org/index.php?/forums/topic/202498-how-to-change-the-decimal-in-the-adf/ John

How are you currently tuning the ADF? This should be possible either using the standard controls or using the FSUIPC ADF frequency offsets. However this can also depend on the aircraft, as some add-ons can implement their own controls (via lvars or custom controls) and not respect the provided controls/events or simvars. I have also noticed that writing to the ADF1/2 standby frequency offsets at 0x0284, 0x0286, 0x0288 and 0x028A was disabled in an earlier version of FSUIPC7. Not sure why this was, but I will re-enable these and check if they are working. Anyway, could you show me your assignments (attach your FSUIPC7.ini file) and let me know which aircraft you are using. Thanks, John

This should make a difference. This will only affect the options that are available to you. John

Those are lvars. To assign an axis to an lvar, the easiest way is to create a preset. First, you need to determine what the maximum and minimum values that the lvar takes (you can list the lvar values when the throttle/mixture levers are at the extremes), and you must also know the maximum and minimum values the axis sends. The preset, which you need to add to your myevents.txt file (create this if not present) will then take the form DuckWorks_Throttle1#@ <conversion> (>L:lvarname) where <conversion> - is the RPM code to convert the axis input value range to that expected by the lvar lvarname - is the name of the lvar that controls the aileron position You can then check the Send Preset to FS in the top-right of the axis assignment panel and assign your axis to the preset DuckWorks Throttle1. There are other posts where I have shown how to use an axis to control an lvar:

I can't help if you don't show me your files. Are you sure that your lua script is running? When using LuaValue, your script should be auto-started from your [Auto] or [Auto.xxx] (profile) section of your FSUIPC ini file.

Can you please attach your FSUIPC7.ini and FSUIPC7.log files, the latter generated with logging for Buttons & keys and Events activated - activate the logging, load your aircraft in MSFS, then press a button or two that is assigned but not working, then exit FSUIPC7 before attaching your files. And if your assignments are using the specific PMDG offsets (e.g. for offset conditions), then make sure you have activated the PMDG data broadcasts in the PMDG config file (details in the PMDG offsets guide). John

I have checked the following presets in the A320-dev version and they all work (i.e. I can see the associated knob rotate): A32NX_LIGHTS_GLARESHIELD2_INC (*) A32NX_LIGHTS_GLARESHIELD2_DEC (*) A32NX_LIGHTS_GLARESHIELD3_INC A32NX_LIGHTS_GLARESHIELD3_DEC A32NX_OH_INTEG_LIGHT_INC A32NX_OH_INTEG_LIGHT_DEC All except the first two (*) also control the brightness for what they are trying to control - with these I can't see any brightness changes (although the knob moves, but that is probably because I don't know where to look! To set to a specific value using calculator code: this doesn't work. It seems that the 'K:2:LIGHT_POTENTIOMETER_SET' event needs 2 parameters (probably what the ':2:' indicates). So try this - it works here: ipc.execCalcCode("25 84 (>K:2:LIGHT_POTENTIOMETER_SET)") So the 25 indicates the percentage, and the 84 the index of the LIGHT POTENTIOMETER simvar that the event is controlling. You can change these values to control the %age and the lights, where 84 indicate glareshield brightness, 87 FCU brightness, 86 the Overhead panel integrated light knob, 85 the pedestal light knob Integ brightness, 83 the pedestal light knob Flood Captain, 90 right PFD brightness, etc I knew some events can take two parameters - this was introduced in an update a few months ago, but I didn't know how you actually used them in calculator code until now, so this has also been a valuable learning experience for me. Hope this helps - let me know how you get on. If you can't get this to work, I will need to see your files - your FSUIPC7.log (with logging for Buttons & Keys and Events activated, as well as Debug level logging set in the WAPI) and FSUIPC7.ini files, together with your lua files. John

Well, the error says it can't find C:\VRInsight\bin\Inst_Panel.exe - does that exist on your new PC? If it does, can you run it? Have you tried re-installing it?

There are no changes between 7.3.21 and 7.3.23 that could affect your VRInsight configuration. What exactly is the problem? Please explain, and also please show me/attach your FSUIPC7.ini and FSUIPC7.log files. I have also attached the exe for 7.3.21 for you to try - temporarily rename your current FSUIPC7.exe (e.g. to to FSUIPC7.exe.7323) and save this to your FSUIPC7 installation folder. I expect you will get the same issue, but if not please also attach your FSUIPC7.ini and .log files for this version. John FSUIPC7.exe