Game Development Community

TGE to TSE - Portability?

by Shyam "Doggan" Guthikonda · in General Discussion · 05/27/2005 (7:54 pm) · 4 replies

I've looked everywhere and have not found a suitable answer, so I am hoping this is the correct place.

I am interested in purchasing the TGE Indie License. What I am curious about is this: The TSE is based on the TGE. How similar are the two designs? If I purchase TGE and later purchase TSE, how easy will it be to port all my code to the new engine? Obviously TSE has more features than TGE, but would the basics remain the same?

Thanks for any info! :)

#1
05/27/2005 (11:34 pm)
Most things will remain unchanged unless you do custom engien code that uses openGL which you will have to port to GFX (TSE's rendering abstraction layer)
#2
05/27/2005 (11:45 pm)
You may want to read the TSE public forums there are a few threads over there that you may glean some info from, like Porting from TGE to TSE, Porting TGE to TSE and TGE Scripts to TSE Scripts?.

There is also a resource From Torque to TSE by Xavier Amado that you may find some useful info in.

In this very forum the thread TSE questions :) also has some info including posts by several Garage Game employees on the subject.

I'm not expert and don't own TSE but I had those bookmarked :P
#3
05/29/2005 (6:02 am)
I'm going to be using DIFF (patch) tools to compare my TGE project with a clean copy of TGE 1.3 so that I can record all of my engine changes into a patch file.
After I put all of my changes from the patch file into TSE (by hand) I'm going to just drop my new TSE exe into my example directory and pray.
The links that Vernon provides also will lend some insight into debugging the port.
This is all theory and I haven't done any of it but it should work out ok.
I've heard alot of positive results in the forums.
My game of course has no shaders or normal maps because TGE doesn't support them so there will be alot of new eye candy work.
Mostly I'm just waiting for TSE to be complete, and my game to hit beta to see if it's even marketable.

Ari Rule
"Measure twice, cut once."
#4
06/02/2005 (1:22 am)
If you use Subversion for version control, you can use svn's merge command to migrate your changes to a new directory. See the Subversion book's advanced section on "vendor" code for the howto. The book is available online, linked from the Subversion site.