336_TheAngryGamer

I used to use it as the reset button. It has been made clear to me, this is not the function and there is a separate reset. I had not bound the reset. And the trim button down was bound as I described. But, I have now found the reset, bound it and everything is working exactly as described to me. So it is my bad but I just do not understand what I was doing before. I am honestly possibly just losing my mind.

After the most recent update, this seems to have zero function. It used to work fine, I double checked my bindings, looked in cockpit while pushing the button down and the trim button in cockpit is indeed going down. But there is no corresponding effect in flight characteristic or control overlay.

I do not wish to be insulting. So please do not take it this way. From my experience with logitech controllers, most recently the X52, Logitech is your main problem. If I could list all the people I have spoken with that have had input trouble with Logitech HOTAS, I would be typing forever. I am definitely not a person with a strong knowledge of anything PC related and I had zero issue setting up the modules in DCS and getting them to work. I can only assume you are smarter than me in this area so I do not believe the UI or your ability is the issue. I mean giving me a pc and expecting me to use it is like giving a caveman a car and expecting him to use it. He may learn but will have zero idea why or how it is working. FYI, I bailed completely on Logitech and now have a VKB setup. Once this caveman figured out the software, it is a wonderful HOTAS. And I have zero control issues unlike before.

Fixed by doubling my RAM. GPU was apparently getting over taxed. Doubling my ram reduced the workload. I do not understand these things. A squad mate helped me out. It occured to me to add this. OpenXR toolKit and HWinfo are 2 downloads my squadmate had me add to my pc. HWinfo was the tool used to help diagnose what was going on with my pc. OpenXR was used to help make tweaks while watching the result in real time. I recommend these to anyone whether or not your having issues.

I will try this and post the results. Thank you very much for the reply. This was not the solution but thanks.

Hardware, Oculus 3 V62 Rog strix b550/wifi motherboard Ryzen 5 3600 CPU Nvidia 3060 12g GPU 32g Corsair 3600 ram/ 32g more on the way I am going to try to attach crash file. If someone can help resolve this, it would be greatly appreciated. Every crash has the same warning on the bottom regarding the skipping of the file due to size? dcs.log

I am also feeling stupid for not mentioning this but maybe it doesn't matter. The PC is hooked to a 55 inch television instead of a monitor. I use it for games and movies. Running the game at 1080p

The thing is, I did try 72hz. 80hz, and 90hz. 90 offered the highest stable fps. I do realize this makes no sense. At least to me because I expected lower hz to offer better stability at the cost of eye candy. But it was completely opposite.

First, Rig strix b550 motherboard, ryzen 5 3600 CPU, 32G of Corsair 3600 ram, RTX3060 12g GPU. All of this is clocked to the maximum reliable level in the bios. Except the GPU of course. I have been trying to get a smoother FPS with the Quest 3. I get about 35FPS. Is this kind of the standard I should expect with my setup? I found from my nvidia monitor that the game is using 100% of my GPU, 75% of my VRam, but plenty of head room for my CPU. I can not remember the percentage of CPU usage because it was low enough that I dismissed it being a concern. I had MSI afterburner running but I found it wasn't helping and possibly hurting the FPS rate. Is this normal? Playing with in game setting seemed to have very little impact one way or the other on performance. Maybe a couple frames either way. I am not a PC literate person. I do not completely understand how everything interacts as well as many of you. I am told my ststem is pretty well balanced and I am contemplating installing 2 more matching ram sticks for a total of 64. I am willing to accept that I gave done absolutely everything wrong in setting things up to play the game. I do not really have expectations because that would require knowledge. But it would be nice if I could maintain a frame count reliable around 40 to 45. Also I use oculus debugger only to disable ASW and tried to force 45fps. My headset is set to 90hz as this yielded the best results at a pixel setting of 1x. Any help would be appreciated. I was as clear and thorough as possible.

I'm not an official representative of a legal dynamics but last I heard there was no hot fix. But they are working on it and it will get released with the update. Until then you can revert back to version 62 on oculus. I know because I did it yesterday.

Did you get it fixed? I had the exact same issue start last night. A person from my flight group helped me revert back to V 62 for Oculus which solved the problem.

So, I just spent all morning getting the game to launch. It was the ever so popular Oculus crash from their V 63 update. After some great soul helped me get back to V 62, the cursor was once again yellow. Leading me to believe this is just one more thing Oculus screwed up for the DCS community.

I dislike AI so much I have offered to buy the game for a couple friends just to have a gunner. Unfortunately, they were not interested. Something has to happen because at the moment I find George so frustrating, I find it extremely unenjoyable to play. Don't get me wrong, I love the Apache. I just am really tired of George.

This seemed like the best place to put this. Now that the mouse cursor is black, it is really fun to try and find. At least in VR and especially at night. I do not know why it was changed but in my opinion, it was better before. And would it be possible to add a binding to center it in the field of view so I do not look like a mad man sliding my mouse all over just trying to locate it?

I have been fighting to come to and maintain a stable hover. Without needing 5 minutes to do it. Removing all curves because of this thread seemed to offer improvement.