What's The Chance Of Combining The CG...
by Michael Hense · in Torque Game Engine · 07/18/2006 (4:41 am) · 4 replies
... water and dif resources into the official code, i mean, seeing as most of the work is already done, and they've been widely tested...
--Mike
--Mike
#2
Also, not every developer would need to, or want to use it aand have a large part of their game littered with CG when they may want to add a GLSL version. They'd have to rip out all the CG calls beforehand.
07/18/2006 (5:23 am)
It probably wouldn't be, as the TGE is meant to meet the compatibility levels for a wide range of hardware. Not everyones GPU can handle CG.Also, not every developer would need to, or want to use it aand have a large part of their game littered with CG when they may want to add a GLSL version. They'd have to rip out all the CG calls beforehand.
#3
Torque is meant for low-end hardware, while CG clearly is not. The performance hit might not be huge, but it's enough not to integrate it into the official codebase. TGE should run on as much hardware as possible, while TSE is geared towards high-end machines.
These two products need their places in that chain and integrating CG into Torque would move TGE closer to TSE and that's not very useful at all.
Also, CG is incompatible with some hardware out there (was it ATI?).
07/18/2006 (6:13 am)
This has been discussed before. Basically what Mincentro said and:Torque is meant for low-end hardware, while CG clearly is not. The performance hit might not be huge, but it's enough not to integrate it into the official codebase. TGE should run on as much hardware as possible, while TSE is geared towards high-end machines.
These two products need their places in that chain and integrating CG into Torque would move TGE closer to TSE and that's not very useful at all.
Also, CG is incompatible with some hardware out there (was it ATI?).
Torque 3D Owner Tom Perry