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.

Of course you're right, Rudel. There are enough annoying aspects of using this sim without making it worse by having to enter my logins manually every time. And when I'm in there, flying, I enjoy it enough that all the annoyances are easily forgotten, but minimizing them to start with is never a bad thing. . Players take note: My friend who reminded me about where the saved logins are stored knows a little about coding. He said that what happened to me could be happening to everyone soon, as part of a security initiative. ED could be expiring PWs after a time interval, requiring players to renew their login info every now and then. Again, that's just a theory, but it does explain what happened to my saved login info. If it does happen to you, it's no big deal, and you now know how to handle it.

Actually, a friend reminded me that my saved logins are saved on my local machine only and no place on any network. So my original question remains: How did my PW get changed on my local machine to something invalid? I'd really like to know, not just to saitisfy my own morbid curiosity, but to prevent it happening again. The only possible solution I can come up with is to not rely on the saved login info but to enter it manually every time I start the sim. I can't think of another way to prevent this.

Rudel, I did as you directed, and was able to log in normally. My question is, why did my saved password get changed to something invalid? I have not changed it in a very long time -- several years. Was someone trying to log in to my account illegally and told the system to save an invalid password? I can't imagine how else this could happen. In any case it all seems better now. Thanks for your help, guys.

Right here. dcs.log

I should mention that I went through Big Newy's list of Things To Do First and removed the "semi-unofficial" aircraft I had (the A-4. the free MB-339 and the C-130) and ran Repair. I deleted all the temp files for DCS and Windows that I could find. And according to time.gov, my computer's clock is 1.114 seconds slow. Anything else I should try?

I've started getting the Invalid username or password message today and NOTHING has changed on my computer lately...or even in the last several years. I'll proceed to open a ticket formally, but wanted to post in here in case somebody knows how to burp my machine to make it all better. Anyone?

I can confirm that drops made below 20K work fine. I did a drop of -38s at 18.5 and got 10 out of 10 kills. So it worked. But I had no success with the JSOWs. I dropped 8 -154As at the same altitude and got 1 kill out of lots of well-clustered targets. Most of them flew into the ground (!) nowhere near what they were aimed at.

I have not tried the -54s, only the -38s and JSOWs. But the -54s use a different guidance package than the non-laser guided JDAMs, which are similar to the JSOWs. I'm guessing non-laser JDAMs and JSOWs use the same guidance modelling in-game, so if one is messed up, so is the other.. If I get a chance I'll try the -54s later today and see how they behave. EDIT: I did use the -54s, but did not use the laser guidance feature, just the JDAM guidance. I've always heard the -54 acts just like any other JDAM if you do that. And it did. I got 1 out of 10 hits.

And using the GBU-38s against high-threat targets was my favorite thing in DCS. Not any more.... First, what was NOT a problem. post-update: entering a designated WP to make the INS system happy. Adding that step was easy. I've been doing the F10 targeting and -38 dropping regularly with no problems at all. (Well, some small problems, but never worth mentioning.) I'm very familiar with the process. After the update, I have been doing everything in the drop sequence just the same as always, with the addition of the WP designation. The HUD displays the JDAM symbology just like before, and up until the bombs leave the airplane everything is working just fine, just like before the update. But the -38s are simply not performing. I've seen them overfly the targets and try to double back to hit them, which never works. Most often they just come down nowhere near what they were aimed at. Used to be I could count on getting 9 out of 10 targets pretty much every drop. Today I had 1 out of 8 in one mission and 1 out of 6 in the other. I tried to attach a .trk file, but by the time I set up the airplane for the strike, took off, climbed out and executed the strike, the file was too big to attach. So here it is in Dropbox: https://www.dropbox.com/s/bkbgzypvzt7f820/incirliktoo-20210104-174753.trk?dl=0 Needless to say, 1 out of 8 effectiveness is basically useless. Help! EDIT: I was told by one of the denizens of the Razbam Discord Harrier help room that his squad mates have been experiencing JDAM problems since the update. I noticed in the ED Stable update notes that a lot of work was done on the JDAMs this time around. Maybe it's time for someone from Razbam Support to tap someone from ED Support on the shoulder and let them know they've broken the JDAMs. Just sayin'. SECOND EDIT: Tried the JSOWs today (in the F-18) and they exhibit exactly the same literally aimless behavior as the JDAMs. The problem is definitely NOT confined to the Harrier, or just to the JDAMs.

For those following along with this thread, (since I have been utterly unable to find an answer anywhere) the solution to my problem is the ERAS function. It's one of the tabs in the ODU, and with repeated clickings will remove the targets imported into the Recall page. A new set of 10 targets can then be imported and hit, just like the first 10 were. Works like a charm. Many, many thanks to the denizens of the Razbam Harrier Discord room, who Knew.