Major Corvus

This sim is all about the immesion, so why wouldn't we want to walk around these icon aircraft before we figuratively strap into them? Especially in VR as you get the full scale of the aircraft, and yes maybe people won't do it every single time, but every now and then on those cold start early morning missions, I personally would love to walk around my aircraft and check it out. This same feature works well in MSFS 2024, so as long as it's not a massive drain on dev resources, bring it on for me.

That's the preset I'm using, but it wouldn't work on mine. Saying that though, I've tweeked the profile a bit to suit me so I might have upset something.

Included for your QA. This track did not use the Moza Frogfoot preset as per HIP Gaming's work around, but my own custom MIG 29A preset failed acfs on cold start.trk

Holding the joystick whilst the AFCS does its start up bit didn't fix the issue. However HIP Game's solution of switching to the default Moza Frogfoot profile in the Moza cockpit app did solve this problem. I noticed that the stick moved through a much greater range of movement with this profile set, and I was able to switch to my preferred Mig 29 profile after the startup, which although being a bit of a drag as I have to unplug and climb out of my VR simpit to do so, is at least a work around. First world problems eh?

I'll preface this post by first saying nice mod ED she looks great! However, no matter how many times I've tried, and even during the cold start tutorial, the AFCS system fails and I get a caution after the bit test. It's okay on a hot start, but I cannot get the system to work on a cold start, I use a Moza AB9 FFB base and stick, and at first I thought that the sticks' feedback was upsetting the position of the stick in the cockpit during the bit, but I get the same results even if I disconnect the Moza stick, so at the moment a hot start is my only option. Has anyone else encountered similar issues.

Same for me. I know that it's unlikely, but I'd love a full fidelity Frog

I'm having the same issue in SP in the F-14 but not the Hornet. It says 'Awaiting Salute...' etc but I'm saluting my head off many many times, but the deck crew just remain static with their collective thumbs up their assorted As. I'm also getting this nonsense about air supply when I ask for the chocks to be removed. That is to say, the text about the air supply displays but no corrisponding voice.

Also include the DCS folders in your USERS/YOURUSER/SAVED GAMES folder. Run a fast repair from the launcher then reboot. That worked for me

I had this exact same issue, but putting the root DCS folder and the DCS folders in the USERS/SAVEDGAMES folder as a Windows Security exception, then running the fast repair and rebooting, seems to have fixed it

I'm having the same issue

Nice work on the F5 refresh, it looks great. The 8 quid was worth it for the clean canopy alone, love it!

If that's how it's meant to work, then that's fine. I'll have change my tacticts in near peer head on engagements.

It has been my experience that after creating a simple mission where I cold start th F4 with an air to air load out. I take off and climb to 30'000 and after a certain trigger a single Mig21 will spawn 100 nm in front of me at co alt on a hot heading. even though I can actually see the target approaching in the centre of my reticle, long pressing of Jester context yeilds "no can do", until at between 18-20 nm he calls out the bandit and I've instructed him to lock the taget, and by the time I've waited the requisit number of Mississippis, the Mig has already launched it's antique fox one and shot me down. Even if I have that spare second or so where it hasn't yet launched, and yes I have the switchology correct, the sodding Sparrow refuses to come off the rail.

I'm Having this same issue

I'm having this exact same issue, and for me it's totally random as to which module is effects. It's either thrust or collective that's effected and remapping the axis doesn't work, neither does rescanning or unplugging the device in question (TM Warthog). The only fix that seems to work for me is exiting the game and reloading it, and that may or may not resolve the issue on a seemingly random basis. It's becomming a a bit of a B ache