New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple guns in Rift mode #138
Comments
This seems to be a duplicate of issue #117 |
@vgf89 Thanks for the issue report. If you take a radiation suit effect (type "idbeholdr" during gameplay), do both weapons take on the green color? How is each weapon image affected by each of the other "idbehold" effects? http://doom.wikia.com/wiki/Doom_cheat_codes (r, i v, l, s). If you have the ability and time, could you please post some screen shots here in a comment on this thread? |
I know it's super old at this point but just noticing this issue thread. I have the same problem too. AMD R9 390x. The extra gun goes away with biohazard and steroids, stays with the others. All take on the color of invulnerability, invisibility, and night vision. See the attached screenshots. |
@picklefart9 Thanks for the screen shots. These are very interesting. |
Those different terms are just because I was using freedoom for the screenshots. In freedoom when typing idbehold, a different prompt shows up than in doom2: The weapon doubling goes away with idbeholdr and idbeholds, and comes back when they're toggled off. As vgf89 says, the screenshot shows one gun but in the Rift, you see it at the bottom center of both eyes. They don't converge so you see three guns in total. |
Ahh! OK. Thanks for clearing this up for me. Now I understand that whenever there is an actual blend effect, such as radiation/hazard/green or steroids/berzerk/red, the second unwanted weapon image does NOT appear. It so happens that I use the same framebuffer to pre-draw the weapon, and to pre-draw the blend effect. So what seems to be happening is that this framebuffer is not being cleared between the weapon pass and the blend pass, unless the blend pass actually does something. And the failure to clear only happens on AMD boards. I still don't have a machine to actually test this problem on, but I now have a much sharper view of where to look in the code for tactics that might help this problem. |
In particular this call to bindAndClearHudTexture() does not seems to be living up to its name: |
Pistol in project brutality is doubled in a similar fashion but the lower gun is transparent. I have R9 280x, other guns are fine so far. Also kicks and slashes don't show up. Maybe its related to the PB/BD wad. |
The top half of a gun is visible at the bottom of each view, and on the mirror window. It doesn't track, it's just stuck to the screen. The Hud's gun shows up fine and tracks properly. Happens in both DOOM.wad and freedoom.wad, with and without Brutal Doom, so I assume it's an engine bug and not at all related to some specific wad/pk3 file
This guy's image is the same problem I get. : https://www.reddit.com/r/oculus/comments/4f3vi2/new_bugfix_release_of_gz3doom_for_cv1/d26gpfe
I'm running an AMD R9 390 on the latest drivers (16.5.3), an Oculus Rift CV1, and this release of GZ3DOOM: https://github.com/cmbruns/gz3doom/releases/tag/GZ3Doom1.8.10_e
The text was updated successfully, but these errors were encountered: