Horde3D

Here's a (temporary) link to my XCode projects should anyone be interested.

Horde3D 0.15.0 XCode Project

It's loosely based on swiftcoder's work, but with my own little twist (no longer needs to install the horde3d framework separately, and no absolute paths)

Out of interest, where were those absolute paths? I thought I had eliminated them.

Horde3D-Info.plist
Knight-Info.plist

those had absolute paths to /Users/tristam/Developer/Horde3D/XCode/*.plist

What do you see in debug view? I get only bounding boxes so far, so I think we will have to tweak the built-in debug shaders.

_________________
Tristam MacDonald - [swiftcoding]

In debug mode I see light sources and wireframe meshes (no mesh animation, but like moving statues) inside bounding boxes.

Debug view screenshot

That is what I should be seeing. Damn, and I can't find a thing wrong with the debug shaders - they upload successfully and are set correctly, nothing in the logs either.

_________________
Tristam MacDonald - [swiftcoding]

Update: I've further tracked down the issue to the AMBIENT shader contexts of skinning.shader.xml and parallax.shader.xml. Without AMBIENT, the samples run at the expected speed but the pedestrian and stone textures are translucent. I think that's normal with AMBIENT removed, but correct me if i'm wrong. More testing underway.

I can't figure it out. I give up. All I can do now is pray to the shader gods.

This is the best I can come up with: Screenshot. That's pure 0.15.0 except the removed AMBIENT contexts for skinning.shader.xml and parallax.shader.xml. Samples run at expected framerates but obviously the translucency issue kinda sucks. No other funky glitches to be seen.

Thank you very much for your efforts! The shots are already quite close to what they should look like. The transparency really comes from the fact that you disabled the ambinet pass and that the lighting pass is additive. I wonder why the AMBIENT context doesn't work. Actually it doesn't do anything more than making a lookup in a cube map with the normal vector...

Afraid I am in much the same boat at the moment. Everything works, just extremely slowly, and no debug view.

If you are willing to try a few more things, try commenting out the cubemap and cubemap lookup in he AMBIENT pass of skinning and paralax:

_________________
Tristam MacDonald - [swiftcoding]

Yes! I am willing to try any suggestion from anyone. I tried what you suggested, but it had no effect.

Horde3D 1.0.0b1 still renders the same as 0.15.0 :\

1.0.0b1 also renders identically to 0.15.0 on my ATI. I was rather hoping for a miracle

_________________
Tristam MacDonald - [swiftcoding]

Success! At last...

I finally happened to notice the source of all my performance troubles on the terrain sample, and now my frame rates are back in the triple digits where they belong! It turns out that the detail texture was actually 512x513 pixels, which was triggering a software fallback for NPOT textures on my card. You might want to resize that image in the distro...

On that note, I am going to package up a binary and developer package for 1.0.0b1, using Vurlix's suggestions. Hopefully will be ready in a day or two.

_________________
Tristam MacDonald - [swiftcoding]

Congratulations! I've fixed it in the SVN.