Buzz313th

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...
Set cockpit display res to 256 Restart DCS Start mission Open kneeboard and recognize low res maps. Quit mission  Set cockpit display res to 1024 Quit DCS Delete shader files in FXO and Metshader2 folders Restart DCS Open same mission as before  Open kneeboard and recognize High res maps. Quit Mission Set cockpit display res to 256 Restart same mission Open kneeboard and recognize High res maps even though you set cockpit display res to 256 Quit DCS leaving cockpit display res at 256 Restart DCS without forcing a shader recompile Restart same mission 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.