Dynmap-Forge/Fabric

Dynmap-Forge/Fabric

888k Downloads

Wood logs rendered incorrectly with texturepack

velnias75 opened this issue ยท 16 comments

commented

Issue Description: Wood logs are rendered incorrectly with texture pack. The upside of the log is rendered, instead of the side
The texturepack uses CTM and works perfekt ingame.

[x] I have looked at all other issues and this is not a duplicate
[x] I have been able to replicate this

Screenshot_20220228_055924

commented

Dumb question - are you using a texture pack? There are a bunch of blocks I don't quite recognize

commented

Dumb question - are you using a texture pack? There are a bunch of blocks I don't quite recognize

Yes, I've linked it in the section Other Relevant Data/Screenshots

commented

it could be the resource pack, as the default dynmap renders them correctly: https://dynmap-setup.jurgenmk.nl/?worldname=world_res&mapname=surfacesvh2&zoom=4&x=122&y=64&z=-111

commented

Do they also render properly if they are connected, not single?

commented

So I need to check the texture pack.
The pack uses CTM a lot so please don't close this bug too early, since in the running game there are no problems.

commented

only CTM V1.1 is supported, the ctm_compact type is not supported, maybe that is what is clashing with it?

commented

yup - happy to keep open for a bit. unfortunately dynmap isn't coded with optifine (which is closed source)

hopefully, its just the one type of log affected, and so possibly an easy fix?

commented

I've checked the texturepack for errors, but couldn't find any, but it seems that all types of log are affected.
I've attached the *.properties-files of spruce and jungle logs as example.

jungle_log_top.properties.txt
jungle_log.properties.txt
spruce_log_top.properties.txt
spruce_log.properties.txt
.

commented

dynmap seems to support almost all other optifine features and how should I disable the Optifine part?

commented

Its not errors, but what the base block looks like. Try the resource pack without Optifine - it might be similar.

Unfortuantely, dynmap doesn't support Optifine texture packs

commented

I was suggesting to try in your MC client to view the texturepack without optifine mod... just incase it presented the same log texturing. Its a good base comparison if nothing else, and could only take a minute to try?

Im not sure what optifine features you mean - CTM1 is supported, as are normal texture packs. No other Optifine features are present afaik?

commented

Currently I'm the maintainer of the texture pack, so I know how it looks like without Optifine ๐Ÿ˜ธ

At least the logs are not using any sophisticated CTM features as you can see in the attached files.
Overlays aren't working and I removed them in the TP for dynmap to avoid log spam.

commented

Ah cool ๐Ÿ˜ I hoping there might have been some insight that we could have gotten from in, but if its different I suppose its just acting borked.

Unfortunately I can only suggest maybe some tips or workarounds in simplifying the resource pack so it looks better.

Like, I see that there are opensource CTM mods out there but I have no idea how quickly those standards change - it would be awesome if we had someone who could provide the CTM algorythms but currently most people don't use texturepacks let alone CTM specific ones and tends to generate more issues than creating awesome dynmap imagery.

I'd love to provide a CTM texturepack to bundle with dynmap ๐Ÿ˜† just the simplier random rotations and variations stuff, but it really needs the support behind it

sorry - ramble off

commented

Before I forget again - if you have the pack set up to work 'without optifine', there is an option in dynmap to turn CTM off. That might be another good workingaround so things dont look weird while things are being looked into

commented

closing this issue because we couldn't reproduce from our end.