PawlaczGMD

If you lose an engine, you need to land ASAP, you're not supposed to be taking off...

This seems to be the underlying issue. Yes, you can argue that the failure is reasonable given the documented G limits. But literally no other jet experiences this type of failure this easily, while having similar documented G limits. So the question is, why does it only happen to the F-5? Clearly, either something is unique to its design, or it is modelled differently.

I have the 7900 XTX, and I'm running a Pimax Crystal, which has a significantly higher res than Q3 (nominal 2880x2880). I have most graphics settings maxed out, running at 1.0 res scaling, and with foveated rendering, I'm getting 70-80 FPS in most situations (except busy airports). So you should not encounter any bottlenecks with this GPU using Q3.

FYI, there is an indicator button to the left of your TACAN knob. "PLT" uses your setting, "NFO" uses Jester's. The front and back seat TACAN knobs are not connected. Click this button to switch.

All fighters have a "soft" G-limit around 6.5-7.5 G, but it's more of a "don't exceed if you don't need to, it will shorten the lifespan and cause problems over many years" limit. But such stress damage is not modelled in DCS, and all other fighters can exceed it "safely" by a few Gs. E.g. the F-18 has a 7.5 G limit too, but will not snap. Flying the F-14 now, the stress limit is only 6.5 G, but the plane can pull 10 G without breaking apart - no problem. I've only ever snapped other planes by doing something really stupid, but in the F-5, it happens much easier. I will try to get back into it and see if it's still the case.

GPU resources are used to draw the image to display in the Oculus from abstract game data. What you see on your 2D screen is just copied from your Oculus. It's more like opening a jpg - don't need a beefy GPU to do that. The image has already been drawn once.

The one I had didn't have to 90 deg, but it's still fine. In theory, any USB 3.0 to USB C will work, the headset doesn't need crazy speed. It's more about the physical quality of the cable. I has to be USB C on one side because that's what your headset has, right? I think all these cables are good. When you play in VR, your monitor just mirrors the VR view. It doesn't rerender a 2D view in a different resolution. So the in-game res should not matter at all for performance.

I really liked both campaigns. However, in Reforger II, it was frustrating to follow ATC commands after the missions. I have broken every single approach into the airport except mission 1. I was following the commands maybe not perfectly, but pretty well, I'd say. Every time, I would not receive further instructions, and just give up after flying away from the airport for a while, land myself, and not get mission completed after parking correctly. The frustrating part with this is that the player gets no feedback or redo if you miss a single trigger, which effectively softlocks the mission (I just skipped it after parking correctly...). Can I suggest a simple fix - just pass the mission after parking on the spot, even if previous ATC triggers were missed?

Anker USB to USB C works fine. For DCS I recommend the cable, wifi is never perfect, and you're sitting down anyway.

Even though you were wrong, I've learned that the radar is horizon-stabilized - interesting!

It's debatable whether airlink or VD is better TBH. Start with airlink. Quest link = cable. Air link = no cable. VD = third party app, no cable. Turn on airlink in headset options, install oculus on PC, pair it, enter airlink and launch the game. It should just work, really, but if not, just buy VD, it's more intuitive to set up. Then, you can either try to launch the DCS .exe directly through the toolbar, which doesn't always work. Or, you can launch steam VR, and launch DCS through that, which should work. You can add standalone DCS as a non-Steam VR game to Steam.

I have no idea then. Since I opened the stick and messed with reseating the wires and tightening the PCB, I have not had a stick D/C in a few day, but I still have it on the throttle. I will try to do the same to the throttle now, we'll see if it makes a difference.

I don't think so. I have it plugged in directly. I have heard some advice that it might be related to my CPU or motherboard. Are you on AM4? what is your hardware?

It isn't fixed in the latest update. In MT VR, screen is often black. As someone above pointed out, quitting the mission, and clicking "fly again" fixes it! PS: this also affects LANTIRN when it happens. The pilot's screen will be solid green, and nothing is visible.

In some situations, the Jester wheel A/G weapon selection information is wrong. It shows a weapon selected, but nothing is actually selected. This might only happen in hot/airstart? To reproduce: start the bombing training mission. Jester wheel shows bombs selected, but nothing will drop if you pickle. Only reselecting the ordnance fixes this. This also happens in the Reforger campaign. Possibly, punching tanks also deselects your bombs, but the Jester wheel does not reflect this. You need to reselect something manually.

For real, this was the most difficult engagement in the whole campaign. I managed to get it after a few tries, but I'm convinced that the Mig-21 (and F-5) AI FM is complete nonsense. I almost think it's easier to beat Flankers or Vipers in BFM. On paper this 2v1 should be totally doable in the Tomcat, but it is actually extremely tricky, and I had to luck out with not missing the first shot.

Having played more missions, it's not that big of a deal. I had problems, because I had to abort one of the missions due to damage. But it seems like radio/Jester guides you in precisely most of the time if you do things by the script. You can also "cheat" by making an ATC call if you really need to, your guy magically knows the radial and DME even without being able to get a reply.

The dev has the right to put it on sale or not. All I'm saying, I would buy it instantly with a 50% sale, but probably won't for full price.

I have possibly the same issue, where randomly either stick or throttle will stop responding for around 20 seconds. They don't actually disconnect as a device, just freeze. This happens maybe once every 2 hours, so it's not often, but if it kills you, it's extremely annoying, and basically makes it useless for any longer MP mission. Did anyone manage to resolve this? I like the devices, but this is a major problem for multiplayer especially.

The Mig-21 has multiple issues that bug me, but is still a fun and functional module to fly. While I hope that they will update it properly one day, it is definitely worth $20 on sale. It is also one of the most iconic aircraft, and a staple of red Cold War gameplay. You're missing out so much if you neglect it because muh 3rd party developer.

I think it's totally doable. For tanking, turn HUD off, and really crank up NVG gain - you will see just fine. Your gain seems extremely low from the screenshot. Other than tanking, you can get away with not seeing anything, and just flying instruments, and following radio directions. Your flight is usually going full mil power in the direction they tell you, just do that. And if you want to "cheat": if you're conservative, you can probably get away with not tanking, just go easy on the burner when launching the TALDs... I had to dump around 2k lbs of fuel for landing in this mission. You tank around 3-4k, so you should be fine if you don't go crazy.

Bump. What OP is trying to say is: The scale of the altimeter is non-linear, but the increment/decrement inputs are linear in altitude, not bug rotation angle. So you have to crank the knob forever to get to high altitude values. Instead, the amount the needle moves per button input should be constant, and the altitude change non-constant. This would make the altimeter easy to set at whatever value.

Thanks, I will add this type of stuff to the mod manager!

Perhaps, but I just did a slow repair and removed all mods in relation to performance issues. The only non-stock files I should have now are FC3 cockpits. Could this be causing such issues?

Any tips on how to find the boat, coming back to land? I understand that the initial position is saved as Defense Point. But even with this, going back after an hour, I have trouble finding the fleet. Do they follow a predictable course/speed? I get that the mission enforces no radio contact, but is there some way to get a bearing on the fleet, at least from a large distance?