John Dowson
-
Posts
11,109 -
Joined
-
Last visited
-
Days Won
219
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. I have moved your post, but please take care to post in the correct forum for support.
1 hour ago, ifhandp said:Can any of you help me to setup my Throttle A320 from FlightPM on my p3d game version v5?
What have you tries? What problems are you having? Does FSUIPC recognise your throttle? If so, it should be relatively straightforward to assign.
What aircraft are you using in P3D? -
You can save offset data when saving a flight using the SaveDataWithFlights ini partameter - see the Advanced User guide on using this parameter. It can be controlled from the Miscellaneous option (Options->Miscellaneous...) Reload FSUIPC data - change this from Never to Always or for Autos.
John
-
This has been reported many times already - see
John
-
2 hours ago, John Dowson said:
or better to re-install and accept the default installation options, which should auto-start via the batch file and not the EXE.xml file.
It wasn't obvious where to download the new installer in the post I referenced as it was included in a comment further down the page. I have updated this now to reference the installer in the first post. You can download from here: https://fsuipc.simflight.com/beta/Install_FSUIPC7beta.exe.
John
-
28 minutes ago, GoldenAero7 said:
How about this link?
That link is good,
Your log file shows that FSUIPC7 was auto-started via the EXE.xml file:
Quote390 12748 Auto-started via EXE.xml with DetectToConnectDelayAuto=60, InitialStallTime=20
As I said in my post above, there is an issue with lua performance when FSUIPC is started this way. Can you either exit FSUIPC7 once started and restart it manually, or better to re-install and accept the default installation options, which should auto-start via the batch file and not the EXE.xml file.
John
-
7 hours ago, GoldenAero7 said:
I have uploaded the files onto this link
I get a 404 error (page not found) with that link.
-
2 minutes ago, Darth JBell said:
Ok, Sir! I’ll give it a shot. Thanks for your work on this!
No problem...however, I just updated the attached script, so please download again if you already downloaded.
-
Can you try the following lua script. To use, first save this file to your FSUIPC6 installation folder (or your Lua library folder if you have set a different folder for lua files via the LuaPath ini parameter).
You then need to:
1. Have the lua file auto-started. To do this, add to your profile [Auto.xxx] section (or just [Auto] if using profiles-in-separate-files, in your profile file), e.g.:
Quote[Auto.Nanchang]
1=Lua nanchangBrake2. Assign your rudder axis with Send to FSUIPC Offset, and use control Offset Dword Set and offset xA010 (you can use a different offset, but if you do you also need to change the offset used in the script, local variable rudderAxisOffset)
3. Open the lua file you installed and set the following variables to specify the joystick & button you are using to control the brake lever:
Quotelocal brakeLeverJoystickLetter = "S" -- the letter of the joystick that has the button used to control the brake lever
local brakeLeverButton = 0 -- the number of the button on the joystick that is used to control the brake lever4. You can also set logging if you want to see what is happening by changing the enableLog value from false to true.
5. You can adjust the repeat rate for standard brakes by altering the brakesInterval value - increase for slower braking, decrease for faster braking
Let me know how it goes and if you need further tuning. I have commented the script so you should be able to tune for your needs.
John
-
1 minute ago, jabloomf1230 said:
Ok, Thanks. I was trying to write a DLL interface to FSUIPC and I thought that there was. I apologize.
To interface to FSUIPC, use one of the provided SDKs. Look in the SDK folder - I have attached the programmer API documentation.
John
-
5 minutes ago, C.Schaffhausen said:
This is what I use:
[Buttons.PMDG 737]
1=PC,9,C65966,1 -{THROTTLE1_DECR}-
2=UC,9,C65967,0 -{THROTTLE1_CUT}-
3=RC,25,C65966,0 -{THROTTLE1_DECR}-
4=UC,25,C65965,23 -{THROTTLE1_INCR_SMALL}-
5=PC,10,C65971,1 -{THROTTLE2_DECR}-
6=UC,10,C65972,0 -{THROTTLE2_CUT}-
7=RC,26,C65971,0 -{THROTTLE2_DECR}-
8=UC,26,C65970,23 -{THROTTLE2_INCR_SMALL}-Ok, interesting. So you are using the buttons at the bottom of the axis to decrement on repeat rather than the reverser (buttons). Maybe better then to send THROTTLE1/2_IDLE on the reverser buttons (9,10 in your config) rather than Throttlw1/2_DECR - or even both (i.e. an idle followed by a decr), although the throttle should already be in the idle position when you activate reversers so not that important.
Does this config prevent the aircraft from jumping directly from reversing to forward motion? I will try this when time permits.Thanks,
John
-
18 minutes ago, Freccia said:
Wow, everything works now.
👍
-
3 minutes ago, Freccia said:
I replaced the string in the myevents.txt file but it doesn't seem to work and I don't understand why.
Did you restart FSUIPC7? Presets are only loaded when FSUIPC7 is started. Also, check you are using th correct preset - the image shows that you are still using the MF preset from the events.txt file.
3 minutes ago, Freccia said:Furthermore, I continue to delete the check marks on Up and Down but every time I reopen I find them selected, as in the figure.
You need to delete them - click Delete all followed by Ok.
John
-
1 minute ago, Freccia said:
However, it works the opposite of how I would like (I would like the value 16384 to correspond to the carbheat being deactivated). But if it's not possible to do it, it doesn't matter, I'll make it work for me.
Then you need to reverse the axis range in the preset, i.e.
//A2A SIM/Comanche 250/Engine MY_PA24_250_Carbheat_Axis#@ -1 * 16384 + 327.68 / 0 max 100 min (>L:Eng1_CarbHeatSwitch, Number)John
-
1. If you are assigning the preset to an axis, then you do not need to check Select for preset'(top-right). This is for sending presets on axis ranges as button controls, Remove this.
2. The correct way to send axis values to a preset is by checking Send Preset to FS, which you have done, but then you also need to check the first box below this and select the preset from the drop-down menu.
3. The following preset:
PA24_250_Carbheat_Axis#@ 15 - 10.0 / 0 max 100 min (>L:Eng1_CarbHeatSwitch, Number)
subtracts 15 from the axis value ("15 -") then divides by 10.0 ("10.0 /"). If you are using a standard axis, that will have a range of -16384 to +16383, and you need to calibrate this to the lvar range of 0 - 100. To do this. define your own preset in the myevents.txt file as follows://A2A SIM/Comanche 250/Engine MY_PA24_250_Carbheat_Axis#@ 16384 + 327.68 / 0 max 100 min (>L:Eng1_CarbHeatSwitch, Number)Then assign your axis to this preset (using the left-hand side of the axes assignment panel, not the right-hand side).
John
-
25 minutes ago, GoldenAero7 said:
I could not attach the files you requested here due to file size constraints.
Your upload limit will increase as you post more - it is restricted/rather low for new users. Try compressing/zipping them - they should compress well as they are only text files. Otherwise, you can share them using one of the web transfer services to do this, such as https://filetransfer.io/ or https://wetransfer.com/.
30 minutes ago, GoldenAero7 said:The aircraft I have loaded is Guimbal Cabri G2 which, correct me if I'm wrong, is a GA aircraft.
I have the G2 so I can check with that aircraft here.
John
-
Sorry but I do not understand what you are talking about. There are no facilities in FSUIPC to create SimObjects, - I have no idea what 'FSUIPCInt.CreateSimObject' means...
-
What version of the ATR do you have installed? Maybe check for an update.
I have just checked here and all is working as expected. On my dev system, I have both condition levers assigned to the same axis, and this works fine:
Quote4=TY,256,F,PMSATR CONDITION1 LEVER SET2,PMSATR CONDITION2 LEVER SET2,0,0 -{ TO SIM: Preset Control, Preset Control }-
which is using the following presets (in the myevents.txt file):
MSATR CONDITION1 LEVER SET2#@ 16384 + 10923 / near 0 max 3 min (>L:MSATR_CONDITION1_POS) MSATR CONDITION2 LEVER SET2#@ 16384 + 10923 / near 0 max 3 min (>L:MSATR_CONDITION2_POS)I have also tested with the following macro (ATRCondition.mcro):
Quote[Macros]
1=L:MSATR_CONDITION1_POS=Set
2=L:MSATR_CONDITION2_POS=Setand have assigned buttons to this, just testing with condition lever 1 only, and setting the parameters on the assignment as such:
Quote2=P174,0,CM7:1,0 -{Macro ATRCondition: L:MSATR_CONDITION1_POS set}-
3=P174,1,CM7:1,1 -{Macro ATRCondition: L:MSATR_CONDITION1_POS set}-
4=P174,2,CM7:1,2 -{Macro ATRCondition: L:MSATR_CONDITION1_POS set}-
5=P174,3,CM7:1,3 -{Macro ATRCondition: L:MSATR_CONDITION1_POS set}-
6=P174,4,CM7:1,4 -{Macro ATRCondition: L:MSATR_CONDITION1_POS set}-and they all work as expected.
So you are certainly doing something wrong.... Please check that you are using the latest version of the ATR and try the above - either on an axis or buttons or both. If not working, please attach your ini and log files again, the latter with appropriate logging activated (i.e. Extras, Events and Buttons & Keys if using buttons, and Axis Controls if using an axis). Maybe easier if you try the buttons first, but up to you.
John
-
11 minutes ago, Darth JBell said:
I have a brake “handle” on my X56 HOTAS. I’ll get the Joy Number and Button Number in just a sec.
No need. I will just use a spare button. You will have to update the scripts I provide for your controller letters, axes letters button numbers and offsets to use anyway.
This seems very similar to the Spitfire differential braking, except the control for that was on a brake lever which is an axis. Should be simpler on a button.
John
-
52 minutes ago, Darth JBell said:
I’ll take a look although I’m running PREPAR3D w/FSUIPC version 6. The Behr Studio/Sim Market folks say the Chang doesn’t work w/MSFS 2020.
This post is for the Spitfire brake. I referenced it for you as you need to do something similar for the CJ-6 Nanchang. I will help you with this in the thread where you asked. Once this is done, you can create a User Contribution similar to this to explain to others how to do this in the CJ-6.
-
10 minutes ago, Darth JBell said:
It’s weird right? So in the real aircraft 3 things are going on:
- First, when one moves the rudder bar, the rudder deflects a proportional amount just like any other aircraft as the two are connected via cable.
- Second, when one grasps the “bicycle” brake handle, air from the pneumatic system is sent to both wheel brakes in equal amounts when the rudder bar is centered (not deflected more than 16 degrees either direction).
- Finally, when one positions the rudder bar past neutral (anything greater than 16 degrees) with the brake handle also depressed, air from the pneumatic system is metered more toward the deflected side and less from the other side causing a differential braking condition for ground steering.
Ok, that should be possible via lua. How are you planning to control the "brake handle"? Do you want this assigned on a button or key press?
I will take a look and provide you a lua script to test, but it may take several days as I am pretty busy at the moment (well, always!).John
-
11 minutes ago, voltigeurramon said:
he fuel shutoff positions aren't on an axis, they are using the toggle feather switch 1/2. Everyting else on the condition lever (feather, auto and 100% ovrd) is on an axis (prop pitch 1/2). Using the "Toggle feather 1/2 switch" in FSUIPC works most of the time, but not all the time. So that's why I wanted to use the lvar to control it, as others do as well.
Not sure I understand this. The ATR has 2 condition levers that each have 4 discrete ranges. Why don't you just use two of the Bravo axes to control this using those presets?
33 minutes ago, voltigeurramon said:I can hear the lever clicking in the sim, but it doesn't move and the engines does shut down. When I set the lvar from the WASM menu to the other positions, that doesn't work either. The ini and log (logged buttons and events) files are attached. The buttons were pressed, but an event didn't happen. There isn't much in the log, scroll all the way down for the buttons and events logged. Thanks again for all the help.
Ok, so setting the L:MSATR_CONDITION1_POS and L:MSATR_CONDITION2_POS lvars to a value between 0 - 3 no longer moves the condition lever? That is strange, and something must have changed. I will take a look and get back to you.
John
-
2 minutes ago, voltigeurramon said:
I'm soooo encredibly stupid. I'm so sorry for wasting your time. All I had to do was using the reverse thrust with the engines running. Whenever I did a flight I just didn't use them and all the testing I did for this thread was with the engines off. I'm really sorry you trying to help me, but I just had to think with a bit og logic for one second......
Ah, ok....
7 minutes ago, voltigeurramon said:I do have one question left tho about the ATR. I'm trying to bind the condition lever lvars to shut off the fuel, as said in this (and many more) post:
Can you attach your macro file please. As the condition lever has 4 discrete positions, I am not sure how you are controlling this on a button. Why don't you use an axis (the Bravo has plenty!) and use the axis presets defined in this post:
John
-
Also, please see this comment on the same issue (PMDG 737 reversers):
Also see further down for another possible configuration (I have just asked the user to post his settings).
It seems that nothing is perfect for the PMDG 737 reversers - configure and use what mostly works for you. The main issue seems to be a jump from reverse to forward motion when killing reversers which is rather strange!
John
-
@C.Schaffhausen said:
On 12/8/2022 at 11:02 AM, C.Schaffhausen said:Hello, I came up with something to make the following work on Honeycomb bravo reverse with the PMDG 737:
Could you please share your assignments for this for other users to try.
Thanks,
John
setup FSUIPC with FlightPM A320 Throttle
in FSUIPC Support Pete Dowson Modules
Posted
No. As far as FSUIPC is concerned, your controller is just a collection of buttons and axes just like any other hardware throttle, and setting up all controllers is exactly the same.
What is more important is the aircraft you are setting this up for. I don't have the FSLabs A320, but I think that uses quite a few custom controls via the Rotor Brake control. You need to check what custom controls are available if the standard controls don't work. These should be documented with the aircraft, or check the FSLabs forums.
You can also try logging - this should tell you if a standard event/control is used or a custom control (a custom control number or the Rotor Brake control parameter) . Activate logging for Events (non-axes controls) and open the logging console. Then you can click the function in the VC and see what is logged and then use that (i.e. assign to the event/control and parameter used).
Also I think the Pilot's Deck plugin works for the A320 - you could check that out and see what that uses.
John