Current state of TGEA
by Jacobin · in Torque Game Engine Advanced · 04/28/2007 (10:51 am) · 2 replies
It seems while working with TGEA one constantly encounters huge blocks of code that's either commented out or code that still contains OpenGL calls. For example, I'll just open a handful of random files and see what crops up when I scroll down.
collisiontest.cpp - render (commented out)
underLava.cpp - contains OpenGL calls and is not commented out.
audip.cpp - enviromental effects commented out.
tsShapeinstance.cpp - TsetupTexturing, setupFog, renderEnvironmentMap and others (commented out)
lightManager.cpp - The entire file is basically commented out
sceneState.cpp - setupBaseProjection (commented out)
forceField.cpp - render (commented out)
rigid.cpp - checkRestCondition (commented out)
Player.cpp - createSplash (commented out)
That's just clicking on random files. If someone were to make a full assay, it would be rather lengthy.
It's somewhat hard as someone learning torque, to gauge if what's you're looking at is depreciated code, legacy code from tribes with no use or a function that GG still has yet to convert from TGE to TGEA. Not so much as a comment with a date/time, developer's initials, reason for the change/change management ID#. I understand since garagegames has stated they are hard at work getting OpenGL->GFX up and running and that's "at the top of their list", that these are low on the radar. So I have a few questions.
1) What sort of timeframe until the codebase is cleaned up of junk/depreciated code so we don't have to guess at why a block of code is commented out?
2) Is there a public bug-tracker, or at least a detailed list of what is not working in TGEA?
3) Is there a post-release development roadmap?
collisiontest.cpp - render (commented out)
underLava.cpp - contains OpenGL calls and is not commented out.
audip.cpp - enviromental effects commented out.
tsShapeinstance.cpp - TsetupTexturing, setupFog, renderEnvironmentMap and others (commented out)
lightManager.cpp - The entire file is basically commented out
sceneState.cpp - setupBaseProjection (commented out)
forceField.cpp - render (commented out)
rigid.cpp - checkRestCondition (commented out)
Player.cpp - createSplash (commented out)
That's just clicking on random files. If someone were to make a full assay, it would be rather lengthy.
It's somewhat hard as someone learning torque, to gauge if what's you're looking at is depreciated code, legacy code from tribes with no use or a function that GG still has yet to convert from TGE to TGEA. Not so much as a comment with a date/time, developer's initials, reason for the change/change management ID#. I understand since garagegames has stated they are hard at work getting OpenGL->GFX up and running and that's "at the top of their list", that these are low on the radar. So I have a few questions.
1) What sort of timeframe until the codebase is cleaned up of junk/depreciated code so we don't have to guess at why a block of code is commented out?
2) Is there a public bug-tracker, or at least a detailed list of what is not working in TGEA?
3) Is there a post-release development roadmap?
#2
04/30/2007 (9:00 am)
Garage Games has stated that their policy on information is "silence." They do not "officially" state what is going to be developed and when, I have not seen any sort of formal list on what is not working, and they often given only the most sketchy information about what is actually in updates that they release. It's very frustrating. 
Torque 3D Owner J.C. Smith