Asek3 / Rubidium

Rubidium is an Unofficial Fork of CaffeineMC's "Sodium", made to work with Forge Mod Loader.
GNU Lesser General Public License v3.0
118 stars 57 forks source link

CTM broken with rubidium #510

Closed phoennixxempire closed 1 year ago

phoennixxempire commented 1 year ago

I think this is a known issue, but it would be helpful because wonderful building mods like Chipped 2 cannot run without CTM, and I cannot handle the FPS drops incurred by doing the fix in the mixin properties.

katubug commented 1 year ago

https://github.com/Asek3/Rubidium/issues/69 https://github.com/Chisel-Team/ConnectedTexturesMod/issues/168

Some related issues. I came here as well, hoping for a response to this apparently long-lived issue. I would like to include Chipped in my Cottage Witch Recast modpack, but I am unwilling to remove Rubidium and Oculus because they are just too good. I am not looking forward to getting a ton of reports of incorrect textures, haha. So any help would be appreciated!

For me this is occurring on - Minecraft 1.19.2 Forge 43.2.11 Rubidium 0.6.2b CTM 1.1.6+8

Thanks for your time!

villainous-j commented 1 year ago

would be awesome to see this fixed!

loldev69 commented 1 year ago

160 appears to have fixed the issue, as far as I could test, but the relevant commit hasn't been included in any update yet except for the 1.16 one (Rubidium mc1.16.5-0.2.13).

You can still grab the autogenerated builds from the Actions, I used https://github.com/Asek3/Rubidium/actions/runs/6130488996 for testing: and yes, it's named 0.5.6 like the 0.5.6 release but it's not the same file, it's a bit confusing.

Asek3 commented 1 year ago

1.16.5 and 1.19.2 versions was fixed

LandofHeros2234 commented 1 year ago

Still affects 1.18.2

GordonRamsay20 commented 1 year ago

When will this issue be fixed on 1.18.2?

loldev69 commented 12 months ago

@LandofHeros2234 @GordonRamsay20 the fix is in the dev builds together with many others, but for some reason there hasn't been a new release for 1.18 since April 17 aka this commit. @Asek3 maybe there's some CI/CD pipeline issue?