Author Topic: 2012/08/10 - Bugs  (Read 180979 times)

Yes it can
Really? Because when I was building a pinball game at Spade's Arcade, the ball teleporters wouldn't work unless the bricks had rendering turned on. Fully transparent paint worked, though.

Really? Because when I was building a pinball game at Spade's Arcade, the ball teleporters wouldn't work unless the bricks had rendering turned on. Fully transparent paint worked, though.
You have to turn on ray casting for projectiles to come out of them.

Are you forcing on anisotropic filtering?

My bad for late response.

Nope, both the launcher and Blockland.exe (never knew what handles this in the NvidiaCP) have it to Application-Controlled.

DAMNIT I MISSED IT!

Ah well, lol, Im glad to hear that the recent bugs are being resolved :D

I am going to do my best to DL the update soon. (after i get my rig working properly again, that is :P )
« Last Edit: August 16, 2012, 08:28:09 PM by Midway Sentinel »

Shaders are still broken on my intel core [2 cores, 1 procsessor] dua MacBook.

Not sure if this is considered a bug but when the fog distance is really low along with the draw distance the arrows within the rapid and river water bricks show up



when shaders are off they go away

I'm getting a bug where on the player list, it only shows the latest players that joined. It showed all before, now it only shows two. Not sure when the transition was.

Also, the cannon's torch emitter stays active if a player leaves the cannon while it's fully charged, or the player is killed while it's fully charged

How is that major?

Just disable rendering.
It's major because handicaps can use it for griefing: You don't know where the brick is or why the brick is, it's not there. It's a pretty big bug.

There seems to be an issue with taking DOF screenshots where the players are never, ever in focus.
This isn't result of composing them sloppily, it's that the players literally are not in-focus.
No matter how many times I try, I just can't get it in focus.
It also seems to happen on vehicles and JVS?

Some examples:



Not how the bricks are in focus, but the players are not.

THIS HAPPENED JUST NOW

I was building a house on my server, I was half way done, so I clicked save...
"Blockland has stopped responding."

I was patient and waited for it to fix itself.

"Close window."

I loaded my build back up, but since blockland crashed while it was saving, my build was overwrote and I lost the entire thing.

Why me? WHY!? I rarely decide to build and when I finally do my client decides to take a huge stuff on me at the exact moment i click save.

weaver, I suppose you didn't keep the console.log of the event? Could you reproduce it? You're sure this wasn't in relation to some other program running at the time conflicting with the game when the saving process began?

weaver, I suppose you didn't keep the console.log of the event? Could you reproduce it? You're sure this wasn't in relation to some other program running at the time conflicting with the game when the saving process began?
Everything was running fine, it just decided to crash. About seven people were on my server, also building their own houses. I spent like ten minutes running the same addons trying to reproduce the crash but no luck... I didn't get a console.log.

Everything was running fine, it just decided to crash. About seven people were on my server, also building their own houses. I spent like ten minutes running the same addons trying to reproduce the crash but no luck... I didn't get a console.log.
This is why the save saver add-on is so important. It would have backed up the file before attempting to save. So no matter when you crashed your old copy is safe.

This is why the save saver add-on is so important. It would have backed up the file before attempting to save. So no matter when you crashed your old copy is safe.
I'll get that when I decide to build again. It sucks that all of my work is lost though, it was a painful experience.

This is why the save saver add-on is so important. It would have backed up the file before attempting to save. So no matter when you crashed your old copy is safe.

I feel like such a thing if there is some form of save bug could actually just cause "random" crashes due to automated saving - unless that just makes sure you don't overwrite a save you're overwriting.