Closed dobodu closed 4 months ago
Hi,
I just implemented the fill_color_buffer_slow()
correctly. (at least to be my believes). This uses at max 536 x 8 x 2
bytes for buffering. fill_rect()
and fill()
can now be used like usual.
Your program runs perfectly on my device. The v1 one. So.. I hope the update could fixe your issue, otherwise it also might just be hardware related.
Best Regards.
And I've also tried the solution you provide... Guess what: It works !
We made a serious progress !
Moreover, if I check the frame per second, I reaches now the same results as on a Pico. It went from 8/9 FPS to 13/14 FPS. That's not why we expected...
It went from 8/9 FPS to 13/14 FPS. That's not why we expected...
:O wow, that s actually not what I was expecting! nice!
Also, am going to close this issue, but you can still comment on this!
Well, I pulled the latest code in order to be shure I got the latest code. It still works ! But FPS has gone down to 7 FPS ! Nevermind, I now have both lilygo / pico working on the same code !
I've rarely seen someone giving such time for supporting a maker ! Thank you so much !
Ugh... Which bug? Haven't we already got it fixed?
Sorry I was not readable in the last post : I updraded ESP32 IDF chaintool to 5.2.2 to see if there was differences : The use_frame_buffer=False bugfix initialisation method works fine (and provides 14.5 FPS to my program) The use_frame_buffer=True initialisation method still have the bug (and provides 17.5 FPS to my program) Thus, 5.2.2 IDF doesn't change anything.
It's alright! I was just a little bit confused. And thank you for reaching out!
I think backgound color for the write function does not work
Here is the code I wrote to illustrate, coming for the hello.py example.
Can you try and confirm, I send below an appropriate variable bitmap font I used.
large.zip