John Dowson
-
Posts
11,149 -
Joined
-
Last visited
-
Days Won
220
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
Hi Bob,
there is currently an issue in the released version in that the WideFS enabled state is currently not remembered correctly. This could be affecting the full UNC path from being reported. Could you therefore check with the latest beta, available here:
If you still get the same issue with that version could you attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look.
Cheers,
John
-
It shouldn't make any difference to the functionality of FSUIPC if you auto-start FSUIPC or start it manually, or if you start FSUIPC7 before or after MSFS.
John
-
Both if those log files show that FSUIPC was quit manually. You need to look at/show me the log file generated when you get a CTD. And you have still not confirmed if this was an MSFS CTD (when FSUIPC would also exit) or an FSUIPC CTD (when MSFS would still be running).
Your prev log (i.e. the one generated in the penultimate run of FSUIPC7) does show some errors:
Quote41890 [ERROR]: Error setting Client Data Calculator Code: '46002 (>K:ROTOR_BRAKE)'
41890 [ERROR]: Error setting Client Data Calculator Code: '100 (L:switch_126_73X, number) == if{ 12601 (>K:ROTOR_BRAKE) }'
41890 [ERROR]: Error setting Client Data Calculator Code: '100 (L:switch_115_73X, number) == if{ 11501 (>K:ROTOR_BRAKE) } 100 (L:switch_116_73X, number) == if{ 11601 (>K:ROTOR_BRAKE) }'
41890 [ERROR]: Error setting Client Data Calculator Code: '100 (L:switch_122_73X, number) == if{ 12201 (>K:ROTOR_BRAKE) }'
41890 [ERROR]: Error setting Client Data Calculator Code: '100 (L:switch_117_73X, number) == if{ 11701 (>K:ROTOR_BRAKE) }'
41890 [ERROR]: Error setting Client Data Calculator Code: '100 (L:switch_113_73X, number) == if{ 11301 (>K:ROTOR_BRAKE) } 100 (L:switch_114_73X, number) == if{ 11401 (>K:ROTOR_BRAKE) }'
These are due to using presets before the WASM interface is activated.
John
-
I see you also have lots of other logging activated....just log events and buttons & keys - turn the other logging options off. That should reduce the log file size.
You can also provide a second log with Axes controls logged as well as Buttons & Keys (nothing else).John
-
You could try activating logging for Buttons & Keys as well, which would tell you if any of those control are being sent from a button press/release.
Other than that, there are two things that stand-out in your ini file:1. One of your controllers was not connected:
QuoteA=TCA Q-Eng 1&2 << MISSING JOYSTICK >>
A.GUID={A371ECA0-79FA-11EC-8002-444553540000}?
2. You have some controls being sent when your spoiler axes enters/leaves two distinct ranges:
Quote1=AR,1,D,22,0,0,0 -{ DIRECT: Spoilers }-
2=AR,B,6237,11736,4199503,0 -{ DIRECT: SpoilersEntering=Preset Control }-
3=AR,B,11884,16383,4199504,0 -{ Entering=Preset Control }-
Can you check (using the UI axes assignment window) what these presets are that you have assigned to please and let me know?
This actually shows an issue - the control numbers are being used here, where the preset name should really be used (as in your button assignments) as the actual control numbers for presets can change when the events.txt file is updated. Therefore please check that they are still assigned to the correct controls/presets. I will look into this.As for the log file, you could try emailing me the zipped log to jldowson@gmail.com
Can you also check if you have any assignments in MSFS, or are you using an empty profile in MSFS for your controllers?
John
-
What is sending those rotor brake commands? What else do you have running? Can you show me your FSUIPC7.ini file please, as well as attach your complete log (you can zip it if large).
When you relaunch FSUIPC, the rotor brake control with parameter 99003 is just a mouse-move (3) for this control:
#define EVT_ISFD_ATT_RST (THIRD_PARTY_EVENT_ID_MIN + 990) //When you have your issue, many different controls are being sent, most with a mouse move (3) command but also a click (1) and release (4):
15 minutes ago, wawona said:1345968 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 38303 (0x0000959f) ROTOR_BRAKE - EVT_MCP_CO_SWITCH
1346000 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 38303 (0x0000959f) ROTOR_BRAKE - EVT_MCP_CO_SWITCH
1346062 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46503 (0x0000b5a7) ROTOR_BRAKE - EVT_MPM_SPEED_REFERENCE_CONTROL
1346343 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE - EVT_MPM_MFD_SYS_BUTTON
1346359 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE -
1346375 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346406 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346422 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346453 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346468 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346500 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346531 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346562 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346593 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346625 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346656 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346687 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346703 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46203 (0x0000b47b) ROTOR_BRAKE
1346718 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE - EVT_MPM_MFD_ENG_BUTTON
1346750 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE
1346797 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE
1346812 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE
1346843 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE
1346859 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE
1346953 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46301 (0x0000b4dd) ROTOR_BRAKE - EVT_MPM_MFD_ENG_BUTTON (left click)
1347031 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46304 (0x0000b4e0) ROTOR_BRAKE - EVT_MPM_MFD_ENG_BUTTON (left release)
1347047 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE
1347078 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE
1347093 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE
1347125 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 46303 (0x0000b4df) ROTOR_BRAKE
1347265 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 36603 (0x00008efb) ROTOR_BRAKE - EVT_EFIS_CPT_BARO_IN_HPA
1349156 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 34903 (0x00008857) ROTOR_BRAKE - EVT_SYSTEM_ANNUNCIATOR_PANEL_LEFT
1349312 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 33903 (0x0000846f) ROTOR_BRAKE - EVT_DSP_CPT_AP_RESET_SWITCH
1349390 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37303 (0x000091b7) ROTOR_BRAKE - EVT_EFIS_CPT_DATA
1349406 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37403 (0x0000921b) ROTOR_BRAKE - EVT_EFIS_CPT_POS
1349437 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37403 (0x0000921b) ROTOR_BRAKE
1349656 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE - EVT_EFIS_CPT_TERR
1349672 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE
1349703 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE
1349718 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE
1349734 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE
1349765 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE
1349797 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37501 (0x0000927d) ROTOR_BRAKE
1349890 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37504 (0x00009280) ROTOR_BRAKE
1349906 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE
1349922 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37503 (0x0000927f) ROTOR_BRAKE
1349953 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37403 (0x0000921b) ROTOR_BRAKE - EVT_EFIS_CPT_POS
1349984 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 37203 (0x00009153) ROTOR_BRAKE - EVT_EFIS_CPT_ARPT
1350015 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 36003 (0x00008ca3) ROTOR_BRAKE - EVT_EFIS_CPT_MODE_CTR
1350031 26324 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 35703 (0x00008b77) ROTOR_BRAKE - EVT_EFIS_CPT_MINIMUMS_RSTYou need to determine what is sending those commands. FSUIPC does not send anything unless asked, so I am not sure where those are coming from at the moment.
John
-
Yes, looking at the code, that would seem to be needed. All the controls are sent on the first button push, even if there is a double push, so the second push is triggering the single push action when it should be ignored. In fact, without that additional line, the ignorepress variable is never set to true! I am not sure why this hasn't been picked-up before, but I will update the example script.
Thanks for reporting back,
John
-
Those presets (and executing the calculator code directly) seem to work ok here - the MFD ones control the range on the right-hand screen and the PFD ones control the range on the left screen.
-
I don't need to see a pic (which you didn't attach anyway!) but your FSUIPC7.log file. But what CTD'ed - FSUIPC7 or MSFS? If you check the FSUIPC7.log file first, you will probably see that FSUIPC7 exited as MSFS was no longer available (and maybe preceded by a couple of simconnect dispatch errors).
If it is MSFS crashing, then check the Asobo or PMDG support forums. Also check the windows event viewer for information - you may see a fault report for FSUIPC there, but this will be after a crash report for MSFS.
-
8 minutes ago, ark1320 said:
So I seem to have a timing issue that I need to figure out.
Use the lua plugin logging facility - that should tell you what is happening, and maybe also log Events...
John
-
1 hour ago, ZOUZAC-L said:
Unfortunately the method indicated does not change anything.
1/ I enter H:AS1000_MFD_RANGE_INC
2/ I click on Activate
3/ I enter HH:AS1000_MFD_RANGE_DEC
4/ I click on Activate5/ I click on Done
Is this the correct method?No! Sorry, you need to use the Add-ons->WASM->Execute Calculator Code.. option, and enter
(>H:AS1000_MFD_RANGE_INC)
to increase the range and
(>H:AS1000_MFD_RANGE_DEC)
to decrease the range. The Activate Hvar menu item is for hvars known to FSUIPC only (via *.hvar files). Sorry about that - I will correct my previous post...55 minutes ago, ZOUZAC-L said:I downloaded the WASM client v0.4.8
Launched and connected but no improvement.You don't need that - that is just a test client and everything that does you can do from the Add-ons->WASM menu.
As I said, I will take a look, probably tomorrow...
John
-
It is the debug log that will show you what is happening....
John
-
If assigning to FSUIPC's Throttle axis, you dont need to map to 4 throttles or use the individual throttle calibration page. You only need to calibrate that control on the first calibration page. So, remove the mapping and individual throttle calibration, and try just calibrating on the first page. Also, maybe check the calibration of the throttle in windows controllers. And make sure that you have not installed the saitek/logitek drivers or software - if so, uninstall and let windows install the default drivers.
If you continue to get issues when assigning 'Direct to FSUIPC Calibration', try with 'Send to FS as normal axis instead'. This will have various throttle axis controls - the "AXIS_THROTTLE_SET" controls go from idle to max only (idle at -16384, max at +16384), and the older FS98 controls (THROTTLEn_SET) provide a reverse range (for those the numerical throttle position for IDLE is always 0, max is 16384, and reverse is negative -- the max reverse depending on the AIRCRAFT.CFG parameter for reverse thrust percentage -- for example 25% would be -4096 (25% of -16384). FSUIPC calibrates to -4096 but auto-scales this according to the specific aircraft).
You also have the throttle mapped to 3 distinct axes on two different controllers:
Quote[Axes]
PollInterval=10
RangeRepeatRate=10
0=AS,1,D,4,0,0,0 -{ DIRECT: Throttle }-
1=AP,0,F,66416,0,0,0 -{ TO SIM: PAN_VIEW }-
2=CY,256,D,4,0,0,0 -{ DIRECT: Throttle }-
3=CZ,256,D,4,0,0,0 -{ DIRECT: Throttle }-You should only assign one axis - have multiple assignments to an axis can confuse things.
Your ini also showed now controllers/devices were connected, which is rather strange:
Quote[JoyNames]
AutoAssignLetters=Yes
A=SideWinder Precision 2 Joystick << MISSING JOYSTICK >>
A.GUID={E3204030-CAE3-11EA-8002-444553540000}
B=Alpha Flight Controls << MISSING JOYSTICK >>
B.GUID={AEB89220-CAE3-11EA-8001-444553540000}
C=Saitek Pro Flight Quadrant << MISSING JOYSTICK >>
C.GUID={EC637680-1B6D-11ED-8001-444553540000}
John
-
14 hours ago, ark1320 said:
I have been able to confirm the script is being called when I push the yoke button, but event.button() does not seem to be calling the function "buttonpress".
How have you confirmed this? Is it running from an [Auto] ot profile-specific [Auto.xxx] section?
14 hours ago, ark1320 said:-- ipc.control(66375) -- GPS/NAV toggle used just for testing if script is being called. This does work when the ipc.control code is enabled.
If the script is running and working correctly, that control must always be sent (when uncommented) as it is not within a function definition. If that is not being calles, then neither is the event.button(joy, btn, 1, "buttonpress") call.
Could you please activate debugging for Buttons & Keys and Lua Plugins, generate a log file where you load your aircraft and start the lua and then press the assigned button (joystick Y, button 0), and then exit. Then attach (not copy) your FSUIPC7.log, FSUIPC7.ini and lua script.
John
-
On 8/13/2022 at 6:53 PM, ZOUZAC-L said:
do i have to install the wasm client?
Yes, you have to install and enable the WASM module - which you seem to have done.
Are you using the default G1000 or the one from Working Title?
Your assignments look ok, so I am not sure why it isn't working. I will take a look and get back to you, but as the range presets just activate a hvar, could you try setting these manually to see if that works. Use the menu option Add-ons->WASM->Execute Calculator Code... and enter
(>H:AS1000_MFD_RANGE_INC)
to increase the range and
(>H:AS1000_MFD_RANGE_DEC)
to decrease the range, and let me know if those have any affect.John
-
On 8/13/2022 at 2:59 PM, Reynaldo Duarte said:
THE WINDOWS OPENS AND THEN CLOSES WITHOUT START THE PROGRAM
What window? Did you see a splash screen? Did you see any pop-up error message?
If not, try opening a command prompt window and start FSUIPC7 from the command line, and see if that gives an error message.On 8/13/2022 at 2:59 PM, Reynaldo Duarte said:YES I DID INSTALL THE REDISTRIBUTED VC++ IN MICROSFOT SITE
Every issue I have previously seen for FSUIPC7 not starting is due to the correct VC++ redisitributables not being installed. Did you install the combined Visual Studio 2015, 2017, 2019, and 2022 redistributable packages for both x64 and x86, and also manually uninstall any individual or combined VC++ redistibutables from those years if already installed before you installed the latest packages? If not, please do that.
Also please check the event viewer - of it is not starting, it must have crashed and there must be evidence of this somewhere...
And are you sure FSUIPC7 isn't tunning - when you start FSUIPC7, it should show a splash screen for a few seconds and then it will be iconised to your system tray, from where it can be opened. You can also use Alt+F which is the default hot key to open the FSUI{C7 main window.
John
-
First, try using the latest beta release which has the additional PMDG 737 offsets enabled (in case you need to use them), available here:
The presets in that version are available via a new checkbox - most (but not all) presets start with PMDG* so they should be easy to identify, otherwise you can use the search interface provided by the MobiFlight HubHob site: https://hubhop.mobiflight.com/presets/
There is also a FAQ entry on how to use the PMDG custom controls, which use the Rotor Brake control, although most of these should be available via presets which are easy to assign:
Note the SDK for the PMDG 737 has still not been published, but for the time being you van use the P3D NG3 header file, which i have attached.
John
-
1
-
-
Check the available presets for the G1000 - they will be listed as 'Preset:AS1000...' (in the current release), or you can use the HubHob site https://hubhop.mobiflight.com/presets/ which you can use to find a preset. There is also an event file for the MobiFlight G1000 events provided in a sub-folder called EventFiles, but these days it is easier to use presets.
-
11 hours ago, Reynaldo Duarte said:
I tried to reinstall vcruntime140.dll with no success at all.
What does this mean?
If you want my assistance in this matter, it would help if you could answer my questions and follow my instructions...
Did you try starting FSUIPC7 directly (by double-clicking the FSUIPC7.exe)? What do you see?
Have you re-installed the combined VC++ redistributables, as indicated in the README.txt (i.e. uninstall the ones currently installed and install the combined package available from Microsoft)? -
As Luke says, auto-save has always been an issue with PMDG aircraft, but it normally only causes a freeze for a few seconds (while the data is being saved). If it takes longer, it can be due to anti-virus/anti-malware software. Make sure the save-flight folder is excluded from such software (or just disable auto-save). The SDK save-flight function (which is what FSUIPC7 uses to save a flight) is also still not functioning correctly anyway, so its probably not worth using at the moment, although it does work sometimes, it is not yet 100% reliable.
John
-
I don't have this aircraft so cannot investigate, but maybe these other topics on the same issue can help:
John
-
Did you try starting FSUIPC7 directly (by double-clicking the FSUIPC7.exe)? Did you try re-installing the VC++ redistributables, as recommended? Did you trad the README.txt?
-
8 hours ago, chanchu81 said:
I solved this issue. please close this thread.
It is always helpful for others if you can give your solution. Also, you should always specify what aircraft you are using as problems/solutions can be very different depending upon the aircraft in question.
John
-
On 8/10/2022 at 10:27 PM, Moderate Chop said:
By default, when I open the Button & Switch Assignments dialog, or the Key Assignments dialog, the Profile Specific check box is NOT checked. Again, functionally this behaves as one would expect. I can assign buttons and keys that show up in FSUIPC.ini or, if I check the box, those assignments will show up in the aircraft profile. That seems logical, and gives one the flexibility to move between general and aircraft-specific assignments.
The Axis Assignments & Calibration dialog does not seem to provide this flexibility - once an axis is assigned using a profile, the ProfileSpecific check box is greyed out. This is not a big deal - if I'm going to assign axes for an aircraft I will (almost) always do it within a profile. Just curious if this was your design intent.
This is by design. General button and key assignments are inherited by all profiles, unless overwritten by that profile, so you can always assign a button or key press to the current profile or to the general profile. General axis assignments are not inherited by a profile, so only axis assignments in that profile apply. When you initially create a new profile, you are asked if you want to import the general axis assignments into that profile. Once the profile is created, and an aircraft is assigned to that profile, new axis assignments can only created in the aircraft profile.
John
PMDG 737 FSUIPC - Sending Hdg sel Switch event (Control)
in FSUIPC Client DLL for .NET
Posted
As Paul suggests, check that you have enabled SDK broadcasts in the 737_Options.ini file. If that is the case, I am not sure why the offset isn't populated correctly, but it may be because the offsets have changed and the PMDG SDK still hasn't been updated to reflect this. Note the SDK still hasn't been published and the last confirmation I got from PMDG was for release 3.0.25, so I have had no updates on any changes since that version (current version is 3.0.31.
John