I ran BeyondCompare (a diff tool) on my 2.7 install and compared it to my 2.8 install and looked for differences in the A-10C_2 files between the two versions.
From the install folder, the following script was changed in 2.8 - DCSWorld\Mods\aircraft\A-10C_2\Cockpit\Scripts\MFCD\indicator\BAKE\page.lua
The change was to enable SRGB on the MFDs. I have commented on the lines that were added with 2.8. picture.input_space_SRGB is the culprit. Removing the line will resolve the problem. Why was SRGB set at the MFD base? In all other aircraft it is only set at a weapon or system level, such as TGP, SLAM, MAV, FLIR, PNVS and TADS. Although for the latter two it's commented out (disabled)
SetScale(1)
function addPicture(left)
local verts = {{-1, 1},
{ 1, 1},
{ 1,-1},
{-1,-1}}
local inds = {0, 1, 2, 0, 2, 3}
local hud_only_background = CreateElement "ceMeshPoly"
hud_only_background.material = MakeMaterial("",{0,0,0,255})
hud_only_background.vertices = verts
hud_only_background.indices = inds
hud_only_background.additive_alpha = false
hud_only_background.controllers = {{"render_purpose",1,2,3}}
Add(hud_only_background)
local picture = CreateElement "ceTexPoly"
picture.material = MakeMaterial("ccMFCD_Bake_SRC",{255,255,255,255})
picture.vertices = verts
picture.indices = inds
picture.input_space_SRGB = true -- Added in 2.8, remove to fix the issue
picture.additive_alpha = true
if left then
picture.tex_coords = {{0, 0},{0.5, 0},{0.5,1},{0, 1}}
else
picture.tex_coords = {{0.5, 0},{1, 0},{1,1} ,{0.5, 1}}
end
picture.controllers = {{"display_backlight"}, --[[Added with 2.8, doesn't contribute to the issue--]] {"render_purpose",0}}
Add(picture)
--[[
picture2 variable and logic added with 2.8. Does not contribute to the issue.
Removing this has no noticeable difference. Is it serving a purpose?
--]]
local picture2 = Copy(picture)
picture2.controllers = {{"display_backlight"}}
picture2.parent_element = hud_only_background.name
picture2.input_space_SRGB = false
Add(picture2)
end
If this isn't enough evidence that the issue was introduced with 2.8 then I have absolutely no idea where to go next with this bug report. Furthermore, if this issue isn't going to be fixed then at least don't make it any worse. At the very least I'd like to be able to use OvGME to fix this myself by patching over this file.
