jonsky7

Only thing I can think of is playing with a user curve for the axis. You could set the centre position to be nozzles full back, and mini stick down end point for nozzles fully forward but, but you would only have half of the axis travel for the full nozzle travel. I think this would be very difficult to hold any in-between position. I use my left throttle for nozzles, and right for engine, not the right way round sure, but it works for me.

The Bios manual for your board can be found here https://dlcdnets.asus.com/pub/ASUS/mb/13MANUAL/PRIME_PRO_TUF_GAMING_Intel_500_Series_BIOS_EM_WEB_EN.pdf You should be able to enable XMP memory profile by going to this page, I believe it's in the Ai Overclock tuner, as the information says at the bottom of the page, XMP1 loads the memory timings from the data stored on the memory itself but lets the motherboard choose some settings, and XMP2 loads all the info from the memory module. I don't mean to insult your intelligence at all, you haven't really disclosed how familiar you are with playing with these settings. If you have a good cooler on your CPU you could also try setting the ASUS Multicore Enhancement to enabled see page 15 of the manual.

It kind if depends on what benchmark you were using. If it's a graphics benchmark then they are pretty much designed to test the GFX card, so you won't see much difference if you don't change your graphics card. I'd highly recommend digging into the Bios for your new mobo though. Think you will probably have to select XMP.2 to get the absolute best out of your new Ram. Definitely have a look to make sure Intel Speed boost is enabled. We might need more info, board type etc, or some pics of current settings to be of more help.

Guess I'll try that but I can't think why it would open in a different position to all the other aircraft. Which is bottom right of my resolution. Where does it open for you if I may ask? I do have some undisplayed screenspace to th top right.

Yes, worked for every other aircraft I tried, F15C, SU25 (FC3), Mi8, etc, just not the 25T. If it's working for everyone else then I guess I'll have to have a play.

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