Leg2ion

Quick odd update - though unsure if of any relevance? My DCS World Open Beta shortcut on the desktop was pointed at "D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.exe", and not "DCS.exe". Having read the post about checking whether you are in MT or 'normal' DCS (beta), I opened the game from the DCS MT OpenBeta shortcut and verified - yep - in the MT version - said so in the lower right corner. I then launched from the standard beta shortcut, and also ended up in the MT version? Then navigated to the open beta bin and I launched directly from the DCS.exe in the OpenBeta bin no flashing was experienced (though was a quick check) - but hopefully that may help others that might be getting thrown into the MT version and not set up for it? Hope the above makes sense?

Also getting this on odd occasions. Sat on the runway, controls go unresponsive/locked and the tarmac goes purple. Can swap between seats, change MPD screens etc but no reaction to any other inputs. Will try to get a track next time it repeats.

OK - understand the post to say videos are useless, but I cannot record a track as the attached happens while the mission is loading. It happens as the 'preload' counts to 1 on the load screen, pauses then flashes through multiple screens - I am guessing another 59 in time with the count to 60? Happens on beta/MT but not stable - so probably not the latest Nvidia drivers. In addition as this happens the graphics cards fans ramp up - so definitely a draw on the card which doesn't happen as the load screen moves through the preload sequence in stable. VID_20231026_172851.mp4

That sounds similar to what I am seeing, but it happens while the mission is loading so I cannot take a track. My left hand screen displays the loading splash screen, the RH screen is blinding white then flashes between multiple cockpit views quickly in succession, then all is normal. Happens in any map, any aircraft. In addition the MFD/helios screens start displaying data before the mission is flyable - which I haven't noticed before. Latest Beta, latest Nvidia drivers. Issue not present in Stable.

Running 2 x 27" curved screens, as the mission loads the RH screen displays a cockpit view, then blooms almost white, then darkens and flashes between multiple views. Once in mission all is OK. Updated to the latest nvidia drivers prior to the beta update and all is ok in the stable - just affecting the beta after yesterdays update.

Oh cripes - a year in and I'm still trying to control the beast! Think I have used the gun 2-3 times. Just think you're getting there - update - back to square one. Have now dropped back on to stable so updates are few and far between. Admittedly due to occupation can only get 1-2 hours a week in, so if I want to 'kill stuff' resort back to the A10. Back 'in the day' loved Gunship! and Tornado (Digital Integration)...sigh...

Slightly different question - and to be honest not sure if it is 'doable'. Have a AH64 setup (with a very hybrid .lua file that uses both a Helios setup and standard viewports) on a 15.6" touchscreen - to which I export the MFDs - which now swap between Pilot/CPG when I move seats. I also have a pair of cougar MFDs - to which I currently export the CPG MFDs - the consequence of which is that they only display what is being displayed in the CPG position - and the moving map doesn't move until I flick between seat positions. Is there any way to display the pilot MFDs in two positions - so on both the touchscreen and the cougar MFDs - so they both swap between stations as I move seats?

Yep - unfortunately its a bit of a misnomer where people think that pulling pole will get them out of a situation. All they end up doing is slowing the disc as the engines try to catch up by ways of the anticipators - working in lag. There is a need to allow the rotors to pick up speed, and to be honest does require a bit of faith on the part of the driver, which for the most part will only happen by decreasing collective initially to 'feather' the blades allowing them to increase speed then pulling up..

You would be surprised. That is the whole idea behind AFCS/hydraulic control systems - it removes the need to 'gorilla' the controls to where you want them to be to remove pilot fatigue. Think old style vehicle steering with what we get nowadays with power assisted. Lighter and easier. Why not? The blades are 'flexing' as part of their dynamic rotation dependent on where they are in that rotation. When you say shouldn't be instantaneous what sort of delay are you expecting? Having flown in a large variety of rotary wing aircraft for the most part a control input induces an attitude change, so stick left bank left with next to no lag unless there is major wear in the control run...

@Able Dog Agree with @jaylw314 - get a head tracking system - it will help improve things and give you a better immersive feel. I was very sceptical at first, but now won't fly without it. You get to look around the cockpit and zoom in/out by actually moving your head. These forums are a gold mine for information and most on here are very helpful and will offer advice and assistance where needed/called for...

Hi @cgcoons Quite possibly one of the best guides for exporting (if you're not already sorted) is here (forget my post as it drew one response which didn't really help for the question asked). Page 1 has the guides - which goes from basic to advanced config: Basic export of the MFDs to a cougar is fairly easy, and ended up with this: Hope that helps?

@scrupeus & @jonsky7 - many thanks for pulling this through - just what I was looking for and couldn't figure out how to do myself. Currently have Apache MFDs on a touchscreen, and A10 MFDs on a cougar setup - which was causing me a headache in configuration - and what was being displayed where.

With the release of DCS: A-10C II Warthog, an important update will be the changes to the HOTAS. This was requested by our professional clients and now represents the true USAF configuration in particular when considering the Thrustmaster HOTAS Warthog™ throttle and stick. Here is an overview of the new feature set that will be available upon release: Updated External Model Improved 3D mesh and textures Removal of TISL pod Updated Cockpit Weathered (dirty bird) textures option Addition of the ARC-210 radio head Removal of the TISL control panel Addition of the Scorpion HMCS control head AGM-65E2/L Laser-Guided Maverick DSMS Status and Inventory Pages HUD and Weapon Video Symbology READY, ACTIVATE, SCAN, TRACK, and SLAVE Modes Updated Maverick HOTAS Commands PRF Code Input (DSMS) Missiles and Guided-Bombs AGR-20 Advanced Precision Kill Weapon System (APKWS) Laser-Guided Rockets GBU-54 Laser-JDAM ARC-210 VHF/UHF Satellite Radio Radio Start Menu Pages Manual Frequency Selection Preset Channel Selection Guard Channels Selection Setting Preset Channels 1–25 Setting Preset Channels 26–30 Scorpion Helmet-Mounted Cueing System (HMCS) Control Head HMCS Display HMCS HOTAS Commands HMCS Setting STAT Page Targeting Pod projection window Data Link PPLI, Mini-SPI, EPLRS, and Designated Target Symbols Waypoints/Steerpoint Symbols SPI and Hookship Symbols TDC and TGP Symbols Hands on Throttle and Stick (HOTAS) Updated HOTAS Commands

If you have head tracking - bin it when you are learning until you have basic flight manoeuvres nailed. I found the IHADSS was messing with me, in that the eye to horizon to HUD was skewing things, so once I fixed the view things became a lot easier.

Ultimately, DCS aside - the end game is to reduce pilot fatigue so he can concentrate on flying/fighting the vehicle.

Yup - found that to. It is so fast and whereas for the most part I think I am definitely heading to oblivion it is somehow recoverable. I have noticed the yaw/drift indicator may be slightly offset (normally with a bit of right pedal bias) then with a little bit more it suddenly deviates to max deflection and a subsequent roll.

Yup - seeing the same - though think its more to do with yaw controls - but since the last update I think I have managed to barrel roll unintentionally 3 or 4 times, whereas previous to the last update hadn't done any.

Hi @16th Widowmakr - did you get this sorted? I am new to Helios - so have been experimenting with it over the last week. In answer to your question - make the changes as per the OP - as they have probably been overwritten by the updates. I have downloaded @Bunny Clark AH64 profile (awesome work), followed the instructions resetting the monitors, and all looks good with the various panels being displayed on my touchscreen. That said - I think the KU was working - up until the last couple of patches to the OpenBeta. As it stands - the KU keytouches work and display in both the Pilot and CPG cockpits, but do not show on the Helios touch. I then made the changes to the KU_Init as per the original OP, and then had display on the touch screen as well as in the 3d cockpits. However, if the cursor is flashing in the pilots station and I swap views to CPG - I now get two cursors (and characters) overlaid on top of each other in the cockpits, and no matter what configuration I try I either get nothing on Helios (but cockpits display OK), or Helios display is correct yet have the double cursor issue. If anyone has any suggestions it would be a great help.

The problem I have is that the utility is not available unless I unplug/replug the screen, and the settings do not save - which makes it a bit cumbersome having to reset it every time I restart the PC.

Hi @Floyd1212 - many thanks for the response - as that would be so much easier, but for some reason it will only calibrate/setup if I unplug/replug it back in with a USB lead to carry the touch commands. I can then select screen 1 as main and screen 3 as a touch, but if I reboot the PC screen 3 loses its abilities to maintain the touch capabilities and they show up on the main screen.

Hi All, Reaching out for advice and assistance - please. I have a 4 monitor set up, 1 x 15.6 touchscreen (recently purchased - bit by mistake - don't ask!) - so attempting to use with Helios, 2 x 27 curved main screens, and one 11.6 monitor for MFD exports. The 2 x 27 are idented 1 and 2, the touchscreen 3 and the 11.6 as 4. However, the rub is that in order for the touchscreen to work properly and detect touches on its screen - it needs to be selected as the main screen - so the monitors are set up in order 3, 1, 2, 4, to account for DCS being pedantic about taking x/y as 0/0 from the main screen. I set the main viewport up so that the display HUD central point was about 2 thirds across screen 1 by adding a value to the x (1080) - so in effect the viewport starts 2/3 across screen 3 (leftmost), and extending across screen 1 and 2, The above alignment was OK, but I cannot find anyway to blank the background of the touchscreen in this configuration so that the only display is the helios overlay. If I do a background fill the viewports do not display data, and if I do not I get the 3d world running behind (and visible) in the viewports. Hopefully the above makes sense - but am at a bit of a loss. The only workaround I can come up with is by moving the touchscreen above the 1st main screen so both x values are the same, then dropping the main viewport y value down to align with the main screens. Ideally I want them all in a line to assist in mouse pointer transition between screens. Any guidance and assistance well received.

Personally agree with you. I dip in and out - A10 being my main vehicle of choice - but certainly after the last few updates I do believe the flight model is more manageable/stable. I think I have a fairly good understanding of rotary wing, having maintained them for around 40 years, and have a modest amount of stick time on various helo types. When the module came out it felt like I was trying to balance a marble on a needle - slightest lapse in concentration and things went badly wrong - fast. Now I am quite content to let the aircraft do its own thing and settle into stability. Gone are the days of yawing down the runway, putting in some left/right boot and ending up in a fiery mess...

After some assistance/guidance - setting up a triple monitor display. I have 2 x27" (1920x1080) and 1 x 15.6" (1920x1080) monitors. The width of the 15" is (give or take) the same as the height of the 27" screens, so was thinking of rotating the 15" screen and placing it in the middle to give an uncluttered HUD view, to look like this: However, I either get this (grey area the DCs view) - height set at 1080: Or this - height set at 1920 - which cuts off the options top left and bottom of the right hand menu: I have tried playing with the 3 camera lua, but for the life of me cannot fathom how to set up three independent views - is it actually achievable? Would something like Helios or DisplayMagician help?

I think what would be helpful would be to create a reporting form, or at the least a 'if you're going to post give us these parameters' sort of post (unless there is and I've missed it!) along with maybe a standard mission download to fly on a common air system/map with certain (common) settings. It's new, everyone is excited and reporting 'stuff'. As a for instance, I have my own 'Marianas test flight' mission which I use to test settings, which on regular, non VR, and with certain settings, gives me around 55 - 80FPS, if I move to MT I get between 110 to 186, most settings on high/extreme, FPS counter bouncing between GPU bound and CPU bound, with the following hardware etc... Maybe a small Navex Mission, high/low alt, coastal feet dry, low plains, forestation and a valley would enable to see the effects the MT.exe is having on various (I am guessing for the most part) bespoke home manufactured hardware setups, with a request to report at certain points. Basically - help us to help you (in a more logical manner). Perhaps even a sign up to participate and reward program - but at least then you may get consistent reporting against a baseline?

??