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

Jookia's chase cam has never moved when i used it for a long time, perhaps the update changed the command that's used to delay the camera movement so that it has a limit on it?
Possibly, at about the time the chasecam moves from its fixed position the console says "Window Reactivating..." about 3-5 times or something.

I have a problem with the chasecam. I tried using the keybinded chasecam and after a certain amount of time the fixed position moves; I also tried the console command in which to place the chasecam in a fixed position and even that moved too after a certain amount of time :c

Before v21 it moved after a certain amount of time too. I'll be releasing an add-on which you can use instead of chase cam that doesn't move after any amount of time.

Before v21 it moved after a certain amount of time too. I'll be releasing an add-on which you can use instead of chase cam that doesn't move after any amount of time.
Thank you very much :)

I have a problem with the chasecam. I tried using the keybinded chasecam and after a certain amount of time the fixed position moves; I also tried the console command in which to place the chasecam in a fixed position and even that moved too after a certain amount of time :c
I believe that badspot failbinned one of the chasecam mods. I dont remember which one though.


Is it a bug or intended that you can no longer focus the DOF on your player?

It always does that for me.


It seems No Lights Installed is a Mac Problem, and I have the log files from me loading a world:
basically there are NO shadows in the Mac version as far as I can tell (tested on two computers)

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
Skipping shader shadow initialization.
LightManager::uninstallGLLights: no lights installed!
LightManager::uninstallGLLights: no lights installed!
LightManager::uninstallGLLights: no lights installed!
LightManager::uninstallGLLights: no lights installed!
LightManager::uninstallGLLights: no lights installed!
LightManager::uninstallGLLights: no lights installed!
LightManager::uninstallGLLights: no lights installed!
LightManager::uninstallGLLights: no lights installed!
and so on and so forth.
You sir haven't looked at my post....

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

Quote
You better luv me.

Spam: LightManager::uninstallGLLights: no lights installed!

The caused by anything that the shader tries to do its light thang with. (Everything expect lights?)

Trust, me.
Make a server and duplicate this error by trying to do a emitter, even a wrench can cause this.

[P.S. I think the cause may be the shaders and Shadows trying to make the emitter emit a light? And it's not there because the Intel users have Shaders activated, but due to Intel, shaders don't show, causing this problem.)

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

Plz halp me D: I wanna play BL

Plz halp me D: I wanna play BL
What's your problem?

Post you launcher.log
and console.log.

Big post that'll either help the devs or make me look dumb:

Badspot should force blockland to use a GLSL version above 1.20

http://stackoverflow.com/questions/7224461/setting-the-glsl-version-on-mac

...and then put in a check that determines if the hardware supports it. If the check fails, then shaders are automatically disabled.

EDIT: http://www.opengl.org/discussion_boards/showthread.php/166283-GL_EXT_texture3D ehhhh Badspot should also force OpenGL 1.2+
GLSL Language Version? NULL

this is all it says.
Your graphics card is extremely old and you should get new hardware that supports a GLSL version above 1.20
That's happened to me since V20, I just kind of dealt with it, but It's on blinkers of some vehicles too, they will be green instead of orange, but from a distance they will fix. I guess it's some kind of texture problem.
It has been determined that this is a bug with nVidia's pre-rendered frames.
« Last Edit: August 12, 2012, 04:03:59 PM by Axolotl »


GLSL Language Version? NULL

this is all it says.

I don't know about you guys, but Ctrl+F-ing for GLSL in my console log finds nothing.


It has been determined that this is a bug with nVidia's pre-rendered frames.
You sure about that? Cause I dunno, but I thought nVidia was supposed to support S&S, and I see a sticker on my computer that says "intel I5", and yet that bug still shows up for me.