True, the Dev update has often looked more like a way to promote the MarketPlace products…
1 Like
NO not if you select GPU in the Task Manager
Apologies I misread the response as well. My mistake thanks for the correction.
Cheers
1 Like
Anyone getting these continental fault lines in southern uk?
I was testing rendering at ULTRA with render 150 (5760x2400) and maintains 30FPS, which is impressive, but its still only using 5GB RAM and 6.349GB VRAM.
The image while incredibly high res seems more lifeless than before, especially the ambient occlusion and lighting.
Edit: I can confirm you cannot fly under the fault
1 Like
Give it a shot. Do task manager then check in devmode. See if there is a difference
I personally go by the Developer Mode it is accurate for all developers inside the game.
Or go by the Xbox 16GB memory that has to be shared. You can cut it any which way but all you have is 16GB GPU Ram CPU Ram and system Ram.
They should have given the Xbox 24GB of ram the problems would be half the amount.
That is why Asobo/Microsoft had no choice but to turn the system down to fit into the Xbox. There is only one system for PC and Xbox.
Don’t you think that should have been part of the plan from the start? Why would someone build a Flight Sim without realistic aerodynamics? But then again, why would anyone continue releasing buggy code, update, after update, after update…
3 Likes
Over london I can see it using over 8GB VRAM
RAM is stuck at 6.82 as a hard limit though
Sorry I do not have the answer.
Look at it this way the 16GB is shared memory. GPU, CPU, System Ram.
they can share it any which way.
System 2GB
Ram 8GB
CPU Ram 6/GB
No matter what it cannot exceed 16GB
You are right on some things but I have shown this statement is false.
I suggest you go create a Rolling Cache on a Ram Drive to see if that improves things for you. Flying over London and my data is not getting hammered at all as its all in the cache.
It will be right at one time and wrong at another time. Shared Memory it changes all the time.
Lets look at it again.
If you give the vRam 11Gb
System Ram 2 GB
CPU Ram left is only 3GB
You will have other problems. They are trying to balance the Ram.
No you are completely wrong. MSFS VRAM is not limited to 6.5GB.
RAM yes, but not VRAM
1 Like
I wish I could test this now, but unfortunately my internet service is down due to a storm we had last evening. Tech coming tomorrow morning( Verizon)
. Thank God for mobile wireless. Anyway before the update system memory was utilized much higher. I have 64 Gigs and would use into the teens at times. My RTX 3090 would go over 10 gigs, but not now. Hopefully WU 6 will give some of the PC resources back to us.
Can you explain to me, if we are using the xbox version, why the flight sim can ask for 17GB memory to be comitted to the app? See screenshot:
comitted memory is not allocated magically by the OS, comitted memory is requested by the app and then, only then given by the OS.
An app may not know how much it would need, but requests if that amount is available and “asks” for a “reservation”. If there is not enough, an app will not get it. So max comitted on my pc can be 64, minus what already has been given.
Does the XBox also have a page file?
I do not know for sure but one can assume probably. But small because of the 16GB limit.
Ok, I have now managed to get RAM usage over 6.5GB by reloading all of London photogrammetry… so myth busted I think. It must be said it aggressively culls back down to <6.5, but peak was 7.2GB.
But I agree the overall image is less detailed than before as it tries to maintain a lower overall RAM usage.
.
If this is in response to my post, assumptions leads to misinformation. We must know to say for sure 
So, if we are running xbox memory code and as you are saying quite often we are limited, we would never get 17GB of comitted (promised by the os). Because the app would not dare to ask for more memory then there is available if it was capped.
Yes it does like all operating systems, its basically a cut down instance of windows.
I think its clear now that its not capped but in SU5 it is now highly aggressive at removing textures above 6.5GB so as not to be hitting the Page File on the Xbox.
To get round this aggressive limit, create a RAM based disk (R:) How to Create RAM Disk in Windows 10 [Guide] | Beebom
Then set your rolling cache to 32GB - 6.5GB or roughly 24GB to be safe, now you can store 32GB of textures in RAM.