Log In  

found a bug in 0.2.1b (also current bbs version) while using tline() to shear rectangles

see the cart

observe that there's only 2 configurations that get chopped incorrectly (one where the startpoint is below the screen and one where the endpoint is above the screen) (although others also have ugly artifacts)

Cart #dimumayuyi-0 | 2020-09-26 | Code ▽ | Embed ▽ | No License

P#82316 2020-09-26 21:29 ( Edited 2020-09-26 21:35)


This happened to me too when I was using tline() too close to the edges if the screen, in (https://www.lexaloffle.com/bbs/?pid=80206#p) you can move the flag up/down and I noticed that when it touches or gets close to for the bottom it disapears ;\

I think that's related

P#82365 2020-09-27 05:32 ( Edited 2020-09-27 05:52)
:: Felice

(ignore me)

P#82367 2020-09-27 08:59 ( Edited 2020-09-27 13:39)
:: Felice

Okay, on top of the line culling bug, it's also actually failing to clip to the correct pixel on all four edges, leaving 1-pixel gaps.

I took a cue from @db0z's repro and made a new one that shows the 1-pixel wide glitches on all four edges, which happen with both line() and tline(), along with the original line-culling bugs that happen on top and bottom edges.

Adjust the speed with ▲/▼, ❎ to pause, and 🅾️ to toggle tline() vs. line().

Note: The additional 1-pixel-wide bug is easier to see in line() mode.

Cart #fatufabuza-0 | 2020-09-27 | Code ▽ | Embed ▽ | No License

P#82374 2020-09-27 13:37 ( Edited 2020-09-27 13:42)
:: db0z

@Felice Oh that's a much better way to show it, making the squares spin was too artsy haha

P#82375 2020-09-27 13:45
:: zep

Fixed for 0.2.2 -- thanks for the nice test carts @db0z, @Felice

A souvenir from testing:

P#84023 2020-11-09 07:47

[Please log in to post a comment]

Follow Lexaloffle:        
Generated 2021-09-22 07:53:35 | 0.043s | Q:26