Traincraft

Traincraft

1M Downloads

1.7.10 Textures From The Rails Bugged

TheKatherineManaiac opened this issue ยท 7 comments

commented

2019-10-05_15 13 45

commented

Just to be sure, which version was this on?
Looking at the image the geometry is right, and the texture is horribly wrong, not just positioned wrong but never bound in the first place, which would mean displaylist interference from something like optifine

commented

Got the similar issue with rail and vanilla chest only. Nothing on another mod is affected
The chest has gravel texture ? And rails takes particle texture, I really don't know why
2022-07-22_21 00 21
2022-07-22_21 05 10
Edit: Only railroad crossing haven't this bug

commented

Just to be sure, which version was this on? Looking at the image the geometry is right, and the texture is horribly wrong, not just positioned wrong but never bound in the first place, which would mean displaylist interference from something like optifine

My mods:
image
Got this on 4.4.1_021
I'm not sure this is the last version
But this bug is random, I restarted the game, rails became normal but a freight became pink and black (missing texture)
I can't really explain precisely, this bug is strange and occurs randomly

commented

4.4.1_021 is very outdated, the latest is currently TCCE 5, it's currently available on curseforge. I think the texture binding has been changed since, so maybe it's fixed...?

commented

image
got the problem with the bridge pillar and the high star switch stand and also signs.
image

commented

I have the same issue. It seems every time I start up Minecraft TrainCraft randomly picks a texture from any mod and swaps. Once I saw rail slopes rendering a texture from an Armourer's Workshop block while the said block was rendering the rail texture. My guess is there's a miscount of the slots in the texture atlas.

commented

the issue for textures is related to how the textures are cached.
an attempted optimization for block geometry in 021 accidentally cached textures in the model vector array, which naturally, makes textures not show outside the frame that the cache is created.

a fix has already been made, however we're waiting on an unrelated fix from one of our contributors, before we push out the new version.