You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a bug in code everyone else writes- but Im going to point it out.
You over render.
Your loops- designed for one frame of graphics output- are rendering multiple frames in rapidfire mode- cockblocking input in the process..so bad- it can crash X11 entirely.
Blaming the vendor- and claiming they should fix "your bad code"(which should use timer callbacks) is BAD PRACTICE. They are not going to know what to render or not- at what speed--thats for YOU. Ive heard the blame being passed to ATI before. WRONG.
WRITE BETTER CODE.
The text was updated successfully, but these errors were encountered:
This is a bug in code everyone else writes- but Im going to point it out.
You over render.
Your loops- designed for one frame of graphics output- are rendering multiple frames in rapidfire mode- cockblocking input in the process..so bad- it can crash X11 entirely.
Blaming the vendor- and claiming they should fix "your bad code"(which should use timer callbacks) is BAD PRACTICE. They are not going to know what to render or not- at what speed--thats for YOU. Ive heard the blame being passed to ATI before. WRONG.
WRITE BETTER CODE.
The text was updated successfully, but these errors were encountered: