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

I found this document that says my Mac should have GLSL 1.50 even though Blockland reports it as 1.20. I'm not sure if this is a bug with Blockland or the video driver. I don't think Apple does a very good job of getting driver updates out.
No, it's because kompressor is probably not putting #version 130 into the shader source code.

I think i figured out why I can't see shadows, but can somebody help me on how to fix it?

Here is what it says in console:

EXT_texture3D present? NO

then at the bottom it says...

Skipping shader shadow initialization.

I think i figured out why I can't see shadows, but can somebody help me on how to fix it?

Here is what it says in console:

EXT_texture3D present? NO

then at the bottom it says...

Skipping shader shadow initialization.
Because your GLSL version isn't high enough.
You need to either update your drivers or get a new video card.



Discovered new bug.

Water Scroll stops pushing players when you switch to simple and back to advanced, but the water still visually moves.

Repeated console spam of "LightManager::uninstallGLLights: no lights installed!" - Cause unknown, full console log or duplication case would be helpful

I have this problem, and you said you needed full console log with it.  Here it is.

It only spams the console when I enable shadows.  Also, my shadows do not work.  I enable them, and it is the exact same as without shadows.

I have an NVIDIA GeForce 6150.



If you need more information just ask and I can try and get it.

Blockland isn't showing shadows or fog, just the vignette effect.

I'm running the game with an ATI Radeon HD 2400 GPU and an Intel Core 2 Duo CPU on an iMac G4 from 2008. I'm guessing this is just because my hardware is too outdated, but I've been able to run similar effects in the past. I don't get it.

Please, I need clarification on this. I've attached the console.log file.


Nevermind, I know what the problem is.
« Last Edit: August 12, 2012, 11:57:21 PM by Squideey »

You sir haven't looked at my post....

I will quote them for you, because I already solved it.

P.S. It isn't a Mac problem, it is caused when someone has shaders field selected to anything other than off, and when this,
Code: [Select]
Checking for shader shadow support:
   - Enabled via $Shader::Enabled? YES
   - ARB_shader_objects present? YES
   - ARB_shading_language_100 present? YES
   - GLSL Language Version? 1.20
   - EXT_texture_array present? YES
   - EXT_texture3D present? NO
   - EXT_framebuffer_object present? YES
   - ARB_shadow? YES
   - ARB_texture_rg? YES
   o Shaders are INACTIVE
shows up when you have a graphics card that currently doesn't support shaders and shadows, therefore the error pops up because it's impossible to show the lighting effects.

Current go-around: Select Shaders to OFF
The card supports full shaders when in Windows (running BL in BootCamp). Both Win and Mac versions use OpenGL, so unless parts of the Mac version of either BL or the OpenGL Resources are MISSING, this should not happen. for all of this talking up of your "solution", it has very little to do with the true problem, because this happens with and without any world emitters of any kind, except (obviously) the sun. It also happens on a graphics card compatible with shaders, NOT Intel Integrated, and without any emitters of any kind asides from the sun, obviously.


Please, I need clarification on this. I've attached the console.log file.


Nevermind, I know what the problem is.

Then what was the issue?

You can't place 2x4 bricks. I think it has to do with the Tutorial.
This was probably posted already but just in case...

Fixed I guess.
« Last Edit: August 13, 2012, 12:42:26 AM by Nightmare-Duckie »

You can't place 2x4 bricks. I think it has to do with the Tutorial.
This was probably posted already but just in case...

I can't seem to replicate this. Placing 2x4 bricks works for me in all scenarios I've tested (Tutorial, Freebuild and Custom with default add-ons).

Badspot

  • Administrator
The card supports full shaders when in Windows (running BL in BootCamp). Both Win and Mac versions use OpenGL, so unless parts of the Mac version of either BL or the OpenGL Resources are MISSING, this should not happen. for all of this talking up of your "solution", it has very little to do with the true problem, because this happens with and without any world emitters of any kind, except (obviously) the sun. It also happens on a graphics card compatible with shaders, NOT Intel Integrated, and without any emitters of any kind asides from the sun, obviously.

Apple writes their own drivers and I guess they did not implement that extension.  Right now you need that extension.  If you don't have it, you can't run shaders.  It may be possible to avoid using that extension in the future but that is not the current priority.  

Apple writes their own drivers and I guess they did not implement that extension.  Right now you need that extension.  If you don't have it, you can't run shaders.  It may be possible to avoid using that extension in the future but that is not the current priority. 

Someone posted this earlier, it might be a workaround: http://www.opengl.org/discussion_boards/showthread.php/166283-GL_EXT_texture3D

I can't seem to replicate this. Placing 2x4 bricks works for me in all scenarios I've tested (Tutorial, Freebuild and Custom with default add-ons).
Odd, I guess a quick restart of Blockland was all it needed. It's working again for me.

Apple writes their own drivers and I guess they did not implement that extension.  Right now you need that extension.  If you don't have it, you can't run shaders.  It may be possible to avoid using that extension in the future but that is not the current priority.  

Hopefully this gets solved soon, as I, and all of your other Mac customers, would greatly appreciate being able to have shaders, as that makes up the majority of this update.

Does the post that Tammy linked to provide any help?

Badspot

  • Administrator
Saves upload really slow when you don't have the BL window open

This is a long standing issue.

The Music folder of the Custom add-on select screen is always as big a full one, meaning it will have a massive empty space no matter how many you have.