Leg2ion

Tried installing latest MB BIOS? Also cannot remember if there is a USB setting in the BIOS though may be worth a look. Have you tried setting advanced power settings to high and not balanced.

Still getting the same in Nevada - and the opposite in other maps. Shut down and restarted DCS. Created/started a night mission in the Persian Gulf - getting the opposite! So aircraft positioned in a floodlit position on a runway unknown (apologies - was a quick check). Tarmac now lit up - A10C2 all in blackness. Will do some more thorough testing and report back when I have a bit more time.

Me on the ramp at Tonapah - all bright: Around 10 seconds later: This is first night mission after starting DCS. If I exit the mission then restart it - no floodlight affect.

Does your anti virus not scan any files you download automatically? Or before you run/incorporate them into whatever program you are running carry out a manual scan? Yes - for me it is. Startup is now 8 times longer. Say in the future - v2.8 - is rolled out. Startup takes 8x longer again - 4 minutes - no biggie?

Not sure if my setup - but DCS 2.7 seems to take a lot longer to load. Stable version takes around 5-10 seconds from double clicking the desktop icon to loaded, 2.7 takes around 30 - 40 seconds. Both are installed on the same SSD. After double clicking the beta icon the taskbar icon seems to 'pulse' green a few times.

First mission after DCS start up is a night time - almost as if the aircraft is lit up in floodlighting, and its normally just as I am about to switch on the battery master everything goes very dark. Will try to get a screenshot or track later.

I get this problem initially at the start of a mission pre start up in A10C2, but then everything is plunged into darkness as if a light switch is turned off, when starting a mission at night.

Try either a rescan or unplugging the controllers from the USB then plugging them back in with DCS running.

Wouldn't then the RadAlts be pointing up towards the sky?

Ah - ok. Will fly the same tomorrow with standard weather and see how it goes..

Just back from a training run in Nevada, A10C2 out of Tonopah. All settings on high/extreme. After sortie was on finals - around 6 miles out and suddenly a few clouds popped into view midway between me and the runway. One minute clear view - next - cloud. Unfortunately didn't think to save track! Anyone else experienced this - weather was set to dynamic.

Thanks @Habu_69. Will give it a try. Download freely available?

Thanks @Taz1004 - appreciated. If I were to use a manager - is there a 'recommended' or more user friendly one over the others?

Hi all, Apologies as a bit new to this, but can I simply install this mod by unzipping and putting the files 'somewhere', or does it need a mod manager. Will V5 work with both stable 2.5 and beta 2.7 - as some of the thread seemed to indicate V4 was needed for the stable? Additionally is there any hit to performance/FPS?

Not sure if reported under 2.7, but taxi 'follow' yellow lines are still missing/intermittent on tarmac airfields.

Good to hear @Jarhead0331. Must admit with the size of the new cards I found it a pain to seat mine properly - just built a new system and was only when I was exerting some pressure putting the power cables in that it actually clicked and locked in. Interesting difference regarding size/weight? Same card different manufacturer or different card?

Hi @Jarhead0331 - any progress?

I believe that when you start a mission the engine/throttles may be at a pre-defined setting, and will only then 'synch' once you make an input. I normally start a mission cold, but have noticed if I set a quick training mission beginning in the air I have similar. So I will normally keep my throttles at idle detent, using the keyboard to start the engines. If I start in the air, with my throttles at detent, the engines are at a set speed (not really noticed what it is - possibly around 85 - 90%) but once I advance the levers I can hear them throttle down briefly (as it detects idle) and then back up again to match throttle setting. Just checked and when I hot start on the ramp the engines are around 60%, with no audible acceleration. Additionally I have synch cockpit controls unchecked. I selected it - and it made no difference that I could see. Try setting your throttles up to max before you begin a mission, and then start a mission hot. Note the engine speed, should still be around idle, then slightly nudge the throttles backwards, and I think you will see the engines wind up.

Think this is still present in 2.5, unless of course I am slower with engines needing an overhaul. Get to around 100kts in an A10c2 and the wingman suddenly hammers past me as if he's got an extra engine! By wheels up he is around 0.5 mile in front... Flying the Georgian Hammer Campaign.

Yeah sorry. Took me a while to get my head round what was happening! Not tried assigning keyboard/controller presses, but will have a play later. That was the start of my thread as I have seen old posts on this but nothing lately. Of note - whilst not brilliant - it does seem to work 'better', but not brilliant mind, if you use channels 20 down, instead of 1 up.

Think this depends on whether you go backwards or forwards from pre-set 1 or 20 (the 'ends' of the wheel). Left clicking the wheel will take you forward 1 channel, right clicking backwards 1 channel. So if you are on 1 and right click, you are in effect trying to go backwards to 20, which is why it spins all the way up. In a similar method, if on 20, and then left click - you are in fact selecting 1, so it spins all the way back down. So once off either 1 or 20, left or right will only change you 1 channel fwd or back, once you hit the ends it will spin if you go the 'wrong way'. Track attached cycling fwd normally from 1, then back down to 1 then spinning the wheel by right clicking up to 20, and back again. Hope that makes sense? Wheel.trk

Real long shot - but are all the power connectors plugged into the Motherboard? So both the 24pin and 8 pin connectors are plugged in. And is your GPU powered properly? In that it has 2 x 8pin connectors. Is it powered by one power cable with a 'piggy back' 2nd connector, or 2 separate cables? If the 1st do you have a spare PSU cable available you can plug into the GPU. Is the card in right slot - PCI 1? I see the PSU is the recommended 'minimum' for a 6900XT? Out of curiosity what make is the GPU. Saw a post on the AMD forum whereby someone was running one of these with a underpowered PSU and had a lot of issues, but managed to address most of them by downgrading the PCI-e slot from 4.0 to 3.0 in the BIOS. One other thought, and please forgive me for this, but you are plugging into the GPU display port and not the motherboard display port? Again apologies. And finally - have you tried checking the Windows advanced power settings - make sure they are at high, ultimate if an option.

There are a few third party diagnostic tools that will monitor power output, etc. Might not be 100% accurate but might let you see any spikes when you plug in VR? How is the VR headset powered?

Any motherboard BIOS updates available? Also check for any manufacturers utility software - as they can also install 'stuff' that may not be the best. I have a MSI Nvidia 3070 - and as a for instance MSI utility Dragon Center installs a 'network optimiser' - killed my internet speed both up and down. Good tip from @XPACTabove. Is your cooling working correctly on CPU/GPU, check nothing has been switched to silent mode or has disabled the fans allowing things to overheat? Make sure the cooling is on Auto, or if possible manually crank it up and then run DCS. One other thing - kick out the VR and go with a monitor and see if it is stable.