fixed MT - A/G radar seems the same in GMT / SEA / MAP

[Gierasimov]

It seems that radar is not quite up to the task in MT. No matter which mode I select it shows me this:

I checked and GMT mode in ST works normally - I get to see moving targets.

NOTE: In case you wonder about the export snapshot above, YES I did change the \Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\BAKE\MPD_common_bake_page.lua to fix my exports issue, but I tested this with original value as well

picture.additive_alpha   = true

and it is still the same, so it is not related to my exports fix

picture.additive_alpha   = false

MT MODE - RDR ISSUE.trk

Edited March 11, 2023 by Gierasimov
additional info

[AstonMartinDBS]

4 hours ago, Gierasimov said:

It seems that radar is not quite up to the task in MT. No matter which mode I select it shows me this:

I checked and GMT mode in ST works normally - I get to see moving targets.

When I replay your track on my MT setup, I see MAP, GMT and SEA modes working normally. Try to repair your DCS installation.

Edited March 11, 2023 by AstonMartinDBS

[Gierasimov]

8 minutes ago, AstonMartinDBS said:

When I replay your track on my MT setup, I see MAP, GMT and SEA modes working normally. Try to repair your DCS installation.

 

It works in ST it does not in MT, you sure that your log got this in the first line - APP (Main): Command line: "E:\DCS\bin-mt\DCS.exe" ?

It can't be 'repair' mate, MT is the new stuff.

[markom]

24 minutes ago, Gierasimov said:

It can't be 'repair' mate, MT is the new stuff.

From what I understand, it will among other things ensure shader files and caches are recreated. It has been a fix for various other graphical glitches. So... it could be.

[Gierasimov]

Good. This is AFTER I ran repair: this time testing in the default terrain to rule out Marianas. 

At least in Caucasus region I can see bricks!

SEA-GMT-MAP-MULTI-T.trk SEA-GMT-MAP-SINGLE-T.trk

Edited March 11, 2023 by Gierasimov

[Chain_1]

Just tried your replay in MT and both worked as advertised.  The issue was needing to turn down the map gain under the data page (like in the Viper, if you have that).  The GMT bricks blended in with the terrain until I turned it down.

Edited March 11, 2023 by Chain_1
added text

[AstonMartinDBS]

2 hours ago, Gierasimov said:

It works in ST it does not in MT, you sure that your log got this in the first line - APP (Main): Command line: "E:\DCS\bin-mt\DCS.exe" ?

Thanks for the hint, you've been right! I usually start DCS via desktop shortcut, which always loads the ST version of DCS.exe. At least now I found out that I have to start DCS via Steam to start the MT version.

I ran your track again under MT and had the same issue.

1 hour ago, Chain_1 said:

The issue was needing to turn down the map gain under the data page.  The GMT bricks blended in with the terrain until I turned it down.

Exactly! Decreasing gain level to 2 made the bricks visible, but this is only a workaround.

Edited March 11, 2023 by AstonMartinDBS

[AvroLanc]

54 minutes ago, Chain_1 said:

Just tried your replay in MT and both worked as advertised.  The issue was needing to turn down the map gain under the data page (like in the Viper, if you have that).  The GMT bricks blended in with the terrain until I turned it down.

 

No, this is not the solution.

Yes it will make the bricks more visible, but it doesn’t address the bug. The GMT and SEA modes are both displaying terrain mapping incorrectly in MT.

They should not display ANY terrain unless the INTL (interleaved) option is selected, and then only on alternate sweeps. Compare this with the correct behaviour in Single thread. 

[Chain_1]

2 hours ago, AvroLanc said:

No, this is not the solution.

Yes it will make the bricks more visible, but it doesn’t address the bug. The GMT and SEA modes are both displaying terrain mapping incorrectly in MT.

They should not display ANY terrain unless the INTL (interleaved) option is selected, and then only on alternate sweeps. Compare this with the correct behaviour in Single thread. 

Brick visibility was the OP's issue, but you are correct in that the terrain was not displayed by default in GMT/Sea pre-patch.

[Gierasimov]

Actually my grief was about 

"They should not display ANY terrain unless the INTL (interleaved) option is selected, and then only on alternate sweeps. Compare this with the correct behaviour in Single thread. " 

As nicely said by @AvroLanc, thank you. 

I didn't even know bricks were still visible until I tried the least detailed terrain. I could not see bricks in Marianas but will try your workaround to see, thank you @Chain_1

[maxTRX]

@Gierasimov

I tested this today and got the same results you had initially. Regardless of 'INTL' (boxed or unboxed) it showed the terrain in the background. In the hills, it was impossible to see the target symbology. Instead of repairing, I lowered the gain from default 5 to 2 and the bricks showed up over the dimmer terrain. Once the target was locked, the terrain disappeared.

In standard DCS.exe the terrain only shows up when 'INTL' is boxed.

[Lord Vader]

Hi @Gierasimov

Thank you for bringing this up, we are raising this internally. 

[Jags]

When using the multi-thread version of the current open beta, the Ground attack radar continues to show static map mode data along with the GMT an SEA data when in GMT or SEA mode respectively.  Tried in Desert Convoy and Close Air Support missions.

[Tholozor]

Already reported: 

 

[BIGNEWY]

threads merged