zdog0331 Posted April 13, 2020 Posted April 13, 2020 This issue is exclusive to tank crew. The glitch is that the rendering cone is bound to the mouse cursor and not the vr headset. So what happens is anything behind you or beyond 90 degrees to your left or right simply are invisiable. And they will appear as soon as you move the cursor over. Most of the time the cursor is invisible, but you can see it when you use the command menu and is displayed by a a red circle. The only are that is being rendered for VR is about a 180 degree cone around that red circle and it stays in place despite your head moving. This makes it so you cannot see your allied tanks, wrecks, or other ground features such as roads and some textures. The only thing you can see is the basic ground texture and aircraft also do not seem to be affected by this. I have tried a sorts of reinstalling and even deleting control bindings to see if something is misbound, but nothing has worked. Vereified my game and did a fresh install and the problem persists accross multiple computers. This leads me to believe that it is a systemic problem that has yet to be addressed. Not many people play tank crew in VR due to many of the tank crew issues making it troublsome, but this one to me is by far the most important issue to address. It if is a glitch on my end i will be happy to try things, but for now there hasn't been anything that has worked.
RedKestrel Posted April 14, 2020 Posted April 14, 2020 On 4/13/2020 at 3:32 AM, zdog0331 said: This issue is exclusive to tank crew. The glitch is that the rendering cone is bound to the mouse cursor and not the vr headset. So what happens is anything behind you or beyond 90 degrees to your left or right simply are invisiable. And they will appear as soon as you move the cursor over. Most of the time the cursor is invisible, but you can see it when you use the command menu and is displayed by a a red circle. The only are that is being rendered for VR is about a 180 degree cone around that red circle and it stays in place despite your head moving. This makes it so you cannot see your allied tanks, wrecks, or other ground features such as roads and some textures. The only thing you can see is the basic ground texture and aircraft also do not seem to be affected by this. I have tried a sorts of reinstalling and even deleting control bindings to see if something is misbound, but nothing has worked. Vereified my game and did a fresh install and the problem persists accross multiple computers. This leads me to believe that it is a systemic problem that has yet to be addressed. Not many people play tank crew in VR due to many of the tank crew issues making it troublsome, but this one to me is by far the most important issue to address. It if is a glitch on my end i will be happy to try things, but for now there hasn't been anything that has worked. Is there an option in the interface settings for mouse view? I seem to recall that there is an option outside of the key mapping that enables the mouse view, and that it can be turned off somehow. Maybe in the camera settings...
zdog0331 Posted April 16, 2020 Author Posted April 16, 2020 There used to be one, but I checked like really checked. For hours. I think I have an extra 20 hours in game just trying to fix this through the settings. And the thing is its exclusive to tanks and not something that happens to aircraft which leads me to believe that it isn't one of the customization settings. Though if anyone finds something feel free to let me know.
RedKestrel Posted April 16, 2020 Posted April 16, 2020 10 hours ago, zdog0331 said: There used to be one, but I checked like really checked. For hours. I think I have an extra 20 hours in game just trying to fix this through the settings. And the thing is its exclusive to tanks and not something that happens to aircraft which leads me to believe that it isn't one of the customization settings. Though if anyone finds something feel free to let me know. That is extremely strange. I don't have VR or Tank Crew so I'm not sure how much help I can be. Have you contacted support directly with the bug?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now