Page 1 of 1

The End Of Oom Issue With Conc ?

Posted: Sun Mar 16, 2014 12:45 am
by OAL109 Mike Ionas
Just adding some pictures for the article at FSLabs forum.

The resolution is 1920x1200x32 and the setting are a copy paste from Kosta's guide (with the exception of the LOD Radius that is left to 4.5).

I usually run FSX full screen but for the shake of these screenshots I left it at window mode (there is no significant change between the modes).

Initial screenshots from Athens where the VAS where usually at ~3.2GB after loading the CONC.
VAS-2014-mar-15-001.jpg
VAS-2014-mar-15-002.jpg
VAS-2014-mar-15-003.jpg
The following screenshots are from Heathrow. Up to last week I wouldn't dare go around Heathrow with VAS at the range of ~3.8GB just by showing up at the airport with the CONC.
VAS-2014-mar-15-004.jpg
VAS-2014-mar-15-005.jpg
VAS-2014-mar-15-006.jpg
VAS-2014-mar-15-007.jpg

Re: The End Of Oom Issue With Conc ?

Posted: Sat Mar 22, 2014 10:29 pm
by OAL714 Jean-Louis Leborne
Bonjour Mike,

Saw your related interesting article on the FSLabs forum. Could you please tell me (us ?), make it short if possible, how important VAS (Virtual Address Space, am I right ?) is to avoid OOMs and the rest ?

I've hardly experienced OOM flying Concorde in window mode (full screen mode is not my preference and, AFAIK, it's not recommended with Concorde_X)

I'm currently using the latest driver 335.23 on my nVidia 660

Merci

Re: The End Of Oom Issue With Conc ?

Posted: Sun Mar 23, 2014 9:13 am
by OAL109 Mike Ionas
Hello Jean-Louis,

You can read this short article by Kosta regarding the VAS usage in FSX.

Regards,

Re: The End Of Oom Issue With Conc ?

Posted: Mon Mar 31, 2014 3:42 pm
by OAL269 Kyprianos Biris
By using FSDT KJFK v2.1 and UK2000 EGLL v3 with the ConcordeX apart from the new drivers making it possible to enjoy now both sceneries without OOM I found something else in the process.

For some reason I had 4096 set in TML of FSX.CFG.
[GRAPHICS]
TEXTURE_MAX_LOAD=2048
I always thought Concorde needed it when in fact it needs 2048.
Only if we have 1024 it generates the pop up for 2048.

I changed it and memory use is even better at JFK !

Relevant post in FSDT forum.

The interesting part is that even if an airport has high res. textures the 2048 will limit them to lower resolution and consume less memory.
This is something I did not know.

OOM's no more for sure and by safe(ish) distance ! ;D

Re: The End Of Oom Issue With Conc ?

Posted: Fri Sep 12, 2014 6:03 pm
by OAL269 Kyprianos Biris
Mike in windows7 update I see an optional update:
NVidia - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3 - NVIDIA GeForce GTX 660 Ti

Is this an update in drivers ?
I don't want to risk getting rid of v335.23 and loosing that nice memory management :D

Re: The End Of Oom Issue With Conc ?

Posted: Sat Sep 13, 2014 11:27 am
by OAL109 Mike Ionas
I also have this update but have been reluctant to install it. I haven't performed any GPU driver updates after 335.23 (which I saved also somewhere for safekeeping ;) ). All I know about WDDM is what I can find in wikipedia.

However at some point we will have to experiment with newer drives as nVidia might have implemented more improvements.

Btw, do you remember if increasing screen resolution has an impact on VAS?

Re: The End Of Oom Issue With Conc ?

Posted: Sat Sep 13, 2014 3:42 pm
by OAL269 Kyprianos Biris
I have never touched the resolution since day 1 and ain't planning on experimenting ;-)

Re: The End Of Oom Issue With Conc ?

Posted: Sat Sep 13, 2014 4:37 pm
by OAL109 Mike Ionas
But when you get a new monitor with higher native resolution.. you are forced to experiment..

Re: The End Of Oom Issue With Conc ?

Posted: Thu Jan 08, 2015 10:59 pm
by OAL269 Kyprianos Biris
810309 wrote:Mike in windows7 update I see an optional update:
NVidia - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.2, Graphics Adapter WDDM1.3 - NVIDIA GeForce GTX 660 Ti

Is this an update in drivers ?
I don't want to risk getting rid of v335.23 and loosing that nice memory management :D
I updated to WDDM adapters via Windows7 Update and updated the NVidiaInspector and the elevator & aileron axis of the joystick was not being recognized.

I then updated via the GeForce application to latest 347.09 and all is well.