true,the movie's name was:indiana Jones and ,,,oh,,crystal skull,,may be!
damn it i forgot it.
any way the head in the movie was a little bit taller

ChrisB, the thing I used to be complaining about was less the collision itself (c_trace never failed) but more about the way c_trace never used to have a good system with which to set what entities to ignore (ACTIVATE_PUSH worked but is a pain to implement in some cases).

Also, model+terrain or model+model collision has failed on me before, but I don't know how that is with newer versions.

Seems like that changed with the newest beta, there's now a new way to ignore mutliple groups, but now there's a bug in c_trace, they said... That's the sort of thing that bugged me.


Neat work. At first I was wondering "that can't be realtime"... then I saw your "2 minutes" sentence

in a serious implementation, c_trace would
give out a sorted list of objects, with the objects and hitpositions.

This way the programmer could have full control of what to detect
and what to ignore.

----

the raytracing is really cool btw

Very cool It's a great experiment, and might even be useful for pre-rendered cinematics if you expand it.

Some possible future directions:
Multisample anti-aliasing;
Rendering animations;

Jibb

Hm, looks almost like my renders in blender!
You used the same sky color!

Would this work with a skybox, too?

Using c_trace for raytracing is forbidden in about 15 countries in the world. I just warn you, don't do that again or your soul will be multiplied with



If you don't get this... compare it with floats and doubles ;-)

...

Awesome Gamestudio hack!

Nice raytracing there. But what does raytracing have to do with collision gaps et al. People were walking through walls on spots where it wasn't the case for me. Sounds bad enough to me.

c_trace used for ray tracing ->self-explanatory, isnt it?

awesome work
you should dev a tool for the contest based on this
some kind of baking software...

Damocles, couldn't that get very slow with lots of objects? In cases like ChrisB's example, not stopping after the first detection would be useless and a waste of CPU power... if the trace is long, that is.

Though in many cases, I would've loved to have gotten a sorted list back as a result of c_trace, it would've saved me many an hour...

i think internally c_trace already must have a list like that though since it somehow has to figure out what the nearest hit object is. it's unlikely that it automatically always hits the nearest object first.