Vivecraft / VivecraftMod

An experimental port of Vivecraft to Forge/Fabric
Other
174 stars 47 forks source link

Gui is completely black #120

Closed Helinos closed 1 year ago

Helinos commented 1 year ago

Exactly what it says on the tin. Using Fabric 0.14.14 with a Quest 2 through ALVR on Linux. Vivecraft is the only mod loaded.

alvr client quest-20230226-043258 alvr client quest-20230226-043236

fayer3 commented 1 year ago

log please

Helinos commented 1 year ago

https://mclo.gs/GzvMZ8m

fayer3 commented 1 year ago

can you check without the resourcepack

Helinos commented 1 year ago

It was happening before I applied the resource pack, but I double checked anyways.

https://mclo.gs/0Anm4qZ

2023-02-26_07-35

fayer3 commented 1 year ago

weird, I can't reproduce it, does it happen at other locations as well?

Helinos commented 1 year ago

What do you mean by other locations?

fayer3 commented 1 year ago

not at this patch of dirtpath move around a bit, and check if it goes away try going to a torch or something

Helinos commented 1 year ago

As far as I could tell moving around (Visiting 1000, 1000, flying around the world origin) didn't change anything, nor did going near a torch

rwinkhart commented 1 year ago

Same exact issue with OG Vive+Artix Linux. No other mods loaded, happens with both Forge and Fabric.

The old Optifine version of Vivecraft is fine, this only occurs on the new versions without an Optifine dependency.

rwinkhart commented 1 year ago

Issue is only present in v0.14+. All versions below v0.14 are fine.

The changelog for v0.14 contains the following:

thejudge156 commented 1 year ago

This happens on QCXR as well, I am trying to bump the version but this is preventing progress.

thejudge156 commented 1 year ago

I can rule out the bedrockify commit however, reverting that did not fix it on my end.

thejudge156 commented 1 year ago

Also, what might be worth noting is that the main menu is fine. This only occurs ingame.

rwinkhart commented 1 year ago

Commit acb23328841aecbb7c1e46e955eb21adfcaffe50 is at fault. I reverted this commit and re-built. Everything is now displaying properly.