[FFB Flight Illusion]

Since the release of SU10 / SDK 0.9.3.0, there are issues with masking events for calibration purposes. I am still investigating these issues and will file a bug report with Asobo, but for the time being I have had to remove the ability to calibrate an axis if not assigned with 'Send direct to FSUIPC Calibration'. Therefore if you want to use FSUIPC's calibration facilities, you must assign in this manner.

Note you can still scale (and reverse) an axis assigned with 'Send to FS as normal axis', but such assigned axis will no longer be calibrated by FSUIPC.

John

[FSUIPC to make smaller incremental movements when using keyboard to control flight surfaces.]

24 minutes ago, PythonFlightSim said:

Just to double check, if I have it in the [Auto] section, I don't need to "bind" it through the menu as well on click or release? Or do I still need to keep the on click?

You only need that to restart the lua script if you change it, i.e. while tuning it. Once you have set it up to your liking, no need to restart it again so you can remove that assignment.

26 minutes ago, PythonFlightSim said:

Can I change the values in the lua script without have to restart MSFS, and just FSUIPC7 instead? Thanks again!

That is what your 'End' key assignment is for - to restart the script when you change it...

28 minutes ago, PythonFlightSim said:

I also don't understand why Num5 doesn't work when the rest do. Am guessing that maybe there is back end logic on their end to not allow centering in this fashion?

I don't understand this either - this is using the same controls that move the elevator/aileron/rudder, so if the other keys are working, so should this. Did you try in the C172 - it works in that aircraft here. 

32 minutes ago, PythonFlightSim said:

I am also seeing some weird behavior with the PMDG 738, whereby single clicks do not work anymore when I want to cross the center, so to speak. So if I am turning left, and click right until the point I should be able to start turning right, it only gets to center and stops. Wonder if this is related to the reversed axis comment from earlier. The only thing that works then, is to hold down the left or right rudder key, which then moves it too much. In general it seems the PMDG is a bit harder to control that the Twin Otter is, so I have some tuning work I need to do.

I can't see how any if this relates to reversers - that only affects thrust/throttle. Ground steering for airliners is done in combination with the steering tiller axis, and the rudder only takes affect as the speed increases. You could maybe use the '7' and '9' keys to control the steering tiller. There is also a new nosewheel steering control, but unfortunately this is not yet available for 3rd party apps as it isn't exposed by the SDK. I don't have the PMDG 738m but I have the 737-700 - I can take a look at this, but it will be over the weekend. I can also check the Num5/centering in this aircraft.

John

[FSUIPC to make smaller incremental movements when using keyboard to control flight surfaces.]

7 hours ago, PythonFlightSim said:

I think this was what I was meant to do, after clearing MSFS control assignments, and placing that lua script in FSUIPC7 folder.

No...that will start the script when you press the End key, and then kill it and start it again when you release. Remove the control sent on release - you don't need that. And you only need this to restart the script to reload the changes made when tuning. If always using the script, it should be started automatically using the FSUIPC7.ini [Auto] section.

7 hours ago, PythonFlightSim said:

The one thing that sadly did not work is centering with Num5, even if I kept it pressed. Test model was Aerosoft's Twin Otter.

That is strange as the other keys are working. Also no point keeping it pressed as the '5' key is only assigned to a press, and not a repeat press. Is anything centered (rudder, elevator or ailerons)? You can add trim centering as well if that is the issue. Maybe also check with a default aircraft, e.g. the C172.

John

[FSUIPC 7 connection with MSFS2020]

You need to provide more information - what aircraft? What switches? Can you show me your FSUIPC7.ini and FSUIPC7.log files, the latter generated with logging for Buttons & Keys and Events activated, load an aircraft, press one or two of your assigned switches (that are not working) and then exit FSUIPC7 before attaching the log file.

John

[FSUIPC7 Trial license - available here]

25 minutes ago, C.Schaffhausen said:

Hello John, any updates?

I will provide a new license later this evening or tomorrow.

[Calculator Code on Multiple Lines?]

No - the calculator code must all be on one line, currently up to a maximum of 1024 bytes. It is not possible to change this for various reasons.

John

[SkyDemon with FS9/GPSout in Windows 10]

Thanks for this, but it really belongs in the User Contributions sub-forum - I will move it for you.

Regards,

John

[New offsets for PMDG 737-800? (Recirc fans and FLT ALT / LAND ALT)]

59 minutes ago, OVD said:

sorry but this is already more complicated to me...

What is complicated? You just check the preset box in the button assignments panel and you wo;; see those presets and you can just assign to them to test....nothing complicated....

1 hour ago, OVD said:

As I know, event IDs are <custom control> option in FSUIPC. For P3D were 70504 and 69828.

Maybe, but that was P3D....the PMDG 737/738 for MSFS is quite different. It uses the Rotor Brake control for a start, and not custom controls. But if you have the PMDG header file you can calculate the Rotor Brake parameter to use - see the following FAQ entry: 

 

1 hour ago, OVD said:

The problem now is that 737-700 has one recirc fan switch and 737-800 has two (L and R). One event id of them would be 87201 as you told? And the other?

I really have no idea - I do not own the 737-800 and have never seen any documentation for this aircraft. You can try the P3D custom controls converted to Rotor Brake parameters, as that FAQ entry shows, or use the standard method of determining what control/parameter to use: Logging. Activate logging for Events, open the logging console (Log->Open Console) and then flip the switch in the virtual cockpit with the mouse. See what is logged, the control/event name (most probably Rotor Brake) and the parameter, and then try assigning to that.

 

[MSFS Asobo Daher TBM930 locks FSUIPC]

Ok, thanks for the update, but I really have no idea what can be causing this:

1 hour ago, VBV234 said:

After landing and switching off the engine the problem occurred again

Menus in FSUIPC not accessible en other windows programs did not react.

Back in the MSFS main menu everything worked again.

Reloaded the plane ... error occurred

Load another plan .... no problems.

The only time I have seen such issues is due to logging, i.e. so much is written to the log that it can prevent UI interaction (due to resource hogging). Other than that, I cannot see how this can occur. Except if there is a resource locking issue somewhere, but if that is the case I would expect this to occur and have been reported a lot more often (this is the first time I have heard of such issues!).

1 hour ago, VBV234 said:

After that I deleted the FSUIPC.ini and started all over.

I made most of the assignments for the TBM930 without any problem.

Throttle is assigned in the Honeycomb Bravo and works, but without animation in the cockpit.

Starting the engine according to the manual was also no problem

Finished the flight, switching off the engine is not going well. I have to look further in the assignments.

For me it is clear that continuing with this new ini is the easiest way.

I am convinced this way is less time consuming than debugging the old ini.

Ok, makes sense. You can use the old ini to see what the original assignments were and duplicate/copy as needed. Would be interesting to see if this issue occurs again, and if so what assignment/ini file change provoked this....

John

[New offsets for PMDG 737-800? (Recirc fans and FLT ALT / LAND ALT)]

12 minutes ago, OVD said:

Has somebody published Event IDs for PMDG 737-700 or 737-8000 in FS2020?

Yes - there are presets available for the 737-700 - the ones for the 737-800 are the same, see https://hubhop.mobiflight.com/presets/.
You should always use that site as the first point-of-call for such questions, as that is the THE community-driven resource for such things, led by MobiFlight.
For the recirc fans I find these:

which translate to:

    PMDG B737 Recirc Fan: 87201 (>K:ROTOR_BRAKE)
    PMDG_B737-7_PNEUMATIC_RECIRC_FAN_TOGGLE: 19601 (>K:ROTOR_BRAKE)
    PMDG_B737-7_PNEUMATIC_RECIRC_FAN_OFF: 100 (L:switch_196_73X, number) == if{ 19602 (>K:ROTOR_BRAKE) }
    PMDG_B737-7_PNEUMATIC_RECIRC_FAN_AUTO: 0 (L:switch_196_73X, number) == if{ 19601 (>K:ROTOR_BRAKE) }

The first two are simple Rotor Brake assignments, and the second the same but have an initial test on an lvar value before setting. You can either just use the presets, or assign to the Rotor Brake control with the required parameter. For the lvar checks, you can add the lvars to an offset and also check those, or maybe those values are already available in the PMDG offset area, I don't know... But easier just to assign to the presets.

John

[MSFS & Altitude issue on STD barometer]

First you need to find out what IVAO is using to determine the altitude. I suggest you try monitoring offsets 0x0574 (as S32) which is the Plane Altitude in meters, and also offset 0x0590 (also as S32) which is the Indicated Altitude Calibrated in feet.  First, monitor those offsets using FSUIPCs offset monitoring facilities to see if the indicated altitude is the one that you need.

If the latter is holding the correct value, then you can spoof offset 0x0574 to the value of offset 0x0590 converted to meters. I have attached a script that does this for you - to use it, save it to your FSUIPC7 installation folder and auto-start it by adding it to your [Auto] (or profile specific [Auto.xxx] section) as follows:

Quote

[Auto]
1=Lua calibratedAltitude

If IVAO is not getting the altitude from that offset, maybe ask them how it is getting the altitude...I cannot support IVAO, sorry. Maybe also raise a bug/request with IVAO to ask them  to use this calibrated value.

John

calibratedAltitude.lua

 

[FSUIPC to make smaller incremental movements when using keyboard to control flight surfaces.]

Please try the attached lua. Take a look at it and adjust the delta and delta increment (on repeat) values for each axis as you like.
To use, add it to the [Auto[ section of your FSUIPC7.ini., e.g.

Quote

[Auto]
1=Lua nmpadFltCntrls

I also suggest that to tune the script, assign a button or key to run the lua using the  Lua nmpadFltCntrls - then pressing that assigned button/key will kill the running lua and restart it, so you can test your changes.

One thing I noticed is that the axis values and simvar values for these controls seem to be negated/reversed, i.e. sending a positive axis value results in the relevant simvar taking a negative value and visa-versa., hence the script is changing the sign when reading the offset value.

Let me know how it works and if you have any issues.

John

nmpadFltCntrls.lua

P.S. Make sure you also delete the MSFS assignments to the numpad keys that you are using!

[ini file]

Your ini file is in the folder where you installed FSUIPC6. If you don't know where that is, use the 'Open Folder' button in FSUIPC's logging tab.

7 minutes ago, dragunov2020 said:

it should be in documents > prepare3d v5 addons > fsuipc6 

but now this location contains only add-on.xml file !

That should only contain that file, and is the location prescribed by P3D for 3rd party add-on.xml files. You can install FSUIPC6 there, but I recommend that you don't do this as it can cause issues (due to windows protection on the Documents folder).

John

[Set custom control in PMDG 738 ?]

Thanks for posting the solution. Note that there is also a preset available for this:  PMDG_B737-7_HGS_HUD_UP_DOWN_SWITCH

If you select the Preset check box, you can assign to this preset instead.

You mentioned this preset in your second post!

John

[FSUIPC to make smaller incremental movements when using keyboard to control flight surfaces.]

8 hours ago, PythonFlightSim said:

Do you think there would be lag with the lua script?

Maybe a small lag but shouldn't be that noticeable.

8 hours ago, PythonFlightSim said:

I just went in the game and tried trim, but it's too slow unfortunately.

Standard trim up/down controls can be quite slow, but you can assign to update the trim offsets and specify the increment required.

8 hours ago, PythonFlightSim said:

No worries if you don't have time to write the script

I'll take a look at some point, probably at   the weekend. Note also that you can also assign the keys directly to update the surface controls without using lua. The advantahe of using lua though would be that you could start with a small increment/decrement (delta) and then increase this delta value on key repeats (i.e. if you hold down the key).

John

[FSUIPC7 Restart Question]

1 hour ago, ark1320 said:

it seems the Lua scripts listed under [Auto] are not reloaded.

No they are not - they are only loaded om first aircraft load or on an aircraft change. When you start FSUIPC7 with MSFS running and an aircraft already loaded, lua autos will not be started.

1 hour ago, ark1320 said:

Is there a way to trigger the automatic restart of the [Auto] scripts without restarting the sim?

You would have to assign a button or key to start the lua script or scripts..

I will look into seeing if I can also start the lua [Auto] scripts in such situations.

John

[New offsets for PMDG 737-800? (Recirc fans and FLT ALT / LAND ALT)]

1 hour ago, OVD said:

The only pending think is the offsets for Recirc fans.

Check to see if there is an lvar that can be used. i.e. list them and see if any look applicable. If so, you can then add that lvar to a free user offset.

1 hour ago, OVD said:

Could you put the link to the pmdg subforum?

https://forum.pmdg.com/

Cheers,

John

[MSFS Asobo Daher TBM930 locks FSUIPC]

Sorry, missed this one:

2 hours ago, VBV234 said:

Throttle Daher TBM930  does not react on assigned axis of Honeycomb Bravo

The throttle in the TBM930 has always been problematic...I think the throttle is/was working, when assigned correctly, but the animation of the throttle in the VC was broken, i.e.  it works but no the animation. I believe there was a dux if using the TBM improvement mod, possibly in conjunction with an XML file update. However, I am not sure if the current status, with or without the mod. In fact, I can't use the mod anymore as most of the aircraft isn't visible any more when using this!

Here are the references to this issue when previously reported, although I am not sure how relevant they are since SU10, but worth reviewiing:

 

 

 

 

John

[New offsets for PMDG 737-800? (Recirc fans and FLT ALT / LAND ALT)]

3 minutes ago, OVD said:

After changing from PMDG 737-700 to 737-800 I have noted two issues in my overhead:

-FLT ALT and LAND ALT displays won´t work anymore (with offsets 656C and 6572, String type). Do you know if they have changed in 737-800?

-As 737-800 has two Recirc fan switches instead of one as in 737-700, I would need the corresponding offsets if you know.

Sorry, but I have no details on the SDK for the PMDG 737-800, and the SDK for the 737-700 has not even been published yet. I cannot look into the PMDG specific offsets until PMDG have published the SDK details.

Try asking on the PMDG support forum.

John

[MSFS Asobo Daher TBM930 locks FSUIPC]

10 minutes ago, VBV234 said:

Done as you suggested. Problem does not occur anymore.

It, then that indicates that something in your TBM profile is causing this issue.
I have just looked at your ini again and it is a bit of a mess....you have this a the top, that is not part of any section:

Quote

0=Saitek Pro Flight Rudder Pedals
0.GUID={FB245FC0-E5E4-11E9-8001-444553540000}
A=Saitek Pro Flight Rudder Pedals
A.GUID={FB245FC0-E5E4-11E9-8001-444553540000}
B=Pro Flight Cessna Trim Wheel
B.GUID={FB25E660-E5E4-11E9-8003-444553540000}
C=Saitek Pro Flight Yoke << MISSING JOYSTICK >>
C.GUID={FB260D70-E5E4-11E9-8006-444553540000}
D=Logitech RumblePad 2 USB
D.GUID={FB263480-E5E4-11E9-8008-444553540000}
E=Alpha Flight Controls
E.GUID={B7226050-FB11-11E9-8001-444553540000}
4=Alpha Flight Controls
4.GUID={B7226050-FB11-11E9-8001-444553540000}
F=Bravo Throttle Quadrant
F.GUID={FF705280-FAE8-11EB-8001-444553540000}
2=Bravo Throttle Quadrant
2.GUID={FF705280-FAE8-11EB-8001-444553540000}
3=Logitech RumblePad 2 USB
3.GUID={FB263480-E5E4-11E9-8008-444553540000}

That needs to be removed. This is the [JoyNames] section that is used, which indicates missing devices:

Quote

[JoyNames]
0=Saitek Pro Flight Rudder Pedals
0.GUID={FB245FC0-E5E4-11E9-8001-444553540000}
2=Bravo Throttle Quadrant
2.GUID={FF705280-FAE8-11EB-8001-444553540000}
4=Alpha Flight Controls
4.GUID={B7226050-FB11-11E9-8001-444553540000}
A=Saitek Pro Flight Rudder Pedals
A.GUID={FB245FC0-E5E4-11E9-8001-444553540000}
B=Bravo Throttle Quadrant
B.GUID={FF705280-FAE8-11EB-8001-444553540000}
C=Logitech RumblePad 2 USB
C.GUID={FB263480-E5E4-11E9-8008-444553540000}
D=Alpha Flight Controls
D.GUID={B7226050-FB11-11E9-8001-444553540000}

F=<< MISSING JOYSTICK >>
E=<< MISSING JOYSTICK >>
3=Logitech RumblePad 2 USB
3.GUID={FB263480-E5E4-11E9-8008-444553540000}
 

You still have many assignments to those missing devices, which presumably were previously your Homeycomb Alpha and Bravo.

I have tried to correct these issues for you in the attached ini, so could you please try this: FSUIPC7.ini

Note that there are still some axis duplications that can cause issues, so please review these:
1. Throttle an PropPitch axes assigned twice in Axes.TBM930 :

Quote

[Axes.TBM930]
RangeRepeatRate=10
0=AX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=AY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
2=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=BY,256,D,4,0,0,0    -{ DIRECT: Throttle }-
4=BZ,256,D,5,0,0,0    -{ DIRECT: PropPitch }-
5=BR,256,D,5,0,0,0    -{ DIRECT: PropPitch }-
6=BU,256,D,13,0,0,0    -{ DIRECT: Mixture1 }-
7=DX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
8=DY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
9=BX,256,D,4,0,0,0    -{ DIRECT: Throttle }-
 

2, Throttle1 axis assigned twice in [Axes.FBW 320 NEO]:

Quote

[Axes.FBW 320 NEO]
RangeRepeatRate=10
0=AX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=AY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
2=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=BX,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
4=BY,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
5=BR,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
6=DX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
7=DY,256,D,2,0,0,0    -{ DIRECT: Elevator }-

3. Throttle2 assigned twice in [Axes.CJ4]:

Quote

[Axes.CJ4]
RangeRepeatRate=10
0=AX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=AY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
2=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=BX,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
4=BY,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
5=BZ,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
6=BR,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
7=DX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
8=DY,256,D,2,0,0,0    -{ DIRECT: Elevator }-

4.  Rudder assigned twice in [Axes.Drone]:

Quote

[Axes.Drone]
RangeRepeatRate=10
0=AY,256,D,3,0,0,0    -{ DIRECT: Rudder }-
1=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
2=BY,256,D,4,0,0,0    -{ DIRECT: Throttle }-
3=DX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=DY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
 

So, download that and and review and correct those axes assignments mentioned above, if needed, and then try the updated ini.

John

[FSUIPC to make smaller incremental movements when using keyboard to control flight surfaces.]

Btw, maybe you just need to use the trim controls rather than the primary surface controls?

[PMDG NGX ANNUNCIATORS]

The PMDG data is just supplied as received from the aircraft, and I only have the information supplied in the SDK header file.  You should check that file for any further information, otherwise I suggest you redirect your question to the PMDG support forums, as it is they that supply this data.

Sorry I canny be of any further assistance with this.

John

[MSFS Asobo Daher TBM930 locks FSUIPC]

13 minutes ago, VBV234 said:

Don't spend to much time on it, I can reassign and copy back the PMDG 737-700

No need to do this....

First, your ini shows that you have two missing controllers:

Quote

F=<< MISSING JOYSTICK >>
E=<< MISSING JOYSTICK >>

There are no GUIDs associated with these, but you still have quite a few assignments those controllers - I suggest you clean-up your inii by removing them.

Restore the full ini and remove the TBM from its profile, i.e. change

Quote

[Profile.TBM930]
1=TBM 930 Asobo
2=TBM 930 01 Livery

to

Quote

[Profile.TBM930]
1=Not used

and see if you get the same issue.

Are you using a VRInsight device?

 

[Fenix A320 Bind switch to key]

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. Please take care to post in the correct forum for your issue.

I don't have the Fenix so it is difficult to advise, but first check to see if there are any controls logged when you do this in the VC - activate logging for Events, open the FSUIPC logging console window and flip the switch to see if anything is logged, and if so you can try assigning to that.
If nothing is logged, you can try listing the available lvars to see if any of them look appropriate, and if so see if the value of the lvar changes when you flip the switch. If so, you can try manually changing the lvar value to see if that has the same effect, and if so then you can assign to use that lvar either by adding to an FSUIPC offset, using a macro or defining a preset.

John

[FSUIPC to make smaller incremental movements when using keyboard to control flight surfaces.]

7 hours ago, PythonFlightSim said:

just bought FSUIPC 7 for MSFS, and would like to use it with the PMDG 738. Problem I am trying to solve with this addon is as follows:

You should really have tried with the trial license first to see if FSUIPC7 is suitable for your needs....

There are various things you can try  to achieve this. The first, an easiest, would be to assign your key presses to the *_UP, *_DOWN, *_LEFT, *_RIGHT controls, but this would probably just duplicate the movement that you see when assigning in MSFS.
For more refined control, you would need to write a lua script which would wait for your key press (using event.key) and in the handling function read the offset with the current value, most probably offset 0x0BBA for rudder, then adjust thus value with the required change and then write the value back to the same offset.

I am a bit busy at the moment but when I get time I can look inot providing you with a lua script that does this for the rudder to get you started. What keys are you planning to use?
Noe that if you have keys assigned in FSUIPC, you should remove any assignments to those keys in MSFS.

John