BuildCraft|Core

BuildCraft|Core

7M Downloads

ZonePlanner crashes when Full Screen activated

LachimHeigrim opened this issue ยท 6 comments

commented

I'm using BuildCraft on MineYourMind Regrowth server. Client contains the following BC versions: buildcraft-7.1.19.jar, buildcraft-compat-7.1.5.jar.

Reproduce steps:

  1. Place Zone Planner in the world
  2. Load zone from Map Location item
  3. Activate full screen using FS button.

Client crashes with the attached logs:
2017-01-27-2.log.gz

crash-2017-01-27_16.57.24-client.txt

commented

does the same crash heapen when you do the same when you are already in fullscreen before opening the zone planner?

commented

that's not what i ment: does it crash when you switch steps 2 and 3? if you go to fullscreen before you open the zoneplanner GUI?

commented

Actually it does.

I tested exactly these steps:
( 0. Break Zone Planner block with pickaxe)

  1. Place Zone Planner in world
  2. Activate ZP's UI with right-click
  3. Go to fullscreen using 'FS' button
  4. About 3-5 seconds later the client crashes

Similar stack trace as before:
crash-2017-01-29_10.18.06-client.txt

commented

Sorry I don't understand what you mean. In order to display the 'map' in full screen I first need to open the Zone Planner UI which contains the 'FS' button for step 3. Is there any way to do it in reverse order?

Just to avoid confusion by 'go to full screen' I mean 'enlarge the Zone Planner's map to full screen' functionality provided by Zone Planner. Not enlarging (or changing the size of) my Minecraft client screen in any way.

commented

ah then i misunderstood, i thought you ment MC fullscreen, in that case this is definatly a bug

it needs to be verified in 1.8 though as most likely there will not be anymore 1.7.10 builds

commented

Does this happen in single-player?

Currently the client clears out the "inventorySlots" list whenever it goes into fullscreen mode, so that they don't render. Normally the server doesn't send any packets to change any of these slots, but that looks like it does. This could probably be fixed by moving all of the slot's position's off-screen instead of clearing the list.