I have an I5-2500K overclocked to 4.5 and its quite the workhorse like that. Have a great case and keep system cool, and with FSX running it never got much warmer than 34c inside the case. CPU stays around 48-53c. 

Running p3d, it was pretty good. Adding weather and loading a lot of graphics then became somewhat of a bottleneck, so i sold my 660 (which wasnt too bad at all) but found a super deal and got a 770 for 120$ net of my 660.  It made a huge difference from the 660. Vas is not a threat. Just monitor it. Dont need hi res clouds. 

Wilailuk you remind me a bit like ex member summer1, your "Turn your sliders down" advice seems very familiar. Anyone else agree?

Forget it! Moving on.  I apologize to everyone for going straight for the flame bait.

@styckx: 

 

Why is that "pompous" ? - and I really don´t frown, it´s just a matter of fact IMO.

 

http://forum.avsim.net/topic/415988-haswell-i7-4770k-vs-i7-920-960-bloomfeld/page-2

 

Upgrade is needed, i5 is what? - 3 year old tech now?

 

Pure nonsense. Three year old tech means nothing with an eight year old architecture. Everyone needs to understand that the 32bit VAS limitation is a BIG problem that cannot be fixed by MS, LM or ******* Christ himself.

 

The time for 64bit flight simulation has come, and I think I am holding out my P3D purchase until they address this.

 

 

Or am I confusing things?

Only slightly. A32-bit application on 64-bit Windows has maximum of 4 Gb of virtual Address space (VAS), no matter how much physical RAM is installed. OOMs occur when all that 4 GB is used.

 

To quote Mark Russinovich (Microsoft's memory expert)

 

"There is NO (well, almost no) connection between virtual memory and physical memory"

Someone accused someone else of having Meigs syndrome. Proudly Guilty!!!

 

 

Now this error may be due to OpusFSX (adding too much clouds maybe? Or perhaps OpusFSX is buggy?) but still... this is a big show stopper, of course. If going Back to reality brings me Back to hell... I am losing hope fast. Never ever had this in FSX.

 

I wonder if the problem lies with OpusFSX. They were pretty quick to jump on the P3d "bandwagon" and after all, (like the long-standing FSX version), it is still just a beta.

 

Why don't you try the weather generator pinned above as a starting point. I must admit I haven't at this stage as I am waiting for FSGRW which takes the more simplistic approach and deals purely with weather and, more importantly, without making too many changes to the underlying platform. I could well be wrong but I suspect that Opus is too complicated for its own good at this stage.

 

Just thoughts and I might be very wrong here.

Why don't you try the weather generator pinned above as a starting point.

 

I even get OOM's when I don't use a weather engine but load one of the presets and 'make it heavy'.  Somehow those clouds push P3D over the edge. So this makes you think, just like a lot of others already posted, what happens if you add more 'heavy' things. As I said I only use REX clouds at 512x512 so if that already brings P3D to its knees... then there isn't much hope for the future unless LM finds a way to address this (which I thought they already did btw).

 

BTW My GPU has 1.5 GB VRAM. If I get a GPU with at least 3 GB will that make a difference...? Are things that don't fit into my GPU's 1.5 GB now handled by the PC's RAM? Does that add up? Or do certain things only go to the VRAM and other things to the RAM (if you know what I mean)? If the latter is true even getting a GPU with 12 GB VRAM wouldn't make a difference as longs as that 4 GB RAM limit exists.

I even get OOM's when I don't use a weather engine but load one of the presets and 'make it heavy'. Somehow those clouds push P3D over the edge. So this makes you think, just like a lot of others already posted, what happens if you add more 'heavy' things. As I said I only use REX clouds at 512x512 so if that already brings P3D to its knees... then there isn't much hope for the future unless LM finds a way to address this (which I thought they already did btw).

 

BTW My GPU has 1.5 GB VRAM. If I get a GPU with at least 3 GB will that make a difference...? Are things that don't fit into my GPU's 1.5 GB now handled by the PC's RAM? Does that add up? Or do certain things only go to the VRAM and other things to the RAM (if you know what I mean)? If the latter is true even getting a GPU with 12 GB VRAM wouldn't make a difference as longs as that 4 GB RAM limit exists.

One of the things I have done is try the majority (not all) the preset weather settings. On my system they didn't have much of an impact FPS wise and I haven't had a single OOM yet! Again, during these test I was randomly checking my vas usage which was within limits. I only have one addon airport and no scenery loaded yet so all this is on default P3D. If you know of a default situation that causes you issues I can try it and monitor vas to do comparisons. Also most of the time I was checking the weather was during the time I had my system as maxed out as I can sensibly use it.

I even get OOM's when I don't use a weather engine but load one of the presets and 'make it heavy'.  Somehow those clouds push P3D over the edge. So this makes you think, just like a lot of others already posted, what happens if you add more 'heavy' things. As I said I only use REX clouds at 512x512 so if that already brings P3D to its knees... then there isn't much hope for the future unless LM finds a way to address this (which I thought they already did btw).

 

BTW My GPU has 1.5 GB VRAM. If I get a GPU with at least 3 GB will that make a difference...? Are things that don't fit into my GPU's 1.5 GB now handled by the PC's RAM? Does that add up? Or do certain things only go to the VRAM and other things to the RAM (if you know what I mean)? If the latter is true even getting a GPU with 12 GB VRAM wouldn't make a difference as longs as that 4 GB RAM limit exists.

 

It will make a difference in regards to performance.

 

It won't make a difference for OOM issues.

 

Are you still trying to run LOD 6.5? I'm getting no OOM errors running FSDT airports with 100% AI traffic (WOAI) and max autogen. But I'm running LOD at 4.5 (default FSX setting). 

 

I'm watching football right now, but maybe tonight I'll measure VAS to see exactly where I'm at in these higher load situations I've tested.

 

BTW My GPU has 1.5 GB VRAM. If I get a GPU with at least 3 GB will that make a difference...? Are things that don't fit into my GPU's 1.5 GB now handled by the PC's RAM? Does that add up? Or do certain things only go to the VRAM and other things to the RAM (if you know what I mean)? If the latter is true even getting a GPU with 12 GB VRAM wouldn't make a difference as longs as that 4 GB RAM limit exists.

 

I answered this earlier in this thread (but I didn't specifically state that my GTX 780 SC has 3GB of VRAM).:

 

 

Upgrading to a 780 would improve your FPS, but your OOM message might have been caused because your settings were still too high, which caused you to run out of system memory. My 780 gives me a steady 50-60 FPS (outside of large cities), but I can still an get OOM crash if I have stuff like cloud density set too high. Reducing a few settings a bit got rid of my OOM issues, and P3D STILL looks way better than FSX.  I'm still loving P3D because I'm not trying to run it at the edge of what a 32-bit program can handle. 

 

So it appears that some graphics are only being handled by the system memory ... and the 32-bit 4GB limit is the bottleneck for P3D.

 

 

It will make a difference in regards to performance.



It won't make a difference for OOM issues.

 

 

So it appears that some graphics are only being handled by the system memory ... and the 32-bit 4GB limit is the bottleneck for P3D.

 

 

Well, I was thinking that if my VRAM has been filled with 1.5 GB while P3D needs something like 3 or 3.5, the rest of that amount is being send to the PC's RAM and added to what is already there in that 'block' that may not get bigger than 4 G B. But apparently whatever doesn't fit in the VRAM is being handled somewhere else and not being added to the 4 GB P3D can use...? (Hope I make any sense here LOL)

Well, I was thinking that if my VRAM has been filled with 1.5 GB while P3D needs something like 3 or 3.5, the rest of that amount is being send to the PC's RAM and added to what is already there in that 'block' that may not get bigger than 4 G B. But apparently whatever doesn't fit in the VRAM is being handled somewhere else and not being added to the 4 GB P3D can use...? (Hope I make any sense here LOL)

 

We honestly don't know yet. And yes, you make sense. There's just no answer yet. 

 

Rob was reporting something to this effect but how P3D is actually setup to manage memory is a mystery right now. 

 

When LM gets back in the office tomorrow we will hopefully get some answers throughout the week about what is going on under the hood.

If you run LOD 6.5 and Opus in heavy clouds you are very likely to OOM. Have you tried the lates Opus beta which has been tweaked for P3DV2?

I was under the impression that Vram and 4GB of system ram within the VAS are independent of each other. However DX11 makes better use of VRAM even though even that is capped. I can see this clearly when running FSX in the same conditions as p3d therefore in theory unnecessary texture loading into VAS and into VRAM. I suppose it all depends on how well its programmed and assigned where to load. 

 

Jeroen, why not go bare minimum and slowly add graphics settings, but each and every time load up and monitor the VAS? Process of elimination troubleshoot. Youll need to start with a fresh cfg to be fair. Im using pretty much the same settings as you, and I havnt seen the VAS go over 3gb yet.