Open mittorn opened 6 years ago
With -gldebug it seems to be not reproducible.
Although, I reproduced it even on latest NVidia drivers.
Workaround is very slow, as wants memory bandwidth.
So I decided to disable VBO renderer for NVIDIA on Windows.
Actually i get this bug on an AMD R9 390 so it seems not specific to nvidia.
Can you run with -gldebug option?
check r_vbo_dlightmode Maybe it fix rendering
r_vbo_dlightmode fixed issue on nvidia, it will be enabled for desktop platforms by default
@revelator, check last test build on AMD with r_vbo 1 and r_vbo_dlightmode 1
Sorry been away for some time, nothing immediatly shows up with gldebug but turning vbo off fixes the bug. Last test build seems to work ok also but i havent yet had an extensive runthrough.
Does last version work with both r_vbo and r_vbo_dlightmode enabled? second should fix issue that caused r_vbo to glitch and improve performance
seems to do so far, havent had time for a longer run yet though. question btw. does half-life even use R_DrawWaterSurfaces ? or is this part for quake only. Asking because i was adding glsl based code for water warp and other effects, but the effect newer shows up in game.
It is back. Latest pull from here breaks flashlights in half-life and ir googles in opposing force with vbo's on. r_vbo_dlightmode 1 or 0 does no difference.
Try enable -gldebug command-line option
Hmm not getting any log with that option, do i need -condebug also ?.
-console -dev 5
hmm not getting any problems with debug enabled ... Hard to hunt this one down it seems allthough it partly seems to be caused by the latest AMD driver for my card, previous driver works fine so urgh.
Some users reports bad behaviour: broken lightmaps, disappearing surfaces when using flashlights. Please attach log with -gldebug if you get something wrong in latest test versions