Leg2ion

I believe it was posted in AH (with a reference to A10), having searched for any similar issues, but thanks.

Obviously! Mebbe you could request 'Multi-display Helios Touch Only (cos nothing else counts)'...

See attached. Mission hot start. Engines shut down. APU off. Battery off... MFD Remaining On.trk

When you say MFDs do you mean the ones on your main screen or exported to a 2nd monitor? I had a similar issue in that my export MFDs stay blank after start up - until I jumped into the CPG position and back again. After shutdown try doing just that and see what happens. Out of curiosity how have you exported them. I have the CPG MPDs displayed on a 2nd monitor but have no control - them freezing on the image at the point I leave the CPG station.

Yup - agree. Only things that may effect wear would be possible 'chattering' due to lack of load - but minimal in terms of wear. However - if you look at the AH start as soon as you accelerate No1 to GI it starts turning the rotor - indicating more load - though I would believe that load/wear would be more borne by the MGB input drives and not the engines.

Hi @Toni Carrera - been playing with AH over the last few days - and can only but empathise! What seems good in one situation goes completely wrong in another. I ended up setting up custom curves (reference here) - and not generic - which give me a 'softer' central control position for yaw/pitch/roll - but also give me a linear input above a certain value. These have definitely improved my general handling.... Would also suggest setting up a local mission to play with 'on finals' landings - to get use to the sensitivity/reactivity of the collective for landing practice. When I initially started I set up a mission at High Altitude in the test range - oh how so twitchy. I then set up another mission in Caucasus - completely different handling characteristics...

Good question. Personally always go with the start order of No1 then No2. Normally you will find that an engine manufacturer caters for most scenarios, and doesn't care about starting order, as it would have been designed to cope with a start under load (direct drive to the transmission) if say on a single engined aircraft. Alternating starts may effect engine life cycles, which in turn will effect maintenance and overhaul - potentially leading to No1 Eng undergoing maintenance more often if No1 is always started first - albeit dependent on how long it is between No1 and No2 starting... . The alternating method may have been a 'local order' from the maintenance section to help alleviate supply and stores issues to try to align running hours. It also does depend on how the user records usage - whether operating hours, airborne hours, hours above a certain % Ng or Np...the variables are endless and quite often co-dependent on the end user. In the case of the British Army - up until the AH appeared the helo of choice was a Lynx - with the ability to run No1 engine in an accessory drive mode, so whilst burning and turning was not providing any drive to the main transmission - but all the while was running up operating hours resulting in maintenance if the metric was op hours and not flight (under load) hours. Apologies but you did ask!

Must've missed that post!? Regarding this - I have found there does appear to be some differences. Very new to this module, and up until now have been doing hot starts (everything already online) just to practice take-offs/landings and to start mapping my controls/setting axis curves etc. Now I think I have my curves set (many thanks to @mwlueposting his custom curves here - slightly tweaked to suit my setup) I have looked into basic start up training mission. Once I have gone through a start the aircraft does seem slightly more 'twitchy' compared with starting a training mission already up and running - and in particular the yaw - to the point I had to go back into options to check they were still being applied, and then into the MPDs to make sure SCAS was selected. Maybe its me - having noticed this at the end of a 2 hour session - but did seem more 'lively'.

@JIMJAM - well said. This module does take practice (only had it 3 days) but enjoying the steep learning curve - deffo out of my comfort zone from loitering around a FEBA in an A10...

So - finally got around to downloading the AH module, jumped into the seat - and (I think) veered violently to the left then rolled. So - what did I do wrong...maybe lack of respect expecting to graduate through flight school in around 5 minutes!? Went again, and again, and again...different issues though same sort of result - major work for the maintenance teams! Bit of research - happened upon this thread (I was trying to fly 'raw') and have now messed with trim and curves. My issue now is I cannot settle on any particular curve values. Initially set all three axis at 8, then after some trial and error bumped them up to 35, back to 25, then to 15, then back to 25....basically what seems good in one scenario may not be too good for another. Looking at all 'the discussion/arguments' on trim reset in my mind live and let live - if you don't like it don't use it. The main issues appear to be around landing, take-off and hover. I now have around 3 hours flight time (1 death) and only really tend to use trim once airborne to establish S+L flight. Take-off not too bad but landing (hover is another matter completely that I need to master) is too 'needy' to be able to keep trimming - once on a slowing descent towards the tarmac I tend to trim once and then 'handle it' - only again using trim once safely back on the ground. Unfortunately I don't think any level of trim will equate to stability - which I believe the majority are looking for from the get go. The AH is a wiley beast - and does need a fair degree of respect until its nuances are mastered. If anyone has a quick fix to leap into a 20ft hover, maintaining a 0 drift please let me know. After my aforementioned 3 hours I can now take off (tarmac rolling - a hover then transition is more luck) and for the most part land - and in a breakthrough last night - where I actually intend on landing and not close by!

Top bit - PNVS - Pilots Night Vision Sensor. Right bit - clear windows - ORT, DTV, Laser Rangefinder Left bit - dark window - CPG Night Vision Sensor

Hi @dradecki - apologies for a late reply. The screen is a 11.6" Wimaxit 1920X1080 16:9 Display - USB powered version (from Amazon - happy to send a link if you cannot find it). The screen display is pretty good - good colour and brightness. I have attached the files I used for the faceplate in the photos in this post, along with a 'blank' with no cable guides. A word of caution - I had mine printed out remotely - and the left edge kept distorting/warping - although once on the screen and the MFD screwed on flattened out nicely. One solution may be to increase the thickness to 3mm from 2mm. Faceplate.stl 2mm Blank Faceplate 110.stl Faceplate.3mf

Appears anytime someone brings up the subject it is locked...

We've all been there - and yep can be really difficult when all you want to do is drop ordnance on stuff and blow s**t up - but then spend 2 hours trying to figure out why something didn't work as advertised. What head tracking did you go for in the end? I use a delanclip - very good, lightweight and once I got my head around certain settings and tuned it a little bit have often asked myself why (oh why oh why) did I not explore this years ago - if not for DCS but certainly for some FPS that satisfy my 'inner infantryman'...

Think I said that once.... Another tip - look up the command for Active Pause - which pauses the game but allows missions to continue - so you can freeze flight (for instance if you're lining up on a bomb or gun run) but you can still configure weapons and MFDs etc, though a word of caution - if there are SAMs in the vicinity or missiles flying they will still continue on their mission to swat you out the air...nasty surprise when you have your head stuck in a manual trying to figure out bombing modes...

@swaps I started on the A10CII (and haven't left yet despite having a few other modules) - which I would recommend - as the tutorials are pretty good, taking you through basic flight manoeuvres, navigation, MFD use and weapons employment, plus use of the DMS/TMS. In addition the aircraft is slow and fairly forgiving (ish). You may have noticed but the community here is pretty good (apart from the odd grouch) and will help, advise and assist where at all possible. If you get the bug I thoroughly recommend a decent HOTAS setup and head tracking (which is an absolute game changer).

Link for joypro if you cannot find it: JoystickProfiler/Builds at master · Holdi601/JoystickProfiler · GitHub

Hi @Red.01 Screen is a Wimaxit 11.6" monitor from Amazon UK. Not sure if this forum allows links but happy to PM you the details if you cannot find it. The face plate the MFDs are mounted on is 2mm thick - which is thick enough to take the countersunk attaching screws without them pulling through.

Personally use MSAAx4, and SSAAx2. Anything less than this and I get shimmer that no matter how hard I try my eyes are drawn to - even the slightest telegraph pole!

You could fit both MFDs to a 11.6" monitor - then mount it using the monstertech center mount? I have just fitted 2 MFDs to a 3d printed faceplate that slips over a 11.6 screen - which you could then fit onto the center mount. I chose to leave them on the screen stand located just under my main monitor.

After seeking a solution to mount both TM MFDs onto a single 11.6" screen 'cleanly' - I have finally managed to end up with what I think is a fairly decent and useable solution, with the remainder of the 11.6" screen now being covered. Nothing in the realms of a full on cockpit sim - but gives the functionality and appearance that I wanted - i.e both MFDs together under the main screen within easy arms reach. Firstly - many thanks to @Zulu_Uniform. Following his posts here and some additional advice I took his 3d model and tweaked it a little bit - namely to add a box section at the top of the faceplate to allow it to sit firmly on the screen and add a bit more rigidity, some channel guides at the bottom to better protect and feed the USB cables through, and a small raised lip around each cutout to assist in locating the screens. I used M2 14mm countersunk screws to attach the panels onto the plate, which I covered with 1mm thick self adhesive sealing foam to protect the screen underneath. Apologies for the self indulgent post, but felt I needed to tell someone (anyone). If anyone is interested happy to share the 3d file.

Started an Instant Action Mission in the Nevada Test Range, which auto selected Jean Airport as my mission start. I couldn't contact ATC so assuming it is non operational - not having flown from here before? On easy comms but couldn't see the airport on the dropdown list to broadcast to. The mission generator gave me two JTACs - who steadfastly refused to give me any co-ordinates after making contact - but did ask for me a read back - which when I initiated (I) uttered something in Russian (I think). Is this a known issue?

To me then it appears all is well, as I wouldn't expect any steer bars due to daytime low wind conditions - so runway ILS would have been turned off - hence the flags. Thanks.

After some feedback as to whether my ILS is working properly or not? I was returning into Senaki - day sortie, contacted ATC who directed to use runway 09, with windspeed of 3 m/s - so expecting ILS to be off. Dialled in the TACAN and ILS frequencies and turned both systems on via their respective control panels. ILS and TACAN were then both selected to on in the NMSP (not sure whether that is 'allowable' but seems to work OK). As expected I had no steer bars on the ADI but did have the warning flags, but then selected ILS off on the NMSP - at which point the vertical steerbar appeared and the flags disappeared. Is this correct as cannot recall this happening before - but could be wrong?

Hi @Oddball52, as I think Bossco alludes to in his post, it may be worth investigating a separate boot drive - I have a separate M2 drive for Windows, Office and such like, another M2 for DCS only, and then a further SSD for all other games. It might be seen as total overkill - but I like to be able to separate things out if they start going wrong. In addition - just so you are aware - the drive you are looking at has cooling fins on the top (I think) - so you wont be able to refit the M2 slot 'lid'. I have an Asus Rog, and the M2s are fed by a cooling fan which pushes air through the M2 chamber - so not sure how this would affect the cooling of the drives with a built in heat sink - I am guessing not by much - and sure someone will chip in if there are any adverse affects?