Jump to content

Kneeboard Resolution - What is the setting that defines the resolution of the maps on the kneeboard?


Go to solution Solved by Buzz313th,

Recommended Posts

Posted

I remember my map segments on the kneeboard used to be higher res?  I don't know which setting I changed, but the resolution is much lower, to the point where I can't read the waypoint numbers. 

Anyone know what changes the resolution on these maps? 

Could it be "Cockpit Display Resolution"?

 

Thanks 

  • Like 1
  • Rig Specs: Win11, 12900k@3.9-5.2, RTX4080, 64G DDR5@4800, Quest3@4800x2600 (Oculus Link Cable On Link, no VR tweaks)
  • DCS World: MT 2.9 with CPU Core #8 Disabled
  • Module Proficiency: F-15C, A-10CII, F-16C,
  • Modules Owned NOT Proficient: The rest of FC3, F-18C
  • Terrain Owned: NTTR, DCS World Included Maps
Posted

Any chance you started using DLSS or FSR upscaling?  They gain you FPS at the tradeoff of lower visual quality, which would show up more in something like the WP #'s on kneeboard than your general view outside the cockpit.

  • Like 1
Posted (edited)
1 hour ago, rob10 said:

Any chance you started using DLSS or FSR upscaling?  They gain you FPS at the tradeoff of lower visual quality, which would show up more in something like the WP #'s on kneeboard than your general view outside the cockpit.

I did, but went back to no AA and no scaling.  Still the kneeboard is low res.  I'm in VR and on 2.9 btw.

Edited by Buzz313th
  • Rig Specs: Win11, 12900k@3.9-5.2, RTX4080, 64G DDR5@4800, Quest3@4800x2600 (Oculus Link Cable On Link, no VR tweaks)
  • DCS World: MT 2.9 with CPU Core #8 Disabled
  • Module Proficiency: F-15C, A-10CII, F-16C,
  • Modules Owned NOT Proficient: The rest of FC3, F-18C
  • Terrain Owned: NTTR, DCS World Included Maps
Posted
11 hours ago, Buzz313th said:

I did, but went back to no AA and no scaling.  Still the kneeboard is low res.  I'm in VR and on 2.9 btw.

Can you show a screenshot?

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
4 hours ago, draconus said:

Can you show a screenshot?

Here ya go..

Screen_231110_081815.jpg

  • Rig Specs: Win11, 12900k@3.9-5.2, RTX4080, 64G DDR5@4800, Quest3@4800x2600 (Oculus Link Cable On Link, no VR tweaks)
  • DCS World: MT 2.9 with CPU Core #8 Disabled
  • Module Proficiency: F-15C, A-10CII, F-16C,
  • Modules Owned NOT Proficient: The rest of FC3, F-18C
  • Terrain Owned: NTTR, DCS World Included Maps
Posted

Also something I should note.  The only pages in the kneeboard that are low res for me are just the pages that were generated from the F10 map automatically.  The rest of the pages, like the airport, approach charts and Facility directory pages are normal resolution.   So maybe it's the autogeneration process when the pages are rendered that is a bit screwy.

 

Should I report this as a bug?   

  • Rig Specs: Win11, 12900k@3.9-5.2, RTX4080, 64G DDR5@4800, Quest3@4800x2600 (Oculus Link Cable On Link, no VR tweaks)
  • DCS World: MT 2.9 with CPU Core #8 Disabled
  • Module Proficiency: F-15C, A-10CII, F-16C,
  • Modules Owned NOT Proficient: The rest of FC3, F-18C
  • Terrain Owned: NTTR, DCS World Included Maps
Posted
On 11/10/2023 at 5:59 PM, Buzz313th said:

Should I report this as a bug? 

I tested in VR and 2D 2.9 MT - both are fine in the same map place on the kneeboard.

I suggest:

https://www.digitalcombatsimulator.com/en/support/faq/repair/#2463807

and temporarily rename "DCS" or "DCS.openbeta" folder to "Temp" in the user folder: C:\Users\<User Name>\Saved Games\.. and start the DCS again

  • Thanks 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
5 minutes ago, draconus said:

I tested in VR and 2D 2.9 MT - both are fine in the same map place on the kneeboard.

I suggest:

https://www.digitalcombatsimulator.com/en/support/faq/repair/#2463807

and temporarily rename "DCS" or "DCS.openbeta" folder to "Temp" in the user folder: C:\Users\<User Name>\Saved Games\.. and start the DCS again

I just did a slow repair a few days ago, but never did a cleanup.  

What is the purpose of renaming the "DCS" folder in "SavedGames".  My guess is so that DCS generates a new clean folder?

  • Rig Specs: Win11, 12900k@3.9-5.2, RTX4080, 64G DDR5@4800, Quest3@4800x2600 (Oculus Link Cable On Link, no VR tweaks)
  • DCS World: MT 2.9 with CPU Core #8 Disabled
  • Module Proficiency: F-15C, A-10CII, F-16C,
  • Modules Owned NOT Proficient: The rest of FC3, F-18C
  • Terrain Owned: NTTR, DCS World Included Maps
Posted
49 minutes ago, Buzz313th said:

My guess is so that DCS generates a new clean folder?

Yes, just to rule out any user settings or files in the profile that could be the cause.

  • Like 1

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
On 11/9/2023 at 4:00 PM, Buzz313th said:

Could it be "Cockpit Display Resolution"?

I would try altering this. Mine always looked awful until I increased this display setting, and now they look crisp and beautiful. Give it a shot and see if that fixes the issue.

  • Like 1
Posted (edited)
28 minutes ago, FMBluecher said:

I would try altering this. Mine always looked awful until I increased this display setting, and now they look crisp and beautiful. Give it a shot and see if that fixes the issue.

That was one of the first things I tried, didn't see a difference to be honest.   Although, I have not tried changing the cockpit display res and then forcing a shader recompile.

The Kneeboard map resolution looked normal until a certain point.  Dunno if I changed something in system settings or was it 2.9 MT..   

Later today when I get home I'll give some of these a try to see if they work.

Edited by Buzz313th
  • Rig Specs: Win11, 12900k@3.9-5.2, RTX4080, 64G DDR5@4800, Quest3@4800x2600 (Oculus Link Cable On Link, no VR tweaks)
  • DCS World: MT 2.9 with CPU Core #8 Disabled
  • Module Proficiency: F-15C, A-10CII, F-16C,
  • Modules Owned NOT Proficient: The rest of FC3, F-18C
  • Terrain Owned: NTTR, DCS World Included Maps
  • Solution
Posted (edited)
21 hours ago, FMBluecher said:

I would try altering this. Mine always looked awful until I increased this display setting, and now they look crisp and beautiful. Give it a shot and see if that fixes the issue.

Ok, so just tried a few methods and found the culprit to my extremely low res, auto generated F10 maps on the Kneeboard.

The issue is tied to the in cockpit resolution settings under "System", but, the resolutions will not change or correct themselves unless you set a higher cockpit display resolution and then quit DCS and force a recompile of all the shaders in "SavedGames" folder upon starting DCS again.  But here is the caveat, if you change cockpit display resolutions back to 256 after fixing the low res maps (To get better VR performance) and restart DCS, on the next mission load, the maps will be back to a much lower and unusable resolution..   If after I correct the map resolution and change the cockpit display res back to 256 within the same DCS session, the maps remain higher res until a restart of DCS. 

Here is my method for reproduction of what I would consider a bug that needs fixing...

  1. Set cockpit display res to 256
  2. Restart DCS
  3. Start mission
  4. Open kneeboard and recognize low res maps.
  5. Quit mission
  6.  Set cockpit display res to 1024
  7. Quit DCS
  8. Delete shader files in FXO and Metshader2 folders
  9. Restart DCS
  10. Open same mission as before
  11.  Open kneeboard and recognize High res maps.
  12. Quit Mission
  13. Set cockpit display res to 256
  14. Restart same mission
  15. Open kneeboard and recognize High res maps even though you set cockpit display res to 256
  16. Quit DCS leaving cockpit display res at 256
  17. Restart DCS without forcing a shader recompile
  18. Restart same mission
  19. Open kneeboard and recognize Low res maps - The restart of DCS changed or recompiled the maps to be rendered at low resolution

Maybe we can get this fixed so that In Cockpit Display Resolution has no affect on the kneeboard map resolution?

I think this bug is related to the maverick WPN page bug where the crosshairs and fov markers disappear unless you run at a higher cockpit display res with MSA off.

Reporting this finding in the bug section of the forum...

Post to the bug report

Cheers and thanks for helping me find this.  

Edited by Buzz313th
  • Like 2
  • Rig Specs: Win11, 12900k@3.9-5.2, RTX4080, 64G DDR5@4800, Quest3@4800x2600 (Oculus Link Cable On Link, no VR tweaks)
  • DCS World: MT 2.9 with CPU Core #8 Disabled
  • Module Proficiency: F-15C, A-10CII, F-16C,
  • Modules Owned NOT Proficient: The rest of FC3, F-18C
  • Terrain Owned: NTTR, DCS World Included Maps
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...