Silly question Fsdream KLAX is one of those 3rd party airports with high vas values?..seems to me that neither KSFO or KLAX are friendly vas at all with any settings in P3D..

Thanks

one mere question does lighting HDR have any mayor impact in VAS.....?

I'm also experiencing less VAS problems with v2.5 than with v2.4. However, Prepar3d still does a mediocre job in freeing up memory that isn't used any more. The other night, I did a flight from EDDF to SBGR using Aerosoft EDDF and Orbx openLC Europe, FTX Global and Vector. After starting the flight in EDDF with a solid 1.4 Gb of free VAS, free VAS decreased to 800 Mb over the Atlantic Ocean near Madeira. I saved the flight and restarted P3D. Boom. Free VAS back up to 1.4 Gb. So there seem to be a lot of things which are kept in memory that are not needed anymore. Even though 64 bit is certainly the way to go, much improvement could still be made if 32 bit P3D had better memory management.

 

 

So there seem to be a lot of things which are kept in memory that are not needed anymore.

 

Have you ran the same test without any Add-ons?  I've done flights over the Atlantic and my "free" VAS will increase not decrease when over the Ocean.  When I get close to land I will see the free VAS decrease again ... in my case only 200MB used up for the entire flight (started at 2.5GB used VAS and ended at 2.7 GB used VAS).

 

Problem that I've see with folks testing this is that once they get all the Add-ons installed, they rarely go back and wipe and re-test the same flight without add-ons.  I think this is an important step so that we can gauge how add-ons are or are not impacting VAS over time.

 

Cheers, Rob.

Does anyone know if AlwaysFullLoad=1 is still needed in 2.5?

How do you save flight and restarted the P3D.

 

I tried  saved flights and restarted the P3D,  777 was not stable to fly. Specially rudder rapidly  turning left and right, result P3D CTD.

 

 

Does anyone know if AlwaysFullLoad=1 is still needed in 2.5?

 

No, shouldn't need it ... however, with that said best practice to conserve VAS still remains:

 

1.  Goto departure location

2.  Select aircraft of choice

3.  Select time/season

4.  Set weather to clear

5.  Save flight

6.  Exit P3D

7.  Double click the Saved flight .fxml file (associate it with Prepar3D.exe if not already)

8.  Go fly

 

You can try setting this in your Prepar3d.cfg if you do a lot of view switching: 

 

[Terrain]

UseGlobalTerrainView=True

 

 

By default, every camera has its own terrain view which requests texture and dem tiles near the camera to ensure that all cameras get a quality view of terrain. When tessellation is enabled, it is possible for cameras to share data and avoid the extra work required to manage multiple terrain views. For multi-view scenarios in which all views are near each other, it may be desirable to have views simply render the terrain tiles loaded by the default view. Setting this option to True will prevent all camera from creating a terrain view except for the default 3d view. This can help avoid texture flashing and terrain spikes that occur on some systems with multiple views and/or multiple video cards. This value can be overridden by the UseGlobalTerrainView entry in a given CameraDefinition allowing each camera to determine whether or not to create a terrain view. This setting will be engorged if Tessellation is not enabled.

 

I think there was a little typo at the end there "engorged" ... haha ... think LM mean "ignored" ... at least I hope they do!

 

Cheers, Rob.

 

 

777 was not stable to fly. Specially rudder rapidly  turning left and right,

 

You have a device controller conflict ... bring up the controllers in P3D and make sure the AXES for each controller is not being shared by another controller device.  In your case make sure rudder AXES assignment is only showing up as assigned once for that controller and not assigned with other controllers.

 

Controller assignments don't case CTD, so if you're having CTDs then you've got other hardware issues you need to resolve that are not related to P3D.

 

Cheers, Rob.

Rob,

Thanks conflict controller problem solved  removed shared AXES assignment.

Now I have a different problem. I cannot load saved flight  to P3D. When I clink the Load, some other PMDG 777 flight is appearing.

Here is how I saved the flight.

 

http://imageshack.com/a/img910/5301/fnHx0W.jpg

Rob,

Thanks conflict controller problem solved  removed shared AXES assignment.

Now I have a different problem. I cannot load saved flight  to P3D. When I clink the Load, some other PMDG 777 flight is appearing.

Here is how I saved the flight.

 

http://imageshack.com/a/img910/5301/fnHx0W.jpg

Ahmet - I noticed that the file you highlighted has a double ".fxml.fxml" extension.  That just might cause a problem.  Suggest you go to your "...\Documents\Prepar3D v2" folder and change the file names to remove the duplicated file extension and see if that helps.

 

In the future when you save a flight in P3D there's no need to add the file extension to the name.  Just type the name you'd like to use (e.g., KEWR-SPIM) and the program will add the appropriate extension.

Doug, Thanks :smile:

Did some stress test this weekend (at least on sunday as saturday was a hell nailing down issues ) and VAS is indeed better than i have seen before. Maybe it has something to do with the latest hotfix (12944) or maybe placebo because of the NGX?

 

Anyway , i have cranked most sliders up to Ultra but leaving Building Autogen on Normal and TML at 1024 and i see at least 200-250mb diff between the NGX and the PMDGT7.(which should be expected)

 

I dont have Vector installed yet but holding back as it takes up 200-250mb of VAS. 

 

Sitting at Flytampa EKCH C37 with the NGX i am at 2.8-2.9GB and with the T7 i am at 3.1-3.2GB VAS. FTXOLC-EU,Global

 

This is great . LOD did not impact which i found a little mysterious. Have to test some more

 

Did a 3 hour flight between KMCO-MMMX in the 737 with same settings and VAS was between 2.8-3.3GB (without FS2CREW)

 

REX 512 clouds , RAAS disabled in the dll.xml

 

Could Tesselation set on Ultra decrease VAS use ?

 

Michael Moe

 

 

This is great . LOD did not impact which i found a little mysterious. Have to test some more

 

I can confirm most of your findings but not this one. In a populated area LOD certainly makes a difference. From my experience it can be as much as 100 Mb or even more per step increase of the LOD slider. In less populated areas LOD makes less of a difference (but it still makes a difference).

I can confirm most of your findings but not this one. In a populated area LOD certainly makes a difference. From my experience it can be as much as 100 Mb or even more per step increase of the LOD slider. In less populated areas LOD makes less of a difference (but it still makes a difference).

 

ok thanks , must be something on my setup. Will try tonight with a saved approach to MMMX RNAV05R cranking LOD and Autogen for buildings up to max to see differencies.

 

Michael moe

Rob,Hi

 

1-Shared AXES problem is back. When I open the Saved Flight,  PMDG 777 ruder rapidly turning left and right.

 

In AXES control settings>CH ECLIPSE YOKE> Throttle axis>Z Axis 

IN AXES control settings>CH PRO PEDALS USB>Z Axis

 

How can I assign different AXIS to PEDALS or vise versa to Throttle? :unsure:

 

2-When Saved Flight loaded I realized FMC data is no longer saved? Is it possible to save FMC data in Saved Flight? :unsure:

 

Regards