Leg2ion

You know you can deselect the individual patches in helios? I currently use both LEFT_MFCD and LEFT_MFCD_CPG (and pilot versions) - so I can split the views I have - with Plt/CPG swappable displayed on a touch screen (LEFT_MFCD/RIGHT_MFCD), and the CPG only on a pair of TM Cougar Displays so I can keep an eye on what he is doing with weapons.

Agree. First lift off - ended up on my side, in the hover there is definitely some additional 'yaw twitchiness' at play with a slow yaw rate then suddenly kicks in with an oversteer, and coming in to the hover now need to watch for sudden strong yaw changes that weren't there previously (I think).

Hi @Derbroomaster - Thanks for that - it helps. When you import the profile have you reset your monitors to replicate your config, and then if you reset the helios lua it should give you all the co-ordinates you need. Also noting in your lua you provided the width is set at 5760, yet you say the three monitors are 2560 - so max width should be 7680? From your monitor config - If I assume screen 1 is slap bang in the centre of screen 2 (which is 3 screens wide x 2560 = 7680, I believe your co-ordinates should look something like like this - which should be ball park. Viewports = Center = { x = 0; y = 0; width = 7680; height = 1080; viewDx = 0; viewDy = 0; aspect = 7680 / 1080; } LEFT_MFCD = { x = 3215; y = 1228; width = 500; height = 500; } RIGHT_MFCD = { x = 3965; y = 1228; width = 500; height = 500; } It might help if you align the lower screen with the left hand edge of the uppers, as will make figuring x co-ordinates easier.

Got a few other 'choice words'!!

Hi @MAXsenna - one final update. I have just swapped my original TM Warthog stick base for an Ava base. With the new base I do not get the same issues - so all key binds and modifiers the same - no issues - so whether there was some sort of conflict - or my new base is now not working as it should...?

Hi @Caldera So checked mine - full throttle - 101%. When you say 115% - is it a transient reading and then settles back down to 101, or maintains 115%? If the latter, not quite sure how you're achieving 115% as the engines are governed and controlled to maintain 101 by the DECs. When your physical throttles are set to max where do your in game throttles sit - should be at 'Fly'. Only other thing - are you going into lock out - which would remove the automatic governing? Update. Yep - just pushed my throttles into lock out and achieved 116% Np with associated overspeed warnings/bells/whistles....

I'll check mine but I only get overspeed if advancing the power levers too quickly. I have mine bound to my Warthog Throttle slider, so find if I move them to mid, stabilise, then full I get no issues. Will get back to you.

I think I'm in agreement with @ShuRugal, and from what I can recall FRCs would elicit a single engine start process. Makes it pretty pointless if the INU isn't aligned and you don't have maps/GPS on line, as you then have to wait regardless, or spend more time when inputting waypoints. Not a purist - just makes more sense...

How are your screens aligned - if you can do a screen capture or detail how they are aligned to each other it will help massively: Your monitor setup file should be in your saved games folder on your c drive ("C:\Users\username\Saved Games\DCS.openbeta\Config\MonitorSetup\CustomMonitor.lua".). If running Helios and it configures your monitors there will be a lua in there named Helios. For this to take effect you need to select it in DCS Options - Monitors. Your x co-ordinates run left to right, and your y co-ordinates run top to bottom. If your touchscreen is under your 3 main screens - then your y co-ordinates miss - as your total height is 1440 plus 1080 - so a total of 2520 - but your y is shown as 2720 - so 200 pixels below your actual display area. In addition the right hand MFD is positioned at x1345, so to the left of your left hand MFD at x1965 (which may also be outside your view area of the touch as it has a width of 1920. As above - if you can show your monitor setup, and dig out and attach your monitor setup lua it will be a great help. What I have found is if you configure helios to not sure any warnings/cautions when it starts a profile - it sometimes isn't the best - so if you make custom adjustments helios detects it and steers you towards fixing things - which in turn screws the viewports.

Glad you're all sorted.

OK - so think you're on the right track. Mine are here: So if you open one of the folders in the saved game folder - say for the F15, and click through you should hopefully get to the config luas:

Really odd. Try a file search across your drives for joystick in case they have been removed and deposited elsewhere? Not sure if that is the right address, as I don't have the 'common' in mine - as soon as I open input on my c drive I get a list of aircraft I have configured. (Not at my games machine at the mo so cannot have a looksee properly).

@huggy98 Have you looked in your saved games/config/input/aircraft type/Joystick folder - hopefully there are some files in there? I just swapped my HOTAS Joystick Base over - same stick grip, but it created a new folder and ID. All I had to do (same grip mind) was cut and paste the contents of the old into the new. Not sure but believe it may happen if there are other hardware changes.

3 Regt AAC (653, 662 and 663 Sqns). The regiment was the first to move back to Wattisham, UK in 1993 (and not Gutersloh) following the end of the cold war. Just need the Westland Lynx Mk7s ....

As per @MAXsenna, and also then make sure your 'viewport centre' in your monitor setup is only set up to show your main view screen in your monitor setup lua. Helios likes to create a view across all your screens (or whatever you tell it), so I tend to check it to make sure it aligns with the main screen only. Then DCS will only display your main view in that area. For a single main screen (1920x1080): Viewports = { Center = { x = 0, y = 0, width = 1920, height = 1080, aspect = 1920/1080, dx = 0, dy = 0 } } You then need to ensure your resolution in game in the options is set to display across all screens - which it must be if your live cockpit is displaying there? Jonskys post here is very good at holding hands through a multi screen setup:

Hi @Derbroomaster - I did post in the comments section following your comment against the profile, and also PM'd you if you needed help? One thing looking at your profile - have you run a helios monitor configuration, as your lua would appear to be a 'stock' set-up? What I tend to do is carry out an export so helios creates a helios monitor lua, which I then use as a master list of co-ordinates for my viewports etc. Second check - have you applied the helios patches which reconfigure the MFCD.init luas? Thirdly - your 'x' co-ordinates of your left MFD appear to be further right than the right MFD? I have attached my monitor lua - but basically the way the profile is set up minimal exported viewports are needed - I only export to the the pilots EUFD, TEDAC, Left and Right MFCD onto a touch screen that swap, and the CPG MFCDs (separately onto TM Cougar displays). Your co-ordinates generally don't look right, as in the profile the TEDAC sits between the 2 MFDs and lower, yet your lua shows the TEDAC sitting to the left of both MFDs and higher? Also be interested to see your monitor setup of your 4th screen if still having issues - as your Y co-ordinates seem quite large? HeliosAH.lua

Guys - thanks for the input. I do understand nav, wind effect, bearing v heading etc - in my OP I was purely asking whether what I was seeing was correct, and was curious whether the direct line route should/would stay tethered to my aircraft to show a constant relationship between me and my selected point as I either deviated from it or transitioned towards that point. It doesn't.

I guess my thoughts were along the lines of not being too bothered about course deviation, just asking if it was correct as it looked 'odd', as once deviated from (for whatever reason) it sort of becomes an 'Indirect' Route Line. Yep? But that is what you have using the steering bug - as it would constantly change to show a direct to, having to fly an offset dependent on wind, regardless of the line, to minimise the flight path deviation. Thanks both for the input.

Here you go. dcs.log HeliosFinal.lua

I asked a question - bignewy was kind enough to give a steer, which then set me in the right track to replicate it and then suss out what was happening and why. What I don't like is the 'what do you expect' kinda answer like I should have known (that is why I asked for help and asked the question!) - as a lot of strange things happen in DCS due to the variety and complexity of individuals differing hardware and software set ups. I guess I was thinking that regardless of where the slider was, it would stay unaltered until I interacted with it, also coupled with the fact I (purely by co-incidence) made a button press at the same time. Sorry but where I have some switches mapped to say lights or similar - when I fire the aircraft up, if they are in the on position they don't automatically turn the lights on, having to cycle off then back to the on position - so would it be unreasonable to think similar in this instance? But thanks anyway! Cheers! Yep - done! Quickest way - and TBH not sure why I added a modifier to it in the first place - must have been a good idea at the time!

Hi @BIGNEWY Think I've got to the bottom of it. I have the pinky lever on the cyclic grip assigned as a modifier, and the increase/decrease slider on the throttle unit assigned as the throttle power control coupled with the modifier (to prevent unwanted throttle inputs - doh!). The button 11 is a red herring, and was purely co-incidental as I selected that at the same time I pulled the pinky lever. When I flew a previous mission, I did a shutdown etc, with the power levers (increase/decrease slider) left in the off position. This mission - I started hot, so in game the power levers are forward, on my WH throttle the slider is in the aft position. When then I select the modifier button, and the slider is aft, the in game throttle then moves to adopt the position of the slider, regardless of any input to the slider itself. Created a new joystick file and exactly the same happens. Question is - is there any way of preventing that happening, as in mind the throttle should stay where it is as I am not creating any input into the slider, just depressing the pinky lever modifier? That would also explain why I couldn't repeat it, as to recover I throttled up using the slider, so then were synched with both being forward. Not insurmountable if not - just make sure I check the position from now on...

Hi All, @Lord Vader Bizarrely read this and then had same happen to me in last mission. I was lined up on some training targets, and selected my modifier key and Switch 11 on my TM WH HOTAS grip (forgetting I had remapped the pilots sight select switches to elsewhere - so that key press combination is not in my current control configuration) - and had both engines cut with a pretty rapid nose dive as a result. Restarted a new mission, and pressed same whilst hot on the ground, same effect. As I was on the ground re-accelerated the engines, and then could not repeat with same key presses? Both tracks attached. Eng Off.trk Eng Off2.trk

Does the TSD Direct Route Line move with the aircraft symbol if you have created a bespoke route line. So as a for instance I am flying to WP1, then create an alternative point, select DIR and use my MFD cursor to select it. I then get a route line from my current position to my new point, but the line doesn't reduce in size or stay bound to my aircraft symbol as I fly it - is this correct?

Hi All, Anyone else noticed the MFD fly to cue in the flt page migrating outside the MFD display? I have the MFDs exported to a Helios setup, so thought this may be the issue, as per the below: But then noticed it was doing it in the main view also: Also notice the cue stuck at the far right of the main view screen on occasions, normally when in I am in a banking turn/holding pattern, which then gradually fades away.

Funnily enough I have been playing around in the Scud Hunt mission, and as per @Greyman post, I got an 'Engine 1 out. Engine 2 out' in fairly quick succession last night, BUT both engines stayed in the green and the Nr didn't blink. Happened as I was egressing away from the Scud base after a low level run in and taking some small arms fire. Didn't notice any other issues (but then didn't really look). When my engines are hit it normally isn't good....