Reality Factory

how far away is it from being published? days, weeks,monthe or dare i say it years?

I would say when it's done it's done

I hope it's not far away... I hope the problem is not fundamental to how I tried to code it... I hope it's just something simple that I've been missing...
My hope is that Quest will look at it and say "Here's your problem!" and we can continue on...

The source code is on the FTP site:

Source.Zip is the genesis3d TnL source...
ActView.Zip is the actor viewer code that tests out the source..

I guarantee.... when tnl's finished, and nou has integrated the physcs engine, i will be the first one to Dload the release

when this has been finished, how much wil it improve the engine?
and will it effect compile times.
what i am trying to say is what will change and by how much.

Well guys.. Hows the tnl going? Im too eager for the news. Has the bug been fixed?

QoD thinks he may have found the problem but he will keep us all posted... honestly he's found the problem then I don't know what i'll do? this is great!

scott wrote:when this has been finished, how much wil it improve the engine?
and will it effect compile times.
what i am trying to say is what will change and by how much.

A lot.

I don't think it will affect compile times, but the game will run a LOT smother.
No Hardware TnL has always been the bottleneck of RF, because without it the game does not take advance if you have a Geforce 2 instead of a Geforce 1 chip on your graghic card, as long as they have the same amount of memory. (Ok they're really old, but a Geforce2 is double as fast as a Geforce1)

So having TnL does mean you can have far more polygons on the screen than we could have before.

well, a quick update
the problem is that directx7 has only limited support for skeletal animations so we probably cannot use all the benefits of T&L here
dx8 and up have better support for skinned meshes so I started to convert the d3d driver to dx9...
perhaps wxb1 will find a way around the problem in dx7 so we can use this driver soon
however I'd like to get the driver working under directx9
here's a screen of a 1st test of the dx9 driver:

Whoa! a directx 9 renderer! Im elated.

Will this mean we can use supre duper shader effects in rf and fix the dot3 one light only bug?

One doubt though....
1.We have been using skeletal animations with dx7 for a long time. Why the problem now?

2. whats tnl got to do with skeletal animation?

A directx9 renderer is cool, yes!

I think it would be possible to use shaders then.

One doubt though....
1.We have been using skeletal animations with dx7 for a long time. Why the problem now?

2. whats tnl got to do with skeletal animation?

in genesis all transformation are done on the cpu not using the graphic cards TnL capabilities, this is also true for the transformations that you have to apply to the vertices when rotating a joint (bone) in an animation

now we want to do all these transformations on the gpu, but the problem is that you can only set 1 (bone) transformation matrix for a primitive (triangle) but you might need 2 or 3 (because the vertices of a triangle may belong to different bones)

hmm i can't tell to much from that model you posted quest, it may just be the size of the image,

dunno would you be able to put a comparrison shot of DX7 vs DX9 say?

now we want to do all these transformations on the gpu, but the problem is that you can only set 1 (bone) transformation matrix for a primitive (triangle) but you might need 2 or 3 (because the vertices of a triangle may belong to different bones)

eep!....that sounds tricky like it would take a massive code work around!?! is that the case here or no?....er hang on, or is this refering to DX7.

cool i hope this can be solved, cos this would update genesis so much good luck guys!

hmm i can't tell to much from that model you posted quest, it may just be the size of the image,

dunno would you be able to put a comparrison shot of DX7 vs DX9 say?

you won't see any difference between dx7 and dx9 here, the picture should just show you that the directx9 driver can already render textured geometry (there are pretty large differences in the code since directx7 used directdraw and direct3d which are only one component in directx9)

eep!....that sounds tricky like it would take a massive code work around!?! is that the case here or no?....er hang on, or is this refering to DX7.

I was referring to dx7 here