| Summary: | Screen flickers on radeon 470RX 4 gig | ||
|---|---|---|---|
| Product: | SDL | Reporter: | Michael Staud <bsf.mistau> |
| Component: | video | Assignee: | Ryan C. Gordon <icculus> |
| Status: | RESOLVED ABANDONED | QA Contact: | Sam Lantinga <slouken> |
| Severity: | normal | ||
| Priority: | P2 | CC: | amaranth72 |
| Version: | 2.0.4 | ||
| Hardware: | x86_64 | ||
| OS: | Windows 10 | ||
|
Description
Michael Staud
2016-10-12 17:17:39 UTC
There are a lot of ways to cause undefined or otherwise undesirable behaviour when writing OpenGL code. I recommend using the OpenGL debug callback mechanisms[1] as well as running your game through an OpenGL debugger such as RenderDoc, AMD CodeXL, nvidia nsight, etc. [1]: https://www.opengl.org/wiki/Debug_Output Thanks for your answer. I only knew about the "old" OpenGL error report functions and with these everything was fine. I will check the new ones out. The player now tested the newest version of the game and described the error more clearly: "I didnt have screen flicker it starts in 800 x 600 and fills up only 60% of my screen. When i click anything. It flashes like its trying to adjust resolution with my 40" inch screen. Then its really offset and i have no mouse control to try again. I have to click windows to exit game. I noticed it was a little different this time but same results. It seemd to actually fill my screen a little better but did not fix problem." Starting in 800x600 in window mode is ok. The game is programmed to do this when it is first installed. Then he got the following error messages: OpenGL Renderer: Radeon (TM) RX 470 Graphics OpenGL Version: 4.5.14009 Compatibility Profile Context 21.19.151.3 OpenGL Shader: 4.50 [0x7FF824B67CC0] ANOMALY: meaningless REX prefix used [0x7FF82CDB4250] ANOMALY: meaningless REX prefix used [0x7FF82436CDB0] ANOMALY: meaningless REX prefix used [0x7FF824B6DF20] ANOMALY: meaningless REX prefix used [0x7FF824B6DF80] ANOMALY: meaningless REX prefix used [0x7FF824B6DFE0] ANOMALY: meaningless REX prefix used [0x7FF824378E10] ANOMALY: meaningless REX prefix used [0x7FF824378FD0] ANOMALY: meaningless REX prefix used [0x7FF824379120] ANOMALY: meaningless REX prefix used [0x7FF8243794E0] ANOMALY: meaningless REX prefix used [0x7FF824379520] ANOMALY: meaningless REX prefix used [0x7FF824379430] ANOMALY: meaningless REX prefix used That means that the machine code is corrupted. Never had this kind of error on any of my computers. Used the normal mingw compiler without assembler to create the executables (and I suppose you guys do the same). It only appeared after he upgraded the graphics card. Hello, and sorry if you're getting dozens of copies of this message by email. We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc. Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report. So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues. (please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!) Thanks, --ryan. |