backspace340

It only seems to ask for coordinates if you get something wrong the first time round, e.g. if you see 'GC HOLD' the first time and alignment doesn't progress, then switch INS off and back to GC align, it'll then ask for coordinates (even though the PP coordinates it wants are the same ones that are already input in the UFC).

You probably have easy communications / radios switched on, which will take effect in SP but gets over-ridden by the MP settings (most servers have it disabled).

I wonder if this isn't an INS issue but a desync issue - there's a bug report for LMC desync (where pilot and cpg have different views of where the TADs is pointing after the CPG uses LMC) - if the target coords takes the pilot's view of where the TADs is looking (instead of the CPG's), that might explain why the target points or hellfires are hundreds of metres off target. https://forum.dcs.world/topic/314716-los-reticle-desync-between-pilot-and-cpg-when-using-lmc/#comment-5236896

Still seeing this in the latest open beta - at night on the Syria map, buildings in the cities had different levels of lighting in different eyes (I. E. Shut left eye, building is lit from the right and a particular level of brightness, shut right eye and it's a different lighting direction and brightness on the same building). With both eyes open it's a weird glimmer on all the buildings due to the mismatch. I've never used the shared parser setting.

I use the paddles on the back of my TWCS for the rudder pedals, which works well for me. I've heard of people using a mini-stick to do the same.

The weight definitely has an impact and makes it more likely, but I don't think it was the cause in my cases - I'd kept the weight below 17k lbs (something like 70% fuel, 8 hellfires, 300 rounds, no aux tank) so hovering wasn't a problem for me. Anecdotally, he seems worse over hilly terrain, I don't seem to have as much problem over flat ground - the main cases that got me killed yesterday were stalking through the valleys of low hills trying to stay under the 100ft engagement altitude to get a shot at some SAMs. Once I spotted them, I jumped in the front seat from a stable hover at 60ft, and George immediately rose to 150ft (so was about to get us shot at), commanding him back down to 60ft caused him to VRS and we died.

Yep, he killed me three times today... Doesn't look like this topic has a label, is it wip/reported or is this not going to be fixed?

LMC seems to be worse this patch for me - seems like before if you engaged it, it'd immediately null out the aircraft's movements (without having to touch the TEDAC slew) and basically stabilise the image, but now it's not doing that. It doesn't seem to do much of anything until you start putting inputs into it.

One thing that seemed a bit confusing from your video - it looked like you engaged Atittude Hold straight after takeoff when you weren't actually hovering and then left it engaged for the whole video. But once you went over 5 knots it would have gone to normal attitude hold (not position hold/hover hold) and so I wouldn't expect it to hold a hover after that. I think perhaps worth trying getting into a stable hover first (without lateral movement) with FTR held and then releasing the FTR and activating attitude hold (and alt hold if you want), that should hold the hover. And if you go over 5 knots and then want to hover again, I'm assuming you need to cancel attitude hold, bring it to a hover and re-activate it.

Seeing a big difference in the behaviour when the force trim release is held, feels much more stable in this latest patch compared to the previous one. Since release holding the FTR would make the helo start to roll and feel very top-heavy, but that's now entirely gone - it actually feels natural (like the KA-50) to hold the FTR while changing attitude/orientation and then let go to hold the course once steady. So much easier to fly than it was before!

But it sounds like ED are expecting it to work - bignewy said so when he asked for the dcs.log and it's even in the faq that it should be trialable:

I just activated the trial for Normandy 2 and in the module manager pre-download it referred to it as Normandy 1944 (rather than Normandy 2). Have flown on it and confirmed it has a blurry big ben, dcs log file here: dcs.log.old

I saw Wags has updated the roadmap to say they're planning to give us the AGM-114L Radar Hellfire next month (but no indicative timeline for the FCR) - so I was just wondering if anyone knows how we'll be able to use the radar hellfires without the FCR? i.e. what methods will we be able to use to designate a target / area and what are the likely limitations?

You can fix this pretty easily - just set the Pixel Density in the in-game VR settings menu to 0.6 or so, that'll get you back down to where you were on SteamVR. I've got a G2 & 1080ti and had to do the same thing when switching to OpenXR - my Steam VR resolution was set closer to the actual G2 resolution, but OpenXR is running way more pixels than that by default. I dropped the pixel density, didn't see any drop in visual fidelity (because it was rendering more pixels than I could even see, wasting performance) and my frames recovered.

There's a video of what the same pod looks like in the F-15E here - seems a lot worse than the Litening, can't really see what something is even 6nm away: Obviously ED might implement it a little differently, but that's probably a good idea of what to expect.