John Dowson

Ok, but I am surprised at this as it doesn't work here...I can only get it to work using registers. Ok, interesting - I didn't know that syntax in lua....! John

Sorry, I don't know what this means... Then there must be an assignment somewhere that is doing this. Logging should help - activate logging for Buttons & Keys and Events, open the logging console and see what is logged when you turn the knob. You can also attach your FSUIPC7.log and FSUIPC7.ini files here and i can take a look. Please attach complete files, not paste contents, and make sure the log is full, i.e. exit FSUIPC7 before attaching, and don't use the New Log feature. As this is about FSUIPC7 / MSFS, I will move this topic to the sub-forum for this product.

No problem - I deleted your post in the User Contribution for this script as not needed. John

You have set the key press to start the lua script: So when you press the key, it kills the script and starts it again, Re-read the post - you need to set the keypress to LuaSet Smooth Brake (not Lua Smooth Brake) with a parameter of 211

Can you show me/attach your FSUIPC7.ini file please. The log file looks strange... Also a complete log file - do not use the New Log function when posting logs....

Have you checked that the lua is actually running - have you added it to your Auto section? Try lua plugin logging and take a look at the logging console or log file...

You can assign however you like, either on a single switch or on a double switch. It is up to you. Yes - please see the section COMPOUND BUTTON CONDITIONS on page 21 of the Advanced User guide. John

No. I just want to see (i.e. attach them to a comment posted in this topic) your FSUIPC7.ini and FSUIPC7.JoyScan.csv files, both of which are located in your FSUIPC7 installation folder, in the same location as your FSUIPC7.log file. If you cannot see these files, see the addendum Identifying Files in Windows Explorer on the last page of the Installing and Registering FSUIPC7 document/pdf. And I would like to know what device you are using for the cut-off levers. You previously posted a link to Etsy, which is of no use. Please paste a link to the actual controller. I am only asking you to show me some files on your system (which are easy to find...) and provide information on your controller. This is not difficult, regardless of your computer experience... John

But why are you pasting the contents of that file. As I said: Please read my comments if you want assistance. Also, please attach files rather than pasting their contents.

If the issue is with a corrupt weather file, the problem is in the Simconnect SDK libraries provided by microsoft that read this file. We cannot do anything about this in FSUIPC. Did you try adding that ini parameter, as advised?

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