Woxof

Just to provide some closure to this whole discussion, it turns out my motherboard was defective. Eventually the computer would not even power up, so I took it to the place where I bought most of the parts -- it was a new-built machine, from February this year. The place tested the computer, found the MB bad, and honored the warranty by replacing it with a new one. They said they're seeing a lot of hardware problems with gear assembled during the Age Of Covid, when companies literally could not find qualified people to run the assembly machinery. If you run into unexplainable problems, check the hardware. The likelihood of basic trouble with the hardware has gone from "almost unheard-of'", to "look here first".

Lucid, I'm far from an expert in DCS or the Black Shark (of any number...). But you're talking about two different variables, the avionics and the cockpit labels. If you want English for both, you have to change the settings for both. Change the avionics in the Options settings area, on the Gameplay tab, Avionics Language to English. Then for the labels, on the Special tab, first select the Ka-50 III from the column on the left, then change Customized Cockpit to English. Hit OK at the bottom right and you're set. I don't remember now what the process was in the older versions of the Ka-50, but it's definitely this way in the III. Note that this will only work from the splash screen and not from inside the cockpit of the Ka-50 III.

Still don't know. I'll give you the list of items I disabled: Cortana (useless, I know but I thought harmless, too -- maybe not?) Intel Graphics Command (also useless when using an external graphics card like my nVidia 3060) ScanToPCActivationApp (used by HP only when scanning, I thought) This leaves the only things running in the start folder as the Kensington and Logitech software packages (for the trackball and keyboard, respectively) and Windows Security notifications. That's it. Something in those three items that are now disabled was causing all my problems. But my system is much better now, thanks.

Okay, now it's working. I've started the sim three times now with no trouble getting into VR. The only change -- I mean the ONLY change made between not working and working was disabling a few totally unrelated and outwardly innocuous items in my startup folder. That was all there was to it. So...whew. Thanks for your help, guys. You might think you really didn't do much to help, but that's wrong. Knowing you were out there trying to help kept me encouraged enough to keep sleuthing away until I got it working. Thanks very much.

Neph, reread my last. I have the golden MiG in the golden hangar, but on the monitor and in the headset, both. What I don't have is the splash screen with the right-side and across-the-top menus. I don't have any way to get out of the hangar, not even back to the desktop. Any ideas? I did as you suggested and dumped the VR environment, but it had no effect.

Progress! -- of a sort. After the Stable update today, when I launch using the shortcut described above, I get the golden MiG in the golden hangar on my monitor -- exactly the same as above in my log_TWO entry -- BUT I also get the golden MiG in the golden hangar in the headset. This is without question some progress. However, I get no splash screen on the monitor or in the headset, and thus no way to get out of the hangar and into the sim. So near, yet so far. Is there something I can press to make the splash screen appear? I tried the Esc key which in the sim brings up the menu, but it did nothing here. Neither did the Num5 key, which I've used before in the golden hangar to recenter the splash screen after it got dropped elsewhere in the hangar, out of view. Neph, I've never used the quotes in any shortcuts before but I'll try anything at this point. Unfortunately they had no effect at all so I took them back out.

I did as Bignewy directed and deleted terrain.lua, then ran the "slow" variation of the repair applet to let the sim restore it. Then I made sure the shortcut was D:\DCS\bin\DCS.exe --force_enable_VR --force_OpenXR and I started the sim using that shortcut. But the result was the same as one I got where I generated Log_ONE -- black screen on the monitor, in the cliff house in the headset. It's probably not worth pointing out (but in the interest of completeness I'll do it anyway) that although the terrain.lua was throwing an error (I never modified it, either) I have been running the sim in 2D mode with no problems showing. Whatever was wrong with the terrain.lua was not affecting 2D operation. So...still stumped on this end.

Ah. So that's what Bignewy meant above when he mentioned "clues". Got it. So, whose support do I contact then? Please tell me it's DCS support, because HP support has been less than helpful so far.

Bignewy, sorry for the delay getting back to you. Real life, etc. I spent some time in the interval deciding how to provide as much information as possible. I ran DCS three times with three different startup protocols. I performed a fresh reboot before every attempt. log_ONE = Plain vanilla startup with shortcut aimed at D:\DCS\bin\DCS.exe Result: After DCS loadup box, black screen on the monitor, and in the cliff house in the headset, no changes. log_TWO = Shortcut with the same target, just with the force VR command added, so it's D:\DCS\bin\DCS.exe -force_enable_VR Result: After DCS loadup box, in the golden hangar with the golden MiG and VR hands visible but no splash screen on the monitor, in the cliff house in the headset, no changes. log_THREE = Launched using Skate Zilla's DCS Updater/Launcher Utility, using the VR On launch button Result: After DCS loadup box, in the golden hangar with the golden MiG, but the splash screen appears over them although they stay visible as background off the left side. The view is distorted and "zoomed", so the right-side menu is almost completely off the screen to the right, and the screen-top menu is off the edge of the screen above. This is on the monitor only. The view in the headset is in the cliff house and stays there. Let me know if there's anything more I can supply. dcs_ONE.log dcs_TWO.log Here's the third log file. dcs_THREE.log

Of course. I think you need to have that enabled to get the golden Mig in the golden hangar, which I have, although in the monitor only. Next question?

I know you generally like to have certain files to diagnose performance problems -- I've seen your list, Bignewy -- but I never get far enough to have performance problems. My G2 will not pick up the sim, no matter what. I get the golden Mig in the golden hangar, but only on my monitor. The G2 stays in the cliff house and goes no further. This is after a year of behaving perfectly normally in VR with no problems. I'm running the Stable version (no MT) in Windows 10. The sim runs just fine in 2D mode but stubbornly refuses to show up in VR in the headset. Just for reference, VR works flawlessly in MSFS 20. Is there a command I should be running at startup to get my headset to pick up the sim in VR? I thought about just opening a trouble ticket and hoping for the best (as my computer-savvy friends are advising), but I wanted to try here first. I'd be happy to supply any files needed to solve the problem -- as I said, I have Bignewy's list.

Sounds like me. 'Cept I've been playing for going on 10 years, and don't use Steam. But in my case the sim crashes on the "DCS World" startup screen, only when i try to run it in VR mode. Running without VR I get a normal startup process and the main screen. I can select a mission and get into an aircraft cockpit with no trouble. I've been running in VR mode for over a year with no problems, until today. I should add that I'm running the stable version. Log file attached. dcs.20230325-183928.log.zip

Well, I got the throttle axis to reverse, but I used the setting in Control Manager, not the one in the sim. I was careful to do a reboot and to be sure I had nothing running that was not essential to DCS. We'll see how the process works over time. But at least I can fly the thing now. On to the fun stuff! (...like guns, rockets, Hellfires, etc.) But the in-sim axis reverser still does not work, at least for me, so I'm leaving this here as a bug report.

Yep, did that. No luck.

I'm a RL flight instructor (fixed-wing) and have a very good understanding of helicopter flight controls and how they are supposed to work. I fly with a CH Fighterstick and Pro Throttle and TM pedals. For a more realistic helicopter experience, I reverse the axis on the Pro Throttle so it provides a fairly good substitute for a collective. I've used this setup for many years, starting with EA's Longbow, through EECH and for all the previous DCS helos, all of which I own. I've always been happy with the results I've gotten. Until now. I cannot get the throttle axis to reverse. I can check the box in the Controls setup in the sim, but it doesn't reverse the axis. I can check the box in Control Manager that I've used in the past as a last resort when I could not get the throttle axis to reverse any other way, but it doesn't work, either. I don't know how the RL helo pilots can fly the DCS Apache. I sure can't. So I'm reporting it as a bug. If somebody can tell me how to reverse the axis, and see that it's not a bug, I'd appreciate it.