Jump to content

New MPCD Font - Bug or not?


CommandT
 Share

Recommended Posts

  • 3 weeks later...
  • 2 weeks later...

You can "fix" these fonts by editing one of the lua files in the cockpit folder for the AV8B. You just change a couple of numbers and it looks a lot better. I'll update this post with the exact change when I'm back from work.

Link to comment
Share on other sites

  • 4 weeks later...
19 hours ago, Draken35 said:

Sad to report that there are no noticeable improvement in 2.7 regarding the quality of the MFDs 

 

Yep. Was expecting that this would have been fixed. But can't read the displays so back to configuring on Display_StrokeDefs.lua again to get it fixed. 

i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S.

i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.

Link to comment
Share on other sites

My Display_StrokeDefs.lua looks like this:

 

stroke_thickness  = 0.5
stroke_fuzziness  = 0.4

-- Currently is used for DMC generated fonts black outline
DMC_outline_thickness = 0.0
DMC_outline_fuzziness = 0.0
DMC_stroke_thickness  = 0.65
DMC_stroke_fuzziness  = 0.42
 

Note the changed values in red. I couple this with dialling the gain right back and dropping the contrast a few notches and have a super readable MPCD in 2D and VR


Edited by netizensmith
  • Thanks 1
Link to comment
Share on other sites

Thanks! I'll give it try

 

Edit: That actually works very well... Can't recall what my settings where before, but these works very well!

  

2 hours ago, netizensmith said:

My Display_StrokeDefs.lua looks like this:

 

stroke_thickness  = 0.5
stroke_fuzziness  = 0.4

-- Currently is used for DMC generated fonts black outline
DMC_outline_thickness = 0.0
DMC_outline_fuzziness = 0.0
DMC_stroke_thickness  = 0.65
DMC_stroke_fuzziness  = 0.42
 

Note the changed values in red. I couple this with dialling the gain right back and dropping the contrast a few notches and have a super readable MPCD in 2D and VR

 

 


Edited by Draken35
  • Like 1
Link to comment
Share on other sites

9 hours ago, mwlue said:

Bit of OT, can I disable the moving map via Display_StrokeDefs.lua ???  new to this mod/workaround.  sorry.

 

No, but disabling from the cockpit is just a couple of clicks.... That's what I doing to have a readable EHSDI ... 

 

The alternative is a bunch of clicks (like 50!) to reduce GAIN and play with contrast settings. How much depends on the map you are flying on. 

Link to comment
Share on other sites

Please fix officially...

  • Like 2

Modules: A-10C Warthog / A-10C II Tank Killer / F-15C / SU-33 / AV-8B Harrier / F-16C Viper / AJS-37 Viggen /  F/A-18C Hornet / F-14A/B Tomcat / Supercarrier

Terrains: Persian Gulf / Syria / NTTR

SYSTEM: AMD FX-8320 3.5Ghz, Nvidia GTX 1050Ti 4GB, 8GB Ram DDR3 

alpiinoo_signature.png.92e62da0731ec62ed4f4cd1e7f958385-removebg-preview.png

Link to comment
Share on other sites

  • 4 weeks later...

Well, well, well...

 

Looks like an improvement was made.... Gain looks a lot lower and the Display_StrokesDef.lua file has some new definitions in it.

The values might , still, need some tweaking but it looks definitely better. 

Of course, there is nothing in the change log 😄 .

 

Razbam team, the work on this is appreciated.

 

  • Like 2
Link to comment
Share on other sites

On 5/22/2021 at 12:10 AM, Draken35 said:

Well, well, well...

 

Looks like an improvement was made.... Gain looks a lot lower and the Display_StrokesDef.lua file has some new definitions in it.

The values might , still, need some tweaking but it looks definitely better. 

Of course, there is nothing in the change log 😄 .

 

Razbam team, the work on this is appreciated.

 

No, not really better , much better fonts in F-18 or F-16 ....

MSI Z97 Gaming 5 - Intel I7 4790K - Artic cooling freezer 7 pro rev 2 - GSKILL 32 Go - SSD Crucial M5 120 go - SSD Crucial 2To - HDD western digital caviar blue 1 TO - Gigabyte GTX 1070 Gaming G1 - Windows 10 home 64 bits

Link to comment
Share on other sites

1 hour ago, clanitho said:

No, not really better , much better fonts in F-18 or F-16 ....

Haven't flown the 16 but can't argue against the Hornet's fonts been better.

So, let me rephrase that "it seems that Razbam is trying to improve it" ... Happy now? 😄

 

I think that part of the issue, besides the gain being absurdly high before this patch (that is a bit better now) is the actual color/transparency/width of the font  used in the MCPD. It doesn't provide good contrast. Perhaps, that's why the black outline is there... 

 

My problem with the black outline is that in VR (Quest 2, max resolution) it makes the symbols "vibrate" and unreadable unless you move a lot closer to the MCPD.  It is even unreadable with VR zoom.

 

 

Link to comment
Share on other sites

In case anybody is interested, these are the current values I used for VR (Quest 2)

Quote

stroke_thickness  = 0.5
stroke_fuzziness  = 0.4

-- Currently is used for DMC generated fonts black outline
DMC_outline_thickness = 0 -- stroke_thickness * 3
DMC_outline_fuzziness = 0 -- stroke_fuzziness * 1.1
DMC_stroke_thickness  = 0.65
DMC_stroke_fuzziness  = 0.42

-- MPCDs
-- MFDs
MPCD_stroke_thickness  = 2.0 -- 0.9
MPCD_stroke_fuzziness  = 0 -- 0.4
MPCD_outline_thickness  = 0 --MPCD_stroke_thickness * 3
MPCD_outline_fuzziness  = 0 --MPCD_stroke_fuzziness * 1.1
 

 

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...

Anyones knows how this new parameters in the lua affect the fonts? Whit the old lua I only had to set to 0 the DMC outline and I had great fonts. With the new one I had many tries yesterday but the fonts become semitransparent and they are impossible to use with the map.

 

Also the MFDs night mode appears no to work that well. I have to use day mode at night and turn down a lot brightness and gain.

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

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