Good! Because if you go through the whole list (which I strongly encourage, at least until you find the culprit), you will almost certainly find whatever ails you. I do try to be helpful here, maybe even more than I should when I could be flying, but I probably have a reputation for being something of a hard ■■■. But I’m only that way on people who constantly whine rather than taking real steps to solve their problems, or whine over things that are NBD, and one that really gets me going is expecting something, say an autopilot in a 172, to do something it’s straight up not designed to do, like an autolanding. In both IRL and the sim, the autopilots are not designed to do that, nor will they work! If you try to use an autopilot to do an autoland in a 172 IRL, the only thing preventing you from at least a crash and maybe death is dumb, blind luck.
And yet, for some people (like say, ME!), VR is working the same, or even better than it ever has been. The only time I have problems with VR is when I’m running an overclock (typically on my GPU, which I sometimes (like last night) do by accident), but the symptom is a CTD of the sim, not VR specific issues. I also have issues when I pause a flight for an extended period of time, say overnight while I catch my 
s, then it might crash when I turn it on or off. But I don’t blame that on MSFS, because it happens if I turn VR on or off regardless of if I’m using it for FS or not.
If doing the steps from above don’t help, try @CptLucky8’s recommendations for settings that you can find here. @CptLucky8, do those recommendations still stand, or have you changed them in any way?
It was not an afterthought. Perhaps the “when” of their release schedule was changed due to pressure from this forum, but they’ve been planning for VR for years. And they actually already had a dev team working on it for at least a year before the sim was released, assuming they’ve told the truth about that, and I haven’t known them to be untruthful. Yeah, some of their communications skills are poor, most notably their habit of marking bug reports as “solved” when they are in fact nowhere near being solved! I think that is something that needs to be fixed, we need visibility as to the actual status of bugs and when we can expect a real fix. Even if the answer is 2023, or “we have no idea”. I won’t necessarily like that, but I’d rather be told that than be lied to.
@Jummivana another request from me that I’d like a response to. I’d really appreciate answers, even if it’s “I don’t know” or “I’m not allowed to say”, or “maybe we’ll get to that in 2025”. The truth, no matter how bad you might think it sounds is what I want, and I do expect responses from you, which I’ve found have been sorely lacking. So do better, please.
You are very welcome. I actually enjoy helping people solve problems. I just get annoyed by the things I’ve already outlined, and especially annoyed when people just flat up ignore my advice, because I do know what I’m talking about!
@moadib2709, that is excellent advice!