Bones308th

Okay guys, I finally got the Reverb to work right. Thank you guys so much for your help! I systematically troubleshooted it today, and here's what I came up with: I was running Windows Mixed Reality instead of Windows Mixed Reality for Steam. When I found out I was running the wrong WMR version, when I got the headset, I installed WMR for Steam, but did not uninstall WMR. When I turned on the PC, WMR would launch automatically. There was no obvious way for me to tell the difference in the two applications, as there's no difference in the application window tittle, to indicate which version of the app I was running. In other words Windows Mixed Reality, and Windows Mixed Reality for Steam, looked identical, from looking at the upper left hand corner of the main application screen. So, apparently, those two applications don't appear to run well together. After correcting that, I launched DCS and had the stutters, but at a much less frequency. I then made the edits to the file by removing the "//", and things really improved to almost being completely smooth. The frames where no longer bouncing all over the place. So that was awesome! The final change that made it completely smooth, was bringing down my PD within DCS to 1.0, from 1.5. I do have a couple of questions though: 1. I was abled to see the light indication on the upper left of the headset. What's the difference between the green light, and the blue? 2. If there's anyone here running the Reverb with the i9-9900k, and the 2080Ti. What resolutions are you showing within Steam VR, for Application and for Video? As default, I'm showing like a 19XX X 19XX number, or something like that. I ended up sliding the Video setting to 188%, and I ended up getting something like 22XX X 21XX. I hope the above, helps someone with the same issue I had. Thanks again guys! I really appreciate your help. Ray

I’m trying to find a way of locking the Reverb at 45 FPS. Is that possible? I just bought it a couple of days ago, and I’m seriously considering returning it, because of the stutters. My frame rates bounce between 90 and 45. I have the Rift S, and that thing is smooth with an ocasional stutter every now and then. Frames are constant at 40. The Reverb leaves me with a light headache every time! Hasn’t failed at that yet! Bones

Thanks Revs. I’ll do more on that tomorrow. Not giving up on the Reverb yet! Bones

Okay guys. Here’s the latest: I removed the “//“, and it did make a noticeable difference. However, I’m still getting them. The frame rate changes are narrower after the edit for sure. In other words, instead of swinging wildly between 45 and 90, they’re +/- 5 FPS or so, when the frame rates are somewhere in between 90 and 45. When I get low to the ground and frames are locked at 45, is a smooth experience. Is there any way of locking the frames at 45 FPS? If I can do that, I think it’ll cure the problem. Bones

Oh shit! LOL! Really?! I freaking missed the boat on that one! Okay. Let me try that! Thanks man! See Yah! Bones

Copy man. Thank you. I’ll look for that later today and let you know. At least for now, I haven’t noticed it in game. I contacted HP tech support today about the issue. They seemed to confirm the issue, and are working on a solution. I gave them the link to this forum as well. Bones

Okay. Something I noticed. On the SteamVR Settings menu. On the lower left hand side, I’m showing: Dashboard Off Chaperone Bounds Of Reprojection On Motion Smoothing Off When I launch DCS, I’m left with: Dashboard Off Chaperone Bounds Off Does this mean anything? Bones

I don’t see a color indicator on the Reverb Pro. Bones

Okay. That has been checked, and it was the same as the red lines posted above. I didn’t have to change anything. Bones

Thanks guys. I’ll check it out tomorrow. I put back my Rift S, and is silky smooth. I mean, I occasionally get some stutters every now and then, but nothing compared to the Reverb. One thing I did noticed is the Rift S maintains a constant 40 FPS. On the Reverb my frames are all over the place between 90 and 45. I had the same issue with the first generation Rift, but I managed to lock it at 45 FPS with the Oculus Tray Tool. I think the jumping around in frame rates, may be what’s causing the stutters. Again guys, thanks. I’ll test it in the morning. I’ll post back here. Ray

Dude, I’ve tried both, and no change so far. Thank you though. Ray

What?! In the same file? What?! Lol Sorry man, no idea. Ray

It does show as having Motion Smoothing as off, but I can’t find where to turn it on. Maybe that’s the issue? Ray

Okay. Reprojection is On. Ray

Hey Baldrick! Thanks for the quick reply man. I’m running Steam VR Beta, and WMR for SteamVR. The enable re-projection stuff, I have no idea! I have to check and get back to yah! Thanks man! Ray

Hey Guys, Just got the HP Reverb, and I’m having stutter issues. I have a i9-9900K with the NVidia 2080Ti setup, and is stuttering quite a bit. Especially noticeable when moving my head from side to side, in the pit! I’ve checked settings but kind find if this is a limitation with the headset, or if I’m missing some settings. I also noticed my frame rates bouncing all over the place, from 45 all the way up to 90! This is a show stopper for me with this headset, as it gives me a light headache. It sucks! I was running the Oculus Rift S and that thing was glass smooth. Please let me know what I can check, because I’m seriously considering returning it. Thangs guys! Ray

No worries Mike! Is an awesome and complex module man. Love it! Confidence is high that it’ll be fixed soon.

Then the other option is start on a land base till they decide to allocate resources to fix it, and recover at the ship. It sucks man I know, but that’s what we got to work with. Bones

Guys this has been happening for months now. The fix for me was to set calm winds in the mission and the carrier speed at 28 knots or greater. I found that if I set carrier speed to 27, I would get that issue. Play around with the carrier speed. If is set at 11, it’ll do that to you. If I remember correctly, I was able to make it work with the carrier speed at 24 knots as well. That worked for me. Bones

Hey Guys, Before I start spending countless hours troubleshooting, I’m having the following problem with SRS: When I get in the Hornet, I cannot transmit on the radios nor hear anyone else. This is happening in multiplayer with other Hornets that are able to communicate using SRS, in the same multiplayer mission; with me as the host. On the SRS pop-up I can see the “*” symbol switch between COMMs 1 and 2, but the lines don’t turn white, neither as I’m transmitting or when the other guys in the flight are transmitting as well. Power sources on the airplane are normal. Now, if I jump on the Tomcat in the same mission, other flight members in the Hornets can hear me, but I can’t hear them. As I transmit in the Tomcat, I can see the “*” symbol move between COMMs 1 and 2 again, this time with the TXR, but the lines don’t turn white. However, when the guys transmit, I can see the lines turn white on the appropriate radios, but I can’t hear anything. Again, they can hear me. All I’ve done is updates, and this started a few updates ago. I”m running as administrator, and I’ve purchase the application. SRS used to work fine in both airplanes. I have a little time to troubleshoot today, and I figure if one of you guys can suggest what’s the most likely cause, it can save me some time. Thanks guys! Bones

Hey Guys, Before I start spending countless hours troubleshooting, I’m having the following problem with SRS: When I get in the Hornet, I cannot transmit on the radios nor hear anyone else. This is happening in multiplayer with other Hornets that are able to communicate using SRS, in the same multiplayer mission; with me as the host. On the SRS pop-up I can see the “*” symbol switch between COMMs 1 and 2, but the lines don’t turn white, neither as I’m transmitting or when the other guys in the flight are transmitting as well. Power sources on the airplane are normal. Now, if I jump on the Tomcat in the same mission, other flight members in the Hornets can hear me, but I can’t hear them. As I transmit in the Tomcat, I can see the “*” symbol move between COMMs 1 and 2 again, this time with the TXR, but the lines don’t turn white. However, when the guys transmit, I can see the lines turn white on the appropriate radios, but I can’t hear anything. Again, they can hear me. All I’ve done is updates, and this started a few updates ago. I”m running as administrator, and I’ve purchase the application. SRS used to work fine in both airplanes. I have a little time to troubleshoot today, and I figure if one of you guys can suggest what’s the most likely cause, it can save me some time. Thanks guys! Bones

Yeah, the airplane is always on a constant drift in the same direction as the carrier. Bones

Check out a Tomcat mission named Bone or something like that. Is the one where you escort some B-1s to target. I’ve deleted the carrier, added a new one, changed its course, speed, changed altimeter setting, temperature; I’ve even changed the weather from static to dynamic, and nothing!

Man, I’ve tried at a default of 11 and 27 knots for the carrier, and I have not been successful. However, on an older mission with the carrier set to 27 knots and a wind of just 4 knots, I can launch without a problem. On the newer missions, as soon as I start the number 2 engine, I can see the airplane drift starting. Shut down the engine, the drift stops. On the older missions, the airplane wobbles a little on the deck, but it stays in place.

Guys, this is still happening! Do we have an idea yet what can be causing this? This bug might have been introduced a couple of updates ago. I have missions that I built a couple of months ago, and I don’t have a problem launching the Tomcat on those. Whatever it is, it may have something to do with engines. I noticed that as soon as any of the engines are started, the airplane starts to slide towards the forward part of the ship. When I shut the engines down, the airplane stops sliding. I’ve made changes to parallel the old missions, but I haven’t been successful in braking the code! Is there a workaround for this yet? Have we identified a cause? Thanks. Bones