John Dowson

You can do that using a lua script. You can use the event.key function to register a function to be called when the key is pressed (and released) and send the initial brake value, and also set a timer using event.timer to call a second function to apply the 2nd and subsequent values. The event.key function should cancel the timer function with event.cancel on key release. There are also other ways to do this, e.g. see this User Contribution lua script for smooth braking using a button - this can also be used on a key:

Any FSUIPC crash events should be reported under Windows Logs -> Application

Yes, that is the way to do it. You do this by manually editing the ini file. Find the right brake axis assignment and duplicate this line, incrementing the line index number (to give it a unique index number) and then change the control number (not the comment) from 66388 (AXIS_RIGHT_BRAKE_SET) to 66387 (AXIS_LEFT_BRAKE_SET). Do this either when FSUIPC is not running, or if it is running do this with FSUIPC open showing the button assignments tab, and click the reload button when you have saved your ini file changes. Note that once you have overloaded your button assignment, you will only see one assignment in the assignments panel and this will be grayed-out and you cannot change it - any changes must be done directly in the ini file. John

Yes, that makes sense - I just divided by 100.0 as I thought your axis values went from 0-100 as you said "Problem is that that Axis generates values from 0 to 100". Axis range -16384 to +16384 is standard, and I usually use: $Param 16384 + 32768.0 / ... but '$Param 32768.0 / 0.5 +' is the same. Cheers, John

You can only use the lvars provided, and listing lvars will show all available. Maybe ask QW about providing right-seat lvars.

In what way? Sorry you felt this way, but looking at my comments, there is nothing there that is unfriendly. With your attitude, that is fine by me. John

You also posted in the Download Links sub-form, where it explicitly states NOT for support requests. I have moved your post to the correct support forum. John

Does this work? I have found that sending a value to multiple lvars in his manner doesn't work. You have to use registers, i.e. Also, better to use 'Percent over 100', so value = (value + 16384) / 32767.0 ... calc_code = value .. " s0 (>A:GENERAL ENG THROTTLE LEVER POSITION:4, Percent over 100) l0 (>A:GENERAL ENG THROTTLE LEVER POSITION:5, Percent over 100) l0 (>A:GENERAL ENG THROTTLE LEVER POSITION:6, Percent over 100) " That syntax is new to me....looks strange, does it work?

If you look at your FSUIPC6.log file, you can see when the plane heading is changing from these lines: The GPS tracking info is calculated and logged here: The track 'override' value is being used instead of the actual plane heeding value. This is used as the ambient wind velocity (held in offset 0xE090) is > 2, and so the GPS ground track value is used instead, which is the value held in offset 0x6040 (GPS GROUND MAGNETIC TRACK) adjusted for the magnetic variation. So, as 0x6040 is being used, and not 0x0580, please try logging that value instead (or as well). I have attached another dll you can use which has additional logging in calculating the track value used. It is the FSUIPC6.log you need to check, as this is what is being sent. If it is only changing/updating every second, then this is because that is what FSUIPC is seeing. FSUIPC6.dll

We don't and never have supported anything with X-Plane. Pete has retired. I have no idea what dongle you are referring to - if this is for use by x-plane, then maybe ask them - or PFC. As far as I am aware, if your PFC device is a com device then you can connect directly, if you have a com interface, or you would use a com-to-usb connection cable - maybe that is this dongle you are referring to...

For the PMDG aircraft, you should consider using custom controls before looking at lvars. For L:EVT_OH_ICE_WING_ANTIICE, the following custom control is available (although this is the MSFS version as I don't have the PMDG 737 for P3D - should be the same but check your header file): #define EVT_OH_ICE_WING_ANTIICE (THIRD_PARTY_EVENT_ID_MIN + 156) To use PMDG custom controls, see the following FAQ entry: John

Many MSFS aircraft continually emit events, and these can be different for each aircraft, although I don't know why these are being sent when in the MSFS menu. You can prevent these from being logged by using the DontLogThese ini parameter, which can go in the [General] section of your FSUIPC7.ini to apply to all aircraft, or in your aircraft-specific [Profile.xxx] section. See the Advanced User guide for details. John

That is the ini file. The log file will be in the same folder. If you cannot see it, you have windows explorer set to hide the extensions of know file types - change this setting in the windows explorer settings to see the file extensions. And, as I said, usually CTDs on start-up are due to corrupt weather files. You can check to see if this is the issue by setting NoWeatherAtAll=Yes to the [General] section of your FSUIPC4.INI file. Please read my previous comment.... John

Can you please attach files, not paste contents. If that is the full FSUIPC7.log file and FSUIPC7 was not still running, then it has crashed, which is very strange, Please check the windows event viewer - there should be a crash event there - please show me that. FSUIPC7 will exit if it cannot find the FS and the option 'Exit with FS' is selected. But that would also be logged it it exited in this manner. John

Why do you want to multiply by -0.000030518, and why are you adding 50 if the lvar value is between 0 and 1? This seems rather strange - why not just multiply by 0.01 (i.e. divide by100)? The easiest way to assign an axis to control an lvar is by using a preset. Create a preset in your myevents.txt file (create this file if not present) and add the following lines DuckWorks DC-3 Throttle1#$Param 100.0 / (>DUCKWORKS_THROTTLE1_SET) DuckWorks DC-3 Throttle2#$Param 100.0 / (>DUCKWORKS_THROTTLE2_SET) DuckWorks DC-3 Throttle#$Param 100.0 / s0 (>DUCKWORKS_THROTTLE1_SET) l0 (>DUCKWORKS_THROTTLE2_SET) Then, in the axis assignment panel, check 'Send Preset to FS' and then select the preset name from the drop down on left hand side of the axis assignment panel. '$Param 100.0 /' is RPN syntax that will take the axis input value (which goes from 0 to 100) and divides by 100 to get a value between 0 and 1 to then apply to the lvar. You can adjust as needed. John

Always post FSUIPC7.log files. FSUIPC7_prev.log is the log file from the previous run, ie. when you start FSUIPC7, if there is already a log file this is renamed to FSUIPC7_prev.log and a new FSUIPC7.log file is created/started for the current run. Log files with additional numbers (e.g. FSUIPC7.1.log) are continuation log files, and are there because you have started a new log by selecting the File -> New Log menu entry. Do not use that when generating log files for support issues as I always need to see full/complete log files. Ok, so it is a separate device, and this is no longer recognised. No point sending the log file at the moment then, but I need to see your FSUIPC7.ini and FSUIPC7.JoyScan.csv files.

Yes. Ah, ok then, so its the actual assignment then....Try the previous version but I think you will get the same problem... If you do, revert back to the latest version and remove the calibration that you have on the prop-pitch axis for the DC-6, either in FSUIPC's calibration tab or by removing the following line from your [JoystickCalibration.DC-6] section of your FSUIPC7.ini file (when FSUIPC7 not running): PropPitch=-16384,16383 If you get the same issue, activate logging for Axes controls, then exit FSUIPC7. Start FSUIPC7 again, wait for about a minute for everything to get loaded/started, then move the prop-pitch axis through its full range and back again, then exit FSUIPC7 and attach the FSUIPC7.log file. John

What version is that - FS9? Are you using FSUIPC3? I do not support X-Plane/XPUIPC, only FSUIPC. The PFC drivers for FSUIPC are available from fsuipc.com, as well as in the downlink section of these forums. John

Either way is fine, its up to your personal preference. Some people like to use separate scripts, others prefer fewer but larger scripts. You can also use the same handling function for throttle1 and throttle2 (as well as one for mixture1 and mixture2) and use a conditional statement in the handling function based on the offset value to handle things separately (or set things up separately) for each throttle. But again, thats just personal preference - no problem having separate functions. Cheers, John

If you want to add lvars to offsets, you can do this using lua. Otherwise you can access them via macros. See the Advanced User guide on how to use macros to control lvars. You can do this easily using macros - no need to add them to offsets. See page 39 of the Advanced User manual. John

In your FSUIPC7 installation folder. That is a partial log, pasted from the console window, and shows that FSYUPC recognised 4 devices: Logitech Extreme 3D T-Rudder Bravo Throttle Quadrant TCA YOKE BOEING Which device are you using for the fuel cut-off lever? This does sound like the lever isn't working. Can you see it in the windows game controller config?

I would like to close this issue asap as I need to release the next version of FSUIPC shortly, probably next week. I can release with this included or not...I will probably release with this included, and can address any issues afterwards. Note I will be away for the next few days, back on Monday. John

Sorry for the delay - this is the previous version, v7.3.20: FSUIPC7.exe If you get the same issue with that version, then the issue will be that your registry has this axis defined as a digital axis, and you need to follow the instructions in that post I referenced in my previous column. If it works with this version, I will investigate in more detail. Thanks, John

I have moved your post to the MSFS / FSUIPC7 sub-forum. Please enable logging for Buttons & Keys and Events, then generate a short log file showing your issue. Exit FSUIPC7, and then attach your FSUIPC7.log and DSUIPC7.ini files and I will take a look., John

By dragging them and dropping them to the bottom of the field where you enter comments, where it says 'Drag files here to attach...' or use the choose files link in the same place..... But if you are moving the lever and it is not recognised, then I doubt there is much I can do. Is it recognised by MSFS?