Dawgboy

I worked with PPete to resolve. After adding a module, multiple input devices became mapped to the same axis in the controls for that aircraft. After removing the bogus mappings, ensuring only one device was mapped to each axis, the view stuttering stopped.

If you convert the rotaries, I used the x256 setting, but that, too, is very configurable.

Greetings. I went for the STECS Mini Plus with two accessories: 1) detent frames and 2) additional button modules, which I upgraded from the Saitek X-65F throttle, without their FS stick. My flight stick is the TM Warthog. I'm very satisfied with the VKB STECS and find the engineering to be sound...they've thought through the design, production, ergonomics, and overall modular integration. While the software is a bit overwhelming, the VKB support on their Discord channel is great. This hardware/software provides excellent value, given the cost. The flexibility afforded by the programmable modules is outstanding. I converted the left-hand throttle rotaries (under the left pinky and ring finger) to axes versus DX inputs...better precision. I also replaced the single PTT comms button under the left thumb to a two-way comms button for UHF/VHF. I currently find only the angle/placement of the right throttle thumb rotary to be ergonomically hard to reach...seems I have to go out of my way to find it. Here is how I'm configured currently. Black labels are legit callbacks/keybinds, and the red labels are simulation-related inputs. My button #24 is a simple PTT, and the artwork shows a 4-way/depress. I also didn't use any of the base's buttons or rotaries since they have meaning to the VKB configuration, depending on the combos selected. I used the 4-way/depress for button #23. Hope this helps

@BIGNEWY OK...the final steps fixed the issue. These were: - Set water = low, and - Set preload 60k Pagefile was my issue not hitting SET, but I hit APPLY, thinking that was the proper way. I confirmed the proper settings. My windows setting on the card was already anisotropic disabled. I did some reading on the DX/GPU error you cited and from my additional logs, and depending on source, it could be code, DX mishandling, or bad driver. My simple triage says it must be in the N2 code given the other maps work ok. I had already done the DDU GPU driver cleaning and reload. And if one of the two above, e.g. water or preload, allows me to fly, there might be some clues there for the N2 code. Again, I had a similar issue with Marianas in the beginning, and it eventually worked itself out with no effort on my end. Thanks for your time and effort. Have a wonderful holiday season. db PS SRS also installed and working.

@BIGNEWY I have already used DDU to clean old GPU driver and installed the latest. What type of error is the GPU throwing? Why do other maps work fine? I used to have similar issues with the Marianas map, but those went away for whatever reason. For this test, I changed the pagefile to your recommended setting. I'm testing the changes one at a time, cumulative. Thanks. dcs.log

@BIGNEWY Ok, since your previous guidance didn't work, I decided to uninstall DCS, DCSBIOS, and SRS and begin from nothing. So, during this test, I submitted a crash report with the following, with more added here, which was conducted with a completely new DCS install: - No SRS installed. - No config changes in any menus. - No devices changed via the control settings. - No VR, only a regular monitor. - No overclocking on GPU and/or CPU...raw BIOS. - No TrackIR. - Running DCS as administrator. It crashes when the aircraft picture loads...not long after that point. Normandy is unusable for me. What is going on???!!!??? dcs.log

@BIGNEWY No joy. Here's the log after all of the steps except UPNP failed...don't know what to do with that, but not flying an MP mission...stand alone. UPDATE: Also, I don't know what part of your instructions did it, but SRS was no longer working with DCS. Thanks, db dcs.log

@NineLine are you the triage agent for this subject? TIA!

PROBLEM: As subject describes. STEPS SO FAR: I've performed a cleanup and repair, per the instructions. I've uninstalled and reinstalled Normandy 2.0, and I've cleaned out the FXO and Metashaders2 directories. I've deleted all mods. I've also sent crash logs via the built-in tool each time it crashes. BACKGROUND: Each time I enter, DCS crashes to desktop when I get to the first menu to either select a seat or proceed to the mission. This doesn't happen with any other maps except Normandy 2.0, and it's happened from the beginning of Normandy 2.0. It's unflyable for me, except it occasionally allows me to run the Train Strafe instant action mission in the P47 over Normandy. This happens in both VR and nonVR. Here is the latest log file. Any ideas about the issue?...there are errors in the log, but I have no idea how to interpret them. UPDATE: I was able to do a private MP session with my flying buddy, and no CTD. We were flying P47s on Normandy 2.0, over the UK, cold start. If I were to host on my end, I get a CTD. Don't know if this helps. Thanks in advance. db dcs.log

Also, ensure no other input devices are mapped to the various control surface keybinds beyond what you expect to be mapped.

I just logged in successfully on two different PCs....

@silverdevilwhen live, it corresponds with the screen showing a darker image in the video, but I see flashes of weird objects and it might darken a bit. It shows whenever there's a text menu displayed or closed within the sim. I tried it in the South Atlantic and Syrian map missions, and both do the same thing. I wish the video caught exactly what I see, but it doesn't. Just note the video darkening corresponds with the flashing of weird objects.

Regardless of theater, and only when I toggle the UHF or VHF comms menu as a Viper driver, the screen flickers with various objects, without a discernable pattern. It doesn't do this for any other keybindings or keyboard input. I will post a video of this, in which the actual flickering is there, but exaggerated in length...the flickers are much shorter, but completely bothersome. The introduction of the menu in the top right corner, or removing it, seems to cause this flickering. Screen Flickering This started two Open Beta updates ago. I was hoping the latest update would fix it, but no joy. Anybody else see this issue? I'm on DCS 2.8.2.35759 Open Beta. TIA

Thanks @Flappie

Barely visible taxiway/runway/etc. airfield lighting on various maps w/fog, and even when next to the taxiway lights, you can barely see them, even though aircraft lights are visible. Known issue?

What's the point? I made my point already, and you disagree, which is fine. However, you're bolstering my point in a round-about way...if they don't have the dollars coming in from new modules, there will be no more bug fixes, OR, they will take even longer. This is the difference between the freeware non-profit model and the for-profit model. Running it for-profit is always a delicate balance, full of tough staffing vs priority decisions, especially with Early Access aircraft. With the freeware, non-profit approach, you wait forever for both fixes AND new functionality. Your desires are completely controlled by what the devs can do within their volunteer time. I am amazed at how fast ED introduced some of the new Viper functionality, while being frustrated with the bugs. I even took a break from DCS because of it. MSFS2020 came at a good time for me, since I only fly the Viper. Now, if something's already out of Early Access, I think it's an "all-hands-on-deck" situation. I don't fly any helos, so I can't speak to the Hip issue you cited, but I'd be pissed if the Hip was already fully released and out of Early Access. When you buy an Early Access module, you sign up for the reality that comes with that module until it's fully released...

I understand the logic in this post. I think, though, there are two major groups...yours and the folks that want the jet to be more complete. I see advantages to both; however, I favor the fuller feature approach, mainly because you can test the entire mission flow and find bugs you might not have if you were "handicapped" into a comprehensive testing cycle for each sub-module. As soon as you add more subsystems, these integration bugs will show themselves. I find a more compelling argument in finishing a module's functionality, before starting another aircraft, leaving some bug-fixing teams in place at the end. But that isn't the way things work in this business; to keep the revenue flowing to support the business model and employees, you need to keep introducing new paid modules with a good strategic roadmap. To be sure, there will always be an unhappy contingent. For all the euphoria of the Apache release, as was with the Hornet, Viper, Tomcat, etc., each camp's fans will start the inevitable cycle that caused this post and other similar posts...frustration with bugs, as well as incomplete feature sets that come with Early Access and a lack of qualified experts that dance around ITAR/classified information.

I have seen this same issue, but the track file was too huge. I was in single-player mode.

This is an interesting mod, similar subject:

@razo+r @Northstar98 @Tholozor @norman99 Thank you for your tips. Followed the fusion of them, and connected the first time. Now to practice...

@norman99including turning off the HMCS?

And for some of us, live long enough.

"Move along, sir. Nothing to see here. Keep moving..."