Lixma 06

1070ti

I've DDU'd it twice now - same thing. I'll give .91 a try, though - thanks for the heads-up. e: and .91 is pants, too. Ah well, no biggie. 417.71 seems to be the breaking point - I'll stick with these for a while.

When the usage hits 100% the frame rate drops under 60 (synced) which is bad. I run my setup with lots of spare overhead so this doesn't happen, but these latest drivers have just robbed a chunk of it. My GPU is now working 20% harder for zero benefit.

This is offline - and the 'use these options for all missions' thingy is (and always has been) un-checked.

It might be user error on my part but when I enable labels I can only get either 'Full' or 'Off'. Changing the setting to 'Abbreviated' or 'Dot' does nothing.

My GPU usage has jumped from 60% to 80% in my benchmark mission. I've rolled back to 417.35 and everything is good again. Anyone else seeing this?

Yes, the view limits are not taking into account a real head wearing a real helmet.

And a bump for this too. The gauges are ridiculously hard to read....I'm assuming they are on the to-do list? I don't believe for a second we got into 1943 without somebody tweeting Supermarine about it.

I'm using keys, though. The only available axis I have springs back to the centre.

Bump for this - it's a nightmare trying to dial in just a small amount of rudder trim - the plane ends up swinging left to right. The elevator trim is OK so why not the rudder?

Will the D-9 get similar lighting upgrade?

The current 'Head Movement by G-forces' option is OK but some adjustability would be nice. At around 5:40 in the video you can see the bouncing and vibration from hitting the runway - very immersive! Also, the turbulence effects in the video look terrific. +1000 from me.

I only caught this because a stray 50.cal pinged me during a mission. It knocked out my oil gauge but the mission debriefing disagreed, saying it was the coolant indicator that failed. It seems the two gauges have their wires crossed somewhere. In the mission editor I arrange a failure of the oil gauge, but in-game it's the coolant gauge that breaks. The post-mission debriefing nevertheless insists that it was the oil gauge that malfunctioned. FW-190D oil-gaugeD.miz

I think historically that's how 99% of all encounters played out during WW2. That's the way to do it. Before Track-IR everyone was using the hat-switch (or keyboard) to look around, track aircraft and dogfight. We did just fine. Once you got proficient with your thumb it became second nature. Personally speaking it took years for me to transition over from hat-switch to Track-IR; having a fixed point of reference during dogfights combined with lightning-fast changes of view were boons of the hat-switch days. Even these days during a vicious scrap I'll find myself disorientated in a way that would never happen when I was using the hat-switch. But I'd never go back - the advantages of head-tracking do outweigh the disadvantages, in my opinion. If you are considering Track-IR make sure you look into the vastly cheaper alternatives. Track-IR is great but very, very expensive.

It's been reported. https://forums.eagle.ru/showthread.php?t=227452

e: nm

Seems to be all skins - even Reflected's unofficial ones; I guess they're using the same prop texture. I've attached a mission file - it should be visible from the start. P-51prop.miz

They look fantastic now (Spitfire needs some love, though) The only thing I'd ask the devs to consider is increasing the resolution of the textures used on the canopy. Mostly it's fine but particularly when the sun hits them the glare effect looks just a bit too pixelated; mainly because the player's virtual head is so close to the canopy. Other than that, they're great - I hope other aircraft/helicopters get similar treatment.

I don't think the rudder was doing anything. I've noticed that even when 'flat' shadows are enabled aircraft will nevertheless use a projected ('default' style) shadow when passing over buildings, trees etc. It looks really good so I wonder why it can't be the same for the ground too? That way we can still use 'Flat' global setting and also have a great-looking aircraft shadow - minus the performance/aesthetic hit that 'default' shadow settings currently come with.

One thing I don't like about the cannon sound is that you can hear the reverb/echo from when it was recorded. This might make sense when parked on the ground among buildings etc, but not so much when airborne.

Sounds like a calibration issue. Some things to check... Ensure you haven't got two controls mapped to the throttle. If you haven't already check the 'Slider' box in your throttle axis settings. When you move the throttle is the red dot tracking the black box across the whole range of movement - like this? Also, is it just the lower end of the throttle giving you trouble - can you reach 100% power? It might not be as noticeable.

I think this happens when 'FLAT ONLY' shadows are selected in the options. A few other aircraft are manifesting the same flickering. https://forums.eagle.ru/showthread.php?t=228985 Try turning cockpit shadows on and see if it goes away.

In the controller options check your throttle axis - it sounds like it might not be calibrated properly, so 'all the way back' might not actually be registering in-game as fully back. e: does it also creep forward when starting a mission hot from the runway?

Yes. It's a big one, though, and IIRC the problem occurs near the end of the flight. https://www30.zippyshare.com/v/xq0OgrsH/file.html e: well I just tried playing the track but after 30 minutes I'm still stuck looking at an airfield; I guess it's broken.