DeltaMike

Better to map the TDC slew to your joystick. It needs a big dead zone, I'm at 6 now and that's not even quite enough. Flatten it out, I use a curvature of 25. Until you get used to it, you might want to reduce Y saturation, which limits the maximum speed of the cursor. As for trim, remember maintain straight and level flight with the stick, not the trim. Trying to fly the thing with the trim button never works out. You adjust trim by feel, not by visual indicators. If you're having to pull back on the stick to maintain level flight, pulse the trim button once or twice and see how that affected the back pressure on the stick. Repeat as necessary.

I have a logitech G903, which I'm sure is overkill for dcs, that said I find it useful in VR at least. Mainly because of the programmable buttons. For example, I mapped / to a button, that makes navigating comm menus a one-stop shop. Can't have too many buttons, and in VR it's really nice to have stuff you can operate by feel.

Looks like the throttle is modeled on the F18. Perhaps close enough for the $. The radar elev and the TDC slew/depress work, I'll give it that.

It would be cool if NWS could be used to exit AACQ mode That's what these guys do fwiw, I couldn't find a real reference

So far so good. There's no one place to start, actually there are two BVR modes 1. Nav mode. Neither AA nor AG selected on master arm panel. Like when you first flip on the radar after you take off. RWS --> (LTWS* --> LTWS track -->) STT (return using NWS) Note: AACQ not available 2. AA mode (either by selecting missile or pressing AA on the master arm panel. Which selects a missile.) Difference now is the option to select AACQ out of either RWS or LTWS. If it picks up a target, you can exit using NWS. If not, as of right now, the only way to get out of AACQ is to change modes. Either to AG or Nav mode, then reselect AA mode. Or to WVR mode, then hit NWS. For the sake of clarity, I wouldn't change the fundamental structure of your flow chart, I like that you're basically starting in AA mode, I'd just add a blurb about how to get out of AACQ, because it comes up a lot For WVR, you can go straight from BVR to boresight/HACQ/LACQ then to horizontal or vertical scan. Three ways to exit 1. NWS 2. TDC depress *3. RTS button on DDI* (for what it's worth) Gun mode is exited via NWS. At this time there appears to be no way to get back into gun mode except via switching to nav or AG mode, or by selecting a missile and then going back into guns. With this in mind, I think for the sake of clarity, I would make the starting point "AA mode" and make gun mode a sub-branch looping back to AA mode. No idea if any of this is how it "really" is, and it's probably not any of my business. I found this for what it's worth you can see how their control scheme differs from ours. *optional default

Oculus go? It's not the cost of the headset -- not around here anyway, you can spend more than that on a joystick -- it's the computer to run it. Least with Go you don't have to buy the computer, and you'll get some utility out of it.

Also NWS doesn't get you out of AACQ unless it found a target

Just downloaded the -15 the other day, that thing is a blast to fly. But, ye gods, that radio. Curious, how does it interface with SRS? Does it work with the overlay I hope?

I would not recommend the 2600, that CPU is garbage. For DCS you want the maximum single-core performance you can get, and don't count on overclocking. Sweet spot right now is the 3600X (and you want the X, you cannot overclock a 2600 or 3600 to "X" levels) but you could get by with a 2600x and upgrade later if you want Nothing particularly wrong with B450 motherboards and MSI works well enough, just make sure you can update the bios without a gen1 or gen2 chip involved, get one with a bios flash button (I know the Gaming Plus series does this) You're on the right track, you want as much CPU as you can afford, and just enough GPU to get the job done. Nothing in your price range will drive VR, if that's in your future (you need a minimum of 1080/Vega56 for that). NVIDIA is a better bet for flight sims in general, and DCS in particular. In your shoes I would way more want a 1060 than a 570 for the $

If you're a bigger butted man, check out Clutch, which has a range of sizes. Solid, comfy and compatible with monstertech chair mounts. Every jet should have a swivel seat, makes it easier to check six. And cupholders, every jet needs that too. (Dunno what Boeing was thinking)

Very decent! I'm assuming that's single player / empty map? What do you have your MSAA and supersampling (PD) set at? Dude, if we can drive a reverb with a $400 GPU, that's big news

you have the pedals plugged in to the throttle, right? in windows, "type here to search", "set up USB game controllers." If the same stuff is happening without windows running, try a different USB port. If that doesn't work, update drivers and mobo bios. If that doesn't work, I'd suspect a hardware problem. If it works in windows without DCS running, unplug any other controllers, if you have a game controller plugged in, lose it. Go into DCS and make sure you don't have two things mapped to the same axis (which is probably the problem).

^The more pixels you're driving, the more GPU you need. I've heard of people doing VR with a 1070 but it's gonna be close. I'd definitely go with the Rift S, not as many pixels and you only need to be able to hit 40fps and even then your settings need to be low low low. IPD isn't as big an issue as people worry about (imo) as the sweet spot is pretty generous, it doesn't have to be right on it. Plus I've heard from several people who have tried both and prefer Rift S anyway (go up a couple of posts for instance)

awesome.

My feeling so far is, the most important basic skill is stall practice, absolutely critical to understand the jet's handling right on the edge of a stall, and how to recover. Main thing is, yanking back on the stick doesn't make it go up, and giving it gas doesn't make it go right away. Gotta know how to trade altitude for speed. Cool thing about the F18 is, you still have rudder authority even when you aren't technically flying. Among other things you're less likely to just hang there like a sitting duck when you get slow, you can snap the nose around and get going. Bad news is, you'll be on the receiving end of a lot of ground kills until you learn how to manage your energy. If you haven't seen this definitely watch it. 1. When you are nose-to-tail (two-circle) it's basically a race to see who can get around a circle the fastest. Note, going fast and going around a circle fast are two different things. You want to be at corner speed, which is somewhere around 400kts. 2. When you are nose to nose (one circle), as a general rule the slowest guy wins, you're trying to tuck in behind the bad guy. Just don't get too slow and stall out, or give the guy turning room where he can get his nose on you. There's an important comment buried in the video, "this is a descending fight." Under some circumstances slow is good, but I don't see where low is ever good in a Hornet. Finally it's important to understand how the geometry of the fight plays out in the vertical. For one, how you can turn more sharply over the top than through the bottom. Practice your vertical, figure out when you need to flip and still have enough speed to fly. To me the key advantage of the F18 is its nose authority as slow speeds. Key disadvantage is in the vertical. You can do some cool stuff in the vertical, you can snap it around right quick, a split-S can get you out of trouble sometimes. But there's just no way to chase an F14 or F15 (or the AI) to the top, gotta think of something else

What reference lines do yall use for parade formation in the F5?

I think it's a great idea. I'd at least think about running two classes, one for the basics as you describe, just like in r/l. Pound the pattern, practice stalls until you puke. Oops you lost your engine. That kind of stuff. I don't know that startup and navigation would lend itself well to your format. For startup, it's hard to beat the in-game hand-over-hand tutorials, and navigation just isn't a big issue in DCS and you'd need real time telemetry anyway. I'd go straight from pounding the pattern to military style training: maneuvers, formation flying and joins. I wouldn't teach a Western and Eastern class, we are all on the same side here in DCS. Integrate whatever suits your purposes, for example I'd think strongly about this https://www.cnatra.navy.mil/local/docs/pat-pubs/P-1213.pdf, the CNATRA pubs seem to be followed by a lot of people even if they aren't focused on US Navy operations Basics will save people a lot of time. But, seems to me, I think the two biggest issues for people once they start flying is stalls and joins. Lots of ground kills in this game, lots of thrashing around trying to figure out where your wingman is

The beauty of the Rift S is, it's OK enough. I can see well enough through it and I can play DCS well enough with my el cheapo GPU. And yeah the tracking is good enough, it does some weird stuff sometimes but I'm assuming that'll get ironed out eventually. And it's inexpensive enough. Thing is, you don't have to settle for "OK enough" with your rig

CPU utilization is meaningless, DCS isn't multi-threaded. You are CPU limited, but not by much, you have a fine system. If/when you upgrade your HMD you'll work the GPU harder. You can crank the anisotropic filtering if you want. May need to back off on shadows and vis range on a busy multiplayer server.

You're a deadeye with that gun. I'm assuming you're using the snake, the radar pipper is worthless, near as I can tell. Yeah it's a lot of fun. I started to say "just point it where you want to go" but that's not true at all. You can point it where you want to shoot, for sure. But where it's pointing, and where it's going are often two different things. Once you wrap your head around that, it's formidable.

CV1 actually requires a lot of horsepower, you're gonna want to push PD in an effort to make yourself not go blind. 1080ti is optimal, and it gives you room to upgrade your HMD later. Be aware nobody is quite sure what the ideal replacement will be, recognizing that benchmarks don't always predict performance in DCS, in VR. I'd bet money the 5700XT ain't it

For multiplayer Note, changing any setting other than anti-aliasing (PD, MSAA) affects CPU as well as GPU, these settings will free up CPU enough to play on a busy multiplayer map For a Rift S, with a 1080 or equivalent GPU, you can run PD 1.2 (it's on the VR settings tab) or MSAAx2 but not both. If you have more GPU, you can increase PD and/or add in MSAA until images start to stutter in rotation, meaning, if you're looking out the side window, or moving your head around. For single player, add in shadows, trees or whatever floats your boat. You may have to back off on anti-aliasing a bit. To start off, let your application control anti-aliasing. That means leave driver and steam settings at default.

I use my old Sennheiser PX90 on-ear phones sometimes. Tad better than the CV1 phones and the price is right.

My prediction is that the "top gun for cold war jets" will generate a lot of interest, and think the ground attack tournament concept is brilliant

I'm currently exploring the hypothesis that you have to have IIS installed properly and enabled to get localhost working, how to do that is not abundantly obvious to me on Win10 Server but perhaps one angle worth exploring