sasquatch98

The best option would be a checkbox in the special settings menu to require bore sighting or simple automagic boresight like we have for the cursor on the hornet or ins alignment on the harrier.

I just had this exact same issue multiplayer on Syria although my target was a hawk but bricked in exactly the same way. I don’t have track file for it but I’ll try to reproduce in sp to get one.

I’m having this issue right now on tempest blue flash, I’m not bothering with a track since that system is broken as well obviously. Please fire George and replace him with Petrovich, I’m okay with the cpg area reeking of vodka and dirty tracksuits if he’ll follow orders. Also hopping in the cpg seat and swapping the acq source to phs mostly fixed it, seemed like his aim was off with the hellfire k after that though.

The option is there but so far in cold starts on mp servers it hasn’t done anything always on A1

I wasn’t able to get it to designate on oil platforms last night or the handy wind but it was working fine on “live” armored targets.

You choose auto or manual lase on the lantirn (tgp) pod screen it’s along the top row of buttons when you have it up on the mfd I believe the center osb and will cycle between manual and auto lase.

I’m having the same issue crashes about 2/3rds of the time although if you spawn in a different aircraft first then respawn in a harrier it seems to work fine.

Go into steam and find Windows Mixed Reality for Steamvr in your library then go to properties and select the betas tab finally click the drop-down menu under betas and select “lkg_release - lkg_release” and it should fix it. I was having the same issue and it seemed to cause memory overflows related to some new feature they’ve added to make games run “better”. Oddly I just built my new pc and the new version runs fine on it without crashing but wouldn’t on my old system.

Same here

I’ve noticed they exact same behavior but didn’t notice anything about it in the patch notes.

I just have to correct this since no one has yet the Apache and Huey do not have the same rotor system. The Huey has a semi rigid rotor which is why it’s susceptible to mast bumping and the Apache has an articulated rotor system.

I’ve got basically the same setup except I’m using a reverb g2 and the 7700k is already a bottleneck to the 1080ti let alone a 3080.

I’ve just been rotating at 150 and it’s nice and smooth and also for anyone having it hunt or wobble down the runway make sure you turned off high sensitivity nose wheel steering before you start your takeoff roll.

I’m the same really don’t have any issues using it.

+1

I have no problem with the cockpit visibility either before or after the update using a reverb g2.

I have the same issue although it doesn’t happen for as long before it recovers.

I did some experimenting and a depression of 110 works really well between 250-300 ft and around 550 knots.

I’d start with deleting the fxo and metashaders folders and see if that helps I do it every update and if I forget I’ll notice it immediately.

I’m having the same issue with my Orion throttle and don’t have it set to sync with DCS.

Just to be little pedantic I saw it referred to as the Army Air Corps in the thread that hasn’t existed since 1947, it’s the Aviation branch normally just referred to as Army Aviation in the US.

Yeah same here, that’s a heck of a thing not to be a bug. I also get a similar issue with instant action missions in the hornet where the stick goes full left, not a big issue there and doesn’t seem to happen with any other module.

I’d love to help beta testing, I have a lot of free time and a 10.5 iPad Pro (2017), I can also test it on my wife’s iPad mini 4.