{ ED INVESTIGATING } MFD Text and symbology messy with latest update

[Fuchs]

same here!!!

[raptor909]

Yes. I confirm. I export the two MFD on two 8" display. After latest patch the symbology is unreadable and messy. Before was perfect. Plz fix it as soon as possible. Thank you

[RAZBAM_ELMO]

So if im getting this right this is affecting exports only? Our team has a wide selection of VR equipment and so far this seems to be a player/ hardware issue especially if using multimonitor display/ exports. Reported.

[Draken35]

Well, I just fired up the Harrier after today's update, and the blurriness continues ...

 

However, I was bored (more than usual) and had time, so I decided to do a test of the Gain & Contrast  in 2D and VR. My result where the same for both: Reduce Gain by 50 clicks and Contrast by 10 and the moving map is usable again. The other displays improve as well.

[netizensmith]

2 hours ago, Draken35 said:

Well, I just fired up the Harrier after today's update, and the blurriness continues ...

 

However, I was bored (more than usual) and had time, so I decided to do a test of the Gain & Contrast  in 2D and VR. My result where the same for both: Reduce Gain by 50 clicks and Contrast by 10 and the moving map is usable again. The other displays improve as well.

Can confirm. This fixes the problem (pancake and VR). In fact, the clarity might actually be the best it's been (Green, white and Yellow. Other colours are unreadable still)

[netizensmith]

@RAZBAM_ELMONote this is a general issue, in 2D, VR and exported MFDs. The new black outline on the text, coupled with the reduced letter/symbology spacing makes it unreadable by default in 2D and VR. This seems to be the case for everyone; nobody has responded with "it looks fine" or "it looks better". It's worse across the board, for everyone.

 

Best current workaround seems to be a 50 click reduction in gain and a 10 click reduction in contrast. This is good enough in 2D and VR to make the Harrier playable again. It's a particular shame because I always appreciated the superiority of the Harrier MFDs compared to the unusable Hornet's (I gather the Hornet is unusable - with a moving map background - in real life too so there's an argument to not change that one) but what little footage I've seen of the ream AV-8B shows that it does have a quite readable MFD with map background.

Edited February 3, 2021 by netizensmith

[Dunx]

I can confirm that the text in VR is now very difficult to read, even when head close to MFD. Some of the stacked characters bleed into each other and the text is blurred.

 

[imacken]

I mean, it does help, but why do we need to make 50-100 clicks to make this work?  Surely, the norm is 10.

[netizensmith]

Why have we got to do anything? It was fine before they made the changes!

[Draken35]

2 hours ago, imacken said:

I mean, it does help, but why do we need to make 50-100 clicks to make this work?  Surely, the norm is 10.

Somebody change something at the last minute.... 

 

[razalom]

Well thats disappointing they didnt revert these changes.

[wowbagger]

It's been a week now. Has the developer commented on the results of this change at all?       (@RAZBAM_ELMO)

 

Also, anyone know if there is a lua file to set the default settings for contrast and gain? I am simply NOT going to sit there there clicking my mouse 60 times every time I want to hop into the Harrier.

 

Cheers

[RAZBAM_ELMO]

From our lead dev on the matter:

 

"YEs it is a known issue. it is a problem with the stroke (SVG) system. Fortunately it can be fixed in code, but it is a case by case basis. What is happening is that we are using a fixed thickness and fuzziness value when the display is exported.

 

static const double thickness_fix = 1 / 0.8;
static const double fuzziness_fix = 1 / 0.5;

if (purpose == CURR_PURPOSE_GENERAL)
{
//Normal stroke processing for inscreen display
}
else
{
//Exported displays values
shaderLineVariableParams.thickness = 8.0 * thickness_fix;
shaderLineVariableParams.fuzziness = 3.0 * fuzziness_fix;
}

 

So, in the future, we can implement a Special Options that can modify hte fixed value. Unfortunately this cannot be solved for everyone with a single fix as it is a case by case basis.

 

 

 

I am leaving this up here for everyone to share and see so individuals experiencing this issue can adjust as needed for themselves.

[netizensmith]

Appreciate the response but seriously, come on mate:

 

1. I was quite specific that this issue is not just for exported displays

2. Where would someone put the code you specified anyway? If you're gonna tag this with {FIX} for those with exported displays at least tell them what file to put the code in.

[Aarnoman]

This is very frustrating, when will text go back to something readable like it was in the previous update? It's so fuzzy it is almost unreadable on a Reverb G2, while all other modules like the F/A-18 are readable with smaller text. It was also completely fine before the update, I just don't understand why this can't be fixed.

[Aarnoman]

It is a lot less readable in VR compared to the old text as well prior to update. The change to SVG has been a big step back.

[Aarnoman]

Bump this is an ongoing issue and I am disappointed this was not addressed in the recent hotfix considering how many other aspects for the harrier were fixed.

[Aarnoman]

Also this thread is relevant to the topic, although not posted under the bug section.

Edited February 5, 2021 by Aarnoman

[Hawkeye_UK]

Thanks for all the posts - i actually prefer the moving map with the black outline. 

 

The post i was originally relating to was every MFD normal screen, so the menu screen, stores page etc etc

 

RAZBAM DO YOU INTEND TO JUST IGNORE THIS THREAD ???  

[imacken]

From what I can see, they only respond to posts in the bugs section. New thread there with a link to here?

[netizensmith]

I already raised the bug and they have responded

[imacken]

OK, so if they recognise it as a bug, is there any point in carrying on with this thread?

[imacken]

10 hours ago, netizensmith said:

Appreciate the response but seriously, come on mate:

 

1. I was quite specific that this issue is not just for exported displays

2. Where would someone put the code you specified anyway? If you're gonna tag this with {FIX} for those with exported displays at least tell them what file to put the code in.

+1

[netizensmith]

No, we should comment in the bug thread now, particularly as the response isn't satisfactory i.e. they see it as an issue when exporting MFDs only as far as I can tell.

[Dunx]

May I suggest asking someone who has never seen the Harrier MFD screens in VR before to run the Cold and Dark training mission while in VR.

 

It it possible that you may not see the extent of the problem in VR if you have any kind of MFD screen muscle memory.

 

Maybe ED could provide you with examples of how they migrated the F/A-18C, which works well in VR.