John Dowson
-
Posts
11,149 -
Joined
-
Last visited
-
Days Won
220
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
I have looked into this further, and what ever assignments I try I always get the same problem: when I deactivate the reversers, the motion of the plane suddenly changes from reverse to forward motion, even though the thrust is at idle. This seems to be an issue for PMDG (or maybe MSFS) - I will investigate further when I return from my holidays and report/raise a bug if necessary.
This is the simple config I ended up with:
[Buttons.PMDG737] ButtonRepeat=4,2 1=PB,8,C65966,1 -{THROTTLE1_DECR}- 2=UB,8,C1070,112 -{: F1}- 3=PB,9,C65971,1 -{THROTTLE2_DECR}- 4=UB,9,C1070,112 -{: F1}- 5=CR(+B,8)B,24,C65966,1 -{THROTTLE1_DECR}- 6=CR(+B,8)B,25,C65971,1 -{THROTTLE2_DECR}-This only sends the F1 key (throttle idle) when reversers de-activated, but has the affect of changing reverse motion to forward motion in an instant, although the thrust is at idle.
I decided to remove the action on the release of the throttle detent, and I have slowed the button repeat rate to 4 per second. This allows me to slowly increase reverse thrust and move back to the detent to maintain that level of reverse thrust.I did try various other assignments, but they all had this issue. The throttle 1/2 reverse thrust hold didn't work, although others have reported that Throttle Reverse Thrust Hold is working (i.e. all engine version), but I haven't tried that.
John
-
10 hours ago, tdenbrock said:
except that Asobo MSFS FSUIPC 7 auto/start has an issue on initial startup
Yes, this is very strange, I do not know what could cause this, as the auto-start does work on subsequent runs of MSFS You will just have to manually start GSUIPC7 on the first run of MSFS I'm afraid.
Note the desktop MSFS icon created by the installer is just a shortcut to the MSFS.bat file, which shows a splash screen while MSFS is starting. It does not start FSUIPC7 - that is performed by MSFS itself using the EXE.xml file,
-
Only the latest version of each FSUIPC version is supported (apart from betas) - please update to 7.3.8 or 7.3.9c.
If you update to v7.3.8, also manually add the following to your FSUIPC7.ini:[WAPI] EnableWAPI=YesYou should also update your profiles to use substring matching, e.g. change this
[Profile.PMDG 737-700] 1=PMDG 737-700 Southwest Airlines (N268WN | 2021 | Heart) 2=PMDG 737-700 United Airlines (N27734 | 2019 | EvoBlu)to this:
[Profile.PMDG 737-700] 1=PMDG 737-700John
-
Sorry, didn't have much time today to look into this...
On 9/7/2022 at 8:16 PM, rondon9898 said:When I set the throttle detent buttons to set the throttles to parameters -1 upon release, nothing happens. I’m trying to set it so that when the detent buttons are released, the throttles go to reverse idle, then closing the reverse levers cuts the throttles (so they go to forward idle). The reverse levers are working on press and release, and the detents are working on press, but they’re not working on release.
The throttle detent should work on release in FSUIPC...I don't think this works in the FS as I believe the always-on type buttons just continually send presses until turned off, and no release.
This is the config I have which is basically how you describe:
[Buttons.PMDG737] 1=PB,8,C65966,1 -{THROTTLE1_DECR}- 2=UB,8,CPPMDG_B737_Eng_1_Reverse_Thrust_Kill,0 -{Preset Control}- 4=PB,9,C65971,1 -{THROTTLE2_DECR}- 5=UB,9,CPPMDG_B737_Eng_2_Reverse_Thrust_Kill,0 -{Preset Control}- 6=CR(+B,9)B,25,C65971,0 -{THROTTLE2_DECR}- 7=CU(+B,8)B,24,C65820,-1 -{THROTTLE1_SET}- 8=CR(+B,8)B,24,C65966,0 -{THROTTLE1_DECR}- 9=CU(+B,9)B,25,C65821,-1 -{THROTTLE2_SET}-However, the Throttle1/2 Set with a parameter of -1 doesn't seem to set idle reverse, and killing reverse starts forward thrust instead of idle forward.
I'll see if I can take another look tomorrow.... I will check the parameter of -1 to see if I can change this to get idle, and also check what the controls Hold Throttle Reverse Thrust do...
You can always use FSUIPC's logging facility to see what is happening on button presses and releases - best to do this with the logging console window open so that you can see the button presses/releases and events sent in real time.
Note that I will be on holiday from tomorrow evening. back a week Monday.
-
Some issues with that version, try this one, 7.3.9c: FSUIPC7.exe
-
Here it is: FSUIPC7.exe
-
No idea...this is support for FSUIPC and WideFS, not Xplane or XPWide.
-
6 minutes ago, tdenbrock said:
OK, When I first initially start MSFS for the day, There is No FSUPIC 7 Splash screen showing. .
Then FSUIPC7 is not auto-starting... How are you starting MSFS?
6 minutes ago, tdenbrock said:MSFS pauses for about 20-30 secs then continues.
This is normal...
7 minutes ago, tdenbrock said:I shut it down and restart the game again and then and "ONLY" then will FSUIPC 7 show a splash screen FSUIPC7 and it shows running in the system tray.
So you are saying that FSUIPC7 auto-starts the 2nd and subsequent times you run MSFS, but not the first (after a reboot)...I don't understand this - there is no count on the number of times you start MSFS.
9 minutes ago, tdenbrock said:Now if I try to start it for the first time of the day just using the FSUIPC.exe file, MSFS will run along with FSUIPC showing "Getting cabin ready" splash screen, but it will not show a FSUIPC 7 splash screen or show in the system tray.
This I don't understand either... Running the FSUIPC7.exe ONLY runs FSUIPC7, not MSFS. If you see the 'Preparing the cabin' splash screen, you are using the MSFS desktop icon (created by the FSUIPC7 installer) or the MSFS.bat file, and not the FSUIPC7.exe. Please try and start using the FSUIPC7.exe, i.e. go to your FSUIPC7 installation folder and double click the FSUIPC7.exe file, NOT the MSFS desktop icon created by FSUIPC7 installer as that starts MSFS and not FSUIPC7, as the name suggests...
But if FSUIPC7 is just not starting the first time you run MSFS after a reboot, but works on subsequent attempts, then I have no idea what could cause thus. It is an MSFS issue, not an FSUIPC7 one, and I do not know why or how it could be doing this. It is not obeying the MSFS EXE.xml, so you should report this to Asobo.
When this occurs, just manually start FSUIPC7 by double clicking the FSUIPC7.exe, and NOT the FSUIPC7 MSFS icon or MSFS.bat file.John
-
First, you posted in the Download Links sub-forum where it explicitly states NOT for support requests. I have moved your post to the correct forum for this question, which has also been asked many, many times before...
Check the error 2 down from the one you highlighted. This will be an MSFS CTD. When this happens, you also get an fault (not a CTD) in FSUIPC7 as the FS has quit unexpectedly. If you check your FSUIPC7.log file, you will see that FSUIPC7 exited as MSFS was no longer available - and you may also see some SimConnect errors before this.
If MSFS CTDs, report to Asobo. I cannot help with this.
John
-
-
29 minutes ago, John Dowson said:
Try listing the lvars to see if any look appropriate. I will also take a look at some point to see if I can see anything...
See what the following lvars hold and how they change when you set TOGA:
XML_Airbus_Throttle1_TOGA
XML_Airbus_Throttle2_TOGAThere are also the following, but probably less useful:
TOGAPush
TOGARelease
If the XML_* variables hold the correct TOGA state, you could use those...-
1
-
-
Ah, sorry - I think I misunderstood.... You have the TOGA button working, but the offset is not updated and so the motorized throttle doesn't see it...
If that is the case, you need to determine if there is a different simvar or possibly an lvar that is updated instead. Once this has been found, you can either add that to a spare FSUIPC offset and use that, or you can add to an offset and spoof offset 0x080C to the value of the new offset.Try listing the lvars to see if any look appropriate. I will also take a look at some point to see if I can see anything...
John
-
1
-
-
Many standard controls and offsets don't work with the PMDG 737 - you need to use either custom controls (using the Rotor Brake control) or presets.
Presets may be easier, and looking at https://hubhop.mobiflight.com/presets/ I can see the following which you can try:
PMDG_B737-7_AUTOTHRUST_TOGA_L_BTN
PMDG_B737-7_AUTOTHRUST_TOGA_R_BTN
Or assign to the Rotor Brake control, with a parameter of 68401 for the left button, and 68701 for the right button.
To use the Rotor Brake control with the PMDG 737, see this FAQ entry:John
-
Could you try the attached version, v7.3.9c. This fixes a CTD caused in the WAPI (WASM API( that can occur when several config data updates are received in quick succession, usually caused by lvar creation in the WAPI/WASM. I don't think this is the cause of your CTD but worth trying. I have not been able to get a CTD with this version so far...
Could you also enable debug logging in the WAPI, by adding the following to the [WAPI] section of your FSUPC7.ini file:
LogLevel=Debug
and show me your FSUIPC7.log file again if/when you get a CTD.John
Later: beta version removed, some issues...I will repost at some point...
-
Stick with the current script - when updated on an event, the offset reverts back to 0 (when parking brake set) after a few seconds, and so needs to be continually updated.
I did however experience a FSUIPC7 crash, and after restarting had difficulties accessing lvars. I will investigate.
John
-
1 minute ago, rondon9898 said:
The reverse levers are working on press and release, and the detents are working on press, but they’re not working on release.
I am pretty sure they were for me...show me your FSUIPC7.ini and I will take a look (tomorrow now).
-
8 minutes ago, rondon9898 said:
Also, why are all my buttons showing 1 lower number in FSUIPC than in the Windows Game Controllers dialogue?
FSUIPC numbers buttons from 0, whereas windows starts from 1...
9 minutes ago, rondon9898 said:The problem seems to be that either FSUIPC or PMDG or MSFS doesn’t seem to register when the detent buttons are released. It registers when they are selected, but not released.
FSUIPC certainly registers a release...but what button(s) are you talking about? What are you trying to do?
9 minutes ago, rondon9898 said:I’ve tried a conditional thing and have obviously set it correctly in the FSUIPC.ini, but it doesn’t solve the problem.
What problem?
I have a few other settings/configurations that I would like to try - didn't have time today, but will take another look tomorrow...
I can also show you how I used this to prevent reversers activating from the throttle detent when reverser not activated.John
-
7 minutes ago, Chad P said:
Here are another logs after restarting it manually and activated lua logs.
Ok, that shows the lua was sleeping when the crash occurred, so I doubt that is an issue.
9 minutes ago, Chad P said:the second log without crash (waited for 3 minutes), now I've to go to my kids 🙂
So it doesn't crash every time? How come the lua plugin log wasn't still active in that log?
6 minutes ago, Chad P said:I've downloaded the LUA Script from this forum and don't know how it's working..If you can optimize this scipt it would be nice
Yes - I wrote that script a while ago as an example. I will update to use an event when I get a chance and repost.
-
So this only happens with the FVW experimental? As I said:
52 minutes ago, John Dowson said:Maybe also check that you are using the latest experimental release. Can you also let me know if this is the only aircraft/version in which this occurs, and maybe switch to the stable or development version temporarily and check with that version.
7 minutes ago, Chad P said:I've a lua script for the parking brake (for the VA-Tracker), but using it for over a year without problems - could this be the issue?
It shouldn't, but maybe try activating logging for Lua Plugins and send me a log with that. You can also try temporarily disabling it (just rename the lua file before you restart FSUIPC7) to make sure.
That lua could also do with an update - it should really use event.lvar rather than an infinite loop with a delay...
-
No, sorry, but this has been reported before, but not sure what can cause this...
-
5 minutes ago, tdenbrock said:
What I am trying to say is the when I start MSFS.. FSUIPC 7 does not load/Auto start.
So, FSUIPC7 does not auto-start? If that is the issue, see the post I reference in my first comment on your issue.
6 minutes ago, tdenbrock said:I have to restart MSFS for it to load.
This I don't understand...why would FSUIPC7 auto-run the 2nd time but not the first? Each time you start should be the same as the last...and why restart MSFS and not just run FSUIPC7?
10 minutes ago, tdenbrock said:I have also tried manually starting FSUIPC 7 after MSFS has loaded and still it will not load. It doesn't show in my system tray until I restart it.
Your use of the word load is what is confusing...and when you say 'restart it' do you mean MSFS or FSUIPC7?.
And what happens the third or on subsequent attempts to run MSFS?
13 minutes ago, tdenbrock said:I read your response on this issue with another person in not having to restart MSFS but to disconnect/reconnect in the Menu for MSFS in FSUIPC 7 but if it doesn't load how can I disconnect/reconnect it if there is no way to access the menu.
The MSFS menu is only (obviously...) available if FSUIPC7 is actually running...
13 minutes ago, tdenbrock said:I also am not sure where to find all this information that you have posted in how to fix it.
All the information is in the User manuals or in the posts I have referenced...
But I still don't understand your issue... Could you tell me EXACTLY what happens when you run MSFS - do you see an FSUIPC7 splash screen? If not, it is not auto-starting, and if this is the case you should try to start manually by double-clicking the FSUIPC7.exe. What happens when you do that? If it runs ok then, then your issue is with auto-start and you should refer to the link I posted on this issue. Otherwise, it could be a problem running FSUIPC7 - which is documented in the README.
But please explain your issue, without using load. A program either runs when you start it or not - do you have FSUIPC7 running? If it is in your system tray, it is running.
-
Also, did you auto-start FSUIPC7 with MSFS, or start it manually, an if so, when?
Does it crash again if you restart FSUIPC7? If so, can you show me the log, as well as your FSUIPC7.ini.After a few tests, it seems ok here. Maybe also check that you are using the latest experimental release. Can you also let me know if this is the only aircraft/version in which this occurs, and maybe switch to the stable or development version temporarily and check with that version.
-
Not sure if I can do anything if this is just with the FBE A320 experimental version, but I will switch to that and take a look.
Looks to be using something new called SimBridge - are you using that as well?
-
4 minutes ago, kingm56 said:
I thought you were on holiday, John?
From Saturday for 9/10 days...
6 minutes ago, kingm56 said:In short, my application shows the users LVARs are available via WAPI; however, his FSUIPC7 LVAR/HVAR menus are not accessible ('greyed-out'). I'd be grateful for any insight, when time allows...
The log you attached shows the lvar names were received - when this happens, a message should be logged in the FSUIPC7 main window with the number of lvars/hvars/presets loaded, and the WASM menu items should be enabled. I can't see how the menu items cannot be enabled once the lvar names have been received... Make sure the user is checking after this message is logged...
10 minutes ago, kingm56 said:Also, what version of FSUIPC7 is the .exe?
7.3.9b.
John
FSUIPC Upgrade from v5 to v6 oddity. Need Help Please
in FSUIPC Support Pete Dowson Modules
Posted
This indicates that the button is either overloaded, or there is a compound or offset condition in the button press. Activate logging for Buttons & Keys, open the logging console and see what is logged when the button is pressed - that should give you some idea.
Also, check that aircraft name is in your profile - use substring matching in profiles or when you use an aircraft with a different livery it may not match your profile.
But I am now on holiday until Monday 19th. If you are still having issues, post your FSUIPC6.ini as well as your FSUIPC6.log file with logging for Buttons & Keys added as well as Events and I'll take a look when I return.
There really should be no such issues switching from FSUIPC5 to FSUIPC6...