MadKreator

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!

Huh.. that simple eh! Not bad at all! Happy you got it going!

It would be great if we could save the kneeboard position and size, similar to using R-Alt+Numpad 0 for the default view. Yes it can be resized with the mouse, but for us multi-display users it be comes quite the chore mission after mission, flight after flight to move and resize the gigantic kneeboard that its 3/4 off of the mainscreen A Hotkey to save the coordinates and size in a lua file seems like it would be a fairly simple fix. ( I don’t code, just venturing a guess since the camera view uses a similar idea).

Please do! I would love top know a good route. Even If I don’t use that setup

Not sure where it’s at. Might take some deep digging through the forums… On a side note, if you notice exported mfd’s/ viewports being overly dark. Here is the “fix” using ReShade to make a mask of your viewport screen area then adding a couple filters to brighten them up. F-16 isn’t that bad but some like the f-15e are really dim. Almost invisible in night mode. If you want to give this ago ever, and don’t have photoshop or gimp ( you could prob do it in MS paint, maybe), hit me up on here or CZ’s discord that I linked earlier and I’m happy to make the mask for you to use . https://forum.dcs.world/topic/328747-my-workaround-for-exported-mdf-brightnes-issues/?do=findComment&comment=5395740

You just have to use the mouse and resize and reposition it every time you start a new flight. It’s because of the enlarged screenspace dcs now uses with the added monitors. ED has yet to address it after years of requests. There is a thread somewhere to change the size and position in the lua files, however it’s not a simple adjustment but the steps are pretty detailed if you want to give it a go.. I’ll try to find it.

Awesome! Good deal

No worries at all. Here is my helios monitor file..all viewports function as should. The specific naming used, is defined by the Helios Patches. I don't imagine they would work without the patches in place. -I'm still a bit miffed at the OP's issue. To me it looks like a GPU issue, not necessarily directly with the monitor file in dcs or helios. Possibly that the GPU cant render a resolution with that total width? I'm not entirely sire how that works but I have seen users hit a resolution limit on some gpu's, but usually when trying to run 4k triples and part of a screen gets cut off. Not sure why I have a y=5 offset on my primary.. just noticed that one..hmmm<--now fixed

Very interesting. I know the helios code is a bit “messy”, as the developer says, when it comes to translating certain monitor configurations. I’ve been hit or miss getting a monitor to work correctly being on the left of the primary, by letting Helios write the monitor file. It sees the left screens as negative coordinate values coming from windows, and isn’t always happy about it. It’s just doing what it thinks DCS wants. I know lots of users with more complex screen setups seem to have better luck writing their own file instead of letting helios produce it. Helios also has trouble producing proper triple screen setups. - Curious if, in your setup SkateZilla, you are able to use your two left monitors for other windows applications while playing dcs. Or does dcs still see then as part of the screen space, just leaving them blank? - I’d be interested to see your monitorsetup LUA for that particular configuration, if you would be willing to share I would like to compare and do some testing on some modified Helios monitor setups. - as for his mfds being before the viewports. I will check my Helios monitor file. It could be written that way due to Helios’ “patches”( modifications to the core files) for exporting things like the mfd’s, ded, eufi’s etc. <— I will revisit this one. That piques my interest as well. I suppose my previous statement should have been “ limitation based on what Helios THINKS dcs wants”

@TheWizkid Your helios setup looks fine, but that issue you're having is something I’ve never seen. Just for kicks I would turn off monitor 1, reset monitors in helios, configure again in”DCS Monitor setup”, change the resolution in dcs and see if it works correctly. DCS has never really liked monitors being placed on the left of the main screen. IE it doesn’t like being offset from the 0,0 coordinate…. If it works you may just make sure to shut down screen 1 before playing dcs/ helios. You may even be able to trick it and turn that monitor on after dcs starts and helios is started and use it for other windows programs, discord, dcs nav map, the way, helios control center , dcs Olympus etc…. Since helios won’t let you exclude a screen to the left of the main from the dcs screenspace. ( you could if monitor one was on the right)… again, dcs limitations. You will prob get better responses regarding helios here too Captain Zeen/ Helios discord: https://discord.gg/sS5rYAwKsr

I’m not entirely sure since I’ve never setup triple screens to use for dcs. I’ve been kind of looking around and it seems like you almost need to set up a monitor config manually through dcs, using the 3 screen monitor type as a starting point. Helios just writes the monitor file based on what it thinks that dcs wants. It doesn’t have any actual control over how dcs decides to render across multiple screens. I’m not sure if there is something special about DCS’s built in 3 screen layout or not. I know it’s been done, check out “the warthog project” he uses 3 projectors for the game and Helios for all the gauges and viewport. He has some pretty detailed write ups and videos on his setup. But it’s unknown territory to me. I’m just an average dude that started using helios because I never understood enough about writing my own monitor files to make it work. But my knowledge only extends to the things I’ve experienced and personally setup. So far any user that has had triples, and trying to get them working alongside helios, I’ve never heard from or seen how they actually got it working. I’d love to know because I do get asked quite often, but unfortunately I don’t have a definitive answer.

Awesome! I haven’t checked if there is an updated scratchpad version, but for The Way there is. Actually since finding The Way I haven’t used scratchpad….. Come to think of it, ED now has a built in scratchpad, I think L-Alt + y will bring it up, wherever your mouse is over in the f-10 map. (If you didn’t know that)

Recently that has been related to various mods that lost some compatibility. Mine was doing that using “The Way”. As soon as I removed it, no more crashing on exit. If you happen to be using “The Way”, there is a new version out to fix the crashing. “DCS Scratchpad” was giving me crashes as well.

I will try it for fun. I actually keep dcs capped at 60fps normally just because the exported gauges in helios move the smoothest. It seems to be its happy place. My setup with the 4080 can do 120 with maxed settings in free flight, but once other flights start coming in, or in a mission, it sits in a really odd range around 109fps. I suppose I could back off some graphic settings but the OLED looks soooooooo good, I just don’t want to lose the eye candy

Again, I have to point out that I’m 100% in favor of this!! Just a couple check boxes in the re-arm/ fuel window to click.. “re-arm only” or “re-fuel only”, if neither is pushed then it will do both as usual.. I still think re-arming should happen BEFORE refueling though. Really annoying in the f-15e to sit and wait for all the bags to fill first , only to remove them right after ( if you choose to remove them of course). I totally feel the pain in the f-15e if you only want fuel, but it reloads all of the weapons even if you didn’t change the load out from when you landed. Then you get to set the PACS back up all over again for everything I could be mistaken but I believe in the fc3 modules you can chose one or the other with keybinds too

Only disadvantage I’ve found of Fast Vsync is, in some cases it will make exported viewports flicker. I run V-sync on all the time, not necessarily in fast mode. I find it does a better job with tearing than gsync…. However I am capping dcs to 60fps on a 120hz monitor, running dcs in not-fullscreen mode( not sure if its technically “windowed” mode or not) and also using a 60hz touchscreen for helios. Gsync by itself never seemed to get rid of tearing on my setup. But V-sync 100% does….. BTW @SharpeXB, I’m absolutely LOVING the 48” Ultragear! So happy I made the switch

Here's the file, just goes in SavedGames/.../Config. Pic attached of placement and file contents.. Again it may be obsolete at this stage. mt.lua

@LHP @truebrit I tried to find the thread BN posted it in last year but couldn’t. I’ll see if it will let me put the file here. It just goes in saved games/config folder. I think it was just a test run when they were working out MT bugs. It may be incorporated into the game already, but I still have it. What I noticed with it, is it spread the load more evenly across cores. Previous to adding that lua, there were only a small handful of cores doing most of the work. After that file the load seemed to distribute more evenly across maybe 12 of my 24 cores, instead of 4 of them doing 90% of the work.

Adding DCS MT .exe, saved games folder, track IR, Helios and anything else dcs related, as exceptions in windows defender got rid of every micro stutter and lag mine had. So smooth now, even with vsync and capped at 60 fps <—personal preference to give everything some headroom when lots of objects come into play. Consistent 60 is better imo than bouncing around between 90 and 120 Also addin the MT.lua to saved games folder that Big Newey posted several months ago ( not sure if its still valid, but I still have it in my SG folder