Author Topic: Blockland crashes when loading up a build  (Read 3290 times)

So whenever I open up one of my loads blockland crashes. This is only for the one build I have though. As my other builds will load up without crashing. The only new add on I put in is zonebricks (If your wondering I do have lodseaddons). I can put in an add on file for you to inspect if you want.

Start up Blockland and open up the options menu.
Navigate to the tab labeled 'Advanced' and make sure "Disable vertex buffer objects" has a checkmark next to it.

Start up Blockland and open up the options menu.
Navigate to the tab labeled 'Advanced' and make sure "Disable vertex buffer objects" has a checkmark next to it.
Still its crashing

Quote from: console.log
Steam overlay activated, disabling input...
Steam overlay deactivated, enabling input...
Direct load saves/Falcon.bls, 3, 0, 1,
LOADING BRICKS: saves/Falcon.bls (ColorMethod 3)
WARNING: loadBricks() - DataBlock not found for brick named "Zombie Hole"
WARNING: loadBricks() - DataBlock not found for brick named "Christmas Tree"
Window reactivating...
Flushing texture cache...
  +- using default 'black' texture 'base/data/shapes/black.png'
  +- using default 'particle' texture 'base/data/particles/cloud.png'
  +- using default 'black75' texture 'base/data/shapes/black75.png'
  +- using default 'black50' texture 'base/data/shapes/black50.png'
  +- using default 'black25' texture 'base/data/shapes/black25.png'
  +- using blank texture
  +- using default 'darkred' texture 'base/data/shapes/darkRed.png'
  +- using default 'gray75' texture 'base/data/shapes/gray75.png'
  +- using default 'white' texture 'base/data/shapes/white.png'
  +- using default 'black' texture 'base/data/shapes/black.png'
  +- using default 'gray25' texture 'base/data/shapes/gray25.png'
  +- using default 'gray50' texture 'base/data/shapes/gray50.png'
  +- using default 'particle' texture 'base/data/particles/cloud.png'
  +- using default 'black50' texture 'base/data/shapes/black50.png'
  +- using blank texture
\dev\Blockland\trunk\engine\bricks\octShadows.cpp:176 - GL Error: 1281 - GL_INVALID_VALUE
Regenerating Shadow Map FBOs...
LightManager::registerLights: lights are already installed.
Fatal-ISV: (\dev\Blockland\trunk\engine\bricks\octBatcher.cpp @ 364) octRenderBuffer::regenerate - failed to map buffer with 213360 verts!
Quote from: Badspot
In cases like this, the video driver is straight up lying to openGLNot much I can do about that.
[@ the GL_INVALID_VALUE] Looks like Badspot already classified these kinds of errors as, "Unsolvable."
[@ the octRenderBuffer::regenerate - failed to map buffer with 213360 verts!] I found this bit of information.
Quote from: Doomonkey
If you go to the options menu and then look in the advanced tab, there should be something called "Disable Vertex Buffer Objects." Toggle it and see what happens.

My evidence:

Doomonkey - http://forum.blockland.us/index.php?topic=235791.0
Badspot - http://forum.blockland.us/index.php?topic=203576.1195

Hope this helps.

[@ the GL_INVALID_VALUE] Looks like Badspot already classified these kinds of errors as, "Unsolvable."
[@ the octRenderBuffer::regenerate - failed to map buffer with 213360 verts!] I found this bit of information.
My evidence:

Doomonkey - http://forum.blockland.us/index.php?topic=235791.0
Badspot - http://forum.blockland.us/index.php?topic=203576.1195

Hope this helps.
NOEDIT: Forgot to bold
Quote from: console.log
Fatal-ISV: (\dev\Blockland\trunk\engine\bricks\octBatcher.cpp @ 364) octRenderBuffer::regenerate - failed to map buffer with 213360 verts!
in the console.log quote

Id also like to say that this has been happening since the new update. Before it, I could freely host without crashing.

I decided to make an experiment with only bricks for my build. There was no crashing at all. Do you know of any crap ons I should delete?

I decided to make an experiment with only bricks for my build. There was no crashing at all. Do you know of any crap ons I should delete?
Please post the solution first. (ex. What add-ons did you disable to make the save run correctly?) After this, lock the topic.

Please post the solution first. (ex. What add-ons did you disable to make the save run correctly?) After this, lock the topic.

He hasn't solved it yet; he's only narrowed it down. There's also no reason to lock topics.

He hasn't solved it yet; he's only narrowed it down. There's also no reason to lock topics.
Reason to lock topics:
  • Other users know it was answered
  • Can't bump an answered topic if it's locked

Please post the solution first. (ex. What add-ons did you disable to make the save run correctly?) After this, lock the topic.
I decided to make an experiment with only bricks for my build. There was no crashing at all. Do you know of any crap ons I should delete?