John Dowson
-
Posts
11,129 -
Joined
-
Last visited
-
Days Won
219
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
FSUIPC just populates the PMDG offsets with the data received from the aircraft. If it is not holding the correct value, then this can be due to one of two things:
1. The PMDG data format has changed. I can check this.
2. The data PMDG is sending is not correct. I cannot do anything about this and this should be reported to PMDG.I will take a look at 1 and get back to you.
John
-
1
-
-
2 minutes ago, Tigerhawk said:
I ran the new installer, hotkeys worked first time and also on a subsequent start of MSFS.
Great!
2 minutes ago, Tigerhawk said:Logs attached for your info.
Thanks - your files look good. Thanks for testing this,
John
-
7 hours ago, h512243512 said:
i just sovled problem by sending direct to calibration and then i calibrate it
Ah, ok...
7 hours ago, h512243512 said:it is weird , it should be working when i choose to send to fs as normal axis
This depends. Some add-on aircraft don't work well when assigned using Send to FS as normal control and are then also calibrated in FSUIPC7, due to the priority levels. The aircraft will intercept the initial axis control, pre-calibration, rather than the calibrated axis control.
Anyway, glad your issue is fixed.
John
-
12 hours ago, JakedarlingYT said:
FSUIPC7 splash-screen never popped up
Can you show me the InstallFSUIPC7.log please, from when you re-installed after renaming the UserCfg.opt file. Also please attach your FSUIPC7.log file, which will be in your FSUIPC7 installation folder.
12 hours ago, JakedarlingYT said:i belived to have fixed it because it poped up when i opened it
The auto-start issue is not fixed - you started FSUIPC7 manually. You can continue to do this to use FSUIPC7, but if you want this to be automatically started then this issue will need to be fixed. There is a FAQ entry on auto-start issues - see
John
-
Yes, I can see this now after virus definitions update. I have allowed an exception and downloaded and checked the file, and it is the same one as uploaded and so this will be a false-positive.
I will report this to windows, and also see if I can fix here. I think the problem is that the installer runs an embedded program to check the registration details and it is this that is being flagged. This program was recently updated (recompiled only) so I will try with the older version. If that also fails, I will have to remove the registration validation until this issue is fixed.Sorry about this - I will try and fix this asap....for now, please add an exception for the installer to allow it to be downloaded and ran.
John
-
45 minutes ago, John Dowson said:
It must be possible to either disable BitDefender when downloading/installing, or adding an exception to allow the program to run.
Can this not be done?See:
https://www.bitdefender.com/consumer/support/answer/13427/
https://www.bitdefender.com/consumer/support/answer/2393/ -
34 minutes ago, JakedarlingYT said:
what should i reanme the file to?
Whatever you want - User.cfg.opt.notUsed for example. Just give it a different name so it is not detected.
-
45 minutes ago, MM said:
Please note that the new installer is "not found on this server." )
Oops, sorry - its an exe not a zip - corrected.
-
Just now, JakedarlingYT said:
i bit confused on the last part where you say remove or reanme this file!
What is confusing about this? If that file is present, the installer will assume you are using a Steam installation. If that file is not found, then an MS Store installation is assumed. Renaming that file will therefore tell the installer to install for MS Store, not Steam.
John
-
11 hours ago, Kimchi said:
buttons being switched and stuff, maybe this is not a false positive but actual a real problem?
No, it is a false positive. I have no viruses, and SimMarket also scans all files for viruses and they have not reported anything.
As the virus is reported in the RegistrationChecker program, can you not install and skip registration?1 hour ago, Reggie Fowler said:can't even download to my desktop.
Are you using BitDefender? What is it saying, and why is this different from other users reporting this issue - others users could download but had problems running it due to the issue with the RegistrationChecker program. If it is your browser blocking the download, you can tell the browser to download anyway.
1 hour ago, Reggie Fowler said:So I can't even try the workaround they have posted to possible fix the problem.
What workaround did they post? Can you please provide a reference.
It must be possible to either disable BitDefender when downloading/installing, or adding an exception to allow the program to run.
Can this not be done? -
24 minutes ago, JakedarlingYT said:
i not tried lauching game just yet as i am in midflight of doing a flight
But you shouldn't install FSUIPC7 when running MSFS. But try re-launching MSFS after you have finished your flight and see if FSUIPC7 starts. If not, can you at least try starting it manually, by double-clicking the FSUIPC7.exe in windows Explorer - does it then work?
35 minutes ago, JakedarlingYT said:i have downloaded the game off xbox app on pc bec i have a subscription
Then I would expect that you are using an MS Store installation, but your log file indicates that FSUIPC7 is installing for Steam.
Did you previously have a steam version installed but are now using the xbox version? If so, please remove or rename this file:
C:\Users\jaked\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt
and re-install.Do you know where your Community folder is - is it at that location I mentioned?
John
-
I am also going to change the default auto-start-up mechanism of FSUIPC7 back to using the MSFS.bat file rather than the EXE.xml file, although this option will still be available. I am doing this as it seems that when started vie the EXE.xml file FSUPC7 is running more than 10x slower than when started by other means. I have reported this to Asobo.
This new installer is available here: https://fsuipc.simflight.com/beta/Install_FSUIPC7beta.exe
Please re-run auto-tuning with this version by manually adding
StartUpTuningActive=Yes
to the [General] section of your FSUIPC7.ini file.Thanks,
John
-
2 hours ago, Tigerhawk said:
When I was setting it manually I was using 330 Delay, the auto set it to 200.
It set it but the value used was 60 (the default). Once you have ran with auto-tuning active, exit MSFS and run it again to use the new value set.
Can you also activate logging for Buttons & Keys please for future logs.2 hours ago, Tigerhawk said:the hotkeys were unresponsive, as before.
If you exit and restart FSUIPC7, do the hot keys then work?
Can you please try the attached version which has a few improvements. Remove the DetectToConnectDelayAuto ini parameter so that auto-tuning does its thing.
When done, exit MSFS, rename your log file (e.g. FSUIPC7-init.log) then restart MSFS and see if the hot keys are working or not. If not, exit FSUIPC7 and restart it and test again - are they working now?
Then exit FSUIPC7 and show me/attach the three log files - FSUIPC7-init.log, FSUIPC7_prev.log and FSUIPC7.log.Thanks,
John
Standalone program: FSUIPC7.exe
But better to use the beta installer - see following post.
-
14 minutes ago, JakedarlingYT said:
but the App aint running when i lauch the game
Do you mean that FSUIPC7 is not running? Do you not see the FSUIPC7 splash-screen when MSFS is started and loading?
Did you install FSUIPC7 firectly from within the zip file rather than extracting the installer from the zip file first? It looks like it:
QuoteRunning in folder 'C:\Users\jaked\AppData\Local\Temp\Rar$EXa25064.24679.rartemp\Install_FSUIPC7'
Please try extracting the installer before running it.
The Community folder for your Steam installation also looks rather strange:
QuoteCommunity folder is: C:\Games\Microsoft Flight Simulator\HLM_Packages\Community\
Is this correct?
Anyway, please try installing again and extract the installer before running it. Then run MSFS. Do you see the FSUIPC7 splash screen? If so, FSUIPC7 is running.
If not, there may be an issue with your EXE.xml file. Please show me/attach this file, as well as your new InstallFSUIPC7.log file:
C:\Users\jaked\AppData\Roaming\Microsoft Flight Simulator\EXE.xmlAre you running MSFS as admin or as a standard user? If running as admin, you may need to set the FSUIPC7.exe to also be ran as admin (and also all FSUIPC7 clients).
John
-
Again, what aircraft are you using?
I don't see how FSUIPC's aileron calibration can change the display in the attitude indicator. What the calibration will do is adjust the values sent to the FS when you move the aileron axis, so axis positions below the centre will send the negative parameter range (-16384 to 0) and axis positions above the centre will send the positive range (0 - 16384).
Are you sure that you weren't doing something else to configure the attitude indicator?22 minutes ago, h512243512 said:i want the center is a bit shifted to the right for training purpose.
It should be with those settings - have you tried it?
There has been absolutely no change in this area for a very long time. -
5 hours ago, h512243512 said:
but this time whatever center point i set it just stay the same position
Sorry, but what do you mean by this? Do you see the In/Out numbers changing when you move the axis? Are the numbers registered when you press the Set button?
What aircraft are you using, and which aileron axis? Can you also attach your FSUIPC7.ini file please.John
-
8 hours ago, MM said:
Please note that on my setup those additional calls to Simconnect are associated with my running FSUIPC7 v4.12a.
Quote
229765 **** Data not received in required time limit: Re-connecting now...
When I revert to FSUIPC7 v4.11 with a FSUIPC.ini value for DetectToConnectDelayAuto=200, then those many calls are not shown in the FSUIPC.log.What value did auto-tuning set for DetectToConnectDelayAuto? The auto-tuning currently doesn't take into account the re-connections done after a successful open call. One such disconnect message seems to be normal (not sure why - I have raised this with Asobo) and shouldn't cause any issues. However, I will update to take this reconnection into account.
John
-
1
-
-
This all sounds very strange! Re-installing MSFS sounds rather drastic though, especially if your issue is only with the PMDG 737. Not sure what else you can do though, except maybe try Simstaller (freeware) to check for add-on conflicts - see https://parallel42.com/products/simstaller/.
John
-
45 minutes ago, MM said:
However, with the autotuning Beta of FSUIPC7, I now get lots of calls to simconnect that were not there in my previous version of FSUIPC (that is with v4.11 - before or after the manual tuning).
I presume you mean these logged messages:
Quote229765 **** Data not received in required time limit: Re-connecting now...
Such messages are not taken into account when determining the value of the DetectToConnectDelayAuto, ini parameter. This only controls the time between when MSFS detected and when the simconnect open confirmation is received. When this is done, FSUIPC will request initial data (i.e. the user aircraft), and once this initial data has been received, everything will then start. This message indicates that the data from the initial data request was not received in the required time-limit, which is determined by the InitialStallTime ini parameter.
This issue seems to be caused by a SimConnect issue, which I have reported to Asobo (still waiting for a response). It seems that FSUIPC7 is being disconnected from the FS, but no notification or error is received by FSUIPC7, but as it recognises data is stalled, it will close and re-connect. This is why I have decided not to take into account these messages when determining the value for the DetectToConnectDelayAuto ini parameter.
If you have this message logged once, then that should not be an issue. However, if you have this message logged multiple times, you should increase the DetectToConnectDelayAuto time. Looking at you logs, you should try a DetectToConnectDelayAuto setting of 220, or maybe even 240.
There are also performance issues with FSUIPC7 when it is auto-started by MSFS, as it seems to run around 13x slower than when manually started. I have also reported this to MSFS, but for the next release I will change the start-up mechanism so this should not be an issue.
John
Later: you are also having issues with traffic information. You can try increasing the traffic stall time to prevent these, although this will not help (and will degrade performance) if the traffic connection has been terminated. Try adding this to the [General] section of your FSUIPC7.ini file:
TrafficStallTime=2
(the default is 1 second). You can increase further, but if you are still getting those messages then best to remove and allow FSUIPC7 to close and get a new connection.If you are not using the AI traffic information, and are not using any add-ons that use this, then you can ignore. You can also set the following option (to the [General] section of your FSUIPC7.ini file) to disable AI traffic information:
ProvideAIdata=NoJohn
-
Just to close this issue, when using XINPUT devices, such as the xbox one and xbox 360 controllers, input is only recognised by FSUIPC when FSUIPC has the focus. In versions of FSUIPC before FSUIPC7, this will be when the FS has the focus (as FSUIPC is an embedded dll in the FS), but as FSUIPC7 is an external application it will only receive the controller input when it has the focus.
The only way around this is to use an additional program: XInput Plus. This is noted in the README,txt:
QuoteXINPUT devices, such as the XBox One and XBox 360 controllers do not work natively with FSUIPC7.
If you want to use FSUIPC7 with such devices, you will need to install and configure a conversion utility called XInput Plus.
Please see the following tutorial:
https://www.play-old-pc-games.com/compatibility-tools/xinput-plus-tutorial/
It has been reported that the UI for this utility is also now available in English.
Also note that you need to point this utility to the FSUIPC7.exe, not the MSFS.exe.John
-
19 minutes ago, MarcT said:
Sometimes the displayed course at the bottom of SkyDemon shows the course in the simulator.
When it shows this SkyDemon must be connected to the simulator, or at least connect to FSUIPC7.
I cannot help with 3rd party apps, you need to ask on the SkyDemon support forum (presuming there is one).All I can tell you is that most connection issues with 3rd party apps (to FSUIPC7) are due to permissions issues. All applications that connect to FSUIPC7 must be ran at the same privilege level as FSUIPC7. So, if running FSUIPC7 with admin privileges, you must also run SkyDemon with admin privileges, and if running with standard user privileges then SkyDemon must also be ran with standard user privileges and not admin privileges. Please check this, and if you still have issues then report to SkyDemon - I cannot help with this, sorry.
John
-
@Fess_ter It seems that lua scripts (and probably also FSUIPC7) are running approx 13x slower when FSUIPC7 is auto-started by MSFS compared to when it is manually started. This doesn't explain the difference between event.offset for PMDG offsets vs non-PMDG offsets (which is probably due to the data rate, but I will investigate when time permits), but worth knowing if you are having performance issue in your lua scripts.
John
-
The changes in 7.4.11 were minimal - the only change was to change the default value of the InitialStallTime ini parameter that was reduced by too much in 7.4.10 and was causing issues.
The MobiFlight events.txt (that holds the preset definitions) was also updated, but I doubt very much that these presets were changed. The PMDG presets mainly use the PMDG custom control numbers, which also will not have changed. So I have no idea what could cause this. It is also difficult for me to diagnose without seeing your original ini and a log file. So I cannot check what has changed, only if you have any issues with your current configuration. Do you?2 hours ago, Kimchi said:After programming i came back into my PMDG which was started up for engine start and i heard one loud click and the whole cockpit went cold and dark. I loaded the runway cockpit state in the PMDG menu but the buttons still function the wrong way.
Do you get issues every time you use the PMDG 737? If so, please activate logging for Buttons & Keys as well as Events, and show me a log file, together with your ini file again and a description of what you did and what went wrong, and I will take a look.
John
-
46 minutes ago, Mattie941 said:
For those that are interested, SteveFx's suggestion on the AVSIM forum has fixed my CTD issues: https://www.avsim.com/forums/topic/633405-appdll-crash-and-kb5025221/?do=findComment&comment=5039267
That is interesting. Thanks for the update.
John
PMDG 737 offset 0x6568 not displaying correct value
in FSUIPC7 MSFS
Posted
First, note that the gauges display the temperature in Fahrenheit, but the offset holds the temperature in Celsius.
However, there does seem to be an issue. When I start the PMDG 737 I see the offset increase in value from 0 up to around 80, and if I adjust the temperature this can go above 100C!
This is obviously not correct, and should be reported to PMDG.
John