SkateZilla

Apologies I dont handle DCS Crashes.

AH-64 was in plans in 2006 (Originally an A), No one ever said that it wasnt happening, there was posts about the later blocks, some weapons and the -E Variant being a no go.

Who said that about the AH-64? Also do you understand the AH-64D Modelled in DCS isn't even the more recent D Block? Eventually, Testing Sqns always have stuff way before the capability is deployed to the fleet, and manuals are made. Looking at at least 1 year if it passes quals before it's deployed to fleet in a OFP Update and Manual.

We will, that's the thread topic.

if mission designer were to put them in the same mission then that's on them, But realistically naval F-4s and Super Hornets never Flew at the same time, nor did half of the aircraft we have in DCS now, Basing selection off their board call is not a smart business decision. As for Bridle Launched Aircraft, you cant expect a developer to make engine changes based on a 3rd party mod, DCS can support Bridles just fine, the 3rd Party team can integrate it on their own if they wanted.

F-4's and F/A-18 Lot 23+ Never Flew at the same time, so Re-using the Rhino call doesnt affect operations.

Thou gent hast 555 posts since august 2006, th'ref're gent is not new Blame it on auto correct, that's what I do and 99% of the time it's actually true.

this seems more of a System Software/Hardware issue, with USB Polling and latency causing the FPS Stutters you're seeing.. 60 FPS is 1:2 pulldown from the TrackIR's sampling rate, w/ Native being 120Hz, which is why those FPS look the best, If TrackIR is Polling at 120Hz and your FPS is some random low number like 37, then there's going to be latency introduced due to the pulldown and sync, the same happens in VR, TrackIR has yet to update their software to be asynchronous to the GPU Rendering rate. NaturalPoint (is it OptiTrack?) has been pretty much sitting comfortable with trackIR4 and 5 and hasnt done anything to update them to work with today's GPUs.

My thoughts and opinions are of my own, and have no affiliation w/ ED or their Business decisions. But I did give it a re-post.

There is no HB A-4, ...

You'll have partial functionality for steam, Launch Functions should still work, Adv. Launch Functions should mostly work. Anything dealing with the Updating, Repairing, Cleaning or Module Management will not work. as "DCS_Updater.exe" is not part of Steam Distribution.

there is no Fighter / Attack - 18G

you can use them locally on the client PC, VR or Screen regardless, if you want them networked, then OBS -> Set Region, Stream to networked screen.

It fixed in the last patch, before that it didnt work so I did have the app launch it. Next app update will launch MT version if above Version # for MT MV working.

To protect their IP.

You're not going to get any type of release window announcement from ED because this community is bi-polar. If anything is delayed due to game breaking bugs, has a stroke, and if it's released w/ them, they'll also have a stroke. With that being said, if you check off the things like MT, DLSS/DLAA, etc etc. The focus is likely on stabilizing those before adding another major change. MT and DLSS Being stable will only make Vulkan integration quicker and more stable.

They Don't Exist anymore, and there's no chance in this universe or alternate versions within .5 temporal variance % to get the manuals legally without being sent to a very bad place. 3 Prototypes and 8 LRIP were built, they've since been converted to other variants since 1990.

There's Counterpoints to all of those" Larger Engines -> Larger Airframe / Larger Drag Index Larger Fuel Capacity -> Larger Fuel Consumption due to larger airframe, heavier airframe, larger engines, larger drag index. IIRC, A/A42R-1 wasn't added to the OFP and Certified stores until Block II, and didn't actually get used in deployment until S-3B's began to sundown. Outside of Fleet Demonstrations at airshows, 330 GAL isn't enough, and any hornet carrying A/A42R-1 in the Tanker roles now, also carries 4 FPU/11 480 GAL Tanks on both inner and center wing pylons, and NOTHING else, no AIM9s, no Gun Rounds, as the weight and drag index of that configuration is already extremely high. Seeing how the community reacts to things, Developing and releasing a Block I Super Hornet with the same capabilities Limit as the Lot 20 w/ Less available weapons carriage, The community will gripe and complain about having to pay $xx.xx for a less capable version of the same jet they already have, despite Flight model and visual model differences. I've been with the community since the beginning of DCS, and that assumption on the reaction is accurate based on 20 years of reactions.

MSAA Kills Frame Times at 1080P, or 2,072,600 px You're running 3840x1600, or 6,144,000 px which is 300% of 1080p. MSAA 4X at that resolution will kills frame times, Your resolution is high enough, there should be enough pixels for MSAA to Sample at 2X and get clean edges, DLAA As well. I hate to sound like a broken record, but it goes back to Knowing the Limits of the Engine, DirectX 11 Predates all of the RTX Series, all of the RX Series, Predates VR as well. Just because the hardware is getting more and more powerful does not mean the end user can crank the settings of every piece of software they run. DirectX 11 wasn't designed to do any of this, so limiting the "maxxed out settings" is something users need to practice to maintain acceptable frame times, DirectX's API Overhead and it's age limiting what it can do, can not be solved by throwing more powerful hardware at something.

the 4090 is prolly not even 75% Utilized because the DirectX 11 Engine cannot handle the Sim at Maxxed out settings, no matter what GPU you have.

MSAA + SSAO + SSLR + DOF That's a lot of Post Process Screen Space Shader Passes. Just because you have a 4090 doesnt mean it's automatic maxxed out settings.

DLSS @ Quality Renders 66% Scale, so that's why the text isnt as crisp.

The new pilot is still wip, templates likely would come after the model changes are finalized.

Download from the 1st post, Extract and overwrite the old EXE File. There is no Auto-Updater at the moment.

in 2016 we were still on 2.0 Alpha and 1.5 Beta w/ Oculus 1.3 just being integrated in April. A feature request was made in 2021...