2012/08/26 - Blockland r1715

[RagnaTheBroedge]

these bugs are both terrifying and hilarious, especially glass' shadow words
i hope they can be resolved .-.

[Ad Bot]

[Reinforcements]

this is because EXT_Texture3D won't work

notice the "NO"

Changes since r1713:

• ARB_texture_rg no longer required for shaders
• Core function glTexImage3D will be used if EXT_texture3D is not available.  
• Fixed some issues with shadow map blending under low view distances
• Reduced shadow offset

With these changes, the total percentage of Blockland users who can run shaders should increase from 57% to 66%.

[hammereditor²]

Sorry for posting this 2 times, but nobody noticed.
Can shaders run on a video card which supports OpenGL 4.1?

[Tonkka]

You should probably rephrase this or something. If i have it on does Blockland actually detect if the environment is set to dark?

[Doomonkey]

You must not have glTexImage3D either. The update made it so 9% more of the total users can use shaders. There is a chance you are not in that 9%.

[Paradon]

You should probably rephrase this or something. If i have it on does Blockland actually detect if the environment is set to dark?

I'd like it if it was something like 'auto use light in dark areas'.

[The 1]

I'm playing on a mac and still the shaders won't work.

[Brian Smithers]

I'm playing on a mac and still the shaders won't work.

he broke it. :P

[The 1]

he broke it. :P

What do you mean?

[Brian Smithers]

What do you mean?

You'll get an error in console saying that shadow coef is not defined in the vertex shader
thats because badspot forgeted something up (i think)

[The 1]

Do you mean that shaders HAVE worked on macs?

[Brian Smithers]

Do you mean that shaders HAVE worked on macs?

no
because when he fixed it this update
he broke something else.

[Blocky943]

no
because when he fixed it this update
he broke something else.

It's an updowndate!
On topic, this is coolio.

[Badspot]

You'll get an error in console saying that shadow coef is not defined in the vertex shader
thats because badspot forgeted something up (i think)

Could you post the actual error instead of your comedy reinterpretation of it? 

[Cookiez664]

Hmm, i updated it and still no shaders. but I think I can wait a little bit longer for them.

here's the console.

Code: [Select]

Checking for shader shadow support:
   - Enabled via $Shader::Enabled? YES
   - ARB_shader_objects?           YES
   - ARB_shading_language_100?     YES
   - EXT_texture_array?            NO
   - EXT_texture3D?                YES
   - glTexImage3D?                 YES
   - EXT_framebuffer_object?       YES
   - ARB_shadow?                   YES
   - GLSL Language Version?        1.20
   o Shaders are                   INACTIVE

Skipping shader shadow initialization.
optionsDlg::setShaderQuality reloading shaders...

Checking for shader shadow support:
   - Enabled via $Shader::Enabled? YES
   - ARB_shader_objects?           YES
   - ARB_shading_language_100?     YES
   - EXT_texture_array?            NO
   - EXT_texture3D?                YES
   - glTexImage3D?                 YES
   - EXT_framebuffer_object?       YES
   - ARB_shadow?                   YES
   - GLSL Language Version?        1.20
   o Shaders are                   INACTIVE

Skipping shader shadow initialization.
Executing config/server/prefs.cs.
Issuing Disconnect packet.
Exporting server prefs
Exporting client prefs
Exporting client config
Slayer (Client): Deactivating Slayer
Exporting rtb prefs
Shutting down the OpenGL display device...
Making the GL rendering context not current...
Deleting the GL rendering context...
Releasing the device context...