John Dowson
-
Posts
13,317 -
Joined
-
Last visited
-
Days Won
272
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
Took a look...!
- button 1: switch between voltmeter and outside air temperature displays
- button 2: switch between various times (universal, local, flight, elapsed)
- button 3: start/reset ET,; Hold to reset FTbutton 3 is inoperative, so there will be nothing you can do for this.
Buttons 1 and 2 don't send any known events. Looking at the controls available in MSFS, there doesn't seem to be anything related to them there either.
So I think you are out of luck. I've also checked the published variable lists and there is also nothing there that could be linked to those functions.
It is the type of thing that mouse macros are generally used for, so you could wait to see if MSFS provides such an interface somewhere down the line (and then the mouse macro functionality implemented in FSUIPC7).
.
You could also raise a new feature request via Zendesk, asking for either new key events to be added to the SDK for these 2 (or 3) buttons, and/or for additional simvars to be made available to both read the current state and also write to update.John
-
1 hour ago, Benoit Ghio said:
However, i can't find any offset or function related to those 3 buttons ?
Offsets aren't related to buttons. You can program/assign any function that you want to a button.
What functionality do you want to assign to them, i.e. what should they do?
Later...ah, sorry - you mention it in the tile - OAT/VOLT/SELECT...but I don't know what this means. Could you be more explicit?
-
It goes in %APPDATA%\Lockheed Martin\Prepar3D v5 -see https://www.prepar3d.com/SDKv5/sdk/simconnect_api/configuration_files/configuration_files_overview.html, and for an example: SimConnect.xml file: https://prepar3d.com/SDKv5/sdk/simconnect_api/configuration_files/simconnect_xml.html
-
It could be that this issue is created by an old bug relating to the total number of connections used by simconnect clients - this is an old issue known in FSX and has been confirmed over at FSDeveloper. ( Discussion, An improvement in the same thread). To check if this is the cause, you could try modifying the maximum number of clients (MaxClients) in the SimConnect.xml file. You could first try reducing this to see if you can provoke this issue to occur earlier, and if this works then you can set to the maximum value which seems to be 255.
John
-
1
-
1
-
-
Hi Roman,
that's interesting and could well be related. It also makes sense to what I have observed while developing FSUIPC7 for MSFS, when FSUIPC was reconnecting many times due to stalled data.
When you say simconnect dies completely, does this mean that there is not even an error reported in the SimConnect log file (when activated)? And presumably its not just the client requesting the connection that then fails, but all simconnect clients already connected?
FSUIPC can automatically re-connect if the data it is receiving is stalled for a configurable amount of time and a message is logged each time a connection is opened or closed, so it is easy to determine the number of connections FSUIPC7 has used. Not sure about other simconnect clients though, but the simconnect log would be the place to determine the total number of clients and number of connections made by each.
Another strange thing about these reports though is that different users are reporting different symptoms/failures. Some users also report loss of controls in the FS (include mouse operations!), others loss of all flight controls, and some (like this post) just a failure in certain areas.
But I think anyone experiencing such issues after a long period should certainly look into this as a possible cause. It might be worth (following the advice in that link you posted) to initially adjust the maximum number of SimConnect clients (MaxClients) to a lower number, to see if the failure can be forced earlier. If thats the case, then it could then be increased to 255.
Thanks,
John
-
Can you also change the following parameters in the [General] section of your ini:
InitialStallTime=10
NormalStallTime=1
to
InitialStallTime=30
NormalStallTime=-2
which are the new defaults in FSUIPC7. -
8 hours ago, borisvp said:
Is this possible with the method John explained?
Yes, of course. For 50% rudder deflection at 100% joystick with linear response, remove the slope completely, open your FSUIPC7.ini and fine the rudder entry under [JoystickCalibration] (or in a profile specific JoystickCalibration section if you want to apply this there) - here's mine:
Rudder=-16384,-750,750,15648
then just double the max/min values:
Rudder=-32768,-750,750,31296then when your joystick is at max/min deflection (sending values near -16384 or 15648), these will be calibrated using the extended range and so halved, giving you a +/- 50% rudder deflection.
-
When you create a new profile, there will be no buttons or keys section until you create a profile specific assignment for such, so there is nothing to remove.
The generic profile is always applied for buttons/keys, and these will only be overwritten if you create a profile specific assignment instead.This is all explained in the documentation.
-
32 minutes ago, katoema said:
The reverse thrusters were assigned
Not in the ini you posted, as I said.
33 minutes ago, katoema said:if I now use your installer which you attached
It was the FSUIPC7.exe attached, not the installer. I'll be releasing an updated installer later today (or tomorrow), also with a new version of FSUIPC7.exe (which will again be different from the above).
-
Its ok, checked them an it seems that there is an issue with the ini comments for FSUIPC added controls which I will look into.
So you have nothing assigned in FSUIPC7 to do with axes or reverse, so how was this previously working?
-
Hi Martin,
how were you activating the reverse thruster? You have very few assignments, no axes or key assignments and only 3 valid, as well as 4 possibly invalid, button assignments, all assigned to your HOTAS throttle:
Quote1=RA,28,K113,8 -{Key press: F2}-
2=UA,28,K113,8 -{Key press: F2}-
3=RA,30,C1061,0 -{}-
4=UA,30,C1062,0 -{}-
5=RA,31,C1063,0 -{}-
6=UA,31,C1064,0 -{}-
7=PA,19,C66704,0 -{APU_STARTER}-
Controls 1061 - 1064 are for engine 1-4 autostart - I'm not sure why these aren't commented correctly - are they working?
An unrelated question - are you using a Steam or MS Store installation? Seems to be the latter, but FSUIPC isn't detecting your FS Path correctly.
Could you please try the attached version - just run it and close, then attach your FSUIPC7.log file.
Thanks,
John
Later: sorry, it is reported:
78 FS UNC path = "\\PILOT\MSFSPackages\"
just some earlier logging for the MSFS install was commented=out, which confused me.You can continue to use that version if you like - it will be released later today (or tomorrow), with an updated installer.
-
I have no idea. Are you using a registered version of FSUIPC7? If not, please uninstall FSUIPC7 using the uninstaller (located in your installation folder), download the latest installer and re-install.
If you are then still experiencing your issue, please start a new topic and attached your FSUIPC.ini and FSUIPC.log files.
John
-
4 minutes ago, craig_read said:
Note this only happens after several hours (in the order of 10 hours or so)
If it only occurs after 10 hours or so, its certainly not due to anything in your ini file!
There is a related post where the sim stops responding to all controls when using PMDG but after 7 hours:
and also a post in the LM forums on this: https://www.prepar3d.com/forum/viewtopic.php?f=6312&t=139856&hilit=freeze+after+7+hours&start=15
Although this issue occurs with FSUIPC running, it has also been reported without FSUIPC running but with other SimConnect clients.
It therefore seems to be a SimConnect issue and not related to FSUIPC.
-
@Mallinoi Did you try adding
LuaTrapKeyEvent=No
To the [General] section of your FSUIPC6.ini in v6.0.10?This will revert v6.0.10 to the previous behavior (6.0.8) where keys acted on in lua are also forwarded to the FS.
In v6.0.9 and later, keys handled in lua are masked and not seen by the FS.John
-
If you are talking about FSUIPC7, then a free time-limited license is currently provided by the installer. Just download and run it to install.
If you are asking about FSUIPC4/5 or 6, then you can retrieve your license from your SimMarket account.
John
-
Just checked and its still not working. You cannot load flight files saved by FSUIPC (in MSFS or FSUIPC), and you cannot load flight files saved directly by MSFS with FSUIPC, but you can load flight files saved by MSFS in MSFS.
Basically the simconnect flight save/load functions are still broken.
-
11 hours ago, flash said:
I just want to confirm using fsuipc is the only way to make them all work together
Sorry, I just don't know if that is the only way...
-
4 hours ago, Capt. PERO said:
Why isn't it default any more?
Tp make the behavior when handling events more consistent in FSUIPC7. In all other places, when FSUIPC handles an event, it is then masked/trapped and not forwarded to be handled by the FS (or other third party programs), except if specifically requested by the user.
[Note not currently the case in FSUIPC7 (for MSFS) where masking of most event types is broken]
4 hours ago, Capt. PERO said:Can you turn it back to default in further versions?
No, I believe it should be left as it is now. Just use the provided ini parameter.
But any keys should only be trapped/masked if you are actually handling them in the lua script - why are you handling the 0-9 keys in the lua if they are for GSX?
-
6 hours ago, pilotjohn said:
Or would you suggest using profile specific settings?
Yes. Thats what they are for.
6 hours ago, pilotjohn said:Is there a way to apply one certain aspect via a profile, like the mixture (but not, say, buttons)?
No, a profile all three assignment types (axes, buttons, keys) are always applied yo an aircraft in a profile. Note, however, they can be empty, and an aircraft will also have general assignments applied (if not overridden in a profile) for buttons and keys (but no axes).
-
7 hours ago, moxiejeff said:
opened Self-Loading Cargo
What is this?
-
I haven't yet checked this in the latest SDK release (will do this later), but I think there are still issues with the SimConnect flight load/save functions.
11 hours ago, Steku2 said:where to look for the autosaved files (Steam edition)?
If you use the FUIPC7 File -> Load Flight... menu option, this will open a file selection dialog on the default location for autosave files (all editions).
-
I take it you are running the one on the desktop, no? If so, try running the one in the folder that also has the key file. There is no .log or .ini in that folder, so it hasn't been ran. That's where you installed and where the key file is. There is no key file on your desktop. If you want to run it from there (not recommended!), then you need a key file on the desktop.
Its usual to drag a shortcut to an application to the desktop, not the application itself!
I would remove those desktop files, and create a shortcut instead if you want one.
-
Yes, that's the build date and nothing to do with the license!
-
12 minutes ago, MatzeH84 said:
cannot register
But you do not have to register. If you click the Register button it will say its invalid. Just click Skip.
The installer will not valid time-limited licenses, and the beta installer installs the key file anyway so you can skip this process.Try the attached key file, although it should be the same as the one you have: FSUIPC7.key
If you are still having issues, you can post your install log files as well as your FSUIPC7.log file.
Low Speed Elevator/Rudder Sensitivity
in FSUIPC7 MSFS
Posted
No. It is always free. However, there are additional facilities provided when using a registered/licensed version.
Why wouldn't it connect? Did it detect MSFS was running? Are you using auto-connect? Are you using a registered version?
Note that the latest installer doesn't come with a key file (license). You can download one from the FSUIPC7=beta announcements page, valid until 8th November.
In the calibration tab if the axis assignments panel, click the slope button and then adjust until you have a slope of 0. However, as you are editing the ini anyway, you can just remove them there - just look for the SlopeRudder parameter also in your [JoystickCalibration] section and remove that line.