Missing Faces
by Ronald J Nelson · in Constructor · 05/16/2007 (8:45 am) · 2 replies
I am referencing this post I made in the TGE bug area since it looks as if it is a Constructor issue.
www.garagegames.com/mg/forums/result.thread.php?qt=62186
I know Caylo is seeing it, anyone else?
www.garagegames.com/mg/forums/result.thread.php?qt=62186
I know Caylo is seeing it, anyone else?
Thread is locked
#2
I have tried to export 3 DIF that DID work with Constructor 1.0 without leaving missing face behind, (before giving up and deleting Constructor 1.01 talk about crap, im growing so disappointed in the rubbish GG is shoving at us. Its not MY job to work around all of the bugs they leave behind. Im a Torque Customer, not an debug monkey/beta tester, and i expect better from GG.) but none of them work.
So i make a simple box, it works. So i make a complex box, (just a hollow cube with trim around all the edges, and this one DONT work. This is SIMPLE geometry! Classic QUAKE was able to do this and more just fine back in the mid 90's, why is it so hard to get GOOD BSP into Torque, now a decade after QUAKE?
Im may sound a little pissed off and i am, im sick of wasting time on bugs that should never exist in an engine with the age of Torque. Im sick of being told that the fixed working update is coming VERY SOON and it will arrive with great optimizations and improvements. Im quite upset that the Torque SDK i invested time and money into do not even support the things it is ADVERTISED as being able to do. If i wanted to use Torque to build a game that looks like it was made 5+ years ago, Torque is able to do that just fine. And for the now price of $150 i have seen a few other basic rendering engines that offer a heck of a lot more power and support then Torque do.
05/16/2007 (12:25 pm)
And luck Ron? I have tried to export 3 DIF that DID work with Constructor 1.0 without leaving missing face behind, (before giving up and deleting Constructor 1.01 talk about crap, im growing so disappointed in the rubbish GG is shoving at us. Its not MY job to work around all of the bugs they leave behind. Im a Torque Customer, not an debug monkey/beta tester, and i expect better from GG.) but none of them work.
So i make a simple box, it works. So i make a complex box, (just a hollow cube with trim around all the edges, and this one DONT work. This is SIMPLE geometry! Classic QUAKE was able to do this and more just fine back in the mid 90's, why is it so hard to get GOOD BSP into Torque, now a decade after QUAKE?
Im may sound a little pissed off and i am, im sick of wasting time on bugs that should never exist in an engine with the age of Torque. Im sick of being told that the fixed working update is coming VERY SOON and it will arrive with great optimizations and improvements. Im quite upset that the Torque SDK i invested time and money into do not even support the things it is ADVERTISED as being able to do. If i wanted to use Torque to build a game that looks like it was made 5+ years ago, Torque is able to do that just fine. And for the now price of $150 i have seen a few other basic rendering engines that offer a heck of a lot more power and support then Torque do.
Torque 3D Owner Todd Pickens