Missing Water and Lava models/textures #7
Comments
|
That's strange. I had this issue with v0.10.35, and after I updated it to v0.10.36, the issue went away on my test machines. I'm assuming that this is a clean install? You didn't previously have an older version installed? |
|
A previous version of this flatpak? No, this is the first time ive installed it. |
|
OK. Looks like I have more testing to do. |
|
I don't understand it. On my initial test machine, it worked fine after Amulet was updated to 0.10.36, but on every build since, this error keeps popping up and Amulet's log files aren't really providing any insight. Perhaps once Amulet is moved fully over to QT, things will be different? In the meantime, I've been playing around with debug builds and tweaking the Minecraft Model Reader, trying to get to the bottom of this. The .PNG and .JSON files are present in their expected locations, so I don't know why it's throwing this error - yet. |
|
I've filed a report with Upstream Amulet, and I've given them the detailed log. My skills in Python are poor, so I don't know how to fix it outright, but if they can point me in the right direction, I can figure out a fix. |
|
sounds good. |
|
I pulled this from Amulet's log file. It seems like the issue is either something not matching properly between the .JSON files and the .PNGs, or something is read-only that Amulet expects to be writable. I'm still working on it. |
|
With the upstream update to v0.10.37, I thought I would copy the water and lava textures to the cache with the rest of the textures to see if that could be used as a work-around, but the textures are still missing and I still get the key errors in the terminal. Over the next little while, I'm going to experiment with path modding in the textures module and see if I can come up with something. That being said, this is a side project I'm working on, so I don't have a definitive timetable. |
|
I believe with the changes I've made to the Minecraft Model Reader, the missing textures issue is finally resolved. New .flatpak will be uploaded after verification. |
|
I think I need to make a minor change to my brute-force fix. Rather than defaulting non-transparent, I'll see what happens if I default to transparent instead. While the water blocks are indeed rendered, you can't see through them properly. Flatpak Amulet on EndeavourOS, running under Wayland: Flatpak Amulet on Linux Mint, running under X: |
|
I have inadvertently solved my problem by creating a venv (quite literally) at When running from PIP, Amulet is installed to When Amulet is installed inside the Flatpak, the location is changed to I guess not all the paths are relative after all. I feel like an idiot now because it was so obvious. It was right there in every error message, every time. I'm just not sure where this is defined. I'm exploring two options now. One is a way to override the sandbox location from |
|
I modified This is not a permanent fix, as I still don't understand why the paths are being configured like this, but for now, it does resolve the missing textures the Flatpak release was experiencing much better than my last fix, as the textures are actually properly transparent now. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When i load the 3D Editor everything works fine but the water and lava show up as missing textures.
Running on latest release: v0.10.36 - The Flathub Friendly Release (kinda).
System info from
neofetch:Error messages related to issue:
World is in 1.21 full release.
Related past issue: #5
The text was updated successfully, but these errors were encountered: