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
For some reason, LOAD81 doesn't perform very well on the Open Pandora console - its useable, but seems to be very laggy. Normally such an SDL program on OpenPandora/Angstrom performs very, very well, but with LOAD81 there appears to be some performance issue in the inner loop of the app which results in lag. It is very noticeable with the "text.lua" demo, where the text lags behind the mouse cursors as it moves, by a few milliseconds.
It may be related to a build issue (I have built LOAD81 using the CDEV tools, which is an onboard toolchain which runs on the Pandora itself, -i.e. not cross-compiling, but native compiling on the Pandora hardware itself), or it could have something to do with the overall architecture of LOAD81 itself - is the Lua VM somehow being polled too often, or some other unnecessary code-branch being taken during execution of the Lua script, perhaps?
The text was updated successfully, but these errors were encountered:
rlane
added a commit
to rlane/load81
that referenced
this issue
Mar 8, 2012
For some reason, LOAD81 doesn't perform very well on the Open Pandora console - its useable, but seems to be very laggy. Normally such an SDL program on OpenPandora/Angstrom performs very, very well, but with LOAD81 there appears to be some performance issue in the inner loop of the app which results in lag. It is very noticeable with the "text.lua" demo, where the text lags behind the mouse cursors as it moves, by a few milliseconds.
It may be related to a build issue (I have built LOAD81 using the CDEV tools, which is an onboard toolchain which runs on the Pandora itself, -i.e. not cross-compiling, but native compiling on the Pandora hardware itself), or it could have something to do with the overall architecture of LOAD81 itself - is the Lua VM somehow being polled too often, or some other unnecessary code-branch being taken during execution of the Lua script, perhaps?
The text was updated successfully, but these errors were encountered: