Very laggy

[klaszlo8207]

The viewer is very slow on a HIGH end machine

[klaszlo8207]

it is only laggy when you need to draw a lot of points

[hemanthrajv]

Yeah, it is because it's take lots of time time computing. Lots of points put more work on the CPU.

…

On Tue, Jan 7, 2020 at 1:47 PM KL ***@***.***> wrote: it is only laggy when you need to draw a lot of points — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#13?email_source=notifications&email_token=AE32SHJ55OS5KSTY6BXO3BDQ4Q3BTA5CNFSM4KCMZMFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIICI3A#issuecomment-571483244>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE32SHJD4QREX3KBHSIYSBLQ4Q3BTANCNFSM4KCMZMFA> .

[jpnurmi]

• consider parsing .obj once after reading, not in paint() after every rotation etc.
• and batching huge amounts of Canvas.drawPath() calls with help of Canvas.drawVertices()

[nabil-ha]

* consider parsing .obj once after reading, not in paint() after every rotation etc.

* and batching huge amounts of Canvas.drawPath() calls with help of Canvas.drawVertices()

How to do that? can you explain?

[youssefali424]

what he means fork the package change the part starting line 307, in paint function he is reading the file imagine that when you change the rotation he reads the whole file again that's too much I will try the edits locally if it worked I will refer to the forked git here or perhaps a pr