jonsky7

Yep, definitely ticked, also tried unticking restarting and ticking again, still can't get it to open in the 25T. I do run multiple monitors but for all other aircraft it opens on my screen for my MFCDs and then I drag it. Thanks tagomago, also helpful to know it is working for someone else. Weird.

The NS430 GPS window

Can't seem to open the pop-up window in the SU25T, though it works in the SU25. Anyone else?

+1, wasn't like this before, I quite successfully carried out lofting attacks

I believe somebody has done it, try here https://www.digitalcombatsimulator.com/en/files/3318493/

That was awesome!

Thanks

I'm no Adrián Caparzo, but I did put this together

They are separate, I believe you will find more servers on the beta, but I havent been on stable for a while.

You seem well pleased with that Your post alone made it well worth sharing lol Thanks

Loving the new colour scheme. The app as a whole is awesome, I use it nearly every mission, thanks again for sharing it!

Looking through the docs that come with the module there's this picture with the description saying they're loading four 500lb bombs into the bay. Is it correct? Should it be possible to load four in the bay?

If you watch the landing of these Mossies, you can definately hear them backfiring

Mine wouldn't drop in single player either when I used the re-arming window.

If you go into the control binding .lua you can adjust the values for the trim DCS World/Mods/aircraft/MosquitoFBMkVI\joystick\default.lua and DCS World/Mods/aircraft/MosquitoFBMkVI\keyboard\default.lua Find this at line 506 -- Tail Trim Wheel -------------------------------------------------------------- { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = -1.0, value_up = 0.0, name = _("Trim Elevator Nose Up"), category = _("Flight Control")}, { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = 1.0, value_up = 0.0, name = _("Trim Elevator Nose Down"), category = _("Flight Control")}, Change the "value down" value to whatever you like, lower number is slower movement. Or you can add more lines with different values, just change the "name" a bit so it shows up in the bindings menu for example I added -- Tail Trim Wheel -------------------------------------------------------------- { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = -0.25, value_up = 0.0, name = _("Trim Elevator Nose Up 1/4"), category = _("Flight Control")}, { cockpit_device_id = devices.CONTROLS, down = device_commands.Button_16, up = device_commands.Button_16, value_down = 0.25, value_up = 0.0, name = _("Trim Elevator Nose Down 1/4"), category = _("Flight Control")}, So using a modifier key you can have fast and slow trim wheel speed.

@Comrade Doge The latest open.beta update has changed the input for the F-16 slightly. It needs an extra Data control switch down press to get to the latitude, and an extra one up to get back to the steerpoint selection F16.java

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?

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