PawlaczGMD

I left it on, but it doesn't seem to make a difference. I'll try off tomorrow, maybe performance will be better. In adrenalin I have only the settings I specified, in DCS generally high graphics settings.

So I set Override application, x8 EQ adaptive MS in AMD adrenalin, and the game looks a lot better. AMD users should play with these settings outside of the game. Since a few updates ago, the in-game settings don't seem to even work.

After getting the Moza FFB base with self-centering, this issue is solved without needing a deadzone. Still it's a bit silly that it's not a software special option in the Hornet, or something like that.

Yeah, MSAA does absolutely nothing for me, no difference between off and x4. I have an AMD card so DLSS is not an option, FSR sucks as it produces ghosting and blur, TAA also produces blur on moving targets. These are not usable if you want to see in visual range. I will try to force it through AMD Adrenalin when I have some time to play with it.

Sad to hear, I was thinking of upgrading my OG Crystal for better image//display quality. Also, have you tried reducing local dimming?

I just don't fly close to AI if I expect it to do any maneuvers, they are too unpredictable. It's a core AI issue, you can tell them where to go but they will do it their way, which often means breaking at full afterburner to change course by 10 degrees or sometimes just teleporting around. I got collided with once in the break in Mig Killers, but that was my fault tbh, I was on the wrong side of lead.

I did it by just burning to drop on the target as fast as possible, then turned into him and fox3 at around 20nm. He fired at the same time, I then notch and drop to the deck, then turn cold. I reviewed tacview, and he stayed hot and died to my missile. His missile wasn't even close, it dropped loads of speed at low alt. I think bringing it down is the key. If I had missed, I'd try to use terrain to turn back in. Hopefully the lead will sometimes get him if he stays hot on you. Mig31 has no fox3 afaik, so they are at a huge disadvantage 2v1. Just defend if he's on you, attack if you're clean. Bonus protip - you can bug a datalink contact on the HSD with TMS up, and it will show an octagon mark on it on the HMD, no radar lock required to see where he is. I pre-bugged him while on my way to the bridge.

3rd party La-7 and Corsair are in development, but DCS WWII is quite slow indeed, not to say dead. I definitely would not expect bombers ever the way things are going.

I did not mess with it, TBH not sure how they implement force sensing, but the axis travel is not the problem, the problem is that the base is way too weak to enforce it with its torque. It works but just doesn't feel great and is not very precise, so I prefer to use the JF-17 profile with some modifications, since it's the next closest thing I guess. I would have liked to try the real force sensing stick, but I'm not interested in getting it just for the Viper. I might buy the new Winwing FFB base which is much more powerful and try it there.

Yes, it certainly worked better without an extension, but the extension is so much better for every other aircraft. I still think it could work with a stronger torque and better software, but oh well.

I set up a practice mission in that exact spot and figured out a way to do it. I did notice something that bothered me with the damage though. Unless I fire from really close, like dangerously close to not pulling out, the gun doesn't penetrate the SA-9. On some tries I checked the mission log, and multiple hits were logged, but no damage was done. Isn't the SAPHEI ammo supposed to have a decent armor penetration? I checked and SA-9 only has up to 0.55 inch armor. I also tested the HEI-T ammo, and it seems to work better, with more frequent damaging hits. Just wondering, I would have expected the opposite... I have a sneaking suspicion that the SAP rounds don't do damage to the target, or at least worse than the HEI ones.

You don't die IRL if you crash in DCS. You die IRL if you crash IRL. You die in DCS if you crash in DCS

TBH I don't think a two-seater is that relevant to onboarding new people. It's already a niche game, finding someone to act as your personal instructor for free (who has to know the trainer aircraft), coordinating this effort, communicating etc. is more work than just learning yourself or watching a video. You can barely get people to use comms of any kind in MP servers. You really think the first thing a new guy will do is find an instructor and get on a call with him? I would definitely not do that as a new player. Two-seaters provide some benefit for sure, but I am skeptical of how often they're used to train new people. They are definitely not necessary because you don't die IRL if you crash.

FYI, the FSSB mode for me is mostly a gimmick. As implemented in a FFB base, it lacks precision and torque to be used seriously in the Viper. Especially since I use an extension.

Being untrimmed in yaw induces roll. Always trim yaw first with neutral roll, then roll if needed. Pitch is mostly independent.

I'm struggling with this part. I could do it if there was better cover around, i.e. pop up from cover, but the terrain is pretty flat. The strela is spotting me and firing at least 1 or 2 shots during my attack. I have to evade, which spoils my shots, and I still have to roll the dice on the flares. What is the best way to attack this? I was trying to fly as low as possible, and pop up to end in a 30-45 degree dive, but that is giving the strela too much time. I could do it this way if I had perfect execution and a bit of luck, but maybe there is an easier way? It takes an hour to get to that point.

I've found the vehicle groups on the first try. Make sure to enable precise coordinates and pad the grid sequence with 0s if they give you less than 5 digits for lat long. Then switch the zoom, wide/narrow, flir/ccd to help yourself see things. Although, if the other pilot is also in a Hornet, it makes me wonder why the coord format she gives doesn't always match the obvious one...

Additionally, roll rate tends to reduce at high/transonic speeds in general, as control surfaces become less effective. This happens on jets without fly-by-wire too. On WWII prop planes, control surfaces can lock up almost completely at excessive speeds.

Yes, I run the default monocle settings.

I went back to Reflected's P-47 campaign after the engine degraded patch, and did not run into any issues with the engine dying long after WEP use so far. Testing in some difficult dogfights VS the 109, the engine will die after about 5 minutes of WEP despite all temps being in range. This is a reasonable wear limit I guess, but not really in line with how other planes are modelled, where the engine will be fine as long as the temps stay good. I've only tested running 2550 RPM once so far, and it indeed seems to survive much longer. More testing is needed, but there might be something to it. I just wonder what the logic here is. RPM itself is not the issue, because the engine can run at 2700 at lower boost no problem. Temperatures are not exceeded. AFAIK, higher RPM at high boost = lower engine stress.

open the controls indicator in-flight and see what it shows

Did you not warm up the engine? 1 min after takeoff seems like a different failure. I was getting it after an hour of flying and at low power settings.

Definitely for the HMCS, since it's an item the pilot can have equipped or not. Link16 is a little more tricky, since our model just has it. Not sure if it requires external support to work, but if not, I can see how they would not give us the arbitrary power to switch off a system. This is also important for MP in general where players can just ask ground crew to put on the HMCS, but mission date is such that it shouldn't be equipped.

I've already tried the repair, it didn't help. I'm on AMD though. I have all the additional graphics options like upscaling, anti lag, etc. disabled.

I only have reshade and Echo19 sounds installed, I can't imagine it breaks the shader. Should I have something like 'haze.fx' in my "DCS World\bin\reshade-shaders\Shaders\VREM" dir? It looks like this:null