Leg2ion

In addition to that of @NeedzWD40 (especially the "I need extra power to get 100% fuel, 1200 rounds of 30mm, and 16 missiles off the ground!" ) believe those times and min/max values will feed into any pilots post flight report - ie xxx% torque recorded for so many minutes on No1 Engine/I entered the 6 second band for 3 seconds etc. Whilst there are bands of 'allowable' limits and the implications to the aircrew may be minor - those values will be fed into the maintenance policy for the aircraft resulting in either a lot of work for the maintainers or the life of certain components in the engine/transmissions could be reduced. So in essence you're allowed a certain amount of limited time in certain output bands (Ng/Np/Tq/TGT/Nr) plus incursions into transient zones with possibly no penalty - but if you exceed it or enter it so many times then you may need to start doing some type of penalty maintenance on the components. The intent is aircrew/aircraft survivability - knowingly allowing limits to be exceeded - you may end up having to do some internal inspections or worst case reject an engine but you have your driver and aircraft back. Now, sometimes pilot reporting in instances such as these can be historically described as 'not the best' flavoured with a little bit of poetic license so Health Usage Monitoring System (HUMS) has been introduced which record all these values automatically, and post flight the maintainers interrogate it to see what values have been reached - the download system flagging exceedances which then need to be cleared with appropriate maintenance being undertaken. It cuts out the ambiguity of "Chief - I might have had an overtorque. I think I may have ..." to a definite idea of what had happened.

@Martallica In addition to SilverDevils - are the crashes occurring only after adding the third MFD? Just a thought if thats been added and then the crashes started occurring? PSU 850w should be enough but not sure of the draw of all your various peripherals? PSU failures can be a pain sometime to troubleshoot. I have been adamant my GPU was up the swanny previously due to the symptoms and it turned out to be the PSU.

@Martallica Out of curiosity what size PSU do you have, and when you say crash - is it just DCS or the whole PC goes into a shutdown/reboot? Where is the power to the USB coming from - is it a separate mains supply or also out of the PC? Have you upgraded anything recently (either software or hardware), and tried removing any mods you may be running? When you say campaign - which one and which aircraft are you flying? I had similar last year and it was purely down to overheating - initially fixed by popping the side of my case off and directing a small USB powered fan into it. Permanent remedy was to upgrade my cooling fans in my case (and hoover out all the dust from the intakes!).

My CPG does! Not too sure of the range - possibly around 3 1/2 km - both in the open and in a treeline. (Edit Update - just flew a mission in the 4 Horsemen - CPG identified enemy infantry starting @3.6km).

You sure about that?

Was going to promote the dying fly manoeuvre - where I flip the aircraft onto its back in an effort to confuse the enemy into thinking I am no longer a threat to stop any attempts to seriously harm me with AAA... (apologies but couldn't help myself!).

Full Iraq map - flying out of Mosul. Head North and half the map drops off the TSD. Range set to 50km. Doesn't happen on other scales. dcs.log

So just had a play - disabled power service - no noticeable difference in my experience - if anything made things not as smooth so have now re-enabled. One thing I didn't try was to re-enable C-States - take a flight - and then disable power services and repeat. Just pushed my log file through the analyser and the only real advice was to roll back my nVidia driver. All our back and forth aside - OP @PatientSquire27 - any joy, or things worse or better dependent on what you have tried?

One other question, how does this tie up with 'C States' - if at all. I normally disable C states in the BIOS, as they manage power and differing levels of idling state, so would that have the same effect or again 'same but different'..

@PatientSquire27 another link here with more suggestions:

@Hiob Thanks - I'll give it a go and see what happens. Out of curiosity if disabled do you have to do it every time you restart - or does it stay suspended indefinitely?

Hmmm - not convinced I'm afraid...

Maybe not but fixed my issue a couple of years ago where I had almost exactly the same issue? First became noticeable after 'accidentally' installing MSI Dragon Centre thinking it might improve things - it absolutely murdered my system - managing to bring my FTTP connection of around 300MB/S down to around 4! After uninstalling it things were smoother - the bi-product being it had cranked my system up to Ultimate in the power settings. Never looked back. That said what does disabling the Power service do over and above setting things to ultimate? @PatientSquire27 Can you confirm what you have/haven't done - or whether you need any further advice in achieving some suggestions? Not sure what that means - when you say GPU mode is ultimate, and power is on turbo - think those are GPU settings via Armoury Crate? Have you tried setting GPU back to standard and power back to performance - just to gauge if things go better/worse? When I mentioned Power settings I am more suggesting the power mode of the PC (so System/Power and Battery/Power Mode - select Performance mode if not already. In addition you can try setting PCI Express Link State Power Management to Off (Control Panel, System and Security, Power Option, Change Plan Settings, Change Advanced Power Settings - then in the box that appears select PCI Express, LSPM and set it to off for either battery, plugged in or both). Not sure if that would be affected by @Hiob suggestion to stop the overall power process.

Out of curiosity what map or all? Is it worth disabling head tracking so there is nothing interfering with output? Also ensure anything screensaver related is disabled/turned off. Nvidia graphics card? Ensure power set to maximum preferred in the nvidia control panel. Anything overclocked (cpu or memory) - reset it back to base. Likewise GPU. I have an old MSI 3090 which has a switch on it to swap between standard and gaming configuration. My setup gets worse if I put it into gaming mode?

Hi All, First time I have used the Iraq map so not sure if anyone else has experienced this? Created a simple navigation mission in Apache - flying out of a FARP in the middle of Mosul. Lift, hang a right along the River Tigris, then a long banking turn back across the built up area back into the FARP. All is good until I around half way back, at which point I get 'stuttering' (Edit - which is not prevalent on other maps) - more noticeable/intrusive than the 'micro-stuttering' that was apparent a few years back. Not a lot to go on - but not seen any other posts and just want to put it out there in case it is the map or other people are seeing similar before I start messing with settings etc TIA!

One question. How does core parking tie up with C states - if at all? If you disable C States in the BIOS does this negate need to disable core parking etc (thinking core parking is a C State option/sub selection?). Recently hit an issue with the Iraq map - flew out of Mosul no problems (low level Apache) - flew back in and what I would call the 'micro-stutter' that was prevalent a few years ago had re-appeared. Admittedly first time using the Iraq map so unsure if it is the map as have no issues on any other maps. Disabled core parking and the stuttering was awful - down to (rough guess judged by what I saw!) around 1 FPS!

Have you checked your power settings and ensured they are on high or performance (and not balanced or lower)?

Every day is a school day I guess as never heard that one? Think what you're saying is realistic may be questionable when the OP is basically describing slamming max pedal in at speed to elicit a slide skid to slow down and affect a turn after a strafing run to change direction and not orbit a target with the nose continue to point at a given spot on the ground. I am guessing that any such manoeuvre isn't going to be fastest and would also compromise use of rockets/missiles - leaving the AWS only - so may as well let it track the target and continue normal circling flight?

Which for the most part is unrealistic. There are limited controls in the CPG station for a reason - the pilot is the driver, and as such the 'captain' of the aircraft. In the same way that the pilot does not have complete flexibility and control over all the sensors and weapons to the same level of refinement and ease of use as the CPG, aircraft 'management' is similarly limited to the CPG. Jump in the back seat and start the aircraft properly? Could that not be an option - get everything up and running, bring all the systems on line, then swap into CPG and use George to get airborne etc?

Oddly had similar the other week - whereby my Warthog throttle slider was mapped to the power levers with a modifier on the main stick. I had been flying cold starts and accompanying shutdowns, then did a quick training mission with a hot start. Got airborne, but when I inadvertently selected the modifier the power levers instantly chopped as the slider was all the way to the rear with resulting loss of power and catastrophic impact with the countryside! That was with a Thrustmaster Warthog. I have recently changed my base to an Ava - and no longer have this issue (obviously had to try!).

Found the culprit. Its Helios. If I apply (Helios) patches - and the command line 'dofile(LockOn_Options.common_script_path.."ViewportHandling.lua")' is added to the MFCD init.lua along with a 'try_find_assigned_viewport' it causes the issue. Even if I use the standard viewport name the issue is created. I knocked out the patches being applied to the pilot position and the issue disappeared - yet was still present in the CPG position. One other side effect I noticed, is that prior to this the in game MFD displays were appearing washed out but the exported ones were not - and I was living with it. Once I removed the patches both displays (In Game and exported) appeared the same. Just conscious there have been a lot of historic posts on washed out displays...

I believe it is realistic - but depends on how much altitude your are gaining - though whether intentionally modelled is another thing. If you are doing a tail handling check (say after maintenance) - part of that is to move sideways - both left and right - up to a certain speed. From what I can recall when you recover from that condition - ie slow down/stop - the aircraft would have a tendency to rise - not a great deal mind - so not sure how much altitude you are gaining. If you think that the disc would be slightly angled to promote movement in a certain direction, then as you bleed off speed to slow, that relationship changes and the 'fan' starts to blow more downwards then down/side, so if in ground effect you get a bigger 'cushion' of air underneath you forcing you up unless you counter with the collective perfectly. In addition - depending on which way you turn you can unload the disc - so if you turn the same way as the disc is rotating you will possibly see a rise in altitude as there is momentarily more energy available with a increase in torque. The problem you have is that you are entering the sideslip at speed - something the aircraft nor the flying controls/set-up isn't designed to do - and in reality would probably result in severe vibration with possible loss of control. When you rig an aircraft - the blade angles are set to achieve forward flight as the default - so the blades that are considered advancing - ie moving forward in the airflow are nominally set at a lower angle to decrease lift being generated due to higher airflow speed over the blade, and similarly those retreating - ie moving away from the airflow are set at a higher angle to increase lift due to a lower airflow speed. This is to maintain a balanced disc. You are ignoring this relationship. By slamming the aircraft sideways, and assuming then you are then moving the cyclic in the opposite direction to slow as quickly as possible, will increase the blade angles presented to the airflow resulting in an increase of lift, to a point. If doing strafing runs and basically want to do a 180 why don't you pull into a high angle nose up to bleed off speed, then when coming close to stationary go with a large yaw input to swing you around on a dime. The increase in height then allows you to nose dive back down increasing speed pretty quickly towards the target?

That is because, for some strange reason, the ground crew do not like fitting pylon stores or feeding rounds into the sideloader with the aircraft in an armed state...

Ah - apologies - my bad wording! I have completed M2, but it won't roll onto M3 - so the issue with the campaign not picking up the completion appears to be back? Unfortunately flew a training mission without saving it - but will give it another go and spend more loiter time with Warlord - see if that triggers anything. If not will attach it.