DCS 2.9 LOD Behavior

[Bowman-011]

Honestly, I'm quite fascinated with the visuals and the new options this new version offers. Absolutely amazing!

But there's one thing I haven't yet figured out with my G2: regardless of the settings (DLSS, MSAA, DLAA, even in everything set to "off") targets appear as rather huge black block of pixels between about 30 to 5 nm. Depending on the LOD slider when closing in at some point the blocks then eventually dissolve into something that looks like an aircraft.

In 2.8 far away objects were at least the size of a single pixel if they were somehow in what one could call visible range. 

Has anyone else noticed this? It's difficult to show in a screenshot, though.

[Hartsblade]

From the patch notes:

• Improved “spotting dots” added (WIP):
  • Increased dot size at high resolutions
  • Zoom is not affecting dots size

In order to disable new “spotting dots” and revert to previous logic user can put “DotRendererExperiment = False” in autoexec.cfg file located in \Saved Games\DCS.openbeta\Config\

[Fresh]

I had to create that file, and entered the text as above, but the big ugly blobs are still there.. is there a syntax that I am missing?

 

[Dangerzone]

5 hours ago, Fresh said:

I had to create that file, and entered the text as above, but the big ugly blobs are still there.. is there a syntax that I am missing?

 

You don't have dot labels turned on by any chance do you?

Try cycling through Left Shift + F10 a couple of times and see if they disappear. 

Edited October 20, 2023 by Dangerzone

[Bowman-011]

6 hours ago, Hartsblade said:

From the patch notes:

• Improved “spotting dots” added (WIP):
  • Increased dot size at high resolutions
  • Zoom is not affecting dots size

In order to disable new “spotting dots” and revert to previous logic user can put “DotRendererExperiment = False” in autoexec.cfg file located in \Saved Games\DCS.openbeta\Config\

Thanks for the hint!

I totally overlooked this. Will try it out, tonight.

[Fresh]

3 hours ago, Dangerzone said:

You don't have dot labels turned on by any chance do you?

No, all off, but I'll try the LShift+F10, you never know...

Edit: tried, but it didn't work. The problem is only when looking through my HP G2 VR goggles..

Thanks.

Edited October 20, 2023 by Fresh

[lester]

19 minutes ago, Fresh said:

No, all off, but I'll try the LShift+F10, you never know...

Edit: tried, but it didn't work. The problem is only when looking through my HP G2 VR goggles..

Thanks.

 

Same here: wasn't able to disable new dots by setting DotRendererExperiment = False in the autoexec.cfg file I created under \Saved Games\DCS.openbeta\Config folder in VR (HP Reverb G2).

[Leafcutter1008]

Hi,

same problem here with the G2. Dots look super ugly

I hope this is not a completely dumb question but in my DCS folders there is no autoexec.cfg file and I also have no idea how to create one...

Can someone help me, please?

Thanx a lot !!!

[hsth]

Here you have a default one.

Advice: use notepad++ to update files.

If you want me to add the dotrender line, let me know.

autoexec.cfg

[Gun Jam]

I also notice the same thing. Its easier to spot at 30 miles by far than it is to spot a 1 to 3 miles. The dot at distance is about the size of a football stadium. 

I use the G2 im not sure if this is a VR issue or a G2 issue.

Online this is a massive competitive advantage.

The old system by far was superior in terms of accuracy and not having a WTF is that issue.

[oz555]

Same with my G2. Overly huge dot in the distance then almost completely disappears from sight when close in. 

[Bowman-011]

nope, doesn't work unfortunately. 

See https://forum.dcs.world/topic/335325-spotting-dot-bugs-in-vr

[Waxi]

Same issue here using RTX 4090 and Reverb G2. From the distance, units look like big dark cubes. I suppose that this issue might potentially be related to the new LOD (Level of Detail) feature that has been introduced in 2.9. Here is the corresponding item from the changelog:

Quote

• NEW: LOD Switch Factor. The Level of Detail (LOD) slider allows you to adjust the distance at which a unit transitions to lower level of detail models. 1 is the default value, but by setting a lower value, game performance can be increased.

I have not changed this setting after updating to 2.9. Thus, I cannot tell if changing the slider value has an effect.

[TKNARMZ]

valve index here doing the same.  extremely ugly and can't stand it.

[Fresh]

I put the LOD slider to lowest (full left), it doesn't make a difference..

They do say it is WIP..

 

Edited October 21, 2023 by Fresh

[Leafcutter1008]

vor 22 Stunden schrieb hsth:

Here you have a default one.

Advice: use notepad++ to update files.

If you want me to add the dotrender line, let me know.

autoexec.cfg 132 B · 22 Downloads

Thanks a lot! I downloaded the file but I got a warning that the file could be dangerous and it has been blocked... I don´t think you are a hacker and if so you wouldn´t tell me I think  But can you nevertheless reassure me and YES....PLEASE add this dotrender line for me and (others) cause I have absolutely no idea how this works! THANX!!!

Edited October 21, 2023 by Leafcutter1008

[Fresh]

You can use any text editor, even the default Notepad. Copy/Paste the text into it,
then save the file as autoexec.cfg Windows doesn't like the .cfg extension, that is why you get the warning when you download it.

UPDATE: I didn't realise. but my .cfg extension was not being used, because it still had .txt appended. (So check your properties tab to make sure it really has only a .cfg extension)

I added this line:
options.graphics.maxfps = "30"

to test that the .cfg file was being read, so now I know it is being read.

I have tried the following permutations without success:

DotRendererExperiment = False

"DotRendererExperiment = False"

DotRendererExperiment = false

DotRendererExperiment = "False"

dot.renderer.experiment = "false"

 

Edited October 21, 2023 by Fresh

[hsth]

@Leafcutter1008, no problem. Attached the file with the line in. Deleted all previous default lines.

If you wonder, I got the same safety warning because I downloaded the same file I uploaded before. Windows Security is really tight...

I use this file also myself because without it I get a stutter festival, ED is certainly not finished on this topic.

Tried it myself in the L-39C Instant Action - Free Flight because that gives another plane right in front of you.

autoexec.cfg

[Leafcutter1008]

@hsth thank you for your help once again - I appreciate that! I will try this out asap. 

[zb2oby]

hi,

same here with a Reverb G2.

i tried with the last config file from @hsth because i thaught i've forgotten the semicolon but it changes nothing in my case... :-/

[JG1_Labroisse]

Bump. 

Since the "DotRendererExperiment" variable doesn't seem to work, anyone figure out how to turn the new spotting experiment off?

[Fresh]

Negative, so far no luck turning it off...

[neok]

Yep same issue here, it’s really difficult to judge distance now approaching a formation. Please ED let us turn this off in the options.

[Creep]

bump

just found this - i posted about it here as well: 

 

[average_pilot]

Did you try to disable the new spotting system with the autoexec.cfg option? For me it is a lot better disabling it.