Closed Cammin closed 4 years ago
After some more testing, I have been able to fix it by moving the project file back to a former path that it was in, where it attempts to go through the symbolic link's path instead of the referenced path that includes a tilde. I'm thinking the tilde key is the main reason to be causing it. Maybe there could be a way of retaining the tilde in a path for the LDtk editor?
Hmmmm... That's definitely a very plausible problem. I don't think the dn.FilePath
lib I made doesn't support ~
. Could you please provide me the faulty path value so I can add support for that before 0.6 release? 🤔
My symbolic link is named Samples
which points to the folder of Samples~
, which is likely why it was able to work previously for me because I went down the symbolic link path instead of the real path which contains the tilde. So, I can fix it if I pick the symbolic link's path. 👍
Here's the path value; When the file search goes up one level, it runs into the Samples~
folder:
"relPath": "../Sprites/SunnyLand_by_Ansimuz.png"
I'm not sure to fully understand your file hierarchy here 🤔 Couldn't screen me the tree where the LDtk files & images are stored?
Here's the folder tree; the LDtk project is stored in the Data
folder, and the images are stored in the Sprites
folder.
I've to go to bed, but I hope I could help out 🙂
Thanks I'll check that today :) Have a good night
This should be fixed by latest git version of my deepnightLibs
(if you build LDtk yourself), or will be in 0.6 update today.
haxelib update
I noticed an issue where tileset images are unable to be loaded, even if I try re-referencing them. My suspicion is from the tilde key in the path text between LDtk and windows explorer: Is the path having its tilde key changed to an underscore? One more thing to note is that my Samples~ folder is referenced by a symbolic link higher up in the folder tree if that helps out.