
John Dowson
Members-
Posts
13,332 -
Joined
-
Last visited
-
Days Won
273
Everything posted by John Dowson
-
MSFS knows nothing about FSUIPC or the FSUIPC7.ini file. It is FSUI{C7 that re-writes the ini file on start-up, and each time you close an assignments panel. When you see "-{MAGNETO1_SET}-" or "-{SET_STARTER1_HELD}-" these are comments, and are always re-written based upon the control of the assignment. If you want to change a control, you change the control number and parameter (if needed), not the comment, i.e the part in bold. 0=CP(+A,8)A,30,C66400,0 -{MAGNETO1_SET}- If you change the comment only, that will get re-written based on the control number when you start FSUIPC7.
-
I only set up some tests with presets for this (not lua - but the underlying mechanism that executes the calc code is the same) both using buttons and axis assignments. As I said, it didn't work for me when sent using the same value to set multiple simvars, only when using registers. I don't know or understand why. Something else may be going on - I also had an issue with two presets that looked/are exactly the same, but one works and the other not, so it could be related to this. I don't have time to look into this further at the moment. I may revisit this at some other point. Just use whatever works for you.
-
When you have removed that additional P, you may also want to remove this line: You also need to remove/re-assign the buttons/axes that were assigned to your device A: John
-
I have no idea.... I was testing with presets. Simplest example, to just set lever to 50% on a button press, this works: Test Two Engine Throttle 50#0.5 s0 (>A:GENERAL ENG THROTTLE LEVER POSITION:1, percent over 100) l0 (>A:GENERAL ENG THROTTLE LEVER POSITION:2, percent over 100) but this doesn't: Test Two Engine Throttle 50#0.5 (>A:GENERAL ENG THROTTLE LEVER POSITION:1, percent over 100) 0.5 (>A:GENERAL ENG THROTTLE LEVER POSITION:2, percent over 100) For further information, see that discord thread. No idea why...
-
No it isn't. It is the syntax to add a compound button condition. To assign two controls to one switch/button, you just duplicate/overload the assignment. The log you posted is useless - I see no button presses. Did you activate logging for buttons & keys? You also have logging for axis controls activated - please turn that off. And you used the New Log feature, which I explicitly asked you not to use as I need to see a full log. However, looking at your ini: First, you have an additional 'P' (highlighted in bold) that you need to remove. Then, when you press button 30 without button 8, MAGNETO1_OFF will be sent. When you press button 30 with button 8 being pressed, MAGNETO1_SET will be sent, followed by MAGNETO1_OFF. You probably want: i.e. you only send MAGNETO1_OFF when button 8 is not pressed. Similar changes needed for this: to But I am confused as to what you are actually trying to achieve with this....
-
it is valid RPN code, but it doesn't do what you expect when I tried it - there is a discussion about this on the MobiFlight discord channel: https://discord.com/channels/608690978081210392/1028408626643214336/threads/1121089790553632850 If it works as expected for you, then thats fine. Just didn't work for me. i was testing using presets, not lua, but they both use the same mechanism to execute the calculator code, so not sure why it works for you but not for me. Look a the the code i provided: The value provided is stored in register 0 (s0), and then the register is used to provide the value for the subsequent simvars (l0). I am no expert in using registers in calc code - this was provided by the MF team in that thread I referenced. I started that thread as the calc code in the style you are using wasn't working for me and I couldn't understand why.
-
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.
-
Assigning an axis to a button
John Dowson replied to brettt777's topic in FSUIPC Support Pete Dowson Modules
No problem - I deleted your post in the User Contribution for this script as not needed. John -
Assigning an axis to a button
John Dowson replied to brettt777's topic in FSUIPC Support Pete Dowson Modules
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 -
Assigning an axis to a button
John Dowson replied to brettt777's topic in FSUIPC Support Pete Dowson Modules
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.... -
Assigning an axis to a button
John Dowson replied to brettt777's topic in FSUIPC Support Pete Dowson Modules
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
-
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?
-
Assigning an axis to a button
John Dowson replied to brettt777's topic in FSUIPC Support Pete Dowson Modules
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
-
Assigning an axis to a button
John Dowson replied to brettt777's topic in FSUIPC Support Pete Dowson Modules
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
-
XPlane 8.6 using windows xp
John Dowson replied to SGRG's topic in FSUIPC Support Pete Dowson Modules
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 -
XPlane 8.6 using windows xp
John Dowson replied to SGRG's topic in FSUIPC Support Pete Dowson Modules
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