Wow, thank you so much for confirming this issue. I have been beating myself half to death thinking it is my hardware at fault. Ive even done a clean windows install. So thank you for confirming this isn’t related to my hardware.
I actually think your spot on about the rings of LOD being directly effected by the data volume. But i will also add, that this data, which translates to your own system load, is a direct attempt to “memory manage” us PC users. That’s what i have suspected for some time now, that these so called “memory management” strategies used by Asobo in an attempt to maximise performance over graphics and loading of scenery etc, has created this stunted gameplay we now see. Like you say, in 2d this wasnt noticed, but by golly…in VR it is plain as day, and horrible.
If this set of assumptions is correct, this is really bad news.
BTW…400 TLOD is way out of my PC’s caperbilities in VR, as im lucky to get away with 275 on a good day.
78003xd
4090
quest 3.
I really want to thank you for trying and succeeding to replicate this issue, now i know its not on my end.
Many thanks, and i’ll be pleased to hear any reply you may have.
Can you change this issue to a bug logged, because clearly my issue is re-producible. If the guy below has the same issue, then surely it is repeatable your end.
I just want this fixed, I am wheelchair bound and rely on this sim to relive stress and boredom.
What Ive noticed by zooming in and really looking at the tiles, is that Details, buildings, trees and texture doesn’t “pop up” into a shape. The tiles ahead have stuff on them, but in 2d lying on the floor tile.
Interestingly, anywhere with mountains and hills, the scenery pops up.
This is most defo a bug, and re-producable on at least another PC across the world.
If the aircraft is at position X, and TLOD is set to 200, then there is a “ring” around the aircraft where photogrammetric scenery is displayed correctly.
If you zoom the camera to view objects outside the “ring”, they appear blurry
If you increase the TLOD to 400, the “ring” expands, and the objects that were outside the ring are now inside it & display correctly.
The size of the ring appears to vary based on “data volume”. I’m unclear if you are referring to internet download volume (quantity [MB] and/or speed [Mbps]), CPU available memory, GPU available memory or something else.
From the tests I’ve done, the drawing of features associated with TLOD does not change with field of view, which is why ‘zooming in’ always results in worse looking buildings and scenery.
That sounds right to me. If, when zooming, the sim had to keep on loading all data associated with the distant tiles in view (buildings, trees, textures, etc.), would this not quicky overwhelm the capacity of any CPU & GPU to render them?
You are asking the sim to fully render a greater & greater area as you zoom towards the horizon, which could be 10’s or 100’s of miles away, depending upon the altitude of the aircraft.
I’m not sure that this issue could be considered a bug, but rather is actually by design to prevent out-of-resource issues (freezes or CTDs) occurring on the PC.
Here’s an example. What initially looks like a reasonable rendering of photogrammetry turns into a hot mess when the zoom level is increased. Note however that the LoD of the wheel increases appropriately because it’s an object rather than terrain.
Reason I mention this is that much of the time when I see people posting about ‘LoD problems’, ‘bad photogrammetry’ etc. they show examples with a long lens. The problem is that TLoD is simply based on a radius around the camera and doesn’t take FoV into account.
correct, this, i believe, is by design, one of the many performance strategies implemented into the game
correct, although not so much blurry… more like low lod or an agressive data volume cap
correct, this would seem to be the desired behaviour, it works like this for me but apparently for the original poster it doesnt, which is, as i understand, the reason of his post, even with tlod of 400, his distant lod does not improve
the size of the ring seems to be defined by tlod setting, the amount of data loaded into memory for each ring, seems to be capped by data volume, wether this data is downloaded, stored locally or cached seems to make no difference
In my video above, the ‘area’ being rendered at the end - with maximum zoom - is actually orders of magnitude smaller than at the start with the wide angle.
I don’t think it’s as much a rendering problem as a data one, but I can appreciate why from a technical point of view.
I get your point, and appreciate the comments, however… Your picture is stunning compared to what i am witnessing, night and day. I will add more pics not zoomed in.
First of all, thsanks for showing interest, and i appreciate your time and efforts in this matter. My answers are directly below your questions
That’s how it was 9 weeks ago yes. 255 or 275 TLOD was deliciously large. In daylight the whole scene was crisp, and whilst no buildings could be seen near the horizon (naturally) - The general outline of scenery and towns and city’s could be seen, as in pleasant green land for miles and miles ahead, and all around. At night city lights and street lights went waaaay into the distance. Now the ring, or sometimes a thin channel, goes out 15-25% of that distance. The other day, i was literally flying down a mile wide channel. Interestingly, the scenery below that does show up is Stunning!!
Yes, correct, but not just objects, its the tiles, they are grainy and wavey due to the low resolution. Waaay more blurry than ever seen before, like an offline tile. But take note, this can be seen easily without the zoom. I zoomed in to provide a clear picture of the issue, but i will show the issue without zoom shortly.
Sometimes yes, sometimes no. The ring can turn into a pear, a banana or a channel of clear crisp tiles. But generally yes, the size of detail around the aircraft increases, as one would expect. But nowhere near what i had 8 weeks ago. Also, whilst sometimes the scenery gets larger with a TLOD increase, there is missing scenery (flat tiles) in-between the inner and outter ring.
This seems to be the case yes. I say this because in 2d at 275Tlod the ring/banana/channel increases in size, compared to the same settings in VR. It also increases in size if i use Nvidia super resolution as opposed to TAA. This could be Internet data, CPU,GPU or any other data metric causing a suspected “data management trigger event”. That is what i suspect.
@BeardyBrun
Thanks for the video showing this. That area - smaller, but still with some depth to it, and constantly changing if in flight, has to be stored in memory & processed, right? Maybe I should use “process” rather than “render” (Speaking as a complete non-expert in these matters)
All PCs & GPUs have (obviously) a finite amount of memory. At some point one has to start dumping stuff out of memory in order to get the new stuff in to process, otherwise you get an out-of-memory condition that crashes the sim (I hit this condition myself, but the cause is completely different than what we are discussing here).
It appears that the chosen solution is to, as you point out, limit details based on a radius around the camera.
@Cornhole2840
Thanks for your reply. I’m not in any way trying to negate what you are seeing - just trying to clearly define the issue for my personal understanding & so others can replicate. Your responses helped a lot.
Since this this thread is not in the beta forums, I take it you are still on the normal released build. I do not have VR, so cannot assist in this respect, and am also on the SU15 beta, so trying to repro on my PC would be like comparing apples to oranges.
So just FYI, in my latest v1.37.15.0 performance tests, this is my view of Manhattan as I approach the city. This is on a 4K 55" TV:
