John Dowson
-
Posts
13,254 -
Joined
-
Last visited
-
Days Won
270
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
6 hours ago, chasbruce said:
I tried setting x0B47 and x0B48 offsets to 1
The COM SPACING MODE simvar (held in offsets x0B47 and x0B48) report the spacing mode of the COM radios of the currently loaded aircraft, are read-only and cannot be changed. If they are set to 0, then the COM radios are 25khz (or the simvar/offsets are not being used/set).
Do you get 8.33KHz spacing when tuning the radios in the VC, or only 25KHz? If the latter, the only thing you can do is to try to switch out the radios for ones that support 8.33KHz spacing. If they do support 8.33KHz spacing, then it could be that those simvars/offsets are not being used. If that is the case, how are you controlling the frequency - are you using FSUIPC for this? If so, note that offsets 0x034E and 0x3118 are in BCD format and only support 4-digits (leading 1 assumed). To set 8.33KHz spacing, use offsets 0x05C4 and 0x05C8. If using controls/events to set the frequency, you need to use the *_HZ ones.
John
-
I can see the issue - the parameter is converted to an integer rather than a floating point value, so 0.5 is converted to 0. I will correct this.
I could provide you with a beta version, but I have discovered a very strange issue that I need to fix before I can provide any more updates. For some (unknown) reason, all builds since sometime mid-April have an issue with showing the 'Find Preset' panel, and pressing the 'Find Preset...' button causes FSUIPC7 to CTD. Its a very puzzling issue - no code change and even re-building existing released versions, where there was no issue, now suffer from this problem. It is very puzzling - and worrying....
John
-
Hmm, strange....I will take a look and get back to you....
Unfortunately I had a catastrophic crash on a windows (Insider) update last week and have had to re-install Windows, as well as MSFS, P3D, etc. As well as my development environment. No recent backup unfortunately either (the last one I had was from 2023!). So it may take a few days...
John
-
17 hours ago, Ray Lu said:
I guess my problem is I really don't understand how they are supposed to be programmed in Mobiflight.
This is support for FSUIPC, not Mobiflight - try MobiFlight support (on Discord).
John
-
18 hours ago, ose159 said:
Can i assign to that button a "mouse left click" (0x20000000) ? How to do it if possible ?
You can use a lua script to operate the mouse, but I would not recommend this. You would need to move the mouse cursor to the correct position before sending the click, and the position could change depending on the view. Note that the versions of FSUIPC for P3D and FSX had a mouse macro facility, for sending mouse clicks to specific 'mouse rectangles' defined in the aircraft. However, this facility is not available in FSUPC7 as MSFS does not support this.
18 hours ago, ose159 said:I did not find any preset to activate all of them at once but just the left, center, right but i have just a button available.
There are 3 different ways that you can achieve this:
1. Define your own preset to activate all of them (in the myevents.txt file) and use that. Just define the preset to send the calc code of each individual preset. I showed how to do this for the PMDG 777-300ER in another post:
Quote//PMDG/B777 300ER/Lights
PMDG_B777_Landing_Light_All_Off#(L:switch_22_a) if{ 2201 (>K:ROTOR_BRAKE) } (L:switch_23_a) if{ 2301 (>K:ROTOR_BRAKE) } (L:switch_24_a) if{ 2401 (>K:ROTOR_BRAKE) }
PMDG_B777_Landing_Light_All_On#(L:switch_22_a) ! if{ 2201 (>K:ROTOR_BRAKE) } (L:switch_23_a) ! if{ 2301 (>K:ROTOR_BRAKE) } (L:switch_24_a) ! if{ 2401 (>K:ROTOR_BRAKE) }
PMDG_B777_Landing_Light_All_Toggle#2201 (>K:ROTOR_BRAKE) 2301 (>K:ROTOR_BRAKE) 2401 (>K:ROTOR_BRAKE)
PMDG_B777_Runway_Turnoff_Light_All_Off#(L:switch_119_a) if{ 11901 (>K:ROTOR_BRAKE) } (L:switch_120_a) if{ 12001 (>K:ROTOR_BRAKE) }
PMDG_B777_Runway_Turnoff_Light_All_On#(L:switch_119_a) ! if{ 11901 (>K:ROTOR_BRAKE) } (L:switch_120_a) ! if{ 12001 (>K:ROTOR_BRAKE) }
PMDG_B777_Runway_Turnoff_Light_All_Toggle#11901 (>K:ROTOR_BRAKE) 12001 (>K:ROTOR_BRAKE)Not sure if they work in the 777-200. You can try them - or correct to use the 777-200 light presets if different.
2. Define a macro to send each light preset. Macros can be used to send multiple commands on a single button or key press - see the Advanced User guide for details un using macros.
3. Overload your assignments so that you have multiple preset assignments on the same button. To do this, assign the first preset. Then open the FSUIPC7.ini file and comment out the assignment (add a semi-colon after the '=' sign) and reload the assignments. Then assign the next preset. Then comment that one out. Repeat until you have all the assignments you require, then uncomment out the assignments previously commented out.
When doing this, make sure that you edit the FSUIPC7.ini file with the button assignments panel open, and click 'Reload all buttons' when you have saved the changes, to reload the file.John
-
Take a look at the offset mapping document for the PMDG 737 (Offset Mapping for PMDG 737NGX and 737NGXu.pdf) - note that you need to enable data broadcasts in the PMDG to have these offset populated. There is this offset (1-byte each, for each engine):
Quote65D5 2 BYTE x 2 ENG_StartValve[2] true: valve open or maybe this one:
Quote6463 2 BYTE x 2 FUEL_annunENG_VALVE_CLOSED[2] Boolean 12 hours ago, Geferson Alves said:I've configured the GRD, OFF, CONT, and FLT switch positions using PMDG Event IDs.
The current position of this switch is also held in offset 0x64FC:
Quote64FC 2 BYTE x 2 ENG_StartSelector[2] 0: GRD 1: OFF 2: CONT 3: FLT John
-
You dont have to buy again - all upgrades are free. You just need to download and install the latest version.
John
-
17 hours ago, jdriskell said:
What could be influencing the aircraft system to ignore the FSUIPC calibrated hrottles.
Not sure. There have been previous reports of loss of power in PMDG aircraft, but I think these were during climb (and I think for the 737). This issue was identified as being caused by either flaps or spoilers configuration/calibration in FSUIPC, which sometimes doesn't pay well with FSUIPC unless configured correctly. See
But as this only occurs with one variant, I doubt this is the issue.
Not sure what to advise. You could maybe try logging the throttle lever position offset, the auto-throttle arm offset and maybe the engine N1/N2 values to see if that reveals anything. You can also attach your FSUIPC7.ini file here and I will check it to see if anything stands out, but I can't think of anything in FSUIPC which would cause such issues.
John
-
You files still show you are using an old unsupported version of FSUIPC7. please download and install the latest and only supported version.
Your log file also shows that FSUIPC7 connected to MSFS. Sowhat exactly is your issue? If FSUIPC7 is not auto-starting, please see
John
-
15 hours ago, chpmerlin said:
Part of the codebase is heavily inspired by the FSUIPCUser64 C library distributed in the SDK, so this library may count as a derivative work - with this in mind, I wanted to obtain permission before publishing it. I was thinking of the MIT licence but am happy to discuss.
No problem - permission granted (well, not even needed really!).
You could also add it to the User Contribution section if you like, and/or I could include it in the FSUIPC SDK download. Let me know.
Regards,
John
-
1
-
-
Please use the FSUIPC7 support sub-forum for all issues/questions on FSUIPC7 with MSFS2020 and MSFS2024. I have moved your post.
5 hours ago, Russkay said:Just upgraded from Win 10 to Win 11 and having problems with FSUIPC .
Have been a paid user for many years and on Win 10 with MSFS2020 things were working perfectly.
Now with Win 11, cannot use MiniPanel, MSFSPopup panel. Attached my log from Win10
Why are you attaching an installation log from win10 if your issue is with win11?
That log file also shows you installed version 7.3.6. That is quite out of date - the latest version is 7.5.3. Please download and install that if you have not already. Only the latest vertsion is supported.
What exactly is your issue? The title says that FSUIPC is not connecting - if that is the case, then FSUIPC will do nothing. I do not know what a MiniPanel or a MSFSPopup panel is, or what they have to do with FSUIPC.
First, install the latest version of FSUIPC7. Run MSFS and let FSUIPC7 auto-start, and wait for MSFS to arrive at the main menu. Does FSUIPC7 connect?
If not, you probably need to manually tune the auto-start parameters - this is described in the Advanced User guide, and also in the following FAQ entry:You can also try exiting FSUIPC7 and then starting it manually - does it then connect?
Do you have assignments in FSUIPC? If so, your device GUIDs may have changed with the upgrade from windows 10 to 11, and your assignments may no longer be valid. If this is the case, please attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look.
John.
-
1 hour ago, kaha said:
Such a function would be very nice to have.
Ok, but this may take a while...I have other series issues I need to look into, besides rebuilding my PC, before I can look into any further changes to FSUIPC7.
John
-
3 minutes ago, kaha said:
Maybe there's a way to check if a specific input event is valid for the aircraft loaded?
No, but I could add such a function.
3 minutes ago, kaha said:The script does not end, so that's fine.
So there is no real issue - just ignore the message!
2 minutes ago, kaha said:Hmmm... I could read the .log file and parse the input events FSUIPC found.
Sounds like overkill - a lot of work for no real benefit.
-
@Reco I see you posted over on Avsim for the dodsim *.evt used in the P3D version. Does this also work in the FSX version?
If so, maybe you could attach it here for other dodsim users who come across this post.Cheers,
John
-
1 hour ago, kaha said:
I get errors logged if I send input events that are not subscribed. Here's an example:
646938 *** LUA Error: C:\FSUIPC7\l_kaha_lua.lua:706: Error sending Input Event 'AS530_COM_VLOC_Khz'
Does the lua continue or exit with that error?
1 hour ago, kaha said:Can I switch error logging off for this?
No.
1 hour ago, kaha said:Sometimes I send multipüle input events so it works for different aircraft.
Input Events, like lvars, are aircraft specific. However, input event names may be shared between aircraft (although they will be different Input Events, and maybe with different values.
1 hour ago, kaha said:Else I would need to have an if else construct which means I have to touch the Lua file for each new aircraft.
That is what you have to do... If you want to use the same script with multiple aircraft, different Input Events, then just check the aircraft name (offset 0x3D00) and then use/set the name of the appropriate Input Event to use. You can always have a default Input Event to use if the aircraft is not known by the lua script, but if that doesn't work then you would have to edit the lua to add another condition to set the Input Event name for the new aircraft.
Note I have had a severe crash on my development PC (after a Windows Insider Upgrade) and I currently have no access to the FSUIPC source or development environment. Therefore support will be limited for the next week or two while I rebuild my systems.
John
-
46 minutes ago, Dutch60 said:
5125 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B
5125 Failed on SimConnect_CallDispatch for Traffic Message, return = 0xC000014B
5578 MSFS no longer running - trying to find...These errors are due to the fact that MSFS has crashed and is no longer available.
As I keep telling you, there is nothing wrong with FSUIPC7. This needs to be fixed by Asobo.
-
You could maybe try removing the FSUIPC WASM from your community folder. You won't have access to lvars or presets, but that would test if its the WASM thats the issue, not FSUIPC7 itself. There was a report/comment on that link I posted that said this fixed the issue.
-
7 minutes ago, Dutch60 said:
so please take the time to fix it.
There is nothing wrong with FSUIPC and there is no fix, unless SimConnect is no longer backwards-compatible (which I very much doubt!). This needs to be fixed by Asobo.
This has happened on previously beta releases and is usually fixed in a subsequent beta update.
As I said, there is no way I can fix or investigate a sim CTD, only report this to Asobo.
-
...and are you sure this is related to FSUIPC7? i.e. does it run normally without FSUIPC7 running?
There are lots of reports of CTDs in this beta version - see https://forums.flightsimulator.com/t/ctd-loading-into-1-5-10-0/727551And I cannot investigate MSFS crashes - you need to report to Asobo.
Even if the SimConnect API has changed, it should be backwards-compatible, so I am confident, even if this issue is provoked by FSUIPC7, it is an issue for Asobo and must be fixed by them.John
-
As this is in the beta, you should wait for a fix in the beta. FSUIPC7 is an external app and in no way should it crash the FS.
Maybe check the Asobo beta forums to see if anything has been reported there regarding simconnect apps.
I have had a severe crash on my development PC during a windows update and cannot look into anything at the moment until I have repaired this.
John
-
As long as windows recognises the card as an HID joystick type device, and revognises the buttons, then FSUIPC will see them.
I have no direct experience with such cards, but many people use them with FSUIPC so I don't think it will be an issue.John
-
13 hours ago, DaveSCUSA said:
I can't find the discussion in the Advanced Users. Could you please provide a step-by-step or at least a page number.
Its in the Using Lvars section - see page 48, under Logging Lvar Updates.
John
-
5 hours ago, daniellljose said:
I have gone through the offset documentation..., but I am either missing something or not applying it correctly
For controls, you should start with the standard controls, not offsets. For example, the standard control for AP altitude hold would be the AP Alt Hold control (65726).
Note that the standard way to determine what control to use is for any button or switch to set logging for Events (Log->Events), open the logging console (Log->Open Console) and then toggle/set the switch in the virtual cockpit and see what is logged. If anything is logged, use that.Note that many MSFS aircraft continually emit certain events, and these are different for each aircraft. These can make using the log difficult, so best to ignore these by setting the DontLogThese ini parameter (see the Advanced User guide for details).
Many MSFS aircraft, especially third party/add-ons, do not use the standard controls/events. For such aircraft, check to see if an MF preset is available - you can use the search interface on the MF HubHop site: https://hubhop.mobiflight.com/presets/. All MF presets should be available for use in FSUIPC7.
Some aircraft also use their own custom controls (e.g. PMDG, FSLabs, etc). For such aircraft, check the documentation - and there is a FAQ entry on using custom controls with PMDG aircraft.If there are no standard events, presets or custom controls that work, you can look at the available lvars or preset events, or examine the switch/button behavior to see what it is using - see the following article: https://www.badcasserole.com/uncovering-input-events-using-the-msfs2020-model-behavior-dialog/
If you require any further help, please let me know the aircraft you are using.
John
-
Listing lvars shows the currently held value by FSUIPC, which is a max of 166ms or so out of date (using the default update rate of 6Hz).
There is already a facility to log lvar updates, either to the log or a separate ext window. This is done via an ini file section (at the moment) - see the Advanced User guide.
John
MSFS 2024 - LIVERY NAME offset
in FSUIPC7 MSFS
Posted
This was released in version 7.5.2, on 14th February. From the FSUIPC7 Offset status document:
Looks like I forgot to add this to the changes.txt and history document - sorry about that, I will correct this.
John