Sandman1330

Haha, if I need more than 32gb or ram and an SSD faster than the NVMe 960 Evo, shoot me ;) For me, it’s mostly on initial loading, but I do consistently get less smoothness and lower frames than the hornet. It might be related to PG map as well?

Seems like VR only, but I don’t play in 2D.

I have more stuttering and constant no-dump CTDs also. I mostly use the PG map. Specs in sig.

F14? It seems to be bugged this update, especially in multiplayer. Lots of talk about it over in the heatblur forums.

Nice write-up! Two possible scenarios for you that aren’t related to the declination: 1. I don’t have the Mi8, but I fly another type of helicopter in real life that is equipped with Doppler. It is not a very accurate system and is very prone to drift. When we are flying on Doppler, we update it’s position using a known point in flight every 10-15 minutes. This would account for the Doppler being worse, as you’ve said. 2. Does your mission have any winds? If it has wind and you are not accounting for that, then that will cause drift on its own. Even a very light wind will have a significant effect over a distance. As for DCS handling of variation, I’m not entirely sure how it handles it, but perhaps your issue is more related to one of the two points above?

Haha, exactly what I was going to say! I spend all day at work doing checks and maintenance flights, on my downtime I don’t want to feel like I’m at work.

You might get away with a PD lower than 1 in DCS. Never tried it, but I think it goes lower than 1.

I have an X56 for primary control. I use the touch controllers to manipulate switches, I find it easier than the mouse, at least until they decouple the mouse pointer from head movement! In Wag’s recent interview, he did say they are close to enabling the use of touch controllers to manipulate stick and throttle too, so what you speak of may soon be possible.

Be lower than him to increase ground clutter and notch. The F14 is very suceptible to notching in pulse Doppler mode. If you notch, you force the RIO to go into pulse mode. Pulse mode is immune to notching but cannot look down, as it has no ground clutter filter (that’s the Doppler part). So if you are forcing him to look down while notching, you are exploiting both weaknesses.

Has there been any recent news on if DCS will support WMR controllers, as it does for Touch? I think many of us may be jumping ship from Rift to the new HP headset, given this week’s news. I’ve just gotten into using touch in cockpit, and I like it a lot, so I’d like to keep that up when I switch to WMR if I can.

I run constant 45, ASW off to avoid artefacts. I don’t notice an issue until I get around 30, then it starts to get uncomfortable. In short: 45 is still fine for most, I think.

I haven’t myself, but a guy on my server uses a VKB Gunfighter with the X55 throttle. Should be ok.

Ok cool, thx for clarifying!

My Rift FPS is CPU limited in DCS anyway, even with MSAA x4 and PD 1.5. Until I drop a new Ryzen 3700X in this summer, anyway. The extra pixels will probably just balance out the load for me, assuming I turn down MSAA and PD.

Ok, so I then infer that WMR controllers do not work out of the box in DCS, like the Touch controllers do? Too bad. I’ll have to try that solution or go back to mouse again.

I'd asked this earlier with no response: I've gotten used to using Oculus touch controllers in the cockpit to manipulate switches. Do WMR controllers work in cockpit, or would I be stepping back to mouse? I was going to get a Rift S as long as it had even an incremental resolution jump, but then they announced this one - and the Rift S doesn't compete on resolution, unfortunately. If I'm going to buy another headset, I want it to be the most futureproof I can.

Do WMR controllers work in DCS like the touch controllers do? If so, this may be my upgrade...

I’ve only done it client/client as we have a dedicated server.

I’ve noticed it too, I think it is related to easy comms. It seems if you are relying on easy comms to tune your radio for you, the first call must come from the pilot. After that the radio will be tuned to the correct frequency, and the RIO can do calls from that point forward.

I think what he means is the Tomcat (and the F15 too) are locked to USA. If you try to change their nationality to Russian so they can be red air, you can’t choose F14 as their aircraft. OP: have you tried setting the red air to Iran? Might be able to get the F14 that way.

WebGUI seems to work again since the latest hotfix!

Is F10 map enabled in realism settings? Similarly, is it allowed in the mission settings for the mission you are running? I don’t recall off the top of my head exactly what the settings are, but you can disable F10 via the realism menu. Maybe try comparing the settings between you OB and release versions?

Try loading it first in normal UI. Start a new server and create your prioritized list in the game UI. Launch the mission, then exit out and start in norender. It should start the same mission that you set up in the normal UI.

This behaviour is realistic for radars in search mode only (nails/dirt). In STT or launch guide mode, a radar cone is only in the vicinity of 2 degrees wide, +/- a bit depending on the system. Therefore, everyone should get a nails/dirt/spotted when a search emitter goes active, but only the target or other aircraft in very close proximity to the target should receive STT or launch indications (spiked/mud/singer). This is the long standing DCS bug. At long ranges, the distance will be larger than at close range, but no way an aircraft 40, or even 10, miles away should get the threat indication unless they are directly in line front or back with the tracking beam, or many hundreds of miles away. I’m too lazy to do the trig to figure out what that distance is at 200 miles...

Haha, so even though my first go at this went very well, I went to do it again yesterday and struggled like mad. Visibility is tough with the canopy bow where it is, and the new jet wash certainly adds a new element. Gotta keep practicing!