I need to update the example. printer was used in previous SDK but now you have to import CoreLibs/object instead.
Also the example by default will cache the result of the import. It supposed to show how to use it but I think that might be confusing so I will also disable it by default.
You can comment out these lines in main.lua
if playdate.isSimulator then
LDtk.export_to_lua()
end
I will try to fix these issues in the future and to put everything on GitHub. I'll update the thread when this
K so as you can see CoreLibs/object was already included underneath. So I'm just gonna remove the line.
As for the playdate.isSimulator code above, commenting it out wasn't enough. I also had to move the LDtk_lua_levels folder out of the Source folder which seemed a bit weird to me for people not used to the project.
So I made a small code change for you which just adds a variable to live.lua called use_fast_loader
because apparently you already had the option to give the fastloader as second var
Doing this (LDtk.load( "levels/world.ldtk" , live.use_fast_loader)) then made the fastloading easily changeable + defaulted it to being off.
Here's to updated project to save you some time. Don't worry. Nothing else is changed.
@Nic I'm working on creating a Lua project framework/development stack to make it easier for Pulp users to jump to Lua, and your project example is was a perfect base for it. I've already got a great POC right now so asking for your permission if I can continue working on that
Yeah sure no problem. Take anything you want, no credit required (except
for the tiles that was created by Adam Saltsman Monochrome Caves by Adam Saltsman)
Thank you so much for this! Going to be a huge, huge help for me while building my game.
I did run into one issue when trying to use this library; I'm relatively new to Lua and LDtk so not sure if this is my own fault or what, but "out of the box" I was seeing this error:
LDtk.lua:337: bad argument #1 to 'floor' (number expected, got nil)
It looks like line 337 is attempting to floor the value of tiles_list[id], but the id value itself appears to be a float. If I add a print(id) after line 315, I'm seeing values like 195.0, 200.0, etc. Perhaps the floor should be done to the id itself, and not the value returned by the table? Refactoring to this resolves the error:
table.insert(layer.tiles, tiles_list[math.floor(id)] or 1)
But, again, been programming for a while but definitely new to Lua, LDtk, and this library, so forgive me if I'm approaching this incorrectly!
You were on the right track. The fix is a bit different and set the tileID to 0 because we cannot assume the first tile in the tileset is empty.
The issue if caused by some tiles that are not set in your tilemap. With the fix, it should work and display the tilemap properly, however you might have a problem if you create collision with your tilemap because all the tiles are are not set will be solid with the current SDK
Awesome work Nic! Thanks for the great library. The project I talked about earlier has now launched and is called Cotton.
I did a couple of improvements to your library to make it even more awesome. If you want I can offer pull request for them. Again thanks for all the help!
Why is there a guard against having imagetable tilesets in other folders? I tried to run it without that check and it worked fine on simulator but then crashed on device because the imagetable came back nil. Not hard to work around but I cant find any information on why that would be happening and I'm really curious if you know.
That's a good question and I couldn't remember why I've put this path check in the first place.
In short, LDtk is saving the image path relative to the ldtk file. So when you load an image in a different folder the path of the image looks like that "your_ldtk_folder/../your_image_folder/image".
Windows, MacOS or Linux can resolve this type of path but no the playdate system (I guess because this is an embedded system).
Is there no way to re-interpret the file path?
So that when it loads the imagetable source property it will re-write that property to what's needed on the PlayDate instead.
So in principle I don't like to do stuff that should be handheld by the OS especially things related to file path because this is often more complicated that it seems. You might write something that work in most case but there is always a weird edge case that create an issue. And if a future version of the OS fix the issue, it can be overlooked and you still have some glue code on your library.
But I can see that the limitation can be a pain so I added some glue code to go around the problem.
The latest version on GitHub should support loading tilesets in any folder of your project.
Some people in the community were asking me questions about how we use LDtk with our game Comet.
When I got into LDtk there weren't many youtube videos that actually showed people using the tool.
Just general hey look at this thing. Let me read the website and play with it for a few min.
So I decided to make a video.
My not so secret plan is to make it the defacto level editor for Playdate devs so I encourage you to check it out.
First off Thank you so much for this. It has helped me so much on my journey to creating my own game.
Question for anyone with more knowledge then me. Is it possible to import or extract a background If I want to try and do some parallax effects? Right now I'm achieving that by creating and drawing a background sprite the size of the level I made in LDtk, but I would love to be able to do both right in LDtk. Any idea?
