yrodin Posted August 17, 2023 Report Posted August 17, 2023 Hello, I'm trying to get my throttles to respond with this airplane, but I'm having some trouble. This is the setting I used for one of the throttles; My FSUIPC.ini file has these entries; [Profile.Boeing 247D] 1=Boeing 247D Empire Airlines [LvarOffsets.Boeing 247D] 0=L:ENG THROTTLE 1=UB0xA000 1=L:ENG THROTTLE 2=UB0xA001 [Axes.Boeing 247D] RangeRepeatRate=10 0=AX,256,F,x0100A000,0,0,0 -{ FSUIPC: offset byte set, offset A000 }- 1=AY,256,F,x0100A001,0,0,0 -{ FSUIPC: offset byte set, offset A001 }- 2=BX,256,F,x0100A000,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A000 }- 3=BY,256,F,x0100A001,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A001 }- The throttles move, but skip around very quickly and can't really be set. How can I fix this? Thanks.
John Dowson Posted August 18, 2023 Report Posted August 18, 2023 There are a couple of things wrong with this... First, you need to determine the maximum and minimum values that the L:ENG THROTTLE 1/2 lvars take - is it really the same as your axis value range, which is usually -16384 to +16383. Secondly, you are storing the lvar value as 1 unsigned byte, which can only hold values 0 to 255. You should probably use 4 bytes, and also use the corresponding offset set function. But if your axis range is different from the lvar range, you need to calibrate the axis value first and so need to either use axis scaling or a lua script to read the axis value, calibrate it and then set the appropriate value to the lvar. I did show how to do this using axis scaling (different aircraft, in this thread: However, an easier method would be to define your own preset in a myevents.txt file and then assign your axis to use the preset. I also showed someone how to do this in this post (again, different aircraft and lvars but same principle): The preset method is probably easier, but you can use either. Any issues, let me know the lvar's range as well as your throttle axis range if you need further assistance. John
yrodin Posted August 18, 2023 Author Report Posted August 18, 2023 That's great info, but after I made my post I actually figured out that I had the axes entries wrong and corrected them to; [Axes.Boeing 247D] RangeRepeatRate=10 0=AX,256,F,x0100A000,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A000 }- 1=AY,256,F,x0100A001,0,0,0,*0.0030518,+50 -{ FSUIPC: offset byte set, offset A001 }- This got me back to where I started with using the default MSFS axes setting, except that I could now use FSUIPC to control the axes with this particular airplane add-on. My issue is that I am using the VirtualFly TQ6+ throttle control with a reverse thrust detent on the same axes. Since there is no way for MSFS or FSUIPC to know that, both use the full range of the control so that idle is through the detent and into the "reverse" range, which is not ideal. So the whole range is -16384 to +16383, but I need idle to be at about 9400 on one throttle and about 10000 on the other for proper idle point on the throttle. Before reading your post I found a solution that looks like this; [Axes.Boeing 247D] RangeRepeatRate=10 0=AX,256,F,x0100A000,0,0,0,*0.0040518,+35 -{ FSUIPC: offset byte set, offset A000 }- 1=AY,256,F,x0100A001,0,0,0,*0.0040518,+35 -{ FSUIPC: offset byte set, offset A001 }- Now the TQ6 sets idle on the airplane at the idle detent on the control and there is obviously no reverse action. This works great, but I'm not sure if it is technically correct or if the math is right. Can you advise? Thanks again.
John Dowson Posted August 18, 2023 Report Posted August 18, 2023 If it works, then just use that. I cannot advise if this i correct or not as I have no idea what the lvar ranges are, no idea what your full axis range is, and no idea what range of the throttle axis you are using.... It surprises me that you are still using 1 byte to hold the lvar value that you want to set. And, as I said, it is probably easier to do this using a preset.
yrodin Posted August 18, 2023 Author Report Posted August 18, 2023 Thank you, John. I will use this info. Yuri
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now