MadKreator

Option to enable or disable a “background”/ window/ something behind the comm menu in game and the messages to be able to see them easier. Or maybe an option to change the color of the fonts to something other than white

@NineLine #1 reason : The “patches” helios applies places the export script “ try_find_assigned_viewport_…”custom name” “ in each of the appropriate aircraft “viewport” files. Doing this along with the custom names allow helios to place viewports ( mfd’s, ehsi, cdu, ded, rwr’s etc etc) in different locations in different sizes for each aircraft using a SINGLE monitor file. F_16_ left mfd, a10c_left mfd, av8b_ left mfd, can all be exported in different sizes in different locations on a single screen when flying the appropriate aircraft, without switching monitor types each time. - in the ka-50 example, it allows the arbis for the ka_50, ka_50_2, and ka_50_3 to be placed in different places depending on the profile layout a person chooses to create for each aircraft / variant. Using the standard method of exporting confines the viewports, say left_mfcd and right_mfcd to be in the same location and same size across ALL aircraft, unless you create a new monitor setup and switch monitor types for each aircraft. Helios also configures files like this to be able to export some things which may not be exportable natively.. the DED in the f-16 and CDU in the a-10. <— I could be wrong on if some of these are available or not. I work closely with the Helios Dev quite often and without clogging up too much of this thread, we can DM, if you want, and I can send you the very specific files and examples of “patches”, monitor setups and all that. Helios isn’t maliciously pulling info from DCS core files, it simply “allows them, using the tools built into dcs, to export items in different places for each different aircraft. BUT because it needs to have the custom names inserted and called from the appropriate cockpit viewport file, it fails IC. Also if you are willing, maybe through discord, I can help get you in touch with the Helios Dev ( maybe you already know who he is) If you would like some more detailed code/script level explanation and examples from the man himself. Helios, the program is just for creating a graphical interface for cockpit functions. The software itself causes no issues. When it comes to the exported displays, all helios is doing is creating the monitor setup file for you within the format that DCS expects. However the custom names and “patches” are necessary to facilitate the “#1 reason” above. I think the bottom line is, if each “viewport” for each aircraft already had a specific/ alternate name (av8b_left_mfd, f5e_rwr etc) that could be called , instead of a generic “ left_mfcd, right_mfcd” blanket covering all aircraft, then there wouldn’t be a reason for helios to “patch” anything and create the custom naming using “try_find_assigned_viewport_“custom name”. This would, in turn, negate the IC failures from modified scripts… OR if this sort of API was exposed and available on the user end and not an internal SDK, then that could completely change the game, being able to drag and drop exports

I always disconnect boost and use it only at higher altitudes when required to keep MP nominal. I’m sure there are many reasons/ situations where one could/ should use it, but I find no real advantage at lower altitudes. I’ve also read that when using it at low altitudes that it draws more power than it can produce… although I’m not sure if that performance metric is really modeled in DCS.. I can’t really tell a difference one way or the other

I noticed this as well. I’ve got everything tuned to where flight/motion is silky smooth in every aircraft I own, even flying low over big cities( Sinai excluded) through valleys with nothing but trees in view, up close and personal. But in the f-5e, and it alone, I get “microstutters” while banking, turning slow and rolling. Even in Caucuses while not flying NOE.

This is interesting. I have some difficulties in the f-5 as well. As you mentioned, I’m one who have just delt with “inaccuracies” and trial -and-errored my way to a solution. I wonder if you get the same results adjusting the “pilot head position”( r-ctrl + r-shift + numberpad keys) as using the physical seat height adjustment. If so that would be handy to just r-alt+ numpad 0, to save that view position instead of adjusting the seat height every time.

Oh I see… So I have always had an issue trying to exclude a monitor on the far left from the dcs screenspace. You will probably need to pick the monitor type- 3 screen, but you will probably have to do some manual editing of the monitor setup file. That’s going to go a bit beyond me since I’ve never setup a monitor file for triple screens… I know quite a few people do it but I think the tricky part will be trying to exclude the TV from DCS’s screenspace, so you can use it for other things. There are a couple guides on setting up multi-monitors on the forum ( bugs and problems—>multi-display bugs thread). You might get a few answers searching through that section. Sorry I can’t be of much help. I’ve just never done it. Although maybe inconvenient for mouse movement, in windows you could try moving your tv to the right side of your other monitors, that way the dcs UI isn’t trying to start at the top left of your tv ( coordinate 0,0) where dcs expects its screenspace to start. This would essentially make you far left triple the starting point as DCS expects, and your resolution width would stop before your tv, leaving it open for other uses. I still believe you want to select 3 screen in the monitor type, unless you have the three setup in Nvidia Surround, to act as a single screen.

No problem! I did the exact same thing when I set up multi-monitors the first time.

For custom resolutions, you can just type it in the box.

No problem! Holler if you need a hand!

@Kenpilot if you haven’t figured it out yet. You have to edit a line in you viewporthandling.lua ( which works for almost all jets by itself for the in-cockpit displays) but for the a-10 you ALSO need to comment out one more line in the a-10 mfcd file.. give this thread a read through. I posted both screenshots of the correct files to modify. I would use it with ovgme so you don’t have to redo it every time dcs updates.

I believe that it has something to do with Steam not allowing sales without a definitive release date.. ED has mentioned that in the past… But if the f-4e is on there for pre-order then I”m obviously wrong Or maybe it just takes a bit longer for Steam to approve and post it

Most definitely will. Along with Kola, Iraq, ch-47, Hellcat and F-4u.., All easy day one purchases! Thank you guys for everything you do!

Afghanistan map, $48 minus accrued ED Miles=$30 out the door. No brainer Excited for release day/month!

I’m 100% for this as well. If you fly the f16 low ( since there’s no canopy bow) you can really notice a definitive hardline where things come into full resolution. I too have tried to find a way to extend this, to no avail.

I've seen that. Easy enough.. I was looking for one where the guys added some lua files and did some other stuff that tricked it into not breaking IC (supposedly, never tried it) It was a long time ago. I have some viewporthandling mods already, plus the laundry list of things helios breaks, so whats one more!