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
The default buffer size for gfx2.fill() is 64 entries which is far too small to reliably fill all polygons, especially in high res screen modes.
Fix this maybe by using the stack/queue code in #145
Don't forget monogfx.fill() as well.
Another optimization that could be made is to remove the separate calls to horizontal_line, and instead immediately pset() the pixels after the pget()'s. Might even optimize that by using both vera data ports 1 for reading 1 for writing, with appropriate auto increment/decrement.
see discord DM from leroy for code
The text was updated successfully, but these errors were encountered:
irmen
changed the title
change fill() routines to use a much larger buffer so that they don't abort halfway
improve fill() routines
Jun 26, 2024
optimized monogfx a bit, but there's room for future improvements if someone wants to implement masking and vera auto increment/decrement support when drawing the spans. It wil make the span code quite a bit more involved though. So I'm leaving it for now.
The default buffer size for gfx2.fill() is 64 entries which is far too small to reliably fill all polygons, especially in high res screen modes.
Fix this maybe by using the stack/queue code in #145
Don't forget monogfx.fill() as well.
Another optimization that could be made is to remove the separate calls to horizontal_line, and instead immediately pset() the pixels after the pget()'s. Might even optimize that by using both vera data ports 1 for reading 1 for writing, with appropriate auto increment/decrement.
see discord DM from leroy for code
The text was updated successfully, but these errors were encountered: