MadKreator

@MAXsenna Here's a night one F-5E_Night_1.0.4_MadKreator37.hpf

No prob. You can change the button images in the editor to the “generic button’ pressed and normal in the f5e files so it matches the rest of them , then add a label to it in the text editor..

Here you go @MAXsenna F-5E_1.0.4_MadKreator37.hpf I'll do the night one for you after dinner.. you can change the button, I just grabbed one from the Helios toolbox

@MAXsennahaha just tried that.. I had no clue it did that. I've used the profile for many months now and have never seen that... If its how I think it is, then yes its possible, but you would have to drag out an empty panel from the toolbox, make it the size of the entire screen, then select everything in the profile ( except viewports and the new panel), then ctrl-c to copy then double click into the new panel, then ctrl-v to paste everything in there. go back to the "monitor 2" or whatever and delete everything... then add a push-button that has an output bound to "toggle hidden", that new panel... Same effect as I did on the F-15E to switch between Pilot and Wso, only in this case its hiding the panel. Possible that it was an unintentional side effect. - looking at the bindings its all done properly, just like the f-15e but i made the pilot/wso buttons hide when switching so you cant repeat the press.. inCZ's both buttons are still active.. give me a minute and I'll try it for you f5e hide profile.mp4

What overlay? Like Helios in general? I’ll look at the Huey, I’m not sure what you mean, exactly In Helios’ options you can disable the “Always on top” function , so you can use other apps on top of it, and it won’t always cover them.. I have never tried to see if it messes with the functionality though.

V1.0.4- Adjusted viewport names to match, minor UI adjustments. Recommended to delete other F-5E profiles and the F-5e images from Documents/Helios/Images/Madkreator37 before installing the Day/Night Versions https://github.com/HeliosProfiles/DCS-F-5E-Profile-by-MadKreator37/releases/latest

V1.0.4- Adjusted viewport names to match, minor UI adjustments. Recommended to delete other F-5E profiles and the F-5e images from Documents/Helios/Images/Madkreator37 before installing the Day/Night Versions https://github.com/HeliosProfiles/DCS-F-5E-Profile-by-MadKreator37/releases/latest

This is what I do as well, basically. I get reshade setup so the exports are good at night, and just turn it off during day flights, on most aircraft.

*I forgot to put a couple of the new day images into the night images last night. Had them ready to go but put them in the wrong folder. Fixed this morning, same release number. If you download it again and do the first part of the install and let it overwrite it will place the new images in the folder. ( just the hook button and the select jettision panel).

*I forgot to put a couple of the new day images into the night images last night. Had them ready to go but put them in the wrong folder. Fixed this morning, same release number. If you download it again and do the first part of the install and let it overwrite it will place the new images in the folder. ( just the hook button and the select jettision panel).

New version 1.0.3: Recolored cockpit to more closely match the F5-E remaster. Along with it comes a night version of the profile and a little bit of UI cleanup I recommend fully deleting the existing profile and images. Or at least make sure to " ALLOW IT TO OVERWRITE THE EXISTING FILES" when it asks. Download here: https://github.com/HeliosProfiles/DCS-F-5E-Profile-by-MadKreator37/releases/latest

New version 1.0.3: Recolored cockpit to more closely match the F5-E remaster. Along with it comes a night version of the profile and a little bit of UI cleanup I recommend fully deleting the existing profile and images. Or at least make sure to " ALLOW IT TO OVERWRITE THE EXISTING FILES" when it asks. Download here: https://github.com/HeliosProfiles/DCS-F-5E-Profile-by-MadKreator37/releases/latest

I will say that 5.0 has been great… except on IRAQ. Flying near or through mountains absolutely tanks my performance. Normally on Extreme, uncapped with pretty much all settings maxed( except shadows on med and terrain shadows flat), i can get around 90-110 fps( 120 up high), so I purposely cap at 60 to give overhead for running Helios, track IR, and flying at treetop level through canyons, etc… but on Iraq with view kicked up to 5.0 will drop me down into the low 30’s/high 20’s even, without Helios or Track IR. Iraq is a good looking map but whoa baby is she a performance hog! - What would be nice is if the visibility range didn’t require a game restart.

Ver 1.0.4 Updated profile. Minor UI changes/ cleanup. Nothing crazy. https://github.com/HeliosProfiles/DCS-Spitfire-LFMkIX-Profile-By-MadKreator37/releases/latest

Updated profile. Minor UI changes/ cleanup. Nothing crazy. https://github.com/HeliosProfiles/DCS-Spitfire-LFMkIX-Profile-By-MadKreator37/releases/latest

New Version: 1.0.3 - Fixed Stick Position Indicator https://github.com/HeliosProfiles/DCS-CH-47F-Profile-by-MadKreator37/releases/latest

New Version: 1.0.3 - Fixed Stick Position Indicator https://github.com/HeliosProfiles/DCS-CH-47F-Profile-by-MadKreator37/releases/latest

Even cranked up to 5.0 it’s not like there’s buildings visible 30 miles away or anything. Yes it extends the range, but what I notice most is there is more density, if you will, at farther distances, so the buildings “popping in” is reduced. It’s not as dramatic of an effect as one may think. It just feels a bit more “full” but not to the point of unrealistic. … imo

@Mustang added this via Open Mod Manager package. Exactly as in the screenshots and all works well. Insane (5.0) is great! No artifacts or any oddities that I can see, even on Sinai( I was getting some artifacts with LOD’s when altering some of these in the past, like bandit had). Just buildings for days! Good show! @NineLine thank you for passing this idea on. Easy to implement, and adds a very welcomed level of depth. Along side some scenery LOD adjustments( full level LOD’s rendered farther out), this would be stunning, especially for heli pilots.

New CH-47 Profile V1.0.2. Added Controls Indicator, Splash Screen, LAlt/RAlt modifiers, other minor adjustments. If you've installed the temporary "hotfix" interface in Documents/Helios/Interfaces/HeliosInterfaces, you can get rid of it if you updated Helios to 1.6.6120.0002 https://github.com/HeliosProfiles/DCS-CH-47F-Profile-by-MadKreator37/releases/latest (edited)

New CH-47 Profile V1.0.2. Added Controls Indicator, Splash Screen, LAlt/RAlt modifiers, other minor adjustments. If you've installed the temporary "hotfix" interface in Documents/Helios/Interfaces/HeliosInterfaces, you can get rid of it if you updated Helios to 1.6.6120.0002 https://github.com/HeliosProfiles/DCS-CH-47F-Profile-by-MadKreator37/releases/latest (edited)

Sad times for a CORE feature that’s been a part of DCS since… its inception(2011-ish?), and only ever gaining in popularity. Easily resolved by a couple lines of script and a name in each viewport file ((script that’s also native in DCS)…. Of course third party’s need to follow suit too… except DEKA, they nailed it. In the jf17, every viewport is natively exportable and does not break IC when doing so.

Okay no worries, I’m not sure why Helios writes it the way it does either, I’m not a lua guy myself. The Helios dev has a much better understanding of it than I. I’m going to forward your remastered ones to him ad see what he thinks of the difference. Again, just my own curiosity on the subject. - as far as the Helios “Custom Names” for some viewports. It does still write them this way as that is the way the viewports are created in the profiles.. Up until recently, Helios did not use the “Display Tables” format, individualizing each aircraft. It just wrote a big list of custom named viewports so that things like mfd’s could be used on multiple airrcraft, in different sizes and locations all in the same monitor profile. Now with recent changes, it sbeparates each aircraft so any default naming like LEFT/RIGHT/CENTER_MFCD can be used in each aircraft. However those still need to be changed in each profile manually. Other viewports that aren’t native( DED, RWR’s, IEFI,EUFD, most of the CH-47 etc) still need the custom names to function… IC breakers.. However the viewports can be removed easily from a profile and Helios “Patches” ( viewport lua modifications) can be undone with a couple button clicks if the user wishes. Thats why you see lots of mix and matching going on with custom named ones. For anything DCS allows as a “Native” export, the custom names are not needed and the “patches” can be removed from the luas, but its expected that the user do this themselves if desired.. at this point in time.

I saw the error found. Jonsky nailed it.. I was just curious about the added extra lines, nothing more… just being nosey

@MAXsenna your original looked like it had quite a few viewports in the old Helios format at the end ( just a list of custom named viewports). Were those written in by you on top of the Helios generated file?