John Dowson
-
Posts
13,768 -
Joined
-
Last visited
-
Days Won
288
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
21 hours ago, Saif said:
I have this error coming every time i start FSX steam
Please check link https://ibb.co/0M2Y6zx
What happens when you click 'Yes' to run?
-
First, you are not using the latest version of MSFS - can you please update to v.7.0.3. Only the latest version is supported.
If it still crashes, can you provide more information - as well as the event log, can you attach you FSUIPC7.log and FSUIPC7.ini files and provide a brief description of what was happening when the crash occurred. Thanks,
John
-
22 minutes ago, Jon Rodd said:
I have rechecked and cannot see an EXE file when extracted
It IS there. Pete posted the contents - if you see something different then please post a screenshot so that we can see what you can. If you are not seeing the extensions, it is because of your Explorer view settings, but the files should be there non the less. We need this information from you to help you....
22 minutes ago, Jon Rodd said:I have also relooked at your site and noticed that Win 10 64 bit is not mentioned
32/64 bit is mentioned. Win versions are only mentioned when applicable.
John
P.S. Another possibility is that you have some antivirus software running that is removing/quarantining the exe. So check your antivirus settings/history.
-
9 minutes ago, schillermetall said:
I've used other Rotarys as well, same result. Perhaps you can recommend a certain brand?
I'm afraid I'm not that familiar with such issues - I'm a software guy and defer to others when it comes to most hardware issues - maybe @Pete Dowson or @Thomas Richter can help with this. I don't see how the rotary can fire different buttons between win 7 and win10 un less its a driver issue, but maybe Pete or Thomas can explain this.
Regards,
John
-
1 hour ago, FPVSteve said:
Confirmed - yes, instead of Tail Left and Tail Right, Asobo were using Nose Left and Nose Right for the values.
Yes, This was a problem previously reported that we raised with Asobo, but I added a temporary fix so that previous assignments would still work.
When Asobo fix such issues, there is no feedback from them so we rely on user reports such as yours so that we can remove such corrections!.Hopefully there aren't too many hacks like this that need reversing, but due to my failure in properly tracking such issues, I'm afraid we rely on user feedback to correct.
Thanks and regards,
John
-
58 minutes ago, Cap said:
Thank you John, really appreciate your help.
Ok, no problem. Thanks for reporting back.
John
-
Hi Dennhy,
I'm glad this is now working for you (with the key file I PM'ed you), but I am still perplexed as to why you couldn't validate and generate the key file via the FSUIPC4 installer.
John
-
I've been testing the new dll this morning and it seems fine here, so could you try again please and let me know, and supply the information requested if it is still crashing. Thanks,
John
-
On 12/1/2020 at 11:47 PM, mac@bath said:
I turned that switch to 'off'.....lo and behold my ALtitude now changes in 100's and my Hdg changes in single degrees!!!!!
Just FYI, this is a known MSFS issue with certain controllers. See https://forums.flightsimulator.com/t/heading-increment-bug-10-degree-instead-of-1-explained/290173
John
-
16 hours ago, Cap said:
Binding to OBS1 or even OBS2 in MSFS2020 has zero effect on this Course knob or the needle.
Then this does sound like an issue with the aircraft that should be reported to the aircraft developers.
You could maybe try first sending a Heading Slot Index Set control with parameter 1 to see if that gives authority back to the HSI but I doubt it (as this is usually only needed to switch authority to/from the FCU).If you log events (using FSUIPC), can you see any events at all when you rotate the knob in the UI? Do you see the standard VOR1_OBI_INC/DEC events, something else or nothing?
-
7 minutes ago, Paulcoy said:
In that case I won't worry about it
Don't - but make sure you calibrate your axes and define an appropriate null zone.
John
-
Hi Gary,
6 hours ago, iflygary said:Can you provide further details here please or should I contact Tom at FSX Times?
Sorry, I know nothing about those FIP gauges - you should certainly contact the developer for support.
Cheers,
John
-
2 hours ago, Paulcoy said:
Hi, I have the logitech Rudder Pedals, and when calibrating with FSUIPC 7 the centre value settles at 64. Surely this should be 0 or am I missing something.
Most axes don't centre at exactly zero. This is why you have a null zone around the centre which you set-up during calibration. I have MFG Crosswinds and this is my rudder calibration entry:
Rudder=-16384,-650,650,15648
i.e. a null zone between -650 - + 650.John
-
1 hour ago, asessa said:
Can you implement an offset for a simvar (if exists) for AUTOBRAKES ACTIVATED so i can lighton the led DECEL when it was activated ?
There is an AUTOBRAKES ACTIVE simulator variable, but it looks like this isn't exposed via SimConnect at the moment. I'll check it to see if its available (in case its just missing from the SimConnect documentation) and if so I will add it and let you know. In the mean-time, you could see if the standard brake indicator offset 0x32F9 show anything for Autobrakes..
There is also a simvar LIGHT BRAKE ON which is available via SimConnect, which is True if the light brake is on, but this may be for toe brakes. I'll add it anyway so you can check.It may take me a few days to get around to this though.
John
-
1
-
-
16 hours ago, Cuantreau said:
I had to edit, because since overwriting this dll to FSUIPC folder I'm getting almost instant CTD when scenery is loaded in most cases, also at 72% of loading it CTD's. When I replace this new with the original dll, no CTD at all. So conclusion, it worked ones but strangely since that first successful attempt of creating new profile, the sim CTD's almost every load.
That is strange, and worrying. The fix for this was minor and could not cause this, but there are a few other minor updates also in that version. I'll take a look, but would be useful if you could show me a log file after a crash, and also check to see if there is a crash log in the windows event viewer and if so paste the details.
Thanks,
John
-
16 hours ago, John Dowson said:
the button numbers are the same regardless of the direction that you turn the rotary?
So this is the case. It sounds like this is either a problem with the rotary or the driver. FSUIPC is only reporting what it sees from the windows joystick HID API.
Maybe you can check what windows sees under game controllers for that rotary?
What is strange is that you say this was working fine under win 7. What button numbers did it report there in each direction? -
6 hours ago, Goochie said:
I will use it. I was very disappointed to see that after installing it the documentation did not come with it and doesn't seem to be available separately for download. According to your pdf "Installing and Registering FSUIPC7" docs should be in the install folder, but they are not.
The documentation is installed under your Windows documents folder, as explained in that manual. The documentation is only installed in the install location if this location cannot be determined or accessed:
QuoteNote that all documentation will be installed in a folder called FSUIPC7, located under your
windows Documents folder. If, for some reason, the documents cannot be installed in this location, a
folder called Docs will be created under the installation directory, and the documents will be
installed in this folder.6 hours ago, Goochie said:Getting just a tad frustrated. I tried using the license details you posted earlier but they were not accepted.
Time-limited licenses are not validated by the installer. Just download the key file and drop that into your installation folder. I will amend the post above to make this clear.
John
-
Hi Gary,
thanks for reporting back and your kind words.
Regards,
John
-
1
-
-
If you still can't get this working, maybe you can try running FSX with an unregistered version of FSUIPC to see if it works with an unregistered version.
If not, it may be due to your VS redistributables. I have had cases in FSUIPC7 where an issue with the VC redistributables causes an issue with registration (and this issue also prevents an unregistered version of FSUIPC running, hence the test), but have not heard of this issue in FSUIPC4...John
-
58 minutes ago, woolybugger said:
It still is not accepting the 12 digit key code.
Its not just the key code that needs to be entered correctly. but all details, as specified in the email (that you posted earlier).
They have been validated and are ok, so it must be that you are not entering them correctly. Please try again, and paste each field (Name, Email/Address, Key) exactly as specified. -
8 minutes ago, Cap said:
, so setting those on a dedicated VOR instrument wouldn't be a problem. It's having a CRS course knob on an HSI that's alien to virgin MSFS2020
But shouldn't the HSI be slaved to the VOR? Or is this what the problem is with the Carenado?
It may be something that, in the add-on aircraft, is separated and only controlled by lvars (local panel/gauge variables). Currently no lvar access in FSUIPC at the moment, but Im looking into it.
John
-
1 minute ago, Cap said:
If you're referring to the toggle switches that have an 'ON' state that continually sends a windows DX event - then yes.
Yes, that is what I was referring to.
2 minutes ago, Cap said:However, the big one I am trying to solve is with MSFS2020 + Add-on aircraft Piper Seminole. The seminole has an HSI with a HDG knob and a CRS course knob, but MSFS2020 has NO binding for the course knob anywhere. It's only usable (and I use that term loosely) if you use a mouse.
Ok. You can try but I'm afraid that if it doesn't work then it will be a problem with the implementation in the Add-on aircraft. If it doesn't bind in MSFS, then it probably won't via SimConnect/FSUIPC, but you can try.
On a similar note, it maybe be worth reviewing this support request regarding the CRS course knob:
John
-
2 minutes ago, Cap said:
At least I can see if this fixes my issues.
Are you aware of what causes the heading bug incr/decr issue? FSUIPC can get around this, but you need to be aware of what causes this to prevent.
I can supply more information if needed. Try and let me know if you need any further help.John
-
I've generated one anyway. Drop the attached key file into your installation folder:
Note that the installer will not validate this license as it currently cannot handle time-limited license validation.
John
P.S. I will change the title of this post to make it clearer for other users....
Can't Calibrate Joystick Axes
in FSUIPC7 MSFS
Posted
@jockoflocko Sorry for the late reply. I see you have worked out the issue - you have to be 'ready-to-fly' to be able to calibrate the axis, not just connected to the sim.
I'll think of adding a pop-up message/warning (or maybe disable the calibration tab) when not in the correct state, to make it a bit clearer.
John