0 Members and 3 Guests are viewing this topic.
Quote from: Sorunome on May 08, 2014, 01:57:00 pmThat is a known bug, due to abusing L2 as a whole buffer, and there is no way around fixing that except getting rid of double-buffering and thus have it flicker all over the place or by using up 768 more bytes of user ram which is IMO not worth it.Try using ClrDraw(L2+103) before exiting.
That is a known bug, due to abusing L2 as a whole buffer, and there is no way around fixing that except getting rid of double-buffering and thus have it flicker all over the place or by using up 768 more bytes of user ram which is IMO not worth it.
Quote from: Runer112 on May 08, 2014, 05:11:55 pmQuote from: Sorunome on May 08, 2014, 01:57:00 pmThat is a known bug, due to abusing L2 as a whole buffer, and there is no way around fixing that except getting rid of double-buffering and thus have it flicker all over the place or by using up 768 more bytes of user ram which is IMO not worth it.Try using ClrDraw(L2+103) before exiting.still giving that bug >.<