Dawgboy

If any, what did you use before for VR and how does that compare with your Crystal?

Some will say not to, but I had to run TrackIR with administrative privileges after the same upgrade. That MIGHT fix it.

AND, to this end, the castles often served as a backdrop for many military posters for the nearby flying units, who often sold these prints to support their squadron funds. Cochem Castle is another, on the Mosel River. They are all part of THE ambience of the Cold War for many military members.

Agreed. For the Viper, the HSD and FCR cursor function similarly, but the HAD is overly sensitive.

Ordered 1 Oct 2024...only received the emails indicating late June 25. Don't know where I am on the waiting list, if "first buy-first served".

No pun intended? <wink> Good one...

There are estimates that 60ppd is retina quality, so the closer you are to that, the better the resolution. Even Pimax says this decision is up to the user what matters more 1) increased FOV or 2) near-retina-quality. I went for the latter (57ppd) since XRNeckSafer/eye tracking will offset any loss of FOV, for the most part, but nothing offsets for a fixed lower resolution. I used to have the HP Reverb G2, so basically more than doubling the PPD and adding FOV will help my VR experience. It's really what you prioritize for your VR flying experience.

Update: This issue seems to be related to the Cold War map. My testing included Instant Action and scripted Missions made for multiple terrain maps: - Syria: MFDs, using the above Viewport configuration, worked properly, without issue. This was a multiple aircraft mission. - Nevada: Good results but Instant Action only - Kola: Same as Syria....all good. - Afghanistan: Same as Nevada...all good. - Cold War: DCS freezes, most times have to reboot; 10% CTD and I can restart. Reboot, again, most times. All Bad, whether any type of mission on CW map.

I had a 7-8 year old I7 intel MoBo that wouldn't go Win11. Had an AMD Vega GPU, which I really loved for years. It was so easy to setup and use. It was powerful enough to get me into VR for a few years, but end of Win10 and needing more power for retina-quality VR forced an much-needed upgrade. My old system served me well for many years.

I, too, went with the 9950X3D, and it's smoking. Glad to hear your results are similar. I added the 5090 to ensure I was adequately future-proofed, and now I'm just waiting for my Pimax Super. Very excited about the prospects because my old system struggled with DCS.

I did more thorough testing the past few days, and the HAD cursor acceleration is still too quick.

In an effort to to determine what I'm doing wrong with this monitor configuration, I found an issue with Viewports on the Cold War Map. ===================================== _ = function(p) return p; end; name = _('DawgboysMFDExtraction'); Description = 'MainView on top; LMFD and RMFD to the right' Viewports = { Center = { x = 0; y = 0; width = 3840; height = 1080; viewDx = 0; viewDy = 0; aspect = 32/9; } } LEFT_MFCD = { x = 4125; y = 0; width = 900; height = 730; } RIGHT_MFCD = { x = 5390; y = 0; width = 900; height = 730; } UIMainView = Viewports.Center GU_MAIN_VIEWPORT = Viewports.Center =========================== Clean install, no mods. I have the main monitor as 3840x1080 on the left, with two smaller monitors to the right, 1360x768, with all monitors in landscape mode. I have not tested this in MP mode, only SP. Thanks! UPDATED BELOW

@BIGNEWY @NineLine Would you please move this to the "Bugs and Problems" section and track? TIA null

Just flew a HARM/HAD mission on the Kola map...I have the same issue. FCR slew is fine, but the HAD cursor is extremely fast, causing me to oversteer to hover and lock a threat. The HSD cursor also moves faster than the FCR but slower than the HAD. I don't fly any other DCS aircraft except the Viper, so I can't compare it to others. I am using the VKB STECS' X/Y coolie hat axis for my cursor controls. @BIGNEWY @GCRev @Corrigan @pjbunnyru

Viper, IMO. I think its avionics/HOTAS are much more intuitive. However, I would say it depends on which aircraft you cut your teeth and get used to...meaning you must overcome what has become second nature to then rewire your brain, hands, and cockpit scan for the other aircraft. So, it's hard to be unbiased, at least for me, with my answer.

Here you go. New pic coming, size permitting. VKBSTECSthrottle.diff.lua Here's a slightly mod'd version, focuses on BMS, tho.

Sure. I've updated it a bit, both the drawing and the config. I'll share shortly. Sorry...just saw your message.

If I'm not mistaken, the aircraft must also be armed, either for combat or SIM. If you don't see the ASEC after locking a target, cross-check that you're armed, if it's your intent to fire the missile.

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 Force Sensing 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