MadKreator

Yes thats very possible. I’m sure there’s a reason they are the way they are, at the moment.

The sentiment is very much appreciated. I'm happy people are using them! No I don't think there is a divide between the two regarding viewports, I think its just not an important part for them to focus on. Or they are slowly working on a way to do them slightly differently. Oddly, the ch-47 viewports are all located in a folder called GC Base, not in folders withing the aircraft files like every other module. Why its done like this is a mystery to me.. I'm hoping there is a bigger picture at play. a couple of the viewports like the chronometer and sfd's, I had to add the scripts too, but the rest of them already had the scripts in there.. Hopefully they will just name them and un-comment them one of these days so they are natively available.

I agree the UI elements need to be configurable, in some way. All aircraft are affected the same. Fc3 and full fidelity, alike. It would be a welcome change, for sure. I don't use the controls indicator, but the kneeboard and crew indicators for helis are big on my personal list of wants. I edit them anyway to size and place them where I want but it would be nice not to have to mess with editing the core lua files to do so.

The IC breakers aren't the monitor configurations themselves. In the case of the CH-47 and many others it's because the viewports are natively exportable. The "patches" we write for Helios have to modify the core viewport files to let them export... Ironically its the same two lines of script that is built into DCS that let things like mfd's, tedac, etc export.. Odd case in the CH-47 is that the lines of code are already in each(most) file but they don't have names and are commented out. Why they were written in the files and then blocked from use? Your guess is as good as mine lol Some viewports can be exported without breaking ic but it is a very limited list.. LEFT_MFCD, RIGHT_MFCD, CENTER_MFCD, TEDAC, ABRIS, Shkval, are the ones I can think of off the top of my head.. oh and all of the viewports in the JF-17 are natively exportable from DEKA. .. In the CH-47, the only one that works with native naming is RIGHT_MFCD

The problem with the UI elements and multi-monitor use is that the position and scaling is based off of and references the entire "screenspace"in the lua files (as you know). Ideally it should be confined to what is designated as "viewport.center"... the main display for the game. Kneeboard, controls indicator, crew indicator etc all affected .. Why they aren't changeable options like the chat window and messages, who knows. Unfortunately, multi-monitor setups are at the very bottom of their list. Plenty of people have been screaming for literal years to make changes to allow more viewports exportable, change location of UI elements, make exports not break IC etc.. truth is ED doesn't care one bit about this part of the "core", hate to say it, but its very obvious. Addressing these things doesn't make them $$$ so the chances of them working on it is next to nothing. They have their own roadmap and vision and the low thousands of users ( based of the number of users of the Helios discord as a baseline) isn't strong enough for them to waste time on. Trust me, I would LOVE to be proven wrong as I'm a huge advocate for multi-monitor use, exporting etc etc, but I quit holding my breath long ago.

1.0.6 Added the manual file replacements as "patches" to profile so no need to change anything manually. Helios has been re-written to allow "patches" for user mods. 1.0.7 Fixed bad/missing file paths in Controls Indicator in Day version. Download Profile here---> https://github.com/HeliosProfiles/DCS-OH6A-Profile-by-MadKreator37/releases/latest

1.0.6 Added the manual file replacements as "patches" to profile so no need to change anything manually. Helios has been re-written to allow "patches" for user mods. 1.0.7 Fixed bad/missing file paths in Controls Indicator in Day version. Download Profile here---> https://github.com/HeliosProfiles/DCS-OH6A-Profile-by-MadKreator37/releases/latest

I was just flying some MP and thought the same thing. Would be nice if there was some variety. At least to differentiate: mission targets in general (server choice if allowed), player (not you) placed markers, your current mission target and your placed markers.

Excellent! Can’t wait. Day one purchase for sure!

Just to note: * Helios does not and should not ever be required to run as administrator. If you have to run Helios as administrator to get it to function then you most likely have other permission settings/issues on the PC. * Helios versioning has no effect on displays. Helios has absolutely no control over exported displays or monitor types. Other than taking the monitor configuration as set in windows display settings and writing a compatible monitor file for DCS. Exports are solely a function of DCS, not helios. Helios does not need to be running for your monitor file to be read and executed by DCS. It only tells DCS where in the total screenspace to place which export and how large it should be. The same way if you created or re-created the monitor file manually.

I sure hope so. Especially with the new(ish) rain effects. Flying helis like the Huey is super annoying in the rain.

@Cyking Great to hear of future improvements. I agree, a different ship with heli-pad would be a bit easy. Nothing wrong with the containers, especially if it’s a Huey/ED issue itself. Maybe a little inconvenient atm, but I’m not going to cry over it Still loving your work and it’s greatly appreciated! @MAXsenna funny, funny guy!! Land with the front of the skids first What kind of pro do you think I am Although I feel like with the Moza and FFB I’m getting much better… Which btw ( not to sidetrack the thread too much, updating our previous convo), I’m really loving the Moza now, very glad I didn’t return it. I can say now that I would in fact recommend it…or rather, knowing what I know now, I would purchase it again. I don’t think I’ll ever go back to non-ffb. Although winwing has beaten their price by $130 now and with more force( if really needed), albeit a bit bulky/ cumbersome looking unit. The software will be the tell tale. Mozas last update is much better but still some things to work out with accurate centering.

@Cyking I’m having the same issue with mission 5 as of yesterday (3-19-25) . Landing on the containers still causes a “collision” no matter how softly i can touch down. Bits go flying in the air and the heli just starts sliding off the containers by itself. One time it triggered the event to load the passengers, even though I touched down , then hovered over the containers… it loaded all but the last one. I hovered for several minutes but never got the cue that the final passenger was onboard. Tried several more attempts , both touching down first, or just hovering in various spots and could never get the trigger to fire again. Not so sure there is a campaign issue as much as an ED issue with the heli coming in contact with the containers/ objects. If I remember right several months ago people were having the same issue landing on some FOB helipads. ( I can only imagine the chore it must be to constantly deal with changes ED makes ( or breaks) behind the scenes. - Like others, my only real complaint( which isn’t bad since I can also read), is that the voice overs are kind of hard to hear. Maybe they’re a bit quiet, or too much static effect.. but not a deal breaker. It kind of gives the feeling of an old radio from the 60’s/ 70’s. - All in all, I’m having fun in the campaign. Great work!

“DCS Web Editor” 3rd party project.. eventually free but currently seems to still be a patreon only access between $4 and $15/mo, depending on how advanced of features you want. . Might be what you're looking for, although paywall… I’m not much of a mission designer but I would have to agree that since DCS is very heavily focused around the Mission Editor, it need some significant advancements in to bring it up to date and be a bit more user friendly and collaborative.

I ran a 49” ultrawide for quite some time and noticed the same. It’s just the effect the FOV has. It’s reduced when you zoom the fov in, but still there. Not sure if it’s lack of special ultrawide support or just the nature of the beast. It can definitely be annoying at times. I can understand some distortion of object as the FOV warps around but I never understood why it magnified objects so much.

Yes all viewports being natively exportable would be awesome! However many there are

Awesome. Can’t wait! Another day 1 purchase for me.

I will agree, Helios is the way. And fully agree with WRCRob that exporting displays and things should be integrated more efficiently AND not break IC for the MP people. ED’s internal API lets them drag and drop viewports from a list. Early last year a dev implied he may be able to open that up to the user end, but so far nothing has come of it. Over the years, you will come to find that multi-monitor users are pretty much last on the list as far as DCS/ ED is concerned. Unfortunate, but reality. However there are easier ways than randomly typing coordinates.

I will agree with this. I do use trackIR but in some aircraft I also use the absolute camera ( warbirds mostly) on a stick axis. It would be very nice to have the view position stay put instead of snapping back to center. Not a deal breaker but it would be a nice QOL feature, just because.

Yes please! Or at very least confine them with reference to viewports.center and not in reference to the total screenspace/aspect. That way they would, at a minimum, be rendered on the main screen where the game is rendered( just as with using a single monitor). Not rendered in virtual space half off the screen ( or fully in some cases) and 3x larger than they should be( looking at you kneeboard, crew and controls indicators).

Also would very much love to see a P-38 in development.

I’d love to know as well. I managed to edit the color of the main title on each page of the comms menu, but that is the only hexadecimal color value I found in the comms menu files. For the rest of the menu the colors thats seem to be referenced is “white” or “yellow”, but I never found where those values were defined. Or if there was any other color names available. I suppose you could swap them so the menu options show up in yellow instead of white, but I didn’t try that. I also didn’t test other random color names.

This seems like a good idea. No different than IFLOS, the Controls Indicator, Cargo indicator etc. Optional of course.

I like that bit about starting George automatically. Yours looks better than mine. I just slapped some parts in, along with AceFlights CPG grips from his profile, which I don’t use now anyway since I have more than enough buttons between the stick, jet throttle, add on button/levers and now an actual collective lol.. When I jump to the CPG in mine, I have the KU totally hidden with a button to open it up. So far I only use it to set the ranging to auto, and maybe add WP’s to a flight plan if use “The Way” to input the points for me, I didn’t put a ton of effort in, honestly. I was just learning the Apache recently so I just wanted something to get by that was useable in both cockpits. I have been meaning to re-organize it and make it a little nicer. Now I got sidetracked starting the Mossie profile that I’ve been meaning to do for a year. I may just borrow your profile, if thats alright.. literally, mine is borderline embarrassing lol

So I did make an Apache profile much the same way you did. Organized a bit differently but same exact Idea with the KU over top of the tedac