John Dowson

March 4

Can you attach your FSUIPC ini and log files, as well as your WideServer.log, WideClinet.log and WideClinent.ini.
That will ar least give me an idea of your set-up.

And please let me know how the avionics on the client PC is configured - are you using any other additional software? If you have not assigned/configured in WideClient / FSUIPC (and if ButtonScanInterval is set to 0) then these devices (whatever they are) must be assigned elsewhere, no?

i am confused as to why do you think this is related to WideClient / FSUIPC if your client controllers are not assigned in FSUIPC...

March 4

35 minutes ago, flyboy340 said:

When you turn the knob with a mouse you can see the LVAR go to 1 and straight back to zero. So in theory I thought a value of 1 would do it.

Yes, that sounds correct, as that lvar is documented as a BOOL. I have no idea why it isn't controlling the brightness. When you inc/dev the brightness in the VC, do you see the lvar change value (and reset)?

As I said earlier, you should ask on the InBuilds support forums as I do not have this a/c.

March 4

1 minute ago, 4dads said:

That "noise" is preventing me using thrust reverse and is coming in via WideFS from the Avionics PC,

The only way they can be coming from WideFS is if you have set it up to do this and have assigned in FSUIPC. If that is the case, remove the assignments.
Also, if you set ButtonScanInterval=0 in WideClient, it will not forward any button presses to FSUIPC, and so cannot possibly trigger anything there.

What hardware to you have attached to your avionics PC, and how/where are they assigned? If you have not assigned in FSUIPC, why do you think it is coming from there?
WideClient only talks to FSUIPC, not the FS.

March 4

2 minutes ago, flyboy340 said:

DU_MasterBright_Bright# (>L:INI_CKPT_LT_DU_MASTER_BRT_INC, bool) and nothing happens, so I will try setting 1

Yes, you will need to give it a value...probably also a good idea to use repeat when assigning to that preset as well.

March 4

8 minutes ago, Braudoux said:

In order to test my MIAP controller with FSUIPC, I shut down P3D and deleted the FSUIPC.ini file.

But why? Why not just do the correction I suggested?

9 minutes ago, Braudoux said:

After relaunching P3D, I opened the new FSUIPC file and noticed that the controller is not detected (not listed).

It was detected:

Quote

672 ---------------------- Joystick Device Scan -----------------------
687 Product= Saitek Pro Flight X-55 Rhino Stick
687 Manufacturer= Madcatz
687 Serial Number= G0001739
687 Vendor=0738, Product=2215 (Version 0.87)
687 GUIDs returned for product: VID_0738&PID_2215:
687 GUID= {E942D3A0-E721-11EB-8002-444553540000}
687 Details: Btns=17, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R4095,U0,V0,X65535,Y65535,Z0
687 GUID= {E9423760-E721-11EB-8001-444553540000}
687 Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
687 Product= MIAP STD
687 Manufacturer= AXAIR
687 Serial Number= HIDDC
687 Vendor=2354, Product=8049 (Version 1.0)
687 GUIDs returned for product: VID_2354&PID_8049:
687 GUID= {4981D2D0-E40F-11EC-8001-444553540000}
687 Details: Btns=38, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
687 Product= Saitek Pro Flight X-55 Rhino Throttle
687 Manufacturer= Madcatz
687 Serial Number= PP000503
687 Vendor=0738, Product=A215 (Version 0.119)
687 -------------------------------------------------------------------

However, it was not acquired as you now have registry issues:

Quote

703 WARNING: Joystick ID 0 is duplicated in Registry
703 WARNING: Joystick ID 1 is duplicated in Registry
703 Device acquired for use:
703 Joystick ID = 0 (Registry okay)
703 0=Saitek Pro Flight X-55 Rhino Stick
703 0.GUID={E942D3A0-E721-11EB-8002-444553540000}
703 Device acquired for use:
703 Joystick ID = 1 (Registry okay)
703 1=MIAP STD
703 1.GUID={E94396F0-E721-11EB-8004-444553540000}
703 Device acquired for use:
703 Joystick ID = 0 (Registry okay)
703 0=Saitek Pro Flight X-55 Rhino Throttle
703 0.GUID={E942D3A0-E721-11EB-8002-444553540000}
703 Device acquired for use:
703 Joystick ID = 1 (Registry okay)
703 1=Saitek Pro Flight X-55 Rhino Throttle
703 1.GUID={E94396F0-E721-11EB-8004-444553540000}
703 -------------------------------------------------------------------

Continually unplugging and changing USB ports can cause registry issues.
Please go back to your previous ini, make the changes I suggested and try again. If you still get issues, please attach your log and ini files again please, as well as the JoyScan.csv file.

14 minutes ago, Braudoux said:

Is it possible that the bindings set in P3D are preventing FSUIPC to detect the MIAP controller?

No, it is due to registry issues. If assi9gning in FSUIPC, we recommend that you disable controllers completely in P3D. If you don't do this, please make sure that you don't have dual assignments, i.e. an axis or button/switch assigned in both FSUIPC and P3D. Also, P3D has a tendency to auto-detect your controllers (if not disabled) and then make default assignments, which can cause issues if already assigned in FSUIPC.

John

March 4

So it looks like those lvars are acting like a control/event - you set it to 1, this triggers the brightness increase or decrease and then the lvar gets reset back to 0. If you want to inc / dec again, you can set it to 1 again. Does it not work like that? If not, ask on the Inbuilds forums on how those lvars are supposed to work. I don't have this aircraft so cannot take a look here, sorry.

John

March 4

34 minutes ago, 4dads said:

Has been done, still the same issue, repeating within the log when the Avionics PC is sending data is.

   250953 *** EVENT: Cntrl= 66040 (0x000101f8), Param= 16208 (0x00003f50) KOHLSMAN_SET
   250953 *** EVENT: Cntrl= 66488 (0x000103b8), Param= 1 (0x00000001) ANTI_ICE_SET_ENG1
   250953 *** EVENT: Cntrl= 66489 (0x000103b9), Param= 1 (0x00000001) ANTI_ICE_SET_ENG2
   250953 *** EVENT: Cntrl= 66337 (0x00010321), Param= 0 (0x00000000) TOGGLE_STRUCTURAL_DEICE
   250953 *** EVENT: Cntrl= 66040 (0x000101f8), Param1= 16211 (0x00003f53), Param2= 0 (0x00000000) KOHLSMAN_SET

Those are just events that are being logged....FSUIPC logs ALL events applied to the FS. Why do you think that those are coming from FSUIPC or WideClient?
If you have no assignments in FSUIPC / WideFS, they won't be coming from there... Try setting logging for Buttons & Switches - that will log any button press that is triggering an assignment. If those events are being sent from your device and you don't want them to be sent, remove whatever you are using that is sending them.

Note that many aircraft in MSFS continually emit certain events, and these event are different for each aircraft. These events are just noise really, and you can prevent them being logged using the DontLogThese ini parameter.

35 minutes ago, 4dads said:

Last thing before going to bed, would a IgnoreDevice work on those?

No, as they are most probably not coming from FSUIPC or WideFS. FSUIPC is just logging them, not sending them.

March 4

You can try setting
ButtonScanInterval=0

From the WideFS User guide:

Quote

With a user-registered FSUIPC3 or 4 all Windows, EPIC and GoFlight buttons will be recognised on Client PCs and transmitted to FSUIPC for programming unless this action is explicitly turned off in the Client.

This action is automatic. You need do nothing to enable it—except, for GoFlight only, installing the Gfdev.dll as mentioned in the WideClient installation instructions earlier. For WideClient there is only one controlling parameter:

ButtonScanInterval=20

This parameter, in the [Config] section of the WideClient.ini file, controls the rate at which WideClient scans EPIC and Windows joystick buttons. GoFlight buttons are not scanned by WideClient—those are dealt with by the Gfdev.dll. However the parameter is still relevant since if you set this to 0 (zero), it switches the whole facility off.

March 4

1 hour ago, Alhard Horstmann said:

for $7b93 was not successful.

All offsets in the documentation start with 0x and not $. But also only the starting offset is documented (together with the size), so rather than searching for a specific offset, just scroll down to you find the entry that documents the range for the offset you are interested in.

1 hour ago, Alhard Horstmann said:

Now I have to find a doc of Joel DeYoung 😎

Yes - almost all the offsets that have been allocated to 3rd party software use was done many years ago, before my time, and I have no idea what these offsets are used for in most cases!

Cheers,

John

March 4

Note that I also need to see the WideServer.log files for issues with WideFS...

However, it should be obvious why it didn't connect the first time you ran FSUIPC7 if you look at your log file:

Quote

...
453 Auto-started via EXE.xml with DetectToConnectDelayAuto=30, InitialStallTime=15
3297 Simulator detected
3297 Run: "C:\Users\xxxx\AppData\Local\vPilot\vPilot.exe -host"
3438 Run: "C:\Program Files\SPAD.neXt\SPAD.neXt.exe"
33891 Trying to connect...
48891 **** SimConnect open event not received in required time limit: Re-connecting now...
49109 Trying to connect...
64109 **** SimConnect open event not received in required time limit: Re-connecting now...
64328 Trying to connect...
85219 Failed on SimConnect_Open for AI Traffic Client, return = 0x80004005
324250 === Hot key unregistered
...

FSUIPC7 never connected to MSFS and the WideServer was never started. Note that, by default, WideServer is not started until FSUIPC7 is connected and you have an aircraft loaded and ready-to-fly.

The first thing you need to do is to delay the start of SPAD,next and vPilot until at lease FSUIPC is connected top the FS (i.e. add the CONNECTED keyword). vPilot could be started even later, using the READY keyword.

Once that is corrected, try again and take a look at your log file. If you see the following message:
48891 **** SimConnect open event not received in required time limit: Re-connecting now...
then you should adjust the DetectToConnectDelayAuto ini parameter. Please see the section Auto-tuning of initial start-up ini parameters in the Advanced User guide, or the following FAQ entry:

John

March 4

Was this ever working then?

On 3/2/2025 at 9:15 PM, CXA007 said:

So I take it KeySend must be pushing commands to a virtual keyboard or something.

Keysend works via windows messages.

How are you starting the Discord PTT program? Have you tried directing the keypress to the Discord PTT program? If not, see the WideFS Technical guide from section Directing Key Strokes more precisely and onwards,

John

March 4

On 3/2/2025 at 9:06 AM, Braudoux said:

I'd like to add that, for testing purpose, I have deleted the FSUIPC6.ini file and restarted P3D. expecting that a new .ini file would be created but nothing happened.

Well, it cannot create the ini file if it isn't running.

P3D starts FSUIPC from either the DLL.xml file or the Documents\Prepar3d v? Add-ons\FSUIPC6\add-on.xml file (depending on P3D version and maybe the components selected during installation), which are either modified or created when you install and has absolutely nothing at all to do with your ini file.
Check you InstallFSUIPC6.log file for details.

Changing the ini file can in no way affect the starting of FSUIPC6, so you must have also done something else. You can always try re-installing FSUIPC6 to see if that helps, and if not then show me / attach your InstallFSUIPC6.log file.

John

March 4

On 3/2/2025 at 3:40 PM, shorthauler said:

Is it 5.1 as in the LuaFileSystem document?

Yes - its 5.1.4.

March 4

On 3/3/2025 at 1:36 AM, Jim Anslow said:

Received a pop-up notice during startup that there was a new version of FSUIPC (7.5.2e) available

7.5.2e is a beta version, and you should not have received any notification for this as only official releases will prompt a message to download,

On 3/3/2025 at 1:36 AM, Jim Anslow said:

with the exception of the installation folder, which I relocated just as I had done previously.

When you re-install, it is far easier to just install into the same folder. This will then just replace the installed files and leave all other files (e.g. settings, key, lua sctipts, macros, dlls, etc).

On 3/3/2025 at 1:36 AM, Jim Anslow said:

Now, when I start MSFS202, I am once again getting the notice that there is a new version (7.5.2e) available, and do I want to download it, even though I have the newer version installed. Have I missed something?

7.5.2 is the latest official release, and it should say that 7.5.2 is available, and not 7.5.2e. If you are using 7.5.2e, then you are using the last beta of 7.5.2. You should ypdate to the latest official release (hence the message), although there will be no actual difference in the versions (7.5.2e was the last beta and was released as 7.5.2).

Please also use the FSUIPC7 support sub-forum for all issues/questions with FSUIPC7, and not the main support forum. I have moved your post.

John

March 4

On 3/2/2025 at 8:11 PM, Alhard Horstmann said:

Again a question for Offsets: in my Opencockpit script "xpder_2enc.txt" ther is a line "Var 0133, Link FSUIPC_OUT, Offset $7b93, Length 4 // IDT button for Squawkbox "

Again, all information on offsets is in the FSUIPC7 Offset Status document - why don't you look at that?

I provide extensive documentation so that I do not have to spen all day responding to such questions. Please ALWAYS consult the documentation (as well as checking these forums) before posting questions.

March 4

No hay ningún problema con su licencia:

Quote

Checking the Registrations now ...
User Name="Rafael Raya_de_la_Mora"
User Addr="rayadelamora@msn.com"
FSUIPC7 Key is provided

Consulte la documentación - Installation and Regisuration guide.

Los problemas de validación siempre se deben a:
- introducir los datos incorrectos
- no tener instalados los redistribuibles de VC++ correctos
- problemas con el antivirus
Todo esto se explica en la documentación, aunque solo está disponible en inglés.

March 1

20 hours ago, Vovdv said:

Macros]

1=GEAR UP OFF

1.1=PMDG_B737-7_GEAR_UP,0

1.2=C1152,8000

1.3=PMDG_B737-7_GEAR_OFF,0

Does that even work? Should be:

Quote

Macros]
1=GEAR UP OFF
1.1=P:PMDG_B737-7_GEAR_UP,0
1.2=C1152,8000
1.3=P:PMDG_B737-7_GEAR_OFF,0

i.e. presets names should be preceded by 'P:'.

20 hours ago, Vovdv said:

Why can't I use another command while the macro for PMDG 737-800 is running?

Macros are ran in the main thread, and will block that thread until it has finished. If a macro is going to take more than a few hundred ms to complete (and you have an 8 second delay there!), you should use a lua script instead. Lua scripts are ram om separate threads.

John

March 1

52 minutes ago, CXA007 said:

This morning everything worked fine first try 🤷‍♂️... Possibly the 24H2 update hadn't finished installing well I was trying to correct the issue..

👍

March 1

Ah - maybe these are 'scoped' local variables?
See https://devsupport.flightsimulator.com/t/how-to-access-scoped-lvars-l-with-simconnect/12540/20

March 1

This issue is continually getting reported, and my answer is always the same. Please see one of the other many posts on exactly the same issue:

...etc

Basically read the documentation and follow the advise there, and also check out the many posts on exactly the same issue.

March 1

6 hours ago, Braudoux said:

While checking the FSUIPC6.ini file, I noticed that there are twice the same reference and I suspect that it is the origin of the problem. Could you confirm?

[JoyNames]
AutoAssignLetters=Yes
A=Saitek Pro Flight X-55 Rhino Throttle
A.GUID={E94396F0-E721-11EB-8004-444553540000}
E=Saitek Pro Flight X-55 Rhino Stick
E.GUID={E942D3A0-E721-11EB-8002-444553540000}
B=MIAP STD
B.GUID={4981D2D0-E40F-11EC-8001-444553540000}
C=MIAP STD
C.GUID={E942D3A0-E721-11EB-8002-444553540000}
D=Saitek Pro Flight X-55 Rhino Stick
D.GUID={E9436FE0-E721-11EB-8003-444553540000}

So it looks like the GUIDs have changed, not only for that device but also for your Saitek Pro Flight X-55 Rhino Stick, which now has two device letters D and E.

If the GUID if your MIAP STD is now that in the C entry, but your assignments are referencing B, then switch the GUIDs and remove the C entry, ie.

Quote

JoyNames]
AutoAssignLetters=Yes
A=Saitek Pro Flight X-55 Rhino Throttle
A.GUID={E94396F0-E721-11EB-8004-444553540000}
E=Saitek Pro Flight X-55 Rhino Stick
E.GUID={E942D3A0-E721-11EB-8002-444553540000}
B=MIAP STD
B.GUID={E942D3A0-E721-11EB-8002-444553540000}
D=Saitek Pro Flight X-55 Rhino Stick
D.GUID={E9436FE0-E721-11EB-8003-444553540000}

You should also do similar for your Saitek Pro Flight X-55 Rhino Stick.

Also, please attach the full ini file next time rather than posting extracts, and also attach your FSUIPC7.log file for any further issues.

John

February 28

1 hour ago, Alhard Horstmann said:

Q: what is Offset $5428 ??

From the FSUIPC7 Offset status document - 3584 bytes starting at offset 0x5200:

Quote

Reserved:
  5200-527F = Ferry van Aesch (Asst CEO British Airways Virtual)
  5280- 52FF: Andrew McLean: Aerosoft Hardware
  5300-53FF: Mark Hastings B777 Systems Simulator
  5400-5FFF: Enrico's Project Magenta

i.e. Offset 0x5428 is in an offset area that has been allocated to Project Magenta, and you need to look at the PM documentation or ask them what that offset is used for.

John

February 28

1 hour ago, eziocin said:

I run Widefs Client on the networked laptop, but it hangs with the message "Waiting for a connection".

It is not actually hanging is it, its just waiting for a connection, no? Does it connect automatically when you restart FSUIPC, or do you have to also restart the WideClient?

Can you please show me / attach your FSUIPC7.log and WideServer.log files, both from when it initially fails to connect (and after you have exited FSUIPC7) and also from after when you restart it and it connects.

February 28

You should sort out the disconnection issues shown on your log.

On 2/27/2025 at 9:37 PM, intper said:

all i want is a previous version if its possible, i just want to compare it with new version

There are no changes from any version that cause performance issues - your problem lies elsewhere.
You can try an older version if you like (not that this will help!) - current/latest version is:
https://fsuipc.com/download/Install_FSUIPC7.5.2.zip
previous version:
https://fsuipc.com/download/Install_FSUIPC7.5.1.zip

older versions:
  https://fsuipc.com/download/Install_FSUIPC7.5.0.zip
  https://fsuipc.com/download/Install_FSUIPC7.4.17.zip
  https://fsuipc.com/download/Install_FSUIPC7.4.15.zip

etc.

February 28

It doesn't make sense to allow this in FSUIPC due to the way calibration works in FSUIPC. FSUIPC calibrates to an FS control, and as there is no specific control/event when assigning to a preset, it does not know the range to calibrate to. Max/min/scaling etc can easily be handled, either in the RPN itself. or you can just write the axis value to an offset and do whatever you want with it before using it in a preset.

Profiles

Forums

Events

Gallery

Downloads

Posts posted by John Dowson

Important Information