Capt Zeen F/A-18C Beta Helios Profile ! ! !

anyone already patched today? can you confirm helios for the fa18 still works with Capt Zeens package? or did someone encounter any errors?

With the update today, the MFDs on the second screen are not easy to read and the labels near the buttons are impossible to read. Oh well, one step forward and one step back.

I am experiencing the same problem as Sobe.

My DDIs have reverted to the previous thin/faint lettering. Not as bad as they were originally before amending the AMPCD_ini.lua line from "shaderLineDrawAsWire = false" to "shaderLineDrawAsWire = true", but worse than before this latest update.

Needless to say the Stable version is still fine.

I also cannot find changes to any of the lines amended by Capt Zeen in his mod.

Same here, these are my exports now, which worked flawlessly before the update:

If I set the first parameter "shaderLineParamsUpdatable" to false it's playable, but worse than before.

Is this even something we can fix ourselves?

After the patch:

Ok....

ED has activated the viewport export for the DDI in this patch, so we dont need to overwrite those luas anymore.

So.. what you need to do?

-First, remove the monitor configuration lua files from DCS using JSGME or OVGME ( probably you installed the files with one of those programs)

-Now, in the folder monitor_configuration of the profile package, you need to delete the folder MDI_IP1556A from Monitor configuration\Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_Group

- Edit the AMPCD_init.lua and set shaderLineDrawAsWire = false

- Now you can install again the modifications using JSGME or OVGME.

In the 2_monitors-FA18C.lua you need to change F18_LEFT by LEFT_MFCD

and F18_RIGHT by RIGHT_MFCD. Thats the names ED uses in his files.

With this changes you will see something similar to my screenshot

..

Fantastic. Thanks for the quick response. I think thousands of flyers were eagerly awaiting your return home to fix the problem.

Thanks !

I don't know If I have understood well, , but surely you'll change the profile for the new patch , Do you ?

Please tell me when It's done, I fear to do something that could broke my Simulator code . . .

Thanks ! ! !

Thanks mate, much appreciated

Just installed it and am trying to set it up. I have all of the viewports working except for the UFC. Does this work, or has it been porked by some update?? Just wondering what I am doing wrong??

Also, what is the LEFT_MFCD in the MonitorSetup? I don't see what that is for.

Great work as always Capt!!! Thank you for your time and excellent work!!

EDIT:

I just saw your post above and made those changes. LEFT_MFCD, and RIGHT_MFCD work fine, but the viewports are blurry.

And the UFC does not display anything at all.

What am I doing wrong?

mine is still blurry

I like the left and right DDIs but the button names on the MFCD in the bottom middle are blurry. Post #5 of https://forums.eagle.ru/showthread.php?p=3554661#post3554661 had a suggestion, but I found it too light.

I like the left and right DDIs but the button names on the MFCD in the bottom middle are blurry. Post #5 of https://forums.eagle.ru/showthread.php?p=3554661#post3554661 had a suggestion, but I found it too light.

how did u fix the ddis?

that #5 post did absolutely nothing

Just installed it and am trying to set it up. I have all of the viewports working except for the UFC. Does this work, or has it been porked by some update?? Just wondering what I am doing wrong??

 

Also, what is the LEFT_MFCD in the MonitorSetup? I don't see what that is for.

 

Great work as always Capt!!! Thank you for your time and excellent work!!

 

EDIT:

I just saw your post above and made those changes. LEFT_MFCD, and RIGHT_MFCD work fine, but the viewports are blurry.

And the UFC does not display anything at all.

 

What am I doing wrong?

the exported UFC is very dark by default, so turn up the UFC brightness with the button on the cockpit.

Probably related to the bug were the DDI fonts were rendered weirdly if playing at resolutions of >1440p?

I have the blurriness as well but I use a 4K screen.

the exported UFC is very dark by default, so turn up the UFC brightness with the button on the cockpit.

Probably related to the bug were the DDI fonts were rendered weirdly if playing at resolutions of >1440p?

I have the blurriness as well but I use a 4K screen.

Have mine on a 1280x1024 screen, they are blurry also.

Or did you mean the overall resolution of DCS?

Solved: blurry fonts

Just a quick solution concerning blurry fonts on the DDIs:

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

change the follwing values:

Old:

stroke_thickness = 0.8

stroke_fuzziness = 0.5

New:

stroke_thickness = 0.4

stroke_fuzziness = 0.2

This will enhance the fonts and make them more readable.

Pls keep this in mind:

I have have neither tested more/other values nor influences on other fonts (HUD maybe?).

And do not to forget to set shaderLineDrawAsWire back to false. Zeen already made a headsup on this.

Otherwise the fonts will still look garbled, no matter what values you're going to use for the stroke_...

Maybe someone like to support here by testing other values?

Meanwhile I'm going to make a JSGME-file for that viewport stuff. :thumbup:

Just a quick solution concerning blurry fonts on the DDIs:

 

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

change the follwing values:

 

Old:

stroke_thickness = 0.8

stroke_fuzziness = 0.5

 

New:

stroke_thickness = 0.4

stroke_fuzziness = 0.2

 

This will enhance the fonts and make them more readable.

 

Pls keep this in mind:

I have have neither tested more/other values nor influences on other fonts (HUD maybe?).

 

And do not to forget to set shaderLineDrawAsWire back to false. Zeen already made a headsup on this.

Otherwise the fonts will still look garbled, no matter what values you're going to use for the stroke_...

 

Maybe someone like to support here by testing other values?

 

 

Meanwhile I'm going to make a JSGME-file for that viewport stuff. :thumbup:

Nice work well! Thx :thumbup:

For AMPCD:

DMC_stroke_thickness = 0.4

DMC_stroke_fuzziness = 0.2

in same file

Just a quick solution concerning blurry fonts on the DDIs:

 

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

change the follwing values:

 

Old:

stroke_thickness = 0.8

stroke_fuzziness = 0.5

 

New:

stroke_thickness = 0.4

stroke_fuzziness = 0.2

I've tried this solution and it works quite perfectly (with different values) for the exports BUT it completely destroyed HUD and to a lesser extent DDIs on the plane: https://i.imgur.com/Dq0v4CN.jpg

Note that above I had set the values as 0.2 and 0.1 respectively.

With 0.4 and 0.2 like suggested it was still quite bold to me, not as my first screenshots (post #104) but still "worng" and the HUD, while readable, was noticeably thinner. DDIs in the plane were OK.

I've tried Cpt's solution after my post but there was no change at all from my starting point unfortunately.

For now I'm using the original files from before the patch, changing only shaderLineParamsUpdatable = false because it's the most playable to me, even if some aliasing was introduced in the DDIs both plane and exports.

Too bad it was perfect before the patch...

Just a quick solution concerning blurry fonts on the DDIs:

 

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

change the follwing values:

 

Old:

stroke_thickness = 0.8

stroke_fuzziness = 0.5

 

New:

stroke_thickness = 0.4

stroke_fuzziness = 0.2

 

This will enhance the fonts and make them more readable.

 

Pls keep this in mind:

I have have neither tested more/other values nor influences on other fonts (HUD maybe?).

 

And do not to forget to set shaderLineDrawAsWire back to false. Zeen already made a headsup on this.

Otherwise the fonts will still look garbled, no matter what values you're going to use for the stroke_...

 

Maybe someone like to support here by testing other values?

 

 

Meanwhile I'm going to make a JSGME-file for that viewport stuff. :thumbup:

Rep inbound !!

Worked for me too! Thx!

Sent from my Moto Z Play using Tapatalk

@RightStuff these values would be perfect to play with if they also didn't change the thickness/alpha of the HUD.

Do you know if there is a way to tune the HUD itself with similar values somewhere else?

I searched some HUD-related luas but found nothing...

since

DMC_stroke_thickness = 0.4

DMC_stroke_fuzziness = 0.2

alters only the ampcd

and

stroke_thickness = 0.4

stroke_fuzziness = 0.2

alters everything else

i imagine there must be a name for the you could insert before "stroke" to keep the HUD thick.

example:

HUD_stroke_thickness = 0.8

HUD_stroke_fuzziness = 0.4

that line doesnt work, but if we can figure out what to place here:

XXX_stroke_thickness = 0.8

XXX_stroke_fuzziness = 0.4

then maybe we can make it look good

Cloudie, so far: no idea...

But Beamscanner has made a good finding.

Maybe therea some skilled lua-programmers which will pick that up and enhance the code. Even maybe ED themselves? ;)

Hi,

I'm using these export files for a surround monitor,

but for some reason I get the IFEI to start way off the edge of the screen i set for,

i.e. my fourth monitor for instrument start at 6000, and I set it to 6005,

but it starts drawing at around ~6200 ... as if there's a 'tranparent' area to the left of the IFEI that is being drawn.

Anyone has a clue why is that??

Thanks