#vanilla textures are invisible in lonn
69 messages · Page 1 of 1 (latest)
<@&683773388321456184>
its thaaaaat thing 
Try opening the config folder in Lönn, close Lönn, go up a folder and rename the Loenn folder to something else, open Lönn again
sorry but what is the path to the config folder?
i mean where do you open it in lonn
oh nvm its prob this
now it just opens the vanilla summit, still no textures tho
In the config directory there should be a folder with images, what do those look like?
if you're talking abt this folder then here it is
any ideas on why this is happening?
are you running olympus/lönn as admin? 🤔
Im pretty sure im not
wait, i ran lonn.exe as admin and now it works wtf
i guess this is resolved now??? thanks cruor
this is weird. i closed lonn and opened it about 2 hours later and now the textures are gone 
wow i restarted my device and the textures are back, feels like im going insane
funky
could be a case of the folder requiring admin permissions? thats so bizarre
that would only be the case if the first start of lönn was done with admin
the solution would be to delete the lönn config directory and then start lönn without admin
idk because ive seen cases where for whatever reason everest refused to start up because the entire %tmp% folder was locked behind admin
even without running everest as admin
that log is really helpful, thanks 
not sure how you figured out to enable the brand new helpful feature, but bless 
i have a potential fix for this, anyone available to test a dev build in like 20-30min? 🤔
@royal halo if you could try with this version and give me the output log with that debug option still enabled, that would be great 
tell me if you need not windows build :p
can you also try deleting the cache folder in the lönn config folder and then make sure you are not runing either Olympus (if you use that to launch Lönn normaly) or Lönn with admin?
if it still doesnt work after that, go into the cache folder and do this on Gameplay.png: properties -> details -> scroll to bottom
see if Owner/Computer is set to someone else than your user 😓
i have one more thing i want tested on the latest release though (not this test build), but thats a bit... involved :p
Make sure terminal and debug menu is enabled in settings, restart Lönn if you have to enable them
Hit debug -> debug mode, Lönn will freeze
In the terminal input this:
require("runtime_atlas").dumpCanvasImages()
Wait until lua_debug> is back on the second line, the code takes a bit of time
Go to %appdata%/LOVE/src in the file explorer
i mostly just want to see if the celeste atlases end up here or not 😓
The terminal returned this right away: [string "runtime_atlas.lua"]:221: attempt to index field 'canvasArray' (a nil value)
the one time you want to use cursed debug features they assume things exist 
oh that code doesnt support what i wanted you to test anyway...
same cursed debug steps, this is as monkey patched as it gets 
Here's what that folder looks like:
did you execute the debug command again?
yeah
well these are certainly not supposed to be empty images :)
actually are they black with no alpha channel 
no, they're just empty
windows is weird and shows transparent images sometimes as black
can you send image 2, just in case
thanks, thats pretty empty 🤔
awesome
if you copy it :p
celeste: blindfolded edition
the first image being empty is more weird to me
can you check the permissions on the images in the cache folder? 
id be more concerned of the atlas permissions? since if you can create the image you can write to it
unless i am missing something here
i honestly dont know, i have two theories, either they are "added" to the atlas with a bad color set or there is a permission issue
this forces changes the color before adding the image, it shouldnt make a difference but id rather just test it just in case
Nothing changed
updated lonn to 0.9.0 and still facing this issue rip
here's the log in case theres anything different
what are the permissions on the cached gameplay atlases?
wdym
this
oh the owner is set to the user im currently using
will backread and try to apply other fixes
what happens when i run the command:
tried the second build and this same thing happens
same with the third build
at least that confirms it's the exact same issue