Open KuMoNKo opened 2 years ago
iAmErmac
commented
2 years ago gzdoomvr uses only opengl for vr. a video/gif or a few screenshots would be helpful since not everyone owns an amd gpu and it's hard to imagine the nature of the bug only from your description
I also like to add that it doesn't make sense that 3d weapons work for you but the voxel weapons don't. both are using md3 model formats so they should be drawn in vr in the similar fashion
Leeroyzehn
commented
2 years ago Can confirm. AMD Driver 22.4.1 has trouble in rendering Voxel objects in Opengl (every voxel objects appear flat), using Vulkan shows no problem (tested using Hunter's Moon version V3.5.1 + gzdoom 4.7.1)
[](url
)
iAmErmac
commented
2 years ago Ah I see the 3d models appear as sprite. Is it fixed in latest drive update? if not then you should reach out gzdoom devs because it seems more like a bug in the gzdoom engine (and not just this vr fork)
GZDoom version
GZDoomVR 4.7.1
Which game are you running with GZDoom?
Doom 2
What Operating System are you using?
Windows 10
If Other OS, please describe
No response
Relevant hardware info
Ryzen 7 1700, Radeon RX 580, driver 22.2.2, WMR (Lenovo Explorer)
Have you checked that no other similar issue already exists?
A clear and concise description of what the bug is.
When trying to use voxel weapons, all the voxels apear to be compressed in two axes, X and Y, while Z information on position is lost. When animations are played, Z information is recovered (when using the chainsaw or shooting with the gun), but object position starts to jump on Y and Z. This happens using OpenGL driver. Vulkan shows a blackscreen and, after loading a map guided by sounds, exits with error (trying to access 0x000000000). The other two drivers exit with error before the menu screen.
*All axes Im refering to are relative to object, not to the world or the camera.
Steps to reproduce the behaviour.
Explain how to reproduce Using an AMD GPU:
Your configuration
Provide a Log
No response