Tophatter14

You might be interested in researching F-pole and A-pole metrics which quantify these concepts. A very general open source rule of thumb is 1/2 the shot range, assuming the defending fighter has cranked during the timeline. If he took a shot at 30 miles, and you are still alive at 15 miles you can probably turn back in -assuming your RWR status is naked.

After a bit of digging and adjustments audio is good now. Here’s what I did: I lowered the SteamVR speed to 150mbps. Still running at 90hz I plugged the Quest Ethernet mod directly into the Cox router’s 2.5gb Ethernet port and another cat 6 cable from the router to the PC. Ensure you are using cat 6 if you want max speed, according to the internet (I originally tried a wireless 6ghz connection with both VD and Steam to compare with the wired connection, hence having the Eero in the diagram.) Windows audio settings - ensured everything in and out (Steam headphone and mic) was set to 32 bit/48000 so it all matched. (One was 16 bit -Did it make a difference? Who knows but the popping stopped so….) When I used Meta Link, this cable with an additional power adapter let me run the headset all day. Usually keeps it at 87-88 percent charge even after all night sessions. INIU Oculus Link Cable https://www.amazon.com/dp/B0BRQMFDQ3

Same. Ended up having to return the Eero it doesn't play well with Cox Panoramic and need that for TV in a few rooms. WIred as per this thread seems VERY good to me now, but noticing static-like audio (pops etc) for some reason in DCS and also Reentry -Space Sim. Anyone else experience this?

Have some cables, adapters etc incoming. I'll give this a try and update how it's working.

Don- the developer is aware of the radio navigation bug and it will hopefully be fixed in the next update.

Of course. I was just testing you. Thanks for going easy on me haha Found it on page 8.

Question- what if the player wants to skip all the crew chief scripts? Just start the jet and taxi? Sometimes I'm just not that interested in taking 20 mins to run BITs etc. I get enough of that at work.

Edit: Repair export didn't solve my issues. DCS takes a long time to start/load missions/exit to main screen and more often than not crashes (locks up, unresponsive, forcing me to quit via task manager, I don't get the crash log ever). Not sure what's up. I've run a slow repair, deleted all FXO and metashader files, rebooted my PC a few times. Updated BIOS, updated NVIDIA drivers. Could be that, I suppose. Edit: Updated to latest beta 2.9.3. Seems to be working with only the occasional crash. Prob something in the plumbing of my rig and programs running in background.

Beta for Corsair MIGHT be causing DCS to take forever to load and also multiple crashes. I'm guessing it's also something to do with being a different folder than stable? Different export.lua? I think that mean I just need to repair the export? Any advice would be greatly appreciated, thanks. Gotta have that Wasp rumble haha

I agree. I meant to include the above re: a new kit from the same package.

I received the same advice about using two sticks of the same make and production date vice mixing up 4 even if they are the same brand bought at different times.

Touching video. Thanks for sharing. But remember, wings back for the break… always.

Any chance ED can follow up on the infinite chaff/flares the AI have? Or is it enabled if a player enables unlimited weapons for player aircraft?

If you set up a symbolic junction to another drive just for updates as linked below (due to drive size limits), don't forget to add that downloads folder to your windows security scan exclusion list.