(Actor || Scene).Collision(ACCURATE) throws a null reference exception

[freckert]

It would be nice to know what the restrictions are on the types of .X files that the _Collision routines work with.  I had to strip several submeshes out of a complex .X file to fix my null reference exceptions.

Is there a cap on the total number of faces or vertices in an Actor?  Is there a cap on the number of faces or vertices in a Group?

I can provide both the problematic and fixed .X files for debugging.

[freckert]

Only the ACCURATE test throws an exception.

[SylvainTV]

I think it was just a problem with the Actor CPU
It has been fixed and I have tested with several .x files.

Should be ok in the next dll.

Don't forget that if you use that, the engine has to compute the skinning and all that on CPU too

[freckert]

I do not call SetActorMode anywhere, I was under the impression that the default was not CPU.

[SylvainTV]

The default is "fastest/shader"
However to compute "accurate" collision, the engine needs to perform CPU skinning.
(but rendering is still done via faster/shader mode)

[freckert]

If I use ActorMode.CPU with the new build, Collision works.  If I don't set ActorMode, Collision still throws an exception.

Could this be because TV has yet to prepare the CPU-transformed vertices when I call Collision?

Also, disabling Collision groups does not work as expected with Actor.Collision

[SylvainTV]

Interesting. I have your model if I remember well.
I'm going to test that sometimes this week.

[freckert]

A clarification on the Collision Group oddity.

It appears that a ray cast (which would normally hit) against a Group which is disabled for Collision (and Rendering) does collide, but reports failure.  So testing stops as soon as it hits a disabled group and does not continue against further groups.

Crappy diagram follows:

ray 1
X--->   |group a|    Q|group b|
---->   |group a|    R|group b|
---->   |group a|    S|group b|
---->   |xxxx  x|    T|group b|
---->   |xxxx  x|    U|group b|
---->   |xxxx  x|    V|group b|
ray 2

If group A is disabled, ray 1 will not report collision at all.  Ray 2 will work properly. 

If xxxx x is empty space:
Picture a series of rays cast from X to Q, R, S, T, U, and V.
XQ, XR, XS, and XT will not hit, while, XU and XV will collide.

[SylvainTV]

So that issue in the CPU mode right?

[freckert]

Yes, this is in CPU mode in the current build.  I saw this in SHADER mode in the previous build.