[Adjusting trim button speed]

@RISCfuture You can also find detailed instructions in this post: 

 

John

[Can't find the command for Cabin Flashlight.]

27 minutes ago, GPan099 said:

The catering call is not available in the controls menu to change the assignment from requiring the ALT key. I thought I was able to assign it before (I think using FSUIPC 7) but I could be wrong. Zero programming knowledge/experience here!

Ok. Then please wait for the next release - I will add back in the use of the ALT modifier key. I'll post again here when I have a release for you to test.

John

[Can't find the command for Cabin Flashlight.]

The next SDK update has some corrections (and updated documentation) on the MSFS key input events, so I will revise FSUIPC7's key handling when this is released. I'll see if I can also add back in the ALT key modifier so that the default MSFS key assignments can be used.

[Can't find the command for Cabin Flashlight.]

5 minutes ago, GPan099 said:

Does anyone know if there is a way to change keypress assignments through a text or similiar file rather than the controls menu?

Sorry, what does this mean? Are you talking about assignments in FSUIPC7 or MSFS? If the former, all your assignments are stored in your FSUIPV7.omo file. For the latter, I presume that MSFS assignments are stored in a config file somewhere, although I don't know where. I wouldn't ascise changing this file manully though.

8 minutes ago, GPan099 said:

I am trying to change the catering key command ALT+c, but that function is not listed in the Controls menu, even though it works in the sim.

There are many assignments that you can make in the sim but for which no events/controls are available via simconnect, upon which FSUIPC7 relies. If there is no control that suits your needs, you will have to do as advised above for the cabin lights, i.e. assign a different keypress to the Alt+C function (not using ALT modifier) in MSFS and then assign your button/switch to that keypress in FSUIPC7.

Alternatively, if you are looking for a control to open the catering doors, you could try using the control TOGGLE_AIRCRAFT_EXIT_FAST to se if there is a parameter that works for that control for the catering doors.

 

[Installing and registering FSUIPC7 and WideFS7]

On 11/5/2020 at 5:47 PM, Marcos said:

I also completed the steps you suggested for improving the trim wheel sensitivity. However, I must have done something wrong as I did not notice any change.

I checked this in the C208 and it works as expected, although i found that I had to use an increment/decrement value of around 500.
You should really try this again as it would be a better solution to overloading your button presses. If you have any issues, let me know which aircraft you are using and I'll take a look.

John

[Additional axes request]

@f-111sim Hi Rod,

sorry for the delay, there were a few added complications...

Please try the attached dll. I've cleaned-up the recognition of axes controls and added several new axis controls, including the ones you requested.
The axes are functioning in that they are being sent to the FS, although I cannot confirm if working correctly or not as I'm not sure what those axes are supposed to do...!

Please let me know if this is working for you. I have a few other updates (mainly documentation) to add and once done I'll release this version officially.

John

FSUIPC6.dll

[Can't find the command for Cabin Flashlight.]

The standard way would be to use the Toggle Cabin Lights control (or toggle bit 9 in offset 0D0C). However, this event/control doesn't seem to be working at the moment.
The default ALT-L key press uses the TOGGLE FLASHLIGHT control which isn't available via simconnect, and you can't send this key press combination as the ALT modifier is not supported in SimConnect.

Therefore, to assign this to a button or switch in FSUIPC, you would have to assign another known keypress (without using the ALT modifier) within MSFS to TOGGLE FLASHLIGHT, and then assign your button/switch to that keypress in FSUIPC.

 

[P3D v5.1 GS Capture Fail]

On 11/21/2020 at 5:54 PM, peterk54 said:

However when we engaged thru mouse click on the panel button APP it works fine.

Maybe you can check what event this is using (by activating logging for events (non-axis controls)), and compare to that produced by v5 or v4, as well as comparing to what occurs when you try this through your software.

From what you are saying, it does seem like a change in 5.1.

I'm surprised you are using the ' FSX 747-400, original panel' - did you copy this across from FSX and install into P3D?
I have FSX-SE still installed somewhere, I can try adding that to my P3D installations (now only 4.5 & 5.1 though) to see if something has changed, but this would take me a while.
I probably won't have time to do this for a few weeks with my current backlog, so may be better if you can investigate this and report back for the time being.

John

 

[MSFS 2020 G1000 G58 check "Current State" of displayed VOR on HSI]

On 11/22/2020 at 10:05 AM, xdefiantx said:

Is there any way I can extract the current displayed VOR with FSUIPC to cross reference the action?

Have you tried looking at the NAV1/2 flags in 0C4B / 0C5B to see which is active? Maybe in combination with the localiser/VOR flag in 0C4D / 0C70....

[FSUIPC is crashing]

Btw, are you using GeForce Experence? If so, try de-activating the in-game overlay.

Or if you are using MSI Afterburner or RivaRuner, try disabling those.

[Controls Not Recognized]

Just checked you logs and ini and they look good - no more registry issues or warnings, so it looks good to me. And all is detected correctly in your Joyscan.csv file.

Let me know if you get any further issues.

[FSX SE, FS labs A320 with TCA thrust quadrant interface]

I think the FSLabs Axxx series of aircraft have re-purposed the rotor brake control with various parameters for different functions. There is plenty of information on how to use these aircraft with FSUIPC over on the fslabs forums.

["key press" issue]

14 hours ago, cchiozza said:

When trying to assign a key press FSUIPC7 keeps defaulting to a button and will not let me assign another button

This is usually due to a faulty button that keeps firing. You can ignore this in the assignments panel by using the IgnoreThese ini parameter in your [Buttons] section - from the Advanced User manual:

 

Quote

IgnoreThese: This can be used to list a number of buttons which are to be ignored by FSUIPC in the Buttons &
Switches tab. This is to deal with faulty button signals which are repeating without control and thus preventing the
others from being registered on the screen ready to program. The parameter takes this form:
IgnoreThese= j.b, j.b, ...
listing the joystick number (j) and button number (b) of each button to be ignored. To make it easy, you can edit the INI
file whilst in the Button assignments dialogue and simply press “reload all buttons” to activate the changes.
Note that the action of ignoring buttons only applies in the button assignments dialogue—if they are already assigned
the assignment will still be effective.
You can also use the wild card '*' for the button number, in which case all buttons will be ignored. This is for
convenience only, and when used this line in your ini will be re-written to contain the complete button list (numbers 0-
39).
This parameter can also be used in the [Axes] section of the FSUIPC7.INI, using the axes letter instead of the button
number (see later).
 

 

[Controls Not Recognized]

Sorry, but do you have any issues? What am I looking for? 
 

[fsuipc hold pitch 'vibrates']

Is this aircraft specific or a  problem with multiple aircraft? If specific, which airplane are you using?

Also maybe try logging both events and axis controls (also open console to see the log messages in real-time) to see what axes movements are logged when this occurs.

   

[FSUIPC is crashing]

6 hours ago, Guissop said:

Have I to try to exclude  the FSUIPC installation folder from the Antivirus protection?

No, I don't think that is an issue.

On 11/21/2020 at 6:47 PM, Guissop said:

I install it as admin

You shouldn't do this really. No admin privileges are needed by FSUIPC7 or the installer. If any privileges are required then you will be prompted to authorise anyway.

I will investigate that error nest week and get back to you. However, i've a feeling that it maybe due to one of your devices or  device drivers. Check your connections and any usb hubs, make sure power management is disabled on all your hubs, and that all your drivers are up to date.

   

[FSUIPC is crashing]

Why are you using DirectAxesToCalibs:

Quote

219 N.B. "DirectAxesToCalibs" is enabled!

Try disabling that by removing the line from your FSUIPC7.ini], although using this this shouldn't cause any issues. 

Can you a check if you have an event logged in the windows event viewer when FSUIPC crashes, and if there is an entry please post the details.

If you disable WideServer, do you still get crashes?

 

[Windows MSFS FSUIPC7 XBOX]

1 hour ago, granathg said:

While investigating this, I read on the Dowson site that PC MSFS is supported but XBOX MSFS is not.  I'm using Windows 10 on a desktop, nothing to do with an XBOX. Please clarify what XBOX MSFS means.

It means that FSUIPC7 will not work when MSFS is running on an xbox console. It only works with MSFS running on a windows 10 pc.
MSFS, like many games,  runs on both xbox consoles and in a PC running windowa 10. If you are using MSFS on a pc then you are fine.

[Mcro - issue]

9 hours ago, Oscar Speer said:

Hi! When I delete all mouse macros the FSL A321 software works normal. I have two macro files and each files contains 10 commands=20 commands. When I increase the commands in the mcro files the sim starts to lose FPS and I have to restart P3D

You initially reported that your FPS dropped when you try to create a mouse macro. Now you seem to be saying that your FPS is dropping when you have more than a total of 20 commands in your mcro files (presumably you are still talking about mouse macros, no?)? This just doesn't make sense. Mcro files don't do anything, and a macro itself only takes effect once invoked.

As Pete says, you need to clarify what your actual issue is and provided further information.

[Additional axes request]

Hi Rod,

10 hours ago, f-111sim said:

Are you able to assist me?

Yes, I should be able to add them so that they can be assigned, but only as 'Send to FS as normal axis'.  There will be no calibration or offset area for these axes.
These must be newer controls that aren't yet flagged in FSUIPC as axes controls.

I'll look at this in the coming days and post an updated version of FSUIPC6 for you to try/test.

John

[Conditional Axis Sensitivity?]

@ark1320, @pilotjohn I've added this feature in the attached build. To use, you must specify the offset (starting with 'x' not '0x') as the MaxSteerSpeed ini parameter, i.e.
    MaxSteerSpeed=x66C0
The offset should hold (and is read as) a signed word (2 byte) integer. The maxSteerSpeed will be updated on every change of this user defined offset, so you can have a profile-specific auto-started lua to set this for your profile, or a long running lua monitoring the aircraft name (or stall speed) and updating the value when this changes.

I've not had time to do too much testing so please report back once tried.

John

P.S. Changes to the MaxSteerSpeed are logged when Extras logging is activated.

 

FSUIPC7.exe

[FSUIPC7/LUA and SimConnect indexed variable]

13 hours ago, Pliskin said:

The issue regarding the AP Altitude on A320 is here

Ok. That has been reported to Asobo.

13 hours ago, Pliskin said:

In fact, the A320 FCU altitude 7-segment display is mapped to [AUTOPILOT ALTITUDE LOCK VAR:3] and not to [AUTOPILOT ALTITUDE LOCK VAR]

Ok. I can add  [AUTOPILOT ALTITUDE LOCK VAR:3] if required. What about  [AUTOPILOT ALTITUDE LOCK VAR:2] ?

13 hours ago, Pliskin said:

Is it not too "dirty" to add "official" offsets just for this plane ? I mean, this is not a bug from FSUIPC. The issue is on the A320 by design (and I think there is a legit reason for Asobo to have implemented things like this).

Its not an issue to add new offsets which can then be used for specific aircraft. However, I can't change the behavior of existing offsets if they are still functioning for other aircraft.

13 hours ago, Pliskin said:

Perhaps a better solution would be to add new functions to the lua API in order to allow it to query SimVar by their name directly.
Or better, perhaps FSUIPC could give us the possibilitity to publish our own custom offset by providing the name of the SimVar (and mandatory parameters).
The case of the battery push button requires a macro, because it depends on 2 SimVars.

I don't like the idea of allowing any simvar to be requested via lua - it would be very problematic. Its far clearer to identify any needed simvar and add it to the offset area.

16 hours ago, Pliskin said:

Regarding the Local SimVar, I understand that FSUIPC7 has no way to access them. And in fact, Microsoft SimConnect SDK does not provide a way to do this.
The only workaround for now is to create a fake gauge and put the local SimVar in the Client Data Area. Then FSUIPC7 would be able to read/write the Local SimVar through the SimConnect SDK.

The long term plan is to provided access to lvars via an internal WASM module, and have an inter-process communication mechanism between the WASM module and the FSUIPC7 application. Whether this i done via a SimConnect client data area or using standard windows communication protocols is still to be decided, and depends on what facilities are provided on the WASM side.  This is one of the larger development areas still to be addressed.

John

 

[MFS 2020 dvd]

12 hours ago, CHUICK said:

¿Cómo se puede añadir Fsuipc a MFS 2020 en su versión física DVD, ya que no puedo encontrar el ejecutable en mi PC.

La instalación de FSUIPC7 es independiente de la instalación de MSFS. La única dependencia de la instalación de MSFS es el 'Desktop shortcut'  (que inicia MSFS junto con FSUIPC7). Si no tiene MSFS instalado en su PC, no lo instale desmarcando la casilla de verificación en la página final del procedimiento de instalación.

[MSFS Start up]

14 hours ago, imperial321 said:

All was fine on close yesterday...start up today and this...what on earth has changed...

Sorry, I have no idea. Something must have changed. All the link/batch file does is start MSFS and then start FSUIPC7 after a short delay.
What happens when you start MSFS directly (using the MSFS provided shortcut or start menu entry)?

[Multiple key presses not registering]

@johnk515 Yes, that is what that lua script does. Try it - you will need to adjust the button numbers first.

14 hours ago, johnk515 said:

Or is there an easier way. 

The alternative way (not sure if its any easier!) is to add the assignments via the ui and then overload the assignments by editing the ini file, to add the extra press/release controls as indicated in my last comment. To use this method, you will need to use the updated FSUIPC7.exe provided (still not officially released) as this has the necessary additional pause control added.