
John Dowson
Members-
Posts
13,293 -
Joined
-
Last visited
-
Days Won
271
Everything posted by John Dowson
-
I can find nothing in the SDK (in events or simulator variables) that relate to the HotBrake or TerrON, and also nothing related to these in the MSFS assignments. Therefore its not currently possible to control these. John
-
Sorry, I don't understand what you are saying or trying to do here. The offsets you mention hold the gear left/centre/right position. What do you mean by 'extracted' and 'moving'? What are you actually trying to achieve? If the autobrake offset you are using is 0x2F80, this is documented as 'No longer writeable' (in the offset status spreadsheet) I've checked the code and it seems that this was disabled as the Set Autobrake Control was not present in earlier versions of the SDK. As its now available, I will re-activate that offset for writing. What are those? Is there anything in MSFS that you can use to control these? Please try the attached version c7.0.3c where I have re-enabled offset 0x2F80 for writing. John FSUIPC7.exe
-
CRS encoder via EventID's 65663 - 65662 param 0
John Dowson replied to zorzini's topic in FSUIPC7 MSFS
@zorzini I am wondering whether this could be the same MSFS bug explained here: https://forums.flightsimulator.com/t/heading-increment-bug-10-degree-instead-of-1-explained/290173 John -
Did you get this working? It does seem top be an MSFS bug - see https://forums.flightsimulator.com/t/heading-increment-bug-10-degree-instead-of-1-explained/290173 John
-
@ark1320 Thomas has pointed out we are actually receiving the arrow key key presses via SimConnect, but we are receiving these as numpad key events. As they are being received, I can check the state of the arrow keys when the notification is received and re-map to the correct VK code. I've done this in the attached version if you would like to try: FSUIPC7.exe John
-
But remember, the SimConnect API dates back many years, and maybe these keys were not common then. Or maybe they are covered by some of the other VK codes (but I would expect VK_LEFT, etc, or VK_0x25, etc which don't seem to exist). But really, you need to address such questions to Asobo. Well, if they are not assignable I'd rather remove them completely. Or is it worth keeping such key assignments as they do have an effect when FSUIPC7 has the focus? I think the former. But, as the SDK is still under development, for the time being I think its better to accept all and provide a reference to what actually works in SimConnect in the manuals. Once we get to SDK 1.0, I can consider updating the manuals (and maybe the code) to then reflect what is actually assignable. John
-
Overhead A320 VRInsight
John Dowson replied to ALEXANDRE Alain's topic in FSUIPC Support Pete Dowson Modules
Hi Alain, what have you tried? What is the problem? Which VRI insight device overhead? Have you read Appendix 3 in the Advanced user manual (Handling VRInsight serial devices in FSUIPC)? Or is your device recognised as a standard windows hid joystick device? I'm sorry, but your question is so general its hard to answer. Please read the documentation, especially that annex in the Advanced User guide, and the separate document on VRInsight devices (Lua Plugins for VRInsight Devices.pdf). If you still have issues, then please post again (please check for previous posts first) and provide more details on what your actual problem is. John -
You logs don't show anything and are huge. Please de-activate most of the logging options when you supply a log, and only activate those relevant to your issue (or what we advise) - which in this case would be axis logging. However, looking at you ini, you have your aileron and elevator assigned to direct to FSUIPC calibration, but your calibration looks very strange: For your elevator, your null zone is bigger than your axis range! For comparison, this is what mine looks like: I suggest that you try to re-calibrate your axes. Please se the provided documentation on how to do this. You may also want to go into the windows joystick calibration page, and make sure they are calibrated in windows correctly first. John
-
Any valid offset for seatbelts and smoking sign a320 fwb?
John Dowson replied to alesj97's topic in FSUIPC7 MSFS
Just looked at this in the A320Neo (but without the FBW mod). In the default A320, both of the seatbelt and smoking switches are inoperative. You can send the relevant controls (Cabin No Smoking / Seatbelt Alert Switch Toggle) and the offset (and associated simvar) gets updated, but has no effect on the aircraft. It therefore seems that this is not connected yet. I'm not sure if the FBW mod is supposed to correct this as I haven't used this (yet!). John -
But, as I said, it isn't a bug so no fix is required. Its a new feature request that is needed, as the arrow key input has never been available via Simconnect. Previous versions of FSUIPC were an embedded dll and so could receive all keystrokes natively (i.e. using the windows API) and did not rely on SimConnect for this. Now FSUIPC7 is an executable, it can only get the keyboard events (when MSFS has the focus) via SimConnect. Again, check the SDK documentation to see what keys are available. Well, its the same effect/result, but the issue is different. The issue with the numpad keys was due to a defective SDK (and documentation) and a hacked implementation in FSUIPC7 due to this. This was rectified in the 0.8.0.0 SDK release and the v7.0.2 release of FSUIPC7. The issue with the arrow keys is that they have never (and most likely won't) been made available via SimConnect. I will update the documentation to make this clear, and think about removing these other keys from FSUIPC7 as there is really no point assigning to such keys. John
-
Hi Al, there are no key strings listed for those keys yet in the SDK, so I don't think they are even planning to provide support for them at the moment. In fact, looking at the P3D SDK, they are not even available there, so it seems like these keys have never been available via SimConnect input events. John
-
@pilotjohn Can you try the attached version please (v7.0.3a). In this version, I have added read/writeable offsets for aileron slope: 0x08A2 elevator slope: 0x08A3 rudder slope: 0x8A4 steering tiller slope: 0x8A5 Each is a signed byte (SB). Only values in the range -15 to +15 are accepted (values outside will be capped to that range). Also, at the moment, you can log the slope adjustments made by activating Extras logging. I probably won't keep this in the final version - or I'll keep it but move it to a different logging flag, still undecided.... Let me know if this works for you. John FSUIPC7.exe P.S. One thing you should be aware of: if you are changing the slope dynamically, it won't be saved for the next session. However, if you go into the axis assignments and calibration dialog , when you close the dialog any current active slope will be written to your FSUIPC7.ini.
-
It doesn't matter where its located - it uses the registry to determine the previous installation location. It cannot determine the previous installation location if you manually uninstall FSUIPC7 first (by using the provided/generated uninstallers), or if your beta version was very old, before I added the installer. For future reference, when you install future versions/updates, if you just run the installer (without uninstalling first) and accept all the default values, it will update the current installation and preserve all your settings. John
-
I'm not sure where you read that.... Whenever you install FSUIPC7, if the installer detects that FSUIPC7 is already installed, then it will automatically uninstall the current version and then use the same defaults (for installation folder) as your previous installation. If you don't change this and install in the same place, then all your settings will be preserved. If you select to install into a different folder, then to preserve your settings you will have to copy across the FSUIPC7.in file together with any auxiliary files (eg. .lua, .mcro, .dll, etc) that you may use. John
-
To control the trim wheel sensitivity, try the solution mentioned in this post: And please read the Installation and Registration guide, which will tell you where everything is installed. John
-
If there are no lvars, you can check if there is a custom control you can use instead - sorry, don't have the PMDG 737 so I'm not sure what custom controls are available. Otherwise, yes, try using a mouse macro... But why are you looking at the log to create a mouse macro? You don't need to look at the log to create a mouse macro, or to then assign the macro to a button. I see Pete has also just replied.... John
-
The '-FastLaunch' option is automatically added to start MSFS store installed versions, but I don't think this is possible with the steam version as a command line parameter. To use this option with steam, open your library in Steam, right-click on MSFS and select Properties. Under the General tab, click SET LAUNCH OPTIONS, then enter -FastLaunch in the pop-up dialog. John
-
I think the installer uses either %PROFILE% (not %USERPROFILE%), or the Personal registry key under HKCU "SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders" Yes, if you re-install without uninstalling first, it will take ALL previous values from your registry. To get around this, you can manually run the uninstaller (from your installation folder) first. If you do this, the next time you run the installer it will be as a fresh install. John
-
Yes, sounds very strange. I'll keep this open but its difficult to investigate without being able to reproduce. Were you connected to MSFS when these loss of axes occurred?
-
I've moved it to the main support forum. This is all explained in the Registration and Installation manual...can you please take a look at trhat. If you are using the add-on.xml install method (which is recommended), there are three locations used: 1. the location of the add-on.xml file. This is under your windows Documents folder, under Documents\Prepar3D v5 Add-ons\FSUIPC6 (or v4 if using P3Dv4). This cannot be changed. 2. the installation folder, where FSUIPC6 is installed. This is the folder YOU SELECT during the installation process. If you already have installed FSUIPC6 or FSUIPC5 installed, this will default to the current installation folder location. If this is a fresh install, this will default to the add-on.xml folder location (i.e. 1. above), but it is highly recommended to change this. 3. The location where the documents are installed. This is always in your Windows Documents folder, under an FSUIPC6 sub-folder. The location of your Windows Documents folder is determined from your registry, as is the previous installation location of FSUIPC6. John
-
The SDK is still at version 0.8.0.0 - hopefully these thigs will be fixed as MSFS (and the SDK) matures. For this type of thing you should raise a new feature request with Asobo via zendesk, or check if one has already been raised and upvote that. John
-
Could you clarify please? When I create a new profile based upon an existing profile, the axes are also copied to the new profile as far as I can tell. John
-
Scroll lock is not supported yet by the SDK, so you will need to assign another key or key combination - from the SDK documentation: John
-
FSUIPC stutters in FS9
John Dowson replied to Skywatcher's topic in FSUIPC Support Pete Dowson Modules
@JSMR But there is nothing to add to what Pete has communicated. Sorry, but there is no way to investigate issues with FS9. This topic is now closed. John