jonsky7

I like to move my exported displays around depending on the aircraft I'm in. So since they removed the ability to change names of the MFDs in order to do that, we need a new way to do it. I found this in the default config file for the 3 monitor setup --[[ also you can use "displays" table to perfectly match you configuration . it is generated by DCS automatically. displays table is contains information about all currently attached displays for example my setup is : displays = { [1] = { x = 0, -- note : x == 0 and y == 0 is always mark primary windows display y = 0, width = 1920, height = 1200 }, [2] = { x = -1440, -- mark that secondary display is on left side of primary display y = 0, width = 1440, height = 900 }, ... for all displays } screen table also contain x, y members which mark top left corner of DCS window note about fullscreen : directx doesn't allow fullscreen applications with resolutions more than primary display can handle, so multimonitor presets in DCS will fall back to windowed mode if fullscreen initialization failed ( this info also will be printed to dcs.log) for reconfigure viewports setup for each unit type independently you can declare here function function reconfigure_for_unit(unit_type) --unit type is string with unit name if unit_type == "A-10C" then Viewports = ... define new Viewports table -- also you can define cockpit displays viewports here RIGHT_MFCD = ... define new RIGHT_MFCD viewport else Viewports = ... define default for others RIGHT_MFCD = nil -- remove for others end end --]] I'd like to use the reconfigure for unit type part and came up with this _ = function(p) return p; end; name = _('Jordiecam'); Description = 'Jordie'; function reconfigure_for_unit(unit_type) --unit type is string with unit name if unit_type == "A-10C" then Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; } } LEFT_MFCD = { x = 4490; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 5570; y = 360; width = 825; height = 825; } else Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 2560/1440; } } LEFT_MFCD = { x = 4090; y = 360; width = 825; height = 825; } RIGHT_MFCD = { x = 5170; y = 360; width = 825; height = 825; } end end UIMainView = Viewports.Center But it isn't even showing up as a selectable config. I'm obviously doing something wrong. Does anybody know how it works please?

Can't see these mentioned yet Crew indicator move \Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\AI\ControlPanel\g_panel_page.lua \Mods\aircraft\Uh-1H\Cockpit\Scripts\AI\ControlPanel\g_panel_page.lua Cargo indicator move \Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\CargoIndicator\CargoIndicator_page.lua \Mods\aircraft\ka-50\Cockpit\Scripts\CargoIndicator\CargoIndicator_page.lua \Mods\aircraft\uh-1h\Cockpit\Scripts\CargoIndicator\CargoIndicator_page.lua Transparent/move controls indicator Mods\aircraft\Mi-24P\Cockpit\Scripts\ControlsIndicator\ControlsIndicator_page.lua Mods\aircraft\Mi-8MTV2\Cockpit\Scripts\ControlsIndicator\ControlsIndicator_page.lua Mods\aircraft\Uh-1h\Cockpit\Scripts\ControlsIndicator\ControlsIndicator_page.lua Ka-50 English Hud mod https://www.digitalcombatsimulator.com/en/files/607269/ Gazelle TV export \Mods\aircraft\SA342\Cockpit\TV\Indicator\init.lua Set opening position of kneeboard \Scripts\Aircrafts\_Common\Cockpit\ViewportHandling-resize.lua \Mods\aircraft\A-10C\Cockpit\Scripts\device_init.lua (repeat for all aircraft) Petrovich AI helper move \Mods\aircraft\Mi-24P\Cockpit\Scripts\HelperAI\HelperAI_page_common.lua Reposition Mi-24P Sight \Mods\aircraft\Mi-24P\Cockpit\Scripts\9K113_CAM\9K113_CAM_init.lua

Well there's going to be absolutely huge amount of frustration, I've personally spent uncountable hours setting up my multi-monitor config, and mine isn't even that complicated, but it took time to scour through all the threads to find the information needed to do it. Can't imagine what it's like for people who have literally sunk hundreds if not thousands of dollars on their full on replica of a particular cockpit. It's all very well saying list this app and this mod, but most of mine are done by me, for me, for my monitors. Things like making the Kneeboard open where I want it, not on my MFCD screen, which requires an edit of the device_init.lua for every aircraft because ViewportHandling-resize.lua was locked already. The controls indicator, I have nice transparent ones made by the community, and I moved them to where I want them, especially the autopilot indicator in the Mi8 which would show up in the bottom corner of my MFCD screen. Moving the crew indicator for Huey and Mi8, which would show up on my MFCD screen. Then we get onto the RWR, CMSP, Viggen Radar (meh). Moving the Petrovich AI helper, and the Sight camera because it wasn't in the right place for my setup. I'm sure a lot of other people who use multiple monitors have gone through the same process including those who use your app. I have literally never read or heard once, anyone complaining about people cheating. Using the search on this forum for cheat, or exploit, returns zero results of people complaining about cheats in the game. Am I missing that topic?

It's called Trigger Button (release bomb/guncam on) - press

On my UK keyboard, if I re-do the comms button binding to \, it shows OEM102, try rebinding the key

FFS! Well that's completely ruined my multi-monitor setup.... great! Can't even move simple displays like the controls indicator, or crew indicator in the Mi8 or Huey, how would they be exploitable?

All modified files for exporting displays now fail integrity check As per above, I have so many exports that now fail integrity check

Any particular reason why there's lots of files that were ok to modify now fail integrity check? For example, modifying any of the indicator files now fails integrity check! These were modified so that various displays could be exported. Or renaming the viewport in the MFD files from say Right_MFCD to F18_Right_MFCD also now fails integrity check

Well I think it defaults to both because I was controlling both engines with those axis bindings and hadn't even seen the select engine bindings

Engine (selected) RPM / Propeller Pitch - axis controls both engine's rpm at the same time, I have no idea how to select an engine and Throttle, engine (selected) - axis controls both engine throttles ahh, i see Select active engine to both = 9 select active engine left = 8 select active engine right = 0

+1 and may I add the same goes for the Flap lever, maybe we could have Flaps up, flaps off, flaps down?

I've switched over to the blackbox mk2, but I believe all 4 lights were on the orange box, with the BUS light maybe being red IIRC.

Hi, Anyone else getting a lock-ups? Flying along nicely then the joystick will suddenly go full right forward or full right aft input and not respond. If I disconnect the cable from the joystick base and re-connect, then it comes back to life. I'm using the orange box that came with the Mk2 base, but I also have a black box that came with my rudder T-pedals, it's worth a shot I suppose. Any ideas? Thanks

Yes, I probably should have said "more Ai Bombers"

Yes please to at least Ai Bombers for me to shoot at

@Comrade Doge Very much looking forward to the next update. In the mean time I have put together something for the Harrier. The problem with the Harrier is the only coordinate type you can manually enter is DMS (DD°MM'SS) and not the decimal minutes all of the other aircraft are able to use (DD°MM.mmm), it's not a very accurate system with a possible error of around 100ft (30m) in both Latitude and Longitude. I don't know if you can do anything with that, a calculation to convert the coordinates maybe. The harrier does have Razbam's F10 Map marker to CAS import going for it though. AV8BNA.java

Possible to add a "Do not show again" checkbox? Just an idea.

Personally I would answer yes to this question.

Very nice Does the pop-up just happen once?

I think you may be missing the last digits of the coordinates, EG N12'34'56.78, after entering 123456 and pressing enter, the display goes black, you need to enter the last two digits then, or 00 See wags video here

Yes, really well actually. Just make sure precise mode is OFF when transferring waypoints as the tool presses the OSB key, thus turning precise mode on, when doing the coord entry part.

@MAXsenna Goto https://github.com/orgs/dcs-bios/repositories Select the module Open the link for the .lua file They're quite well laid out. Download one of the files I uploaded to use as a template-ish Figure out the "flow" of entering waypoints in your desired module, replace lines in the "template" Or just write out the flow and the button codes, I'm sure it'll come in handy

Here's something for KA50 and Gazelle. Neither has a waypoint increment button unfortunately, the number for the desired waypoint must be pressed. The Gazelle is even worse, for longitude: 1. It will NOT accept a zero for the first digit. 2. It will not accept a 6 digit longitude coordinate on Caucasus/Syria/Persian Gulf 3. It will not accept a 5 digit coordinate on Marianas/Nevada It's so weird. SA342M Gazelle.java Ka-50.java

Try this guide, if you have questions please post them in the guide thread. https://forums.eagle.ru/topic/278775-how-to-multi-monitor-mfcd-display-export-set-up-guide-jan-2021/?do=findComment&comment=4740843

I will certainly try. The enemy fire incident didn't actually cause a fire, just an engine shut down, but the system may have triggered. Thanks.