cannot reproduce and missing track file Did anyone ever sort out the thick/blurry text issue on HUD & Displays?

[Aluminum Donkey]

Anyone gotten a handle on this yet? The F/A-18C module is shaping up to be a real buttkicker, what with the A2A radar now working properly, and AIM-9X and AMRAAMs :)

 

 

I'm still getting the thick blurry text thing... The HUD is pretty nice, but the displays (DDIs) have "clunky" text on them. Zooming in fixes it, but I'm running a 32" 1440p display and would like everything nice and sharp at normal zoom where I see the whole cockpit--HUD and 2 DDIs :)

 

 

Any ideas?

 

 

AD

[feefifofum]

You can find "thickness" and "fuzziness" parameters for the lines in \Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\MDI_IP1556A\indicator\MDI_init.lua

 

It seems to vary by system. The default settings are nice and crisp on my 1080P 60" TV, some of my squad mates had to tweak things.

[Bluegrass]

You can find "thickness" and "fuzziness" parameters for the lines in \Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\MDI_IP1556A\indicator\MDI_init.lua

 

It seems to vary by system. The default settings are nice and crisp on my 1080P 60" TV, some of my squad mates had to tweak things.

 

Yep, it really is extremely random, here is what helped me out.

 

 

 

[wilbur81]

4k user here. Still not fixed...

[Aluminum Donkey]

Yep, it really is extremely random, here is what helped me out.

 

 

Awesome, thanks so much!!

AD

[Dispatch]

Thank you Bluegrass

That worked out well for me

 

[27" 1080 LED Samsung]

[fitness88]

ShaderLineDrawAsWire change back to false...where is this line located and why would it need to be changed back to false if I never changed it in the first place?

[=Panther=]

ShaderLineDrawAsWire change back to false...where is this line located and why would it need to be changed back to false if I never changed it in the first place?

 

It was the previous 'hack' to get the data on the exported MFD to be easier to read. If you didn't change the value to 'true', then it won't apply to you.

Edited August 19, 2018 by =Panther=

[Sustoja]

Fixed the blurry fonts in the MFD and the HUD following RightStuff's advice from this thread: https://forums.eagle.ru/showpost.php?p=3555460&postcount=117

 

I just edited "MDG_strokesDefs.lua" file and reduced the values in its first two lines:

 

C:\Eagle Dynamics\DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\Common\indicator\MDG_strokesDefs.lua

 

Before:

stroke_thickness = 0.8

stroke_fuzziness = 0.5

 

After:

stroke_thickness = 0.4

stroke_fuzziness = 0.2

 

Didn't change anything else. My monitor resolution is 3440x1440.

 

This was my F1 view before changing values:

 

 

And this after changing them:

 

 

Best regards,

 

Juan Andres "Susto"

[BoneDust]

Anyone have good settings for the Oculus Rift?

[bnyhwkr]

I'm not sure if this is the same problem. I use my export lua for the A-10C and fly the F-18C it puts the MDIs in the correct place on the second monitor inside of the cougar controllers. The problem is the exported MDIs are really blurry. the A-10C exports are clean and flawless. so this must be a dcs glitch??

[fitness88]

It was the previous 'hack' to get the data on the exported MFD to be easier to read. If you didn't change the value to 'false', then it won't apply to you.

 

 

 

Does this work in VR?

[Mule]

Anyone have good settings for the Oculus Rift?

 

I was just about to ask the same question. I think changing those settings are more dependent on how good your eyes are at long distance. It's going to be a very personnel thing for VR users.

 

I'm going to mess around with those figures and see what I can come up with because I have to wear glasses for driving etc.

[Mule]

Just tried it for VR.

 

A quick test. I saw a noticeable difference. Objectively it wasn't to my liking but if you change them you will notice something.

 

I have only tried one change just to see if it works.

 

Need to do more testing.

[wilbur81]

Great find. But won't this have to be done after every single update? Here's to hoping for an internal fix. I know they've got a lot on their plate, though.

[Raisuli]

I'm not sure if this is the same problem. I use my export lua for the A-10C and fly the F-18C it puts the MDIs in the correct place on the second monitor inside of the cougar controllers. The problem is the exported MDIs are really blurry. the A-10C exports are clean and flawless. so this must be a dcs glitch??

 

I have the same problem. I also created an export for the AMPCD and if memory holds (I don't use any of it yet hoping they'll fix the resolution issues) it had the same behavior. Now I have 3 cougar MFDs (4, actually) and 3 small monitors to use for the screens, all sitting in a nice pile waiting for it to all work right.

[=Panther=]

Does this work in VR?

 

IIRC it was worse with the value "true" in VR. I did that way back when the Hornet first rolled out.

[Targanon]

OK so it appears the Stroke files have been replaced with other files now.

 

as I don't have them but I have been playing with the lua files in the cockpit scripts folder..

(backing up first of cause)

 

I'm fairly happy with mine now..

Changed these lines in the folding files.. this is in the main Install folder of your DCS.. you will need to backup anything before you change it and remember this is only good till the next update.

 

 

\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\MDI_IP1556A\indicator\MDI_init.lua

 

 

 

shaderLineDefaultThickness = 0.3

shaderLineDefaultFuzziness = 0.1

shaderLineDrawAsWire = false

shaderLineUseSpecularPass = true

 

\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\HUD_AVQ32\indicator\AVQ32_init.lua

 

shaderLineDefaultThickness = 0.3

shaderLineDefaultFuzziness = 0.1

shaderLineDrawAsWire = true

shaderLineUseSpecularPass = true

 

 

\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\AMPCD\indicator\AMPCD_init.lua

 

shaderLineDefaultThickness = 0.3

shaderLineDefaultFuzziness = 0.1

shaderLineDrawAsWire = false

shaderLineUseSpecularPass = true

 

D:18C\Cockpit\Scripts\Multipurpose_Display_Group\HUD_AVQ32\indicator\HUD_page_defs.lua

 

fontIntercharHUD_norm_120 = 1

fontIntercharHUD_mid_120 = 1

 

I have 1080ti and 38" monitor viewsonic 3840x1600 @80Hz and yes I still run V.sync get solid 80fps all day long..

[bnyhwkr]

im not sure why you would have to change to files if the fonts look crisp and clear on the cockpit. I mean if you lean forward or zoom out or in then the displays work without fault why would they change on a different location on the same monitor monitor you are only changing the location on the "single monitor configuration. The A-10C exports work no problem. Im just not a IT geek so to speak, i guess. would some one kind of explain a little more why this is the case.

[fitness88]

IIRC it was worse with the value "true" in VR. I did that way back when the Hornet first rolled out.

 

 

Where exactly are you seeing and setting 'true' or 'false'?

[=Panther=]

Where exactly are you seeing and setting 'true' or 'false'?

Note Default unaltered setting is "FALSE" recommended value is also "FALSE".

 

OK so it appears the Stroke files have been replaced with other files now.

 

as I don't have them but I have been playing with the lua files in the cockpit scripts folder..

(backing up first of cause)

[...]

 

\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group\MDI_IP1556A\indicator\MDI_init.lua

 

shaderLineDefaultThickness = 0.3

shaderLineDefaultFuzziness = 0.1

shaderLineDrawAsWire = false

shaderLineUseSpecularPass = true

[...]

[fitness88]

Note Default unaltered setting is "FALSE" recommended value is also "FALSE".

 

 

 

It is by default 'False' so there was no changing it...however in VR there is no difference.

Thanks for the follow-up.

[Targanon]

@ =Panther=

 

I only put the un-altered lines in as a way of marking it easier to find the changes I made..

 

 

I think the reason we are having to do this is because the simulated low res DDI's used I think that's the purpose of the fuzziness setting I've not tried it with 0.0 yet but its on my list of things to try out.. I guess after the next patch I"ll give that a go..

[=Panther=]

@ =Panther=

 

I only put the un-altered lines in as a way of marking it easier to find the changes I made..

 

 

I think the reason we are having to do this is because the simulated low res DDI's used I think that's the purpose of the fuzziness setting I've not tried it with 0.0 yet but its on my list of things to try out.. I guess after the next patch I"ll give that a go..

 

I’m aware. I was using your post to answer the previous post, regarding the false value question. When hornet was first released, that value was changed to “TRUE” but that is no longer a recommended fix.

[Hammer]

Would you like to sell the 4th one?