Opinions require - move from TGEA 1.0.3 to 1.7 now?
by Andy Hawkins · in General Discussion · 04/17/2008 (5:49 pm) · 5 replies
As you may know I have to get a playable demo out at the end of this month. Stupid bugs, poor texture memory management and poor collision to dif performance is making me think I should just port my code to TGEA 1.7
The question is - being so late in the project should I do this? Or should I just release the demo using TGEA with a bunch of known problems and patch after the release?
The question is - being so late in the project should I do this? Or should I just release the demo using TGEA with a bunch of known problems and patch after the release?
#2
The uncertainty is whether FGE will work with TGEA 1.7 I guess.
I'm also concerned that some tech wont work, so I will be trying DIF/projecticle performance versus DTS/protectile performance (using polysoup) - and any DIF rendering artefacts - all why crossing both fingers and toes that the Atlas system is working.
It's these kinds of considerations that will mean I spend 3 nights on upgrading code rather than completing the demo - that's why I'm asking for opinions.
04/17/2008 (10:23 pm)
The main change is the FGE inclusion (takes about 3 hours to change), plus a bunch of small changes for bug fixes which I documented.The uncertainty is whether FGE will work with TGEA 1.7 I guess.
I'm also concerned that some tech wont work, so I will be trying DIF/projecticle performance versus DTS/protectile performance (using polysoup) - and any DIF rendering artefacts - all why crossing both fingers and toes that the Atlas system is working.
It's these kinds of considerations that will mean I spend 3 nights on upgrading code rather than completing the demo - that's why I'm asking for opinions.
#3
It would be better to delay release & fix the bugs then delay possibly (but not guarantied) 10x longer because you're integrating to a new code base.
04/18/2008 (6:51 am)
Normally it's 100% frowned upon to do a major change to a project to try to fix something. If this is a demo for a product to sale, a bunch of bugs = major lack of sales. Why do you think major game companies don't release a demo until AFTER the game's out? It would be better to delay release & fix the bugs then delay possibly (but not guarantied) 10x longer because you're integrating to a new code base.
#4
04/18/2008 (4:46 pm)
I'm experimenting by porting the code to TGEA 1.7.0. I am getting performace gains on rendering but bugs remain. My main code base is in TGE anyway so if after a few tests, TGEA 1.7.0 proves better in a cost/benefit analysis then I will do the main port to 1.7.0. 
#5
04/18/2008 (7:57 pm)
Eh, the last month should be crunch time, not port time IMO. I'd stick it out with your current engine, but without a huge amount of details, porting might make sense. 
Torque 3D Owner Stephen Zepp