Dynmap-Forge/Fabric

Dynmap-Forge/Fabric

Mods
888k Downloads

[Dynmap] Error while raytracing tile - when used on Fabric together with Shearable Vines mod

Noshire opened this issue ยท 0 comments

commented

Issue Description: Ever since we installed the Shearable Vines mod, the console gets flooded with exceptions and all vines are rendered black, both in overhead and isometric view.

The error:

[14:25:57] [Dynmap Render Thread/FATAL]: [Dynmap] Error while raytracing tile: perspective=iso_SE_60_lowres, coord=-4173,55,-2068, blockid=minecraft:vine[west=false,sheared=false,north=false,up=true,east=false,south=true], lighting=0:6, biome=PLAINS(minecraft:plains)
java.lang.ArrayIndexOutOfBoundsException: Index 57 out of bounds for length 32
        at org.dynmap.hdmap.renderer.VineStateRenderer.getRenderPatchList(VineStateRenderer.java:53) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.hdmap.CustomBlockModel.getMeshForBlock(CustomBlockModel.java:53) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.hdmap.IsoHDPerspective$OurPerspectiveState.getPatches(IsoHDPerspective.java:577) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.hdmap.IsoHDPerspective$OurPerspectiveState.visit_block(IsoHDPerspective.java:605) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.hdmap.IsoHDPerspective$OurPerspectiveState.raytrace(IsoHDPerspective.java:726) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.hdmap.IsoHDPerspective$OurPerspectiveState.access$400(IsoHDPerspective.java:81) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.hdmap.IsoHDPerspective.render(IsoHDPerspective.java:1312) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.hdmap.HDMapTile.render(HDMapTile.java:91) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.MapManager$FullWorldRenderState.processTile(MapManager.java:797) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.MapManager$FullWorldRenderState.run(MapManager.java:728) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.MapManager$DynmapScheduledThreadPoolExecutor$1.run(MapManager.java:234) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at org.dynmap.MapManager$DynmapScheduledThreadPoolExecutor$2.run(MapManager.java:252) ~[Dynmap-3.7-beta-6-fabric-1.21.jar:?]
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572) ~[?:?]
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) ~[?:?]
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        at java.base/java.lang.Thread.run(Thread.java:1583) [?:?]

Render screenshots:
image
image

I'm aware that this is probably an issue with the plugin adding a property to the block data (sheared=false), and dynmap probably not being set up to parse this. I was just wondering if there's any way to get dynmap to work with any mods that add custom data.

  • Dynmap Version: Dynmap-3.7-beta-6-fabric-1.21
  • Server Version: fabric-server-mc.1.21-loader.0.16.0-launcher.1.0.1
  • Pastebin of Configuration.txt: https://pastebin.com/PzXRtVNW
  • Server Host (if applicable): Selfhosted (Ubuntu Noble)

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