As Pete already stated, The G3D.dll fix was introduced in FSUIPC for FSX-Box and the initial versions of FSX-SE, The latest version of FSX-SE fixes the problem internally within FSX, so FSUIPC no longer needs to do this. It still does though for FSX-Box.

 

Stability Updates:

• Potential causes of the terrain.dll crashes experienced by some users has been corrected. A theoretical deadlock where a game may hang for several minutes before either crashing or being terminated by Windows has been corrected. This is a potential cause of the terrain.dll crashes experienced by some users.
• Some compatibility issues encountered by third party add-ons that use SimConnect have been resolved
• Fixed crash in G3D.dll caused by certain add-ons
• Fixed crashes in UI.dll
• Kneeboards & Checklists now display correctly
• The configuration file AFFINITYMASK value is now correctly calculated for all Core i3, i5 and i7 generation Intel CPUs.

 

Most everyone is well aware of the FSX fix offered awhile back...I mentioned it as a correction from an earlier post. Quite a few of the fixes DTG offered were a result of the improvements they were offering for multiplayer play. The affinity mask in the .cfg is something that isn't even recommended anymore...hasn't been for quite awhile. What's important to realize is that the G3D.dll error in most (if not all) instances was/is caused by 3rd party add-ons (as it's stated above).

 

Most people who have issues with FSX are likely a result of:

 

In this order:

 

1. System set up

 

2. 3rd party development

 

3. FSX itself...code/design

You are still not talking about the memory FSX-SE frees the more you fly which helps with VAS, for example.

Most people who have issues with FSX are likely a result of:

 

In this order:

 

1. System set up

 

2. 3rd party development

 

3. FSX itself...code/design

4. Reading unsupported and unproven advice on the Internet...

You are still not talking about the memory FSX-SE frees the more you fly which helps with VAS, for example.

Do you see an issue with my VAS?...No, not an issue. The issue of VAS being sucked up has several reasons... system stability (OS) & 3rd party add-ons are a great contributor.

 

Here's a look at my log from FSUIPC...I run locked at 20fps with a plethora of add-ons

 

********* FSUIPC4, Version 4.939e by Pete Dowson *********

Reading options from "D:\Flight Simulator X\Modules\FSUIPC4.ini"

Running inside FSX on Windows 7

Module base=5F4C0000

User Name=""

User Addr=""

FSUIPC4 not user registered

WIDEFS7 not user registered, or expired

       47 System time = 24/04/2015 15:35:02

       47 FLT path = "C:\Users\udidwht\Documents\Flight Simulator X Files\"

      343 Trying to connect to SimConnect Acc/SP2 Oct07 ...

      343 FS path = "D:\Flight Simulator X\"

      686 LogOptions=00000000 00000001

      686 --- CONTROLS timer memory location obtained ok

      686 --- SIM1 Frictions access gained

      686 --- FS Controls Table located ok

      686 --- Installed Mouse Macro hooks ok.

      686 --- Wind smoothing fix is fully installed

      686 --- G3D.DLL fix attempt installed ok

      686 SimConnect_Open succeeded: waiting to check version okay

      686 Trying to use SimConnect Acc/SP2 Oct07

     3963 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)

     3963 Initialising SimConnect data requests now

     3963 FSUIPC Menu entry added

     3994 C:\Users\udidwht\Documents\Flight Simulator X Files\Student pilot.FLT

     3994 D:\Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR

    93335 D:\Flight Simulator X\SimObjects\Airplanes\Airbus_A321\Airbus_A321.AIR

   145471 D:\Flight Simulator X\SimObjects\Airplanes\CS_B767-300\B767-300GE.AIR

   269086 System time = 24/04/2015 15:39:31, Simulator time = 15:35:07 (22:35Z)

   270038 Starting everything now ...

   271223 Advanced Weather Interface Enabled

  1894991 Sim stopped: average frame rate for last 1626 secs = 19.5 fps

  1904117 Weather Mode now = Theme

  1904117 C:\Users\udidwht\AppData\Roaming\Microsoft\FSX\Previous flight.FLT

  1939779 System time = 24/04/2015 16:07:21, Simulator time = 15:35:05 (22:35Z)

  1939779 *** FSUIPC log file being closed

Minimum frame rate was 15.3 fps, Maximum was 19.9 fps

Minimum available memory recorded was 1744Mb

Average frame rate for running time of 1626 secs = 19.5 fps

G3D fix: Passes 18752, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 742 Allocs, 742 Freed

********* FSUIPC Log file closed ***********

 

 

3963 Initialising SimConnect data requests now
3963 FSUIPC Menu entry added
3994 C:\Users\udidwht\Documents\Flight Simulator X Files\Student pilot.FLT
3994 D:\Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR
93335 D:\Flight Simulator X\SimObjects\Airplanes\Airbus_A321\Airbus_A321.AIR
145471 D:\Flight Simulator X\SimObjects\Airplanes\CS_B767-300\B767-300GE.AIR
269086 System time = 24/04/2015 15:39:31, Simulator time = 15:35:07 (22:35Z)
270038 Starting everything now ...
271223 Advanced Weather Interface Enabled
1894991 Sim stopped: average frame rate for last 1626 secs = 19.5 fps
1904117 Weather Mode now = Theme
1904117 C:\Users\udidwht\AppData\Roaming\Microsoft\FSX\Previous flight.FLT
1939779 System time = 24/04/2015 16:07:21, Simulator time = 15:35:05 (22:35Z)
1939779 *** FSUIPC log file being closed
Minimum frame rate was 15.3 fps, Maximum was 19.9 fps
Minimum available memory recorded was 1744Mb
Average frame rate for running time of 1626 secs = 19.5 fps
G3D fix: Passes 18752, Null pointers 0, Bad pointers 0, Separate instances 0
Memory managed: 742 Allocs, 742 Freed
********* FSUIPC Log file closed ***********

 

You are right  Addons do make a big difference in how much VAS is used. The ones listed in this log are relatively lite in VAS usage. It would be much different with a PMDG aircraft,. Also I think your example results is a bit skewed. While there is a 28 min duration in system time, sim time is 2 seconds, that tells me you paused the sim, and is not relevant to a full flight which is where you would see the lose of VAS, as FSX does not cleanup the terrain cache between origin and destination, while FSX-SE does.

You are right  Addons do make a big difference in how much VAS is used. The ones listed in this log are relatively lite in VAS usage. It would be much different with a PMDG aircraft,. Also I think your example results is a bit skewed. While there is a 28 min duration in system time, sim time is 2 seconds, that tells me you paused the sim, and is not relevant to a full flight which is where you would see the lose of VAS, as FSX does not cleanup the terrain cache between origin and destination, while FSX-SE does.

There was no pause during that run. I ran another instance later using the VRS and averaged 19.8 with a high of 26.8 and low of 19.3. That was a run of ~ 30 mins.

 

I'm not one to sit for hours between destinations. The implications of ones health are horrendous.

I started this thread for one reason - I was really excited on how well FSX:SE performed and just wanted to express my findings. I was previously very sceptical to what was said about the SE version, considering its 99% the same game.

 

When it comes to VAS usage, FSX:SE is superior contrary to default FSX and P3D,