1.0.2: Funky Locomotion Causes rendering block entity, illegal arguement, when entering a tunnel.

  • This section is closed. Please do bug reports over at the FTB GitHub repos.
  • FTB will be shutting down this forum by the end of July. To participate in our community discussions, please join our Discord! https://ftb.team/discord

Jakalth

New Member
Jul 29, 2019
83
0
0
Version:
1.0.2

What is the bug:
Funky Locomotion causes a rendering block entity crash(client side), and a Null Point exception crash(server side) when submitted to this specific event.

The crash happens when I try to lower the 6-axis mining bore I was testing far enough into the ground that the normal frames are in contact with the surface blocks. The bore it's self is a 9x9x16 tower, using a 4-axis frame slider core(Redpower style caterpillar drive) and a 2 axis frame pusher drive(first pusher pushes the frames, second pusher pushes the first pusher back into place), with an outer layer of normal frames that have their outside faces set to not interact. The caterpillar drives are controlled by vanilla buttons that feed their redstone signal to the frame movers using Ender IO covered redstone conduits. Below this tower is a layer of Extra Utilities Tranfer Pipes with hollow cover frames above and below, and a layer of "Open Block" Block breakers. The block breakers enter the ground with no issues and the hollow covers holding them and the transfer pipes also enter the ground with no issues. The first layer of Normal frames also enters the ground with no issues, but as soon as the bore is moved from this point, the frame sliders bug out and move the bore about 5 blocks instead of just 1 and the game crashes.

This crash ONLY happens when trying to plunge the frames through the ground. I have not had any issues using multiple axis caterpillar drives in the air.

Client log relevant info:

Description: Rendering Block Entity

java.lang.IllegalArgumentException
at java.util.PriorityQueue.<init>(Unknown Source)
at net.minecraft.client.renderer.Tessellator.func_147564_a(Tessellator.java:160)
at com.rwtema.funkylocomotion.rendering.TileEntityRenderMoving.leadVertexState(TileEntityRenderMoving.java:197)
at com.rwtema.funkylocomotion.rendering.TileEntityRenderMoving.renderStatic(TileEntityRenderMoving.java:186)
at com.rwtema.funkylocomotion.rendering.TileEntityRenderMoving.func_147500_a(TileEntityRenderMoving.java:55)
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_147549_a(SourceFile:100)
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_147544_a(SourceFile:92)
at net.minecraft.client.renderer.RenderGlobal.func_147589_a(RenderGlobal.java:483)
at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1224)
at net.minecraft.client.renderer.EntityRenderer.func_78480_b(EntityRenderer.java:1011)
at net.minecraft.client.Minecraft.func_71411_J(Minecraft.java:990)
at net.minecraft.client.Minecraft.func_99999_d(Minecraft.java:887)
at net.minecraft.client.main.Main.main(SourceFile:148)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at net.minecraft.launchwrapper.Launch.launch(Launch.java:135)
at net.minecraft.launchwrapper.Launch.main(Launch.java:28)


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
at java.util.PriorityQueue.<init>(Unknown Source)
at net.minecraft.client.renderer.Tessellator.func_147564_a(Tessellator.java:160)
at com.rwtema.funkylocomotion.rendering.TileEntityRenderMoving.leadVertexState(TileEntityRenderMoving.java:197)
at com.rwtema.funkylocomotion.rendering.TileEntityRenderMoving.renderStatic(TileEntityRenderMoving.java:186)
at com.rwtema.funkylocomotion.rendering.TileEntityRenderMoving.func_147500_a(TileEntityRenderMoving.java:55)

-- Block Entity Details --
Details:
Name: null // com.rwtema.funkylocomotion.blocks.TileMovingClient
Block type: ID #1311 (tile.funkylocomotion:moving // com.rwtema.funkylocomotion.blocks.BlockMoving)
Block data value: 0 / 0x0 / 0b0000
Block location: World: (-20,76,277), Chunk: (at 12,4,5 in -2,17; contains blocks -32,0,272 to -17,255,287), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Actual block type: ID #1311 (tile.funkylocomotion:moving // com.rwtema.funkylocomotion.blocks.BlockMoving)
Actual block data value: 0 / 0x0 / 0b0000
Stacktrace:
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_147549_a(SourceFile:100)
at net.minecraft.client.renderer.tileentity.TileEntityRendererDispatcher.func_147544_a(SourceFile:92)
at net.minecraft.client.renderer.RenderGlobal.func_147589_a(RenderGlobal.java:483)
at net.minecraft.client.renderer.EntityRenderer.func_78471_a(EntityRenderer.java:1224)

-- Affected level --
Details:
Level name: MpServer

Server side relevent info:

Description: Exception in server tick loop

java.lang.NullPointerException: Exception in server tick loop
at enetbridge.MainLogic.onWorldTickEnd(MainLogic.java:27)
at enetbridge.EventCallback.onWorldTick(EventCallback.java:31)
at cpw.mods.fml.common.eventhandler.ASMEventHandler_660_EventCallback_onWorldTick_WorldTickEvent.invoke(.dynamic)
at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:54)
at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:138)
at cpw.mods.fml.common.FMLCommonHandler.onPostWorldTick(FMLCommonHandler.java:255)
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:645)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:547)
at net.minecraft.server.integrated.IntegratedServer.func_71217_p(IntegratedServer.java:111)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:427)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685)

Mod & Version:
Funky Locomotion 1.7.10 beta-2

Paste.feed-the-beast.com log:


Can it be repeated:
Every time the mining machine plunges far enough for the full frames to enter the ground. Otherwise, no crashes.

Known Fix:
Update Funky Locomotion too Beta-3
 
Last edited:

Jakalth

New Member
Jul 29, 2019
83
0
0
Fix has been found for Funky Locomotion crash. Update to Funky Locomotion 1.7.10 beta-3. No longer crashes, and redstone clocks no longer forget what cycle they are on.
 

David Benston

New Member
Jul 29, 2019
24
0
0
I'm on beta 3, and after spending all weekend trying to make this frame machine work right, I can't even load the world I've been working on for the past 4 months. And I just had my Thaumcraft room set up perfect too.