FoxFlier

Thanks, I’ll take a look. The card *is* overclocked. I take your point about winter vs summer stability (especially given that in the uk we don’t run air conditioning) but I’ve had no issues sim racing. The CH47 (currently at least) certainly is taxing the system - I can get 90fps (the max the G2 supports) in most situations with the UH1 but not with the CH47. I’ll check a few settings and try again, thanks.

Here we go - a couple of the crash dumps - hopefully from different scenarios. All help appreciated! dcs.log-20240915-123334.zip dcs.log-20240915-130243.zip dcs.log-20240915-131552.zip

Will do tomorrow most probably. I did submit them direct from the crashes but with no context.

Due to a house move, I dropped out of DCS around six months ago but just bought the ch47 and returned to the fold today. I was somewhat dismayed to have DCS freeze and fall over a number of times in just a short period with the CH47 but wasn’t too worried given its early release status. Instead, I fired up the UH1 to brush off the cobwebs - only to find that fell over quickly too! Although I’ve not had time for DCS, I have kept it up to date (Steam install) and one or two Nvidia graphics driver updates aside, it is unchanged (and totally stable in the sim racing I’ve kept up with). System is an i9 14900KF, 4090, HP G2 (OpenXR). Have recent updates destabilised DCS in any particular area? Was it a bad idea to let updates install untested over the last few months (i.e. should I have fired DCS up after each one even if I didn’t have time to fly?) I don’t want to fall into the old trap of trying to ‘fix’ things with my system that are actually update-related teething issues…

I’ve just tried and failed (3Nm short of base) this mission too - but I did have to double back for a minute or two at the crashed heli site. Most of the missions seem to be really tight on fuel - this was the first one I did the cruise at 80-90 knots after reading Chuck’s guide (and absorbed the fact that more torque = more fuel). I’ll try again tomorrow!

Still broken! I’ve tried forming up with Springfield 1 in every possible position - nothing works - S1 will just sit there until we all run out of fuel! What the heck do you have to do to get this mission off the ground?!?

Oh joy! I’ve just tried this mission. Glad to see I’m not the only one… I did follow the correct checkpoint 14 adf first time and pick up the casualty. But then the return ADF for Madrid took me off course and despite using the knee pad to head back, I ran out of fuel just before Madrid. I had a problem with the Madrid adf on the Reporters mission too - that seemed to take me way off course but I can’t be certain I had the correct adf mode setup on that one (frequency was correct though).

It's still broken. Just bought the UH1 as my first helo. Disappointing that it's not been updated after all this time. Not shiny enough, obviously,,,,

I've seen this mentioned (with no solution) in Steam many times but can't find anything here. I've just added the A10-C2 - which is my first full module - and am incredibly frustrated that the cockpit cursor remains locked to the VR which makes it very hard to select controls with a mouse click when flying. I'd much prefer to be able to control the cursor using the mouse or a mini-joystick and not use the VR head position at all. (How) can this be achieved (?) TIA

This isn’t totally specific to the SU25T but I can’t find a better place to ask about it as I’m currently flying the base campaign…. I fly in VR and keep finding (for no apparent reason) that the view ‘randomly’ pops to the outside view. I’ve checked that I have no random control assignments - all I have mapped above and beyond the default is one button to return to the cockpit and one to view released weapons. *nothing* should actually be chucking me out of the cockpit…. is this a known thing?

Hi there - I’m fresh into DCS and FC3 and have a couple of annoyingly simple questions that I’ve not been able to Google… Firstly, the FOV zoom for the Maverick - as a VR user, the standard keyboard mappings (e.g. = ) are unusable but I couldn’t find the relevant entry in the control list to map a button to… Any hints? Secondly, in A-to-A mode (even after re entering my vr position), the lock-on zone pipper circle is placed above the HUD glass area - so I have to physically duck down to get it in view to see it and lock on to other aircraft. This doesn’t feel quite right… Is this the same for everyone or do I (somehow) need to adjust my vr seating position or something? TIA