Czar

(steam hw survey) (yes, it is a good platform to sample)

Crank up these two sliders. (make it three with 'in-cockpit' as well) If it is still not loud (they definitely are), you either has some hardware limitation or else. Edit: Are you referring with fly by sounds exclusively? If so, some planes are indeed dull from distance. ED made ones are loud while others can be a bit too quiet while flying by. Some inconsistencies there for sure.

This is native DCS motion blur. Looks nice on 'High' and intensity lowest on the slider. I didn't mess with it much since I turned it on. For me it is on my sweetspot already. It makes nice captures and eases the eye on a locked 40fps that I prefer. It makes low level flying more intense too. Feels real. I dropped the ball not editing the mirrors as the native motion blur doesn't act there, but it is everything ingame besides the manual color grading on PS on that shot.

Can be neither too, as I stated. Just dim it at night and it is a non issue.

Yw! I don't know. Unfortunately I've never sat in one, let alone at night. It can be a limitation on the backlight tech for its time as lamps and stencils, or can be a limitation of how it was implemented into the sim. Nevertheless, it can be worked around.

Try dimming the backlights so the characters gets sharper. Never use full brightness at night on the Tomcat.

Check for unlimited ammunition check box on DCS main menu option and in the mission options if you made the mission yourself. You have to take it easy on learning the module. First, get familiar with the core sim and options such as unlimited ammunition, then start slow by flying the aircraft in a proper manner before trying anything with weapons. You're only overwhelming your experience by getting it all at once. Cheers, have fun.

This has nothing to do with what I wrote.

It is not a fully mechanical GA aircraft. Its fly by wire control surfaces are inter connected. You're not getting the GA results from GA procedures. *GA=General Aviation

Just go with it without kicking out the crabbing. Timestamped 2:04 and 12:07 further on. The tires will take some sliding as it is usual with fighter jets. The only source I got is practical experience with DCS + Briefing Room, as sometimes that app generates crazy winds, and some videos.

Ahh, apologies. Hmmm, perhaps a few performance passes on the map are incoming. The details of the autogen are higher than in other maps, so is good to keep that in mind. I think you'll have good results with Visibility Range in 'Ultra', SSAO to 'OFF' and ground objects shadows to 'Flat'.

Lord have mercy of my wallet if that Nakajima and Zero become full fidelity modules one day. I still have a few peripherals to get this year. ED is really dragging me to WWII with this. Sensational.

The performance you're getting is pretty rough. This is the Performance I get over Baghdad. Timestamped 5:16.

It puzzles me as well. It is not the first time I see your posts in the forum. The best I can offer is: Check your memory health with memory tests (If everything else fails, because this can be bothersome and a lengthy task. Put it at the end of the list). Reduce or remove overclocks back to factory defaults. Disable ingame SSAO (it causes stutters on my end on some heavy scenes without GPU load reaching 100% for some odd reason. I guess is saturation or something). Use 'flat terrain shadows'. You have it on 'default' which is a MASSIVE hog on performance with autogen in view. If you haven't used 'default' before it may be a good experience. It removes cast shadows from external objects such as hangars on the cockpit, though :(. Visibility Range to 'Ultra' instead of 'Extreme'. Especially on Baghdad, the performance will be MUCH better. Same as SSAO. No 100% usage on nothing but a significant degradation of performance. Disable any RGB managing software running in the background. (some folks were having weird CTDs a while back that were caused by them). Make an exception of the whole DCS rootfolder on your anti virus especially windows defender. (Anti viruses usually monitors files being read from the storage drive and that can cause crashes): Usual path for files and folder exclusion management (windows 11 in english): Search for "windows security" in the search bar Virus & Threat Protection At 'Virus & Threat Protection Settings', click on 'manage settings' Bottom of the page click on 'add or remove exclusions' Add the whole DCS root Folder. Hope it helps. SSAO OFF and Visibility Range to 'Ultra' can be good. Don't worry about aircraft spotting with visibility range settings. It only adjusts city autogen at distance. Ground units visibility range will be unchanged as well.

I fly every two days in the Iraq map since 4 days after its release and I had zero crashes in it. Researching about your GPU didn't get me promising results on its rendering power and your crash log indicates an issue towards the GPU side. 2025-02-01 04:02:55.913 ERROR DX11BACKEND (9984): Failed assert `false && "failed to create vertex buffer"` 2025-02-01 04:02:55.913 ERROR DX11BACKEND (9984): failed to create index buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2025-02-01 04:02:55.915 ERROR DX11BACKEND (9984): Failed to create shader resource view for /textures/asphalt_6l_color.png.dds. Reason: The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action. 2025-02-01 04:02:55.915 ERROR DX11BACKEND (9984): failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2025-02-01 04:02:55.915 ERROR DX11BACKEND (9984): Failed assert `false && "failed to create vertex buffer"` Sure, above Baghdad it does need quite a bit of GPU power because of the autogen but here is more than manageable with only a 3060. I dislike to bring it up but, maybe is it time for some components upgrade? Cheers, best of luck to you.

If ED made configurable presets of cockpit configuration for ground hot, ground cold and air start this would be easily fixable. I don't mind turning the TCN knob down, but again, I don't fly quick air spawns on dogfight servers over and over again. Configurable presets and also a random function for some stuff that can be in the 'wrong' position to get the flight pre check worth doing. The knob detent for ILS knob should be reported as a bug or missing feature indeed...

Is this the same thing? If so, it is reported.

First one is already wrong. Man people fully trusting in AI is scary as f&$#... The Phantom II stabilators/elevators should droop because there is a counter weight on it, regardless of hydraulics. Airflow will balance against the weight with speed resulting in a more neutral position. But of course, any photo evidence can be dismissed by arguing the pilots are pushing the stick forward when taxiing. Only reading about its IRL systems of be in one yourself could serve as proof. Source: see the threads about FFB and how Heatblur coded the phantom controls. Or own the module and you'll see the stick going forwards by itself. F-16s: It is not as straightforward as droop or not. Depends on other factors. F-18s... AI got completely wrong. Their elevators should droop with no power. FBW has nothing to do with it. Just don't trust AI with your life. Mirage 2000Cs should droop too. As so it does in DCS: Which crazy AI was that gave you these wrong answers?

I'm seeing the same discrepancy with the Hornet against all my jet modules. F-15E, F-16C, F-14A&B, F-4E, A-10C, M-2000C.

That can't happen, I fly the viper often. Any chance you have a mod installed? Visor down and up needs a few seconds to finish an animation until you have the HMD back on or off. DMS AFT needs to be pressed LONG or it does something completely different. Check your stick or controller if the input command is indeed constant on that long press. We need a track to see that happening. If you have any steps to reproduce, will be faster to fix if there is a bug.