F/A-18C Modern MPD v 2.1.54 - Updated 25/4/2025

[CapnCoke]

37 minutes ago, Scal said:

I understand your point.
But today I do not want to use the realistic hud addon because it crops the view which I don't like (too realistic today for me)
Could you have 2 versions of the alpha value ? with or without the the realistic hud addon.

BTW, do you know if in VR we can increase the brightness (and perhaps also the thickness) of the HMD ? It is sometime difficult to see with my Quest3...

 

You can make a copy of the folder, rename it to f18c modern mpd (norealhud) then modify the alpha to the one you mentioned. Also you dont need to restart the game to enable my mod or any of its addons. Aslong you spawn in a hornet, it will refresh the cockpit folder.

For the HMD, i feel you and ive been there. if you go to materials.lau, try increase the alpha value in line 102. Some people also increase the green rgb value above 255 and it increases its luminosity. In fonts.lua, there should be in line 291 thickness and fuzziness of the hmd. Higher fuzziness can make it thicker and brighter. While thickness just makes it thicker. You need to play with it. How I do it is I edit it, save (Ctrl+S) without having to close the editor. Disable and Enable the mod, then ingame I leave the jet then enter the jet (Right Alt + J). Then observe changes. Start with thickness 0.8, Fuzziness 0.5, then go higher 1 by one so 0.8 thickness and 0.6 fuzziness. For symbology thickness, its a bit complicated because it depends if you're using jhmcs II or not. If you're not goiing to use JHMCS II, then hmd_symbology_def.lua you can edit the symbology thickness and fuzziness in line 93 and 94.

Edited May 2, 2024 by CapnCoke

[Scal]

10 hours ago, CapnCoke said:

You can make a copy of the folder, rename it to f18c modern mpd (norealhud) then modify the alpha to the one you mentioned. Also you dont need to restart the game to enable my mod or any of its addons. Aslong you spawn in a hornet, it will refresh the cockpit folder.

For the HMD, i feel you and ive been there. if you go to materials.lau, try increase the alpha value in line 102. Some people also increase the green rgb value above 255 and it increases its luminosity. In fonts.lua, there should be in line 291 thickness and fuzziness of the hmd. Higher fuzziness can make it thicker and brighter. While thickness just makes it thicker. You need to play with it. How I do it is I edit it, save (Ctrl+S) without having to close the editor. Disable and Enable the mod, then ingame I leave the jet then enter the jet (Right Alt + J). Then observe changes. Start with thickness 0.8, Fuzziness 0.5, then go higher 1 by one so 0.8 thickness and 0.6 fuzziness. For symbology thickness, its a bit complicated because it depends if you're using jhmcs II or not. If you're not goiing to use JHMCS II, then hmd_symbology_def.lua you can edit the symbology thickness and fuzziness in line 93 and 94.

 

Thanks for your hints !!!

I've already modified the alpha (see picture). I will have not to forget to change it at each of your releases. That's why I was wondering if you could have an "if..then" in your code to distinguish if the realistic hud is on or not...

From your delivery I use the base and the JHMCS II. I will make some trials as you propose for the HMD and let you know...

Edited May 3, 2024 by Scal

[CapnCoke]

6 hours ago, Scal said:

Thanks for your hints !!!

I've already modified the alpha (see picture). I will have not to forget to change it at each of your releases. That's why I was wondering if you could have an "if..then" in your code to distinguish if the realistic hud is on or not...

From your delivery I use the base and the JHMCS II. I will make some trials as you propose for the HMD and let you know...

 

I see your concern. Currently I don't think I need to add anything to check if realistic hud is on and off since the alpha value is controllable via the brightness knob in the cockpit. Realistic hud does not touch thickness/fuzziness value of the hud.

For JHMCS, that's another issue and I need to put a value that fits for VR/2D users. Was the default JHMCS thickness/fuzziness value (Clean F18 with no mods) work well with VR?

 

Another issue why I'm having constant battle with thickness/fuzziness other than it changes because of your fov is that DLAA/MSAA also changes how fonts look. At early versions, I've been working with DLAA and it looked the best with it. But the ghosting effect bothered me so I switched back to MSAA and noticed it was too thick/blurry and had to adjust it again.

Edited May 3, 2024 by CapnCoke

[Scal]

1 hour ago, CapnCoke said:

I see your concern. Currently I don't think I need to add anything to check if realistic hud is on and off since the alpha value is controllable via the brightness knob in the cockpit. Realistic hud does not touch thickness/fuzziness value of the hud.

For JHMCS, that's another issue and I need to put a value that fits for VR/2D users. Was the default JHMCS thickness/fuzziness value (Clean F18 with no mods) work well with VR?

 

Another issue why I'm having constant battle with thickness/fuzziness other than it changes because of your fov is that DLAA/MSAA also changes how fonts look. At early versions, I've been working with DLAA and it looked the best with it. But the ghosting effect bothered me so I switched back to MSAA and noticed it was too thick/blurry and had to adjust it again.

 

In VR I use DLAA mainly because in the DDIs the lines and texts are a bit "destroy" (oblic moving artefacts) with DLSS, with reasonable parameters I'm at a good 70-80Hz
With a 32x9 screen and Winwing DDIs, I use DLSS-quality, max DCS parameters and a stable 120Hz.

Edited May 3, 2024 by Scal

[CapnCoke]

Update v2.1.2 adds a nice helpful feature for SA and BVR. I'm going to be taking a break before updating again.

I've reverted most font/symbology changes to default because I think it gives a nice balance between users who use DLAA and MSAA, and also provides good brightness for different mission weather types. I boosted the outline just a tiny bit for the VR users, but it might not be enough. JHMCS thickness/fuzziness was also reverted back to default but I included a line to check if JHMCS II is installed, then any changes I've made in JHMCS II will be applied. Any changes I made in the HUD will be stay.

As for the SA changes. Theres no a half scale ring, and a gimbal limits indicator. This is the source I've used coming from a SuperHornet simulator.

nullFinal result

I've attempted to make it where it reflects the current radar settings and heading but unfortunately it was proven to be difficult as I cannot retrieve the desired parameters. It might not be impossible and someone might be able to figure it out.

 

With all these updates rolling out daily, I need to find a method for users who has customized their MPD colors, and not have them overwritten everytime they update.

Edited May 3, 2024 by CapnCoke

[CapnCoke]

Apologies, was fooling around in a mission and noticed something strange with JHMCS II appearance. I've missed a line which made some elements look thick. Uploaded version 2.1.25. Also adjusted JHMCS II Yellow unknown material alpha.

[Tusk.V]

Really liking this mod! Thank you!

[Scal]

Hi !
How do you use in the SA page the half circle.
I tried to change in the radar page the scan angle and position but it does not change the SA circle

Edited May 6, 2024 by Scal

[CapnCoke]

1 minute ago, Scal said:

Hi !
How do you use in the SA page the half circle.
I tried to change in the radar page the scan angle and position but it does not change the SA circle

 

Hi, you mean the radar scan azimuth arc? Currently that's going to be stuck at 140 degrees. Tried to find a way to tie it with the radar but we modders can't access the controllers.

[Scal]

1 hour ago, CapnCoke said:

Hi, you mean the radar scan azimuth arc? Currently that's going to be stuck at 140 degrees. Tried to find a way to tie it with the radar but we modders can't access the controllers.

Are you going to keep it if it is useless ?

[CapnCoke]

11 hours ago, Scal said:

Are you going to keep it if it is useless ?

The arc will always show your radar gimbal limits. It's been really useful when I'm at a narrow 20 azimuth scan but positioned myself to quick lock targets that was cold turning hot on the other extreme limits of the radar. I run my hornet left MPD with the SA page and right MPD with the attack radar page.

[CapnCoke]

3 hours ago, Vortexstate said:

This mod was working for me until the new update, to which I've the mod with OVGME and manually, both the correct ways, and it still doesn't work. Can you check this out, please?

Hi, thank you for bringing this to my attention. I don't have much time as I used to when developing this mod, but I'll try to get an update out ASAP.

[Drac]

5 hours ago, Vortexstate said:

This mod was working for me until the new update, to which I've the mod with OVGME and manually, both the correct ways, and it still doesn't work. Can you check this out, please?

Mod seems to still work for me, unless I'm missing something.  Out of curiosity, what is the issue you are having?

[CapnCoke]

Hotfix: Mod updated to incorporate fix included In DCS official update DCS 2.9.5.55300 "Fixed: SA page TDC acts differently from RDR ATTK and AZ/EL TDC, should work the same way.".

I also did a quick sweep for all the important files and see if anything changed but didn't catch anything else. It was tedious but that's the nature of modding. If you're a player that alternates between vanilla and the mod and noticed some strange or missing behavior, let me know. It will make my job easier that way.

Anyways, I'm done with my F4E honeymoon and will be hopping back with the F18. I can't really see anything worth adding to the mod at the moment (That is moddable ofcourse). I might divert to a different path of MPD design instead of trying to replicate what the Super Hornet uses. Maybe dabble with the f16 a bit and try to get some inspiration from there.

 

[CapnCoke]

Minor update: Todays update is a treat for players who enjoy nighttime operations. Added NVG support to HMD with JHMCS II.

Some changes were done with MDI and AMPCD element properties to allow compatibility with NVGs and night time operations. Also, changes were done to JHMCS color elements to be compatible with night/nvg operations. The MDI/AMPCD brightness knob should adjust the new colors now (For the AMPCD brightness knob to work, you have to disable the map. This is a bug with the unmodded hornet).

Due to limitations, I cannot separate the jhmcs colors and NVG (JHMCS II is behind the NVG so colors should work irl but impossible ingame). Also, due to how NVG shaders works ingame, set the HMD brightness knob between 1-5% (As minimum as you can) or certain elements are really bright.

Also, there is a bug that causes blur to elements that are behind your cockpit frame. This is a known bug that affects the A10C II Scorpion HMD and was reported a while ago but still no fix. You can use TAZ Nvg mod to fix that. However, it will break Pure Client Integrity check.

 

As always. Please leave some feedback/bug reports.

 

Edited June 16, 2024 by CapnCoke

[Steel Jaw]

Don't understand...is this for the legacy hornet? 

[CapnCoke]

1 hour ago, Steel Jaw said:

Don't understand...is this for the legacy hornet? 

Includes for legacy hornet, and for cjs superhornet mod.

[CapnCoke]

I uploaded the wrong version which was missing a single comma that broke the right MDI. So I tested the wrong version before uploading. Uploaded v2.1.36 which fixed it. Apologies for the oversight.

[CapnCoke]

Hotfix v2.1.37 is out to fix JHMCS not working with the new patch. I also managed to translate the scorpion fixes with NVG to JHMCS II. The blur mask issue when looking at certain parts of the cockpits is now fixed. Also, you can now see color through NVG as intended. Check screenshots below. Note that you do not need to set HMD brightness to minimum anymore.

I still haven't reviewed the other changes from the new patch as I was focusing on getting this hotfix out quickly. So I want to leave a disclaimer that there might be other bugs when using this mod.

 

nullnull

[CapnCoke]

V2.1.4 is out. I compared every line with the current official F18C and made the necessary changes to my mod. This update includes all the additions and removals made by ED, ensuring that the mod reflects every change from the new patch.

The mission of this mod is to provide a fresh new feel without compromising any minor changes from the official F18. Hopefully I've achieved that in this patch. Enjoy your weekend!

Edited July 12, 2024 by CapnCoke

[CaliJoshua]

3 minutes ago, CapnCoke said:

V2.1.4 is out. I compared every line with the current official F18C and made the necessary changes to my mod. This update includes all the additions and removals made by ED, ensuring that the mod reflects every change from the new patch.

The mission of this mod is to provide a fresh new feel without compromising any minor changes from the official F18. Hopefully I've achieved that in this patch. Enjoy your weekend!

 

Thank you for the fast update

[CapnCoke]

Uploaded v2.1.41. Fixed Mach/Alt not showing in SA page when hovering cursor over contact. Thanks to Spock for pointing it out. Was hoping yesterday's patch was a clean release. Turns out ED did not remove some lines but moved them somewhere else and I wasn't able to catch it.

[EA-18G_BlockII]

On 7/12/2024 at 8:07 AM, CapnCoke said:

Hotfix v2.1.37 is out to fix JHMCS not working with the new patch. I also managed to translate the scorpion fixes with NVG to JHMCS II. The blur mask issue when looking at certain parts of the cockpits is now fixed. Also, you can now see color through NVG as intended. Check screenshots below. Note that you do not need to set HMD brightness to minimum anymore.

I still haven't reviewed the other changes from the new patch as I was focusing on getting this hotfix out quickly. So I want to leave a disclaimer that there might be other bugs when using this mod.

 

nullnull

damn what kind of magic did you use?

[CapnCoke]

6 minutes ago, EA-18G_BlockII said:

damn what kind of magic did you use?

I'm not sure if ED read our report or if they were working on it already but there was a bug report about the A10C Scorpion with NVG blurring some elements when looking at the cockpit frame. I added that since the scorpion is behind the HMD we should also be able to see colors. They fixed it in this patch and I just observed the changes done to the A10 and implemented it for the JHMCS II

[Dunska]

Thanks so much for this CapnCoke.  I'm using the mod v2.1.41 with the addons under DCS 2.9.6.57650, but I'm not getting the JHMCS showing in the NVGs.

I've tried enabling the main mod and the addons as separate mods, and also just combining them all into one mod (as no files seem to be duplicated or overwrite), but still don't get JHMCS in the NVGs.

Any ideas?