-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create initial port prototype for Nintendo 3DS using LÖVE Potion #51
Comments
Very primitive support is implemented on 51-3ds_support branch. This is not officially supported. If basic stuff is resolved and functionality of the 3DS port is the same as on the Some stuff still can be made more portable between these versions however, need to investigate on that though. |
Some of the stuff for reworking controls is done on f0951ef. Level editor have been disabled for now, will work on this either tomorrow or some other day. Also I need to update controls section in README. |
Last bits of level editor controls were implemented in 62938f7. I didn't implement some minor stuff though that's not really needed for anything on 3DS. I will make a Wiki article about this later though. |
I have no idea how do I optimize font drawing, it seems to drop to 9 FPS when doing anything with text, regardless how much is loaded. |
Since I got a New Nintendo 3DS XL, this could be a fun exercise.
Also see #93 for 3DS "fun exclusive features".
Ideas for optimization and small improvements for the prototype:
README.md
with current controls (see aaa5e4f and 6f77d2b).love.graphics.getStats()
to print stats on screen and investigate bottlenecks (implemented in e9fd008, but note that this function doesn't exist in LÖVE Potion, so it was disabled for this port).love.graphics.present()
for that?).drawTexture()
?). Maybe draw tiles to the background using canvas? Could do segments that appear when character is moving through them.Temporarily (or not) add controls instructions on the bottom screen (maybe add them later to a submenu that opens by touching some button). This can be accomplished by writing a function that prints the table on some coords (I really think that's bad idea (this will just crash the console when we approach the sprite limit) unless we use system font. I think having instructions graphics is a better approach (see #93) though. And this can be used on PCs (or more correctly: all compatible devices with keyboards attached) as well. MAYBE JUST USE CANVAS?printInstructions(text, x, y, width, height, line_spacing)
)The text was updated successfully, but these errors were encountered: