Horde3D

If that bug was located in 2004, I doubt it would still exist - several of Apple's own demos bind multiple buffers, and almost all meaningful OpenGL programs do.

_________________
Tristam MacDonald - [swiftcoding]

Hmm, that is a strange problem. I guess we need to try fixing it after Beta4.

Just wanted to add that I'm also experiencing this issue and I'd be glad to test any fixes on that machine or check into fixing the issue myself if someone could direct me.

A quick idea: maybe the problem is caused by mixing built-in and generic attributes.

Could someone please test this little hack which replaces gl_Vertex by a custom vertex position attribute.

That fixed it! Except debug mode (pressing f7 in samples) doesn't work anymore, it produces a completely white screen instead of displaying debug geometry.

Some more observations:

there doesn't seem to be any difference between forward and deferred pipelines in chicago sample (i guess that's better than what was produced before i.e corrupt screen)

particle effects don't work anymore (tested the knight sample) even though they worked before this patch (as did debug mode)

terrain sample doesn't display properly (black screen with a few random white dots where the terrain should be).

Thanks a lot for testing Vurlix!

The patch was just a little test to check if the problem is what I suspected. It is clear that particles and terrain don't work. Now that we know the cause for the problems, we can create a clean patch that will work for everything.

We have a patch now in the SF svn which should fix all issues.
Vurlix, could you please confirm that?

Great work. Everything works perfectly now. It's really nice to see horde running on mac-nvidia systems again

Thanks for looking into this!!