Jump to content
The simFlight Network Forums

Recommended Posts

Posted

I found that sometimes the wind smoothing feature causing problem when landing:

The wind sometimes kept unchanged when descending from 3000 ft to the ground level. It would be grateful if you can fix the problem soon.

The software used:

FSX-steam editon

Windows 10 Home

No other weather software is installed

Posted
1 hour ago, ccy777 said:

I found that sometimes the wind smoothing feature causing problem when landing:

The wind sometimes kept unchanged when descending from 3000 ft to the ground level. It would be grateful if you can fix the problem soon.

The software used:

FSX-steam editon

Windows 10 Home

No other weather software is installed

Sorry, I cannot reproduce any similar problem. Also, FSUIPC is never checking the altitude, so the altitude part isn't really relevant.

Possibly when you are nearing the airport something is getting overloaded and preventing some of the SimConnect actions being requested. Check the Log to see if any problems are reported.

Quite honestly, I cannot change any code related to weather at this stage. It's been the way it is now for 10 years and I'm likely to do more harm than good making any changes at all in this area.

Pete

 

Posted

Here is the FSUIPC log file:

Quote

********* FSUIPC4, Version 4.957b (26th September 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
fsx.exe version = 10.0.62615.0
Reading options from "D:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 8.0 or later
Module base=55BE0000
User Name="*******"
User Addr="********"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       46 System time = 29/10/2016 19:41:01
       46 FLT path = "C:\Users\Billy\Documents\Flight Simulator X Files\"
       62 ------ Module Version Check ------
       62        acontain.dll: 10.0.62615.0
       62             api.dll: 10.0.62615.0
       62        controls.dll: 10.0.62615.0
       78      fs-traffic.dll: 10.0.62615.0
       78             G3D.dll: 10.0.62615.0
       78        language.dll: 10.0.62615.0
       93            sim1.dll: 10.0.62615.0
       93        visualfx.dll: 10.0.62615.0
       93         weather.dll: 10.0.62615.0
      109          window.dll: 10.0.62615.0
      109 ----------------------------------
      140 Trying to connect to SimConnect Steam ...
      187 FS path = "D:\Program Files (x86)\Steam\steamapps\common\FSX\"
      343 ---------------------- Joystick Device Scan -----------------------
      343 Product= Saitek X52 Flight Control System
      343    Manufacturer= Saitek
      343    Vendor=06A3, Product=075C (Version 1.16)
      343    Serial Number= Saitek
      343 -------------------------------------------------------------------
      390 LogOptions=00000000 00000001
      406 -------------------------------------------------------------------
      406 ------ Setting the hooks and direct calls into the simulator ------
      406 --- CONTROLS timer memory location obtained ok
      406 --- SIM1 Frictions access gained
      406 --- FS Controls Table located ok
      406 --- Installed Mouse Macro hooks ok.
      406 --- Wind smoothing fix is fully installed
      406 --- SimConnect intercept for texts and menus option is off
      406 --- All links checked okay
      406 -------------------------------------------------------------------
      406 SimConnect_Open succeeded: waiting to check version okay
      406 Trying to use SimConnect Steam
      406 Opened separate AI Traffic client okay
     4156 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
     4156 Initialising SimConnect data requests now
     4156 FSUIPC Menu entry added
     4187 c:\users\billy\documents\flight simulator x files\TEst.FLT
     4187 D:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\POSKY Boeing 777-200 FSX\Boeing 777-200-PW4074.air
    11046 Weather Mode now = Theme
    23250 C:\Users\Billy\Documents\Flight Simulator X Files\IFR Chiang Kai Shek Intl to Hong Kong Intl.PLN
    23250 Weather Mode now = Custom
    23250 c:\users\billy\documents\flight simulator x files\temp.FLT
    71609 Aircraft="Boeing 777-200-PW4074 Project Opensky Japan Airlines OC"
    71625 System time = 29/10/2016 19:42:13, Simulator time = 15:55:02 (07:55Z)
    74781 Starting everything now ...
    92359 Advanced Weather Interface Enabled
  3708296 **** Restarting traffic scanning due to non-reception ****
  6622546 Sim stopped: average frame rate for last 6548 secs = 21.8 fps
  6622546              Max AI traffic was 115 aircraft
  6672625 Sim stopped: average frame rate for last 29 secs = 8.3 fps
  6672625              Max AI traffic was 115 aircraft
  6684781 C:\Users\Billy\Documents\Flight Simulator X Files\IFR Chiang Kai Shek Intl to Hong Kong Intl.PLN
  6684781 C:\Users\Billy\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
  6703421 C:\Users\Billy\Documents\Flight Simulator X Files\IFR Chiang Kai Shek Intl to Hong Kong Intl.PLN
 

 

Posted

The FSUIPC when the the wind smooth feature operate normally.

Quote

********* FSUIPC4, Version 4.957b (26th September 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
fsx.exe version = 10.0.62615.0
Reading options from "D:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 8.0 or later
Module base=55610000
User Name="****"
User Addr="******"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       47 System time = 30/10/2016 10:12:11
       47 FLT path = "C:\Users\Billy\Documents\Flight Simulator X Files\"
       63 ------ Module Version Check ------
       63        acontain.dll: 10.0.62615.0
       78             api.dll: 10.0.62615.0
       78        controls.dll: 10.0.62615.0
       78      fs-traffic.dll: 10.0.62615.0
       78             G3D.dll: 10.0.62615.0
       94        language.dll: 10.0.62615.0
       94            sim1.dll: 10.0.62615.0
       94        visualfx.dll: 10.0.62615.0
      109         weather.dll: 10.0.62615.0
      109          window.dll: 10.0.62615.0
      109 ----------------------------------
      547 Trying to connect to SimConnect Steam ...
      609 FS path = "D:\Program Files (x86)\Steam\steamapps\common\FSX\"
      766 ---------------------- Joystick Device Scan -----------------------
      766 Product= Saitek X52 Flight Control System
      766    Manufacturer= Saitek
      766    Vendor=06A3, Product=075C (Version 1.16)
      766    Serial Number= Saitek
      766 -------------------------------------------------------------------
      813 LogOptions=00000000 00000001
      828 -------------------------------------------------------------------
      828 ------ Setting the hooks and direct calls into the simulator ------
      828 --- CONTROLS timer memory location obtained ok
      828 --- SIM1 Frictions access gained
      828 --- FS Controls Table located ok
      828 --- Installed Mouse Macro hooks ok.
      828 --- Wind smoothing fix is fully installed
      828 --- SimConnect intercept for texts and menus option is off
      828 --- All links checked okay
      828 -------------------------------------------------------------------
      828 SimConnect_Open succeeded: waiting to check version okay
      828 Trying to use SimConnect Steam
      828 Opened separate AI Traffic client okay
     6125 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
     6125 Initialising SimConnect data requests now
     6125 FSUIPC Menu entry added
     6156 c:\users\billy\documents\flight simulator x files\TEst.FLT
     6156 D:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\POSKY Boeing 777-200 FSX\Boeing 777-200-PW4074.air
    13922 Weather Mode now = Theme
    22109 Weather Mode now = Real World
    83969 Weather Mode now = Custom
   127750 C:\Users\Billy\Documents\Flight Simulator X Files\IFR Hong Kong Intl to Chiang Kai Shek Intl.PLN
   149906 System time = 30/10/2016 10:14:41, Simulator time = 07:55:00 (00:55Z)
   149922 Aircraft="Boeing 777-200-PW4074 Project Opensky JAS Rainbow Seven YU JA007D"
   218156 Starting everything now ...
   218984 Advanced Weather Interface Enabled
  7393313 Sim stopped: average frame rate for last 7178 secs = 20.6 fps
  7393313              Max AI traffic was 117 aircraft
  7402125 C:\Users\Billy\Documents\Flight Simulator X Files\IFR Hong Kong Intl to Chiang Kai Shek Intl.PLN
  7402125 C:\Users\Billy\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
  7414875 System time = 30/10/2016 12:15:46, Simulator time = 10:54:19 (02:54Z)
  7414875 *** FSUIPC log file being closed
Minimum frame rate was 6.5 fps, Maximum was 30.0 fps
Minimum available memory recorded was 1647Mb
Average frame rate for running time of 7179 secs = 20.6 fps
Maximum AI traffic for session was 117 aircraft
Memory managed: 6458 Allocs, 6458 Freed
********* FSUIPC Log file closed ***********

 

Posted
6 hours ago, ccy777 said:

Here is the FSUIPC log file:

It isn't complete! What happened, did FS hang? I always need to see the complete log -- there's important and relevant information in the summaries at the end, after close down.

And here's evidence of very poor performance here:

 3708296 **** Restarting traffic scanning due to non-reception ****

and here:

 6672625 Sim stopped: average frame rate for last 29 secs = 8.3 fps

Your second log, which was complete shows no symptom of poor performance.

Pete

 

Posted
4 hours ago, Pete Dowson said:

It isn't complete! What happened, did FS hang? I always need to see the complete log -- there's important and relevant information in the summaries at the end, after close down.

 

 

After viewing the Windows 10 log, I found that the following 2 errors occur:

Quote
System
   
- Provider
      [ Name] Application Error
   
- EventID 1000
      [ Qualifiers] 0
   
  Level 2
   
  Task 100
   
  Keywords 0x80000000000000
   
- TimeCreated
      [ SystemTime] 2016-10-29T13:32:48.341314400Z
   
  EventRecordID 9344
   
  Channel Application
   
  Computer FUJITSU-LAPTOP
   
  Security
- EventData
      fsx.exe
      10.0.62615.0
      559f9a9a
      MSVCR80.dll
      8.0.50727.9268
      573d297f
      c000000d
      00008aa0
      f5c
      01d231d94a3b93ca
      D:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
      C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll
      a11d2be0-5757-4e25-87d3-55b61b37a1c4
       
       
Quote
System
   
- Provider
      [ Name] Windows Error Reporting
   
- EventID 1001
      [ Qualifiers] 0
   
  Level 4
   
  Task 0
   
  Keywords 0x80000000000000
   
- TimeCreated
      [ SystemTime] 2016-10-29T13:32:50.713733700Z
   
  EventRecordID 9345
   
  Channel Application
   
  Computer FUJITSU-LAPTOP
   
  Security
- EventData
      116195563685
      5
      BEX
      Unavailable
      0
      fsx.exe
      10.0.62615.0
      559f9a9a
      MSVCR80.dll
      8.0.50727.9268
      573d297f
      00008aa0
      c000000d
      00000000
       
      \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER5D80.tmp.WERInternalMetadata.xml
      C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_94cc41e1ce628b8b12539488a3ca148447b433_a37f3a76_12106427
       
      0
      a11d2be0-5757-4e25-87d3-55b61b37a1c4
      0
      eb6775e99c1a9e55eeb6f44a4bcf4073

 

Posted
17 minutes ago, ccy777 said:

After viewing the Windows 10 log, I found that the following 2 errors occur:

Ah, so there was definitely a crash -- they both refer to the same incident. If this happens often I think you will need to try and find which add-on s responsible. The module MSVCR80.DLL is used by FS itself and many other programs, so it could be almost anything -- or it could simply be a memory problem. It is known that some crashes can occur because of memory shortage problems as VAS gets used up.

However, looking back at the FSUIPC log, the date matches to that of the recorded crash, but not the time:

11 hours ago, ccy777 said:

System time = 29/10/2016 19:41:01

So I think the FSUIPC log does relate to a hang rather than a crash -- which won't be recorded in the Event logs.

Pete

 

 

Posted
1 hour ago, Pete Dowson said:

Ah, so there was definitely a crash -- they both refer to the same incident. If this happens often I think you will need to try and find which add-on s responsible. The module MSVCR80.DLL is used by FS itself and many other programs, so it could be almost anything -- or it could simply be a memory problem. It is known that some crashes can occur because of memory shortage problems as VAS gets used up.

However, looking back at the FSUIPC log, the date matches to that of the recorded crash, but not the time:

So I think the FSUIPC log does relate to a hang rather than a crash -- which won't be recorded in the Event logs.

Pete

 

 

In the Windows event log, the time is UTC time while in FSUIPC log, the time is local time.

The crash of MSVCR80.dll is after the hang of FSUIPC

I think the crash of MSVCR80.DLL occurred when I quit FSX.

Posted

Here is another logs show the error.

********* FSUIPC4, Version 4.957b (26th September 2016) by Pete Dowson *********
Windows version reported as 6.2.?.9200
fsx.exe version = 10.0.62615.0
Reading options from "D:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 8.0 or later
Module base=535B0000
User Name="*****"
User Addr="*****"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       63 System time = 05/11/2016 10:05:59
       63 FLT path = "C:\Users\Billy\Documents\Flight Simulator X Files\"
       79 ------ Module Version Check ------
       79        acontain.dll: 10.0.62615.0
       94             api.dll: 10.0.62615.0
       94        controls.dll: 10.0.62615.0
      110      fs-traffic.dll: 10.0.62615.0
      110             G3D.dll: 10.0.62615.0
      110        language.dll: 10.0.62615.0
      110            sim1.dll: 10.0.62615.0
      125        visualfx.dll: 10.0.62615.0
      125         weather.dll: 10.0.62615.0
      125          window.dll: 10.0.62615.0
      125 ----------------------------------
      563 Trying to connect to SimConnect Steam ...
      641 FS path = "D:\Program Files (x86)\Steam\steamapps\common\FSX\"
      813 ---------------------- Joystick Device Scan -----------------------
      813 Product= Saitek X52 Flight Control System
      813    Manufacturer= Saitek
      813    Vendor=06A3, Product=075C (Version 1.16)
      813    Serial Number= Saitek
      813 -------------------------------------------------------------------
      875 LogOptions=00000000 00000001
      875 -------------------------------------------------------------------
      875 ------ Setting the hooks and direct calls into the simulator ------
      875 --- CONTROLS timer memory location obtained ok
      875 --- SIM1 Frictions access gained
      891 --- FS Controls Table located ok
      891 --- Installed Mouse Macro hooks ok.
      891 --- Wind smoothing fix is fully installed
      891 --- SimConnect intercept for texts and menus option is off
      891 --- All links checked okay
      891 -------------------------------------------------------------------
      891 SimConnect_Open succeeded: waiting to check version okay
      891 Trying to use SimConnect Steam
      891 Opened separate AI Traffic client okay
     6938 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
     6938 Initialising SimConnect data requests now
     6938 FSUIPC Menu entry added
     6969 c:\users\billy\documents\flight simulator x files\TEst.FLT
     6969 D:\Program Files (x86)\Steam\steamapps\common\FSX\SimObjects\Airplanes\POSKY Boeing 777-200 FSX\Boeing 777-200-PW4074.air
    16907 Weather Mode now = Theme
    27313 Weather Mode now = Real World
   277313 Weather Mode now = Custom
   357829 C:\Users\Billy\Documents\Flight Simulator X Files\IFR Hong Kong Intl to Chiang Kai Shek Intl.PLN
   487860 Aircraft="Boeing 777-200-PW4074 Project Opensky JAS Rainbow Seven YU JA007D"
   487860 System time = 05/11/2016 10:14:07, Simulator time = 07:55:00 (00:55Z)
   495829 Starting everything now ...
   496500 Advanced Weather Interface Enabled
  1680047 **** Restarting traffic scanning due to non-reception ****
  6877797 Sim stopped: average frame rate for last 6386 secs = 22.6 fps
  6877797              Max AI traffic was 114 aircraft
  7681797 Sim stopped: average frame rate for last 801 secs = 12.5 fps
  7681797              Max AI traffic was 31 aircraft
  7691735 C:\Users\Billy\Documents\Flight Simulator X Files\IFR Hong Kong Intl to Chiang Kai Shek Intl.PLN
  7691735 C:\Users\Billy\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
  7704500 System time = 05/11/2016 12:14:24, Simulator time = 10:53:54 (02:53Z)
  7704500 *** FSUIPC log file being closed
Minimum frame rate was 6.9 fps, Maximum was 30.0 fps
Minimum available memory recorded was 1604Mb
Average frame rate for running time of 7188 secs = 21.4 fps
Maximum AI traffic for session was 114 aircraft
Memory managed: 6442 Allocs, 6442 Freed
********* FSUIPC Log file closed ***********

 

Posted
5 hours ago, ccy777 said:

Here is another logs show the error

I'n not sure why or where you think it shows your 'error', but what I do see is again signs of SimConnect slowing or stopping:

5 hours ago, ccy777 said:

1680047 **** Restarting traffic scanning due to non-reception ****

So again, it's performance. something is clobbering the interface being used between FSUIPC and SimConnect.

Please refer back to my ealrier replay with the same diagnosis.

Pete

 

Posted
1 hour ago, Pete Dowson said:

I'n not sure why or where you think it shows your 'error', but what I do see is again signs of SimConnect slowing or stopping:

So again, it's performance. something is clobbering the interface being used between FSUIPC and SimConnect.

Please refer back to my ealrier replay with the same diagnosis.

Pete

 

It is a good idea to increase the "weather read interval factor"?

Posted
9 minutes ago, ccy777 said:

It is a good idea to increase the "weather read interval factor"?

I don't think that will make much difference.

Sorry I'm not much help here. The code to do wind smoothing in FSUIPC is now very old.

I know it is ONLY related to the wind being now set and the wind as it was before. It simply stops the wind being set reaching the Simulation code directly, but allows the change in increments.

None of it has anything whatsoever to do with location, altitude, airspeed, or any things else. It is just concerned with those two values -- wind speed and wind direction.

If you want to delve deeper into what is happening, you could try enabling Logging of the smoothing actions. You do this by adding

TestOptions=x4000

to the [General] section of the INI file before loading FS. I warn you, the log will get large and it might not be easy to work out what is happening. If you do this AND manage to isolate the portion of the log which you think indicates something wrong, then by all means show me that section (only0 and I will help interpret it. But I still won't necessarily be able to help.

Really, 99% of the the weather-related facilities in FSUIPC have fallen by the wayside with the advent of much more sophisticated and excellent working systems such as those from Active Sky -- which I can thoroughly recommend. In fact any of the forefront weather programs will do better than anything in FSUIPC, simply because the FSUIPC facilities were a stop-gap, a measure originally taken back in FS2002 when there were lots of Weather problems, continuing on to FS2004. FSX looked better but still had a nasty 180 degree switching of winds in some areas of the world (most notably central western Europe, and near Chicago in the USA, but there were others). This was caused by incorrect triangulation of weather interpolation areas (interpolation is performed in FS from the supposedly nearby weather stations, but sometimes one of the three was many hundreds of miles away with very different weather settings).

Anyway, the position now regarding weather features in FSUIPC is that they are pretty much disused in favour of the add-on weather program control, and the code is so old and convoluted I'm not in a position to change it.  (EXCEPT perhaps to rip it all out, which I should probably have done a while back).

Pete

 

Posted

I found that the reason may be the language setting in Windows.

After I change the language setting from Chinese (Hong Kong) to English (US), the wind smooth function seems works better, but still need more experiment

It may be due to the following reason,

In Chinese, Korean and Japanese computing, some ASCII special characters cannot be handled correctly because clash between the ASCII and the coding system used in Chinese, Korean or Japanese 

Posted
On 2016/11/6 at 8:33 PM, Pete Dowson said:
How strange! I don't know how any ASCII characters, special or otherwise come into it.  Please keep me informed.
 
Pete
 

Finally, I found that the reason is not ASCII character issue, is the "supress wind varation" and "supress gust wind" function. If I selected both function, the wihnd smooth function works perfectly. Is it because that I fly into mountain region where the FSX cannot determine the correct surface altitude?

Posted
1 hour ago, ccy777 said:

Is it because that I fly into mountain region where the FSX cannot determine the correct surface altitude?

It might be that FSX is indeterminate between surface wind and the first upper layer, but really it shouldn't affect the wind smoothing.

I suppose it is possible that the wind variation nd gust changes are somehow compensating for or acting against the slow changes which the wind smoother would normally be allowing.

Pete

 

  • 3 months later...
Posted

Recently, I found another interesting problem: Sometimes, there is still sudden wind shift at high altitude when climbing.

If I change the WeatherReadFactor and WeatherRewriteSeconds parameters, the wind shift problem also changes. Is it due to the SimConnect problem?

 

Posted
57 minutes ago, ccy777 said:

If I change the WeatherReadFactor and WeatherRewriteSeconds parameters, the wind shift problem also changes. Is it due to the SimConnect problem?

Very probably. Really most of the bad wind errors in FS9 and continued in FSX cannot be compensated for with minor fiddles. They need overriding using direct control, which is what Active Sky does so well.

Pete

 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.