Author Topic: OpenGL error, completely random crashes  (Read 1193 times)

I get crashes anywhere from 30 minutes in game to 3 hours, and it always has to do with something OpenGL. Tried to disable VBOs to no avail.

The most depressing but plausible option is that my integrated graphics card just isn't up to snuff to handle Blockland much. If it happens again, I will post the console error here, which is only one line involving a GL_INVALID_VALUE error or something like that. I paid 10 dollars for a new key and I seriously don't want it to go to waste because I cannot play Blockland. (Of course, until my 16 GB ram computer comes, which plays Blockland effortlessly with max shaders.)

Of course, I have OCD so this error is really bugging me. I want to build something and it always eventually screen-freezes and crashes. I hope my graphics card isn't the problem.

Processor: Intel Celeron CPU N2830 2.16 GHz
RAM: 2 GB
Bit: 64
Graphics: Intel HD Graphics

P.S. Roblox almost never crashes, not even 1% of the ratio, like 0.2% maybe. It's only ever crashed on my favorite mining game, that's it.

P.P.S Does anyone think I am running out of memory?

P.P.P.S It tends to happen when there's like 500,000 bricks loaded. Could that be a problem? It also happens less often in singleplayer, unless I am fiddling around with the Mission Editor in V20.

anything over 256 is not guaranteed to not be blockland's fault whenever it comes to crashing. certain computer builds can handle higher brickcounts than others it seems - i dont know enough about how it works to say why. Port (portify) may be able to provide some insight into this.

sylvanor once reported always having issues above 256 k bricks, while zeblote's and port's computers can handle 1million+ and not have problems in any aspects.

Helpful. My computer probably can handle 128,000 at best since I have such a low-end laptop.

Could be because of RAM? You have 2GB of RAM so that could explain why.

Well now the guy is banned so case closed.

sylvanor once reported always having issues above 256 k bricks, while zeblote's and port's computers can handle 1million+ and not have problems in any aspects.

That's actually not true. Attempting to get 1 million bricks on screen at once is a reliable way to crash bl.