
John Dowson
Members-
Posts
13,443 -
Joined
-
Last visited
-
Days Won
278
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by John Dowson
-
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: FSUIPC7.key 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....
-
I understand your point. There isn't really a 'trial' version of FSUIPC. There's just one version, and the facilities available depend on whether it is registered or not (i.e. has a valid license). I can supply a time-limited license. I've been thinking of doing this for a while, maybe for every other 10 days or so and making it available via www.fsuipc.com. But, to be honest, its just the extra effort of maintaining this over a long period that prevents me from doing this. For now, I don't mind supplying time-limited license on request. Do you want one? John
-
I still don't know what you mean by this! It would help if you could explain what you are doing and what you are seeing, and what the actual problem is. As far as FSUIPC is concerned, a button is a button, the direction doesn't matter. Various rotaries work in different ways with a different number of buttons. For example, the rotaries on my GF panels are 4 button rotaries, two buttons in each direction, one for slow movement and one for fast, so that they can be programmed/assigned distinctly (i.e. for small or large increments on whatever it is controlling). But, as I have said, what exactly is you issue? Are you saying that the button numbers are the same regardless of the direction that you turn the rotary? And that this is only in FSUIPC6, but is ok in FSUIPC4?
-
Resetting FSUIPC 6/profiles P3D V5
John Dowson replied to Ross McDonagh's topic in FSUIPC Support Pete Dowson Modules
@Ross McDonagh FYI, I have also identified an issue where axis can be lost when adding an aircraft to an existing profile. See this support request for further details: This has been corrected in the attached version, so please try with this: FSUIPC6.dll John -
Not sure what you mean by this... Some rotaries have two buttons in each direction - one for a small increments and another for larger increments. But what exactly is you issue? If you turn you rotary, you thrn get a button number - can't you then assign to it? Or are you saying that the button number changes when you are not turning the rotary? if so, that sounds like a dirty connection. You can ignore such inputs by using the IgnoreThese ini parameter (see Advanced User manual). I will be adding a button to the UI for this, but haven't got around to this so far.... John
-
This should be fixed in the attached version: FSUIPC6.dll
-
When you turn the encoder, you should see the "button number" (as well as the device number) for the rotary in that direction. You will only see an "offset" if you already have an offset assignment to that button. Sorry, I don't understand what you mean by this. Can you explain? Also, please attach your FSUIPC7.ini file so I can see your assignments.
-
This error is mention in the included README.txt, and there are many other support requests asking the same question..... You need to (re-)install the VC++ redistributables. Check the README.txt or other support requests for details.
-
Yes, sorry for not replying sooner. This error is also mentioned in the included README.txt, and there are several support requests already on this error. Please remember to check the documentation and search for similar problems before you post in future. Thanks, John
-
There was an issue with losing axis prior to 6.0.11 which I corrected, but it seems that there is still something amiss in 6.0.11. I'm looking into it. John
-
Hi Sergio, I've had a few similar reports recently but haven't been able to reproduce so far, and the other users who reported also couldn't reproduce. Could you tell me exactly what you did to make the new livery profile specific and I'll see if I can reproduce. Thanks, John
-
Prepar3d v4 crashes when loading a flight
John Dowson replied to malarmao's topic in FSUIPC Support Pete Dowson Modules
In your installation folder, the same location as the log file and the FSUIPC4.dll. -
FSUIPC 7 No Longer Connects To Logitech Panels
John Dowson replied to iflygary's topic in FSUIPC7 MSFS
Hi Gary, What exactly isn't working? Your log shows your 4 devices acquired ok, and you have various assignments that should work. The log also shows you loaded the Bonanza G36, for which you have no profile set-up, so it will just use the default (general) profile. Looking at your ini, you have your throttle, PropPitch and Mixture axes set-up in the general Axes section (i.e. your throttle axes) , but no elevator, aileron or rudder. In fact, you do not have these axes (yoke) assigned anywhere (i.e. in any profile) - do you have these set-up in MSFS? Are the assignments you have working ok, i.e. the throttle should work in all aircraft - does it? You have also assigned your axes to 'Direct to FSUIPC Calibration' but have not calibrated your axes. You should really do this - see the User guide for details. Maybe you could calibrate your axes and tell me in more detail what isn't working. Can you see each of your devices axes/buttons in the FSUIPC assignments windows? You could also activate button and event logging (and later axes) and operate some buttons to see what is logged. John -
Yes. But of course you can always place it over the sim window... I've attached two lua scripts that display the frame rate, one using the standard lua ipc.display function (that uses SimConnect_Text under the covers) and another that uses the Wnd library. Due to the issues with the SimConnect_Text function, the ipc.display version has various issues (although works fine in P3D). John FPS_Monitor.lua FPS_MonitorW.lua
- 3 replies
-
- drawing
- sim-object
-
(and 1 more)
Tagged with:
-
FSUIPC uses the SimConnect_Text function for displaying text. There are currently many issues with this - from the MSFS SK: There are also problems with updating text in a simconnect text window (multiple windows are created) and the 'time to display'.. For these reasons, I have added the lua Wnd library which can be used instead. This displays the text in a separate (moveable and resizeable) window. To display text without lua, you can use offset 0x32FA, but this uses the SimConnet_Text function and so suffers from the same issues as the lua text display functions. If you are writing your own program, you could also use the SimConnect SDK directly rather than using one of the FSUIPC SDKs. No, this is not possible. John
- 3 replies
-
- drawing
- sim-object
-
(and 1 more)
Tagged with:
-
FSUIPC 7 No Longer Connects To Logitech Panels
John Dowson replied to iflygary's topic in FSUIPC7 MSFS
Hi Gary, Something must have changed! What Logitech/Saitek panels are you using? Are you also using spad or spad.next? Could you show me/attach your FSUIPC7.ini and FSUIPC7.log files please. John -
Prepar3d v4 crashes when loading a flight
John Dowson replied to malarmao's topic in FSUIPC Support Pete Dowson Modules
This seems to contradict the title of this post ('crashes when loading flight') - does it crash when you start P3D, or when you load a flight? Do you have a crash log in the windows event viewer? If so, can you please show me that. Also, you should always attach your FSUIPC6.log file when you have such issues. Having said that, P3D crashes on start-up are usually due to a corrupt weather file, usually the wxstationlist.bin file or your start-up scenario *.wx file. If you want to check whether or not it is down to corrupted weather files you can try adding NoWeatherAtAll=Yes to the [General] section of the INI file. If it is a weather file, you should first try deleting the wxstationlist.bin file from your AppData\Roaming\Lockheed Martin\Prepar3D v4 folder (it will be regenerated when you run P3D). If you still have issues, try removing the *.wx files in your Prepar3D documents folder (the folder where your saved flights are). If its not a weather issue, please show me your FSUIPC6.log file and check the event viewer for a crash event and also show me that. John -
Frequently lose TPM throttle with FSUIPC6
John Dowson replied to westhielke's topic in FSUIPC Support Pete Dowson Modules
Strange...you should be able to attach files, not sure whats going on there... Ok, no problem. Hmmm...I don't understand how a restart with no other changes can change things... Ok. If your issue re-appears, try attaching the requested files again and I'll take a look. -
Ok, glad its now working, and thanks for reporting back on how you configured this. John
-
Ok. But I didn't need to see your bat file - I know what is in it! I was just suggesting that you could open it and play around with the command that starts MSFS (including removing the FastLaunch option) to see if you can get it to work. The command is at line 7: cmd.exe /C start shell:AppsFolder\Microsoft.FlightSimulator_8wekyb3d8bbwe!App -FastLaunch Its the same for every MS Store user. This command uses your user AppsFolder settings, which may be the issue. I don't think uninstalling and re-installing FSUIPC7 is going to help. John
-
FSUIPC and keystroke from a remote program
John Dowson replied to Buffort's topic in FSUIPC Support Pete Dowson Modules
Was just looking at this but Pete beat me to it... No, that's the type of the value being written: -
Right-click on the MSFSwithFSUIPC7.bat file, located in your FSUIPC7 installation folder (i.e. not the link on your desktop) in windows explorer, an select 'Edit' or 'Edit with Notepad++' (or whatever your preferred editor is). Run the uninstaller that is generated in the installation process. You can also find this in your FSUIPC7 installation folder. You can also uninstall using the windows settings apps uninstall page, which will run the uninstaller for you. John