SharpeXB

You wanted a real cockpit…. So? Put guards on your switches. They’re there for a reason unless you want to accidentally trip something important.

Of course that would make sense in DCS obviously.

Not sure what you mean by that. DCS no longer has a Game Mode. I don’t think the AH-64 ever had this, some modules used to but it’s gone now afaik. It’s already possible to use any type of controller including game pads. What you’re asking for can be done already so I’m not sure what the point of this topic is. Solutions for thumb stick sensitively could be stick extensions which are available for those and response curves within DCS. The chief problem I would have with a gamepad is the inverted Y-axis for flying vs aiming on the TADS. There’s no solution to that

I think to fix this you need to just delete your old Snapview.lua and generate a new one by creating a custom snap view in the game. That will make a new .lua. Make sure Snap View Saving is checked in the Options Unfortunately that means setting up your views again unless there’s some lua surgery possible. But if all you’re looking to do is set your FOV default (initial spawn and “normal”) that’s this here [13] = {--default view viewAngle = 95.000000,--FOV viewAngleVertical= 63.088276,--VFOV hAngle = 0.000000, vAngle = -10.000000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0,

That’s interesting to know. It’s too bad DCS is such a niche game we likely won’t see any actual tests for a real comparison. I’m curious if any of those benchmarks replicate this type of game usage. According to its description Geekbench tests using system memory. Those tests and benchmarks don’t seem to take overclocking into account though. Some of these oc better than others.

If you press ESC and bring up that menu while you’re in the planes F1 view it will change to the Cockpit FOV

I would think that in DCS any improvements in the game features should be to make them more realistic. The ability to request different weapons in the comms flow fits that. But trying to turn the JTAC into something it’s not IRL doesn’t.

There’s actually an FOV slider in the Options settings. When you’re in the F1 cockpit view it sets your cockpit FOV. Otherwise it sets the external one. If you want to dial in a particular value it’s kinda easier than trying to get that with zoom in and out. Pasting that value into the .lua does the same thing.

AMD X3D apparently does out-perform Intel very well in MSFS. I don’t know if that translates to DCS though. The trouble with buying a CPU because of how it performs on a particular game is rather self explanatory though.

So you just want to use the JTAC as a crutch for players? There are plenty of ways to employ aircraft or find targets besides using the JTAC. And yes the term “modernization” is a bit misleading. It implies that the DCS JTAC is out of date or somehow inauthentic.

I find DLAA with .4 sharpening looks really nice. It eliminates the jaggies or crawling and flickering that can be seen with MSAA x4. I’m running 2160x3840 with DLSS Off. I don’t see any smearing and distant aircraft are easily seen at up to 6 miles without the spotting dots.

Yeah I guess DLAA is a little softer than MSAA. I’m using 4K so maybe it’s hard to tell

Yes. I just deleted my old SnapViews.lua file and recreated it using the FOV slider in the cockpit and pressing Atl+Num0 That sets this value here [13] = {--default view viewAngle = 95.000000,--FOV viewAngleVertical= 63.088276,--VFOV hAngle = 0.000000, vAngle = -10.000000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0, It's working now in both Stable and OB

Try DLAA On with Upscaling (DLSS) Off. The blurry effect I think you are getting from DLSS

The question here was just about CPUs. Unless someone ran an actual test using DCS there’s no way to know the performance difference for certain. So benchmarks are your best bet. In the actual game scenarios can be either GPU or CPU limited. Arguably if a given CPU is 10% faster and that scenario is limited by a particular CPU thread, you’re going to get that % of extra frames. But that just theoretical. No way to know for sure. You wouldn’t go wrong picking a CPU from the top of those charts though. If you’re in a situation where the GPU is the bottleneck then the CPU won’t make any difference.

Yes you can copy over your Saved Games folder. A new PC or Windows version might rename your controllers though. I ended up just remapping mine. There might be a trick to handling that though.

You don’t need to uninstall the game to fix things. Just run a repair. If you delete any folder it will get replaced by a default when you launch the game again.

The difference between 90 and 99 FPS

They look about equal depending on the game. Small advantage to the 4070 Ti including price. https://technical.city/en/video/Radeon-RX-7900-XTX-vs-GeForce-RTX-4070-Ti#benchmarks

I also notice when I reset the Zoom Normal value this also set the initial value when spawning in. That’s nice.

When looking at CPUs for these sim games it’s best to look at their single-core performance. That’s still important even though DCS uses multi-core as the speed of each core matters. Intel looks like the leader on all of them. https://www.cpu-monkey.com/en/cpu_benchmark-cinebench_r23_single_core https://www.cpubenchmark.net/singleThread.html https://browser.geekbench.com/processor-benchmarks

Check out what AI ATC (payware Plug-In) can do in that other big civy sim. It’s not far-fetched to imagine AI you can talk to and they behave entirely human. AI will be doing all our jobs eventually

I just discovered my problem was that I didn’t have User Snap Views checked in the options for the OB version. Now it’s working fine. Neither Stable or OB is running as Admin for me but that didn’t seem to matter.

Good advice and great footage!

Already discussed and “Not Planned”