-
Notifications
You must be signed in to change notification settings - Fork 0
Crashes in glcSaveGLState #3818
Comments
|
raycast uploaded file |
|
vexed commented This patch should be sent upstream to the quesoGLC people on sourceforge. What video card & OS do you have anyway, drivers seems to be reporting the vertex arrays incorrectly ? is good enough. |
|
vexed changed blocking which not transferred by tractive |
|
vexed changed blockedby which not transferred by tractive |
|
raycast commented I belive not trusting I'm on Linux and intel. It worked a few weeks before, but apparently some recent mesa/SDL/intel-driver/something update or git-pull changed this. I don't think my graphics driver is reporting the vertex array incorrectly. I belive just the return value is undefined when a disabled feature is retrieved. Of course, retrieving a feature that was disabled doesn't make much sense anyway. |
|
Cyp commented #3822 probably duplicate of this. |
|
Cyp commented Sent upstream — http://quesoglc.git.sourceforge.net/git/gitweb.cgi?p=quesoglc/quesoglc;a=commit;h=e2f382d The 0.7 release branch wasn't patched, but doesn't seem to be any corresponding code to patch, anyway. |
|
cybersphinx changed status from |
|
cybersphinx changed resolution from `` to |
|
cybersphinx commented Applied in 78a13deb19537497f15fc118ca5f501389a3e90b. |
|
Per commented This patch creates new problems. See #3834 |
resolution_fixedtype_bug| by raycastFreshly compiled WZ master would crash for me, until I applied attached patch.
The crash happens in
glGetPointerv, so I wrapped it in a check whether it actually is needed. Now warzone starts, I havn't tested much more.Issue migrated from trac:3818 at 2022-04-16 10:44:20 -0700
The text was updated successfully, but these errors were encountered: