
John Dowson
Members-
Posts
13,281 -
Joined
-
Last visited
-
Days Won
271
Everything posted by John Dowson
-
This should certainly not happen...are you changing this while FSUIPC7 is running? Any changes to the FSUIPC7.ini file should either be made when FSUIPC7 is not running, or if it is running then you should have the axis assignment UI panel open when making these changes, and when the changes saved you should click the 'Reload all assignments' button. If that makes no difference, then you are certainly doing something wrong. Before you assign the throttle, I suggest you try logging the offset/lvar values to make sure they are as expected. You can do this using the Log->Offsets... menu option, entering the offsets A000 and A004 both as type FLT32. I also recommend that you activate logging for Axis Controls. Then move the throttle in the cockpit UI through its full range. You can do thus with the logging console open (Log->Open Console) to view the messages in real-time If you see any throttle axis events logged, you should use those rather than the lvars. If no such events are logged, check that the offset/lvar values are in the expected range. You should also make a note of the values you see for the different throttle positions. As discussed earlier in this thread, it looks as if the relationship between the lvar values and the throttle position is not linear. This implies that you cannot use just one scaling value and get your controller throttle position to match that of the aircraft. To do that, you would need a lua script to receive your axis values (via offsets), apply calibration/scaling based upon that value, and then set the lvar values to this scaled/calibrated value. If you don't want to use lua, then you need to use the axis scaling method (as previously discussed) to get a response that you can use/lice with. You can start with the values previously mentioned, If you have any further questions, please also attach your FSUIPC7.ini as well as your FSUIPC7.log file with the above offset logging enabled. John Later: if using lvars to control the throttle, you should also change the lvar update frequency in the WASM. This defaults to 6Hz, but you should change this to Frame or VisualFrame to get faster updates if using to control an axis. You should set this in a FSUIPC_WASM.ini file in the WASM persistent storage area - see the Advanced User guide for details. Note that this file will not exist in that location by default - copy the one from your Community folder to your WASM persistent storage area and then update it.
-
Just compress/zip it - it should be fine to attach if you do that. I need to see this file. It is normal for many aircraft in MSFS to continually send certain events, which are different for each aircraft. You can ignore these, or use the DontLogthese ini parameter so that such events are not logged (see the Advanced User guide for details). Note that in your ini you have assignments to an X52 that is no longer available: If you no longer use that controller, you should remove those assignments. John
-
Aerosoft bronco and mouse macros
John Dowson replied to Wsavold's topic in FSUIPC Support Pete Dowson Modules
In FSX/FSUIPC4 the mouse macro facility relies on the coding of the gauges being strictly to FS2004 C++ programming, using the tools originally provided by MS. The facility is a 'hack' into the code. Most gauges just aren't coded to suit. In P3D4 and P3D5 the mouse macro facilities depend on new facilities implemented for us by L-M, and are thereby more consistently applicable. It is therefore probable that mouse macros cannot be used with that aircraft. Try using standard controls where available. If those don't work, try listing available lvars (there is an FSUIPC-added control for this) to see if any of those look applicable for the functions that you want to implement. If you still have problems, maybe create a separate post with the aircraft name in the title and the function you are trying to assign, and other users with this aircraft may be able to assist. Unfortunately, not having this aircraft it is difficult for me to advise. John -
FSUIPC7.exe and ntdll.dll keep getting me to do CTD
John Dowson replied to Blinn1980's topic in FSUIPC7 MSFS
Are you sure that it is FSUIPC7 that is crashing, and not MSFS? Was MSFS still running? If so, what happens when you restart FSUIPC7 - does it connect and function correctly? Also, check for MSFS crash reports before the FSUIPC7 one that you posted. Usually this FSUIPC7 error is reported (it is an error, not a crash!) as it is MSFS that has crashed and then this error is generated in FSUIPC due to the simconnect connection no longer being available. The log you posted indicates that FSUIPC7 exited as MSFS was no longer running: If it is MSFS that is crashing, you should check the Asobo as well as the PMDG forums, and maybe report the crash to Asobo. Note also if using the PMDG 737 for MSFS, you can try with the latest FSUIPC7 beta version with the PMDG offsets available (if you use those) - see this post: John -
Hi Tom, I will check the updates on my windows 10 system the next time I fire it up, but I am pretty sure that is on the latest updates as of a few days ago, and I have not experienced any issues. And if there was an issue with the latest updates, I would have expected this to be reported by many other users... I have just checked and updated to KB5015807 and everything is still working as expected. Are you still having issues? Please update to the latest FSUIPC version, v7.3.7, and let me know if it starts or not. If not, if an FSUIPC7.log file is created, please attach that. Also check the Windows Event viewer to see if there are any errors or crash reports there, and if so please paste the details. John
-
Elevator Trim Assignment Issue
John Dowson replied to CallingBarranca's topic in FSUIPC Support Pete Dowson Modules
This is very strange - if it is trying to update an FSUIPC4.ini file, then that implies it is for FSX, not P3D... Ok. You should change the aircraft names in your profiles to use a substring match, so that all variants are matched. To do this, change: to That will then match all aircraft whose title/name contains "Sim-Avionics". I can't help with the PilotEdge client, but to prevent problems when your joystick ids change (which can happen), you should switch to using the JoyLetters facility. See the User guide for details, but the easiest way to activate is to just change: to If you do this when FSUIPC6 is not running, and then start FSUIPC/P3d, a mapping of letters to joystick ids will be added, and your assignments will be switched to using the letters/characters rather than the using the ids directly. This will prevent issues if/when they change. John -
No, but I don't use the MSFS beta's, and I don't support FSUIPC if/when using the MSFS beta updates. If anything breaks with a beta update, you should report to Asobo on the beta forum. If the problem persists once officially released, I will investigate then. John
-
MSFS - JF HAWK t.1 Throttle problem
John Dowson replied to Luigi Martinelli's topic in FSUIPC Support Pete Dowson Modules
I am not sure how the throttle works on this aircraft as I do not have it, but if there are issues when assigning direct to FSUIPC calibration, try switching to using 'Send to FS as normal axis' instead. Also check which throttle control you need to use - you can do this by activating Axis control logging and moving the throttle in the cockpit UI yo see what control is logged - maybe it is using the THROTTLE1 AXIS SET EX1 control, which I have seen with other users with this aircraft, so you could try that. There are also several presets available for the throttle on the Hawk: HT1_FWD_LEFT_ThrottleTransmit_Press HT1_FWD_LEFT_ThrottleTransmit_Release HT1_FWD_LEFT_ThrottleRelight_Press HT1_FWD_LEFT_ThrottleRelight_Release HT1_FWD_THROTTLE_Idle_Stop_Toggle I am not sure what these are supposed to do, but maybe they also need to be used? Maybe some other users of this aircraft can help? @Shorty01 has indicated that he has this aircraft configured with FSUIPC, and so may know how to assign the throttle with this aircraft... John -
The log files you attached stop after 3 seconds... can you run MSFS with FSUIPC7, select an aircraft and get ready-to-fly, then check the WASM menu options. If they are not available, exit FSUIPC7 and then attach your FSUIPC7.log and FSUIPC7.ini files. Thanks, John
-
Of course - that is the whole point of this topic...and it is available/downloadable from the first post in this topic. John
-
PilotEdge PTT Function Using FSUIPC via SimConnect
John Dowson replied to CallingBarranca's topic in FSUIPC7 MSFS
These are known as Add-on Custom Events - see the Advanced User guide, page 38. To use them, create an event file in your FSUIPC7 installation folder, e.g. PilotEdge.evt, and add the following content: [Events] 0=PILOTEDGE.PTT_ON 1=PILOTEDGE.PTT_RELEASE then restart FSUIPC7, and you should see and be able to assign to those events as you would any other FS events. John -
This will be corrected in the next release.
-
PMDG specific offsets are always (and will always be) read-only. To control, you need to use the provided Rotor Brake controls or presets. You can send these using the facility to send any control at offset 0x3110, or if using presets then offset 0x7C50 may be easier to use, as you can use the preset name directly rather than havung to calculate the control number. John
-
P3dv5 Fsupic6 and thrustmaster warthog drift
John Dowson replied to stevieiz's topic in FSUIPC Support Pete Dowson Modules
Are you sure that the drift is due to your controller, and not for other reasons (e.g. wind, trim, etc)? You can ret activating logging for axis controls and maybe also events. If you then fly with the logging console open (Log->Open console) you will see what controls are being sent to the sim. Are you using FSUIPC for your assignments, and if so do you have controllers disabled in P3Dv5? Also, your title suggests that you are using FSUIPC7 with P3Dv5. FSUIPC7 is for MSFS2020 only, it is FSUIPC6 that is compatible with P3Dv5. John -
Elevator Trim Assignment Issue
John Dowson replied to CallingBarranca's topic in FSUIPC Support Pete Dowson Modules
Ok. Also check that you have controllers disabled in P3D. John -
No, you should only need to enable WideFS just the once. This setting should then be saved to your FSUIPC7.in. However, I have just checked this and it does seem that this setting can sometimes get reverted. Noy sure why this is happening all of a sudden - #i will check this and get back to you. John
-
You have plenty of button assignments in your ini file, so I don't understand this. Can you add your offset assignments again, and once you have assigned them and pressed 'Ok' to close the assignment panel, take a look at your ini file to see if they are there. Also check that you haven't installed FSUIPC7 into a windows protected folder, such as under Documents or Program Files. Once you have your assignment in your ini file, generate a log showing your issue, with logging for Buttons & Keys activated as well as Events, and show me your FSUIPC7.log file as well as your updated FSUIPC7.ini file. John
-
Elevator Trim Assignment Issue
John Dowson replied to CallingBarranca's topic in FSUIPC Support Pete Dowson Modules
Can you go back to your original assignments (i.e. Trim Up/Down), set logging for Buttons & Keys as well as events (non-axis controls) and produce a log file showing your issue. Also, maybe try controlling the trim from the cockpit UI (if possible) to see what happens and what is logged then. Attach your FSUIPC .log and .ini files and I will take a look. John -
Note you can also log IPC Reads and Writes using FSUIPCs logging functionality. This will log all offsets read/written-to by external programs (IPC = Inter Process Communication). However, the log may be large and difficult to understand when using these options, but you can give it a try... Of course, as this is a facility in FSUIPC, you would need FSUIPC (and also the FS) running. John
- 4 replies
-
- wideclient
- dll
-
(and 1 more)
Tagged with:
-
I will check the updates on my windows 10 system the next time I fire it up, but I am pretty sure that is on the latest updates as of a few days ago, and I have not experienced any issues. And if there was an issue with the latest updates, I would have expected this to be reported by many other users... You should always use the latest FSUIPC version for your FS - only the latest release is supported. John
-
Those offset that you are using are in the offset area 6200 - 62FF which I have documented as: 6200-62FF = PMDG projects (Lefteris Kalamaras) fixed [PT1] So those offsets were allocated to a PMDG project many years ago, but they are NOT the official PMDG offsets that we populate - those are in offset areas 0x6420 (512 bytes) and 0x6C00 (256 bytes). See the FSX document Offset Mapping for PMDG 737NGX.pdf for a description of those offsets for FSX. For MSFS, those offsets have changed and are now documented in Offset Mapping for PMDG 737-700.pdf, which is available in the latest FSUIPC7 beta where the PMDG offsets are enabled and working. There is no secret, big or otherwise. The offsets were allocated, but we have no idea what they contain, They must be populated from some software by Lefteris Kalamaras, so you must be using some other software with FSX that is populating those offsets. You need to determine what those offsets contain and have two choices: 1. See if the software that populates those offsets is working with MSFS, and if so use that 2. See what those offsets contain/were used for in FSX, and try to determine if there are corresponding offsets in the PMDG data area that you can use instead, and update your SIOC code to use the new offsets. Lefteris Kalamaras is the owner/founder of FSLabs, although he previously worked with PMDG. I could possibly contact him about this offset area allocation, to find out what this data is and what populates/uses it. John
-
Well, I think WideClient accepts client connections without the FS running, so I guess you can debug, but no offset date would be available if the FS isn't running, so you would probably just get 0/null values. If you just want to know what data an offset contains, why don't you just run FSUIPC and use the offset logging facilities? But you (obviously?) need the FS running if you want to read the value of a simvar held in an FDUIPC offset.... John
- 4 replies
-
- wideclient
- dll
-
(and 1 more)
Tagged with:
-
This is very strange... If FSUIPC doesn't start manually, it is usually due to the correct VC++ redistributables not being installed. However, if it was previously working then those should be ok. Does a log file get created? If so, please show me that (although I suspect not...). Did you try rebooting your system? Check the windows event viewer to see if anything has been logged there. Also maybe try starting FSUIPC7 from a command prompt, and see if you get any errors starting this way. Something must have changed on your system, you need to find out what... That is needed for Windows 11 only.