Moving to TC from 2006 ? YAY or NAY ??

[edion2]

I'm pretty happy with 2006 . . . except I'm getting the "read only" error every time I work on my route.

Assuming that TC doesn't have this bug in it, and since TC came with my package . . .

#1 If I decide to move to TC as my main platform to continue work on my routes, WHAT ARE THE PROS AND CONS about moving to TC?

#2 How is the asset compatibility with most of the assets on DLS?

#3 Importing my routes into TC, IS IT A BIG HASSEL TO DO THIS ??

Any inputs will be greatly appreciated.

Thanks

 

[SuperFudd]

Since no one else has responded yet, I'll give it a try.

#1. Not sure, yet.

#2. As I understand it, pretty good.

#3. Not if you move all the standard stuff from TRS2006 & 4 first.

Yeah, well, at least I will be notified if anyone else responds. :wave:

 

[VinnyBarb]

Why would you limit your creations to just TC (I guess you would release them when done as you did your other creations)? Would it not be better to create for TRS 04 and then test your creations in all the newer versions to see how the work? So a whole lot of other users (TRS04 and 06 users) could use your creations.

Unless this is for your own use only then the above does not apply.

In answer to your questions I will give it a try :

1. I do not have TC but what I read here it seems to be stable. So is TRS 04. Cons...? as above, why limit yourself just to the newest version, a lot of others still use TRS04 and 06.

2. It looks that way with a lot of older content, it might pay you to repair some older content to get it into TC.

3. I guess you always can export them as a .cdp and import them into TC unless TC has an internal import feature like TRS06 (which I do not know as I don't have it).

Cheers

VinnyBarb

 

[johnwhelan]

Why would you limit your creations to just TC (I guess you would release them when done as you did your other creations)? Would it not be better to create for TRS 04 and then test your creations in all the newer versions to see how the work? So a whole lot of other users (TRS04 and 06 users) could use your creations.

Unless this is for your own use only then the above does not apply.

In answer to your questions I will give it a try :

1. I do not have TC but what I read here it seems to be stable. So is TRS 04. Cons...? as above, why limit yourself just to the newest version, a lot of others still use TRS04 and 06.

2. It looks that way with a lot of older content, it might pay you to repair some older content to get it into TC.

3. I guess you always can export them as a .cdp and import them into TC unless TC has an internal import feature like TRS06 (which I do not know as I don't have it).

Cheers

VinnyBarb

It's a lot easier to create in TC and then put a TRS2004 version number on it. It usually works most of the time as long as you don't need some of the scripting that is only available in TC.

Cheerio John

 

[edion2]

Hmmmmmm . . .

Making my route available . . . haven't thought abut that yet. I'm a relative newbie to this virtual Trainz. I got my TRS2006 last November.

Since my route will be very large and full of stuff that eats frame rates, I doubt if anyone would want to bother with it. Everyone seems very sensitive about anything that reduces frame rate. Me . . . I'd rather live with lower frame rate than run trains on a route that looks too "simulated" . . . if you know what I mean. I finally figured out Image Shack so I'll be posting my Work-In-Progress there soon.

I'm expecting another year or two before I can even consider it being close to done. I'm hoping that the driving time between two farthest cities on the main line would be between 3 to 4 hours. I only have the main line between two cities and a branch line at each city almost done. Driving time between two farthest industries is about 50 minutes. I have tracks and yards laid for two other cities but nothing else. I still have to build more branch lines and industries to the two "city" yards that are mostly done.

It sounds like moving to TC isn't as painful as people made it out to be. Apparently, TC is not as forgiving about content errors as 2004 or 2006.

johnwhelan,
If you don't mind, can you expand on "why" you think its easier to create in TC?

I suppose it doesn't hurt to try. But . . . I hate reading manuals. It should be very similar to 2006 except with some new features. Then there is the "download". Its my understanding that moving contents from 2006 that I already downloaded into TC is quite time consuming. Someone said it might just as fast to re-download. But . . . another purchase of a different version of 2006 is $30 or so . . . and after all, time IS money.

In either case, I think I'll wait until I get more response/comments.

I've been keeping my "Auto-Save" duty time to less than 1-1/2 hours . . . and so far it hasn't quit on me yet . . . . fingers crossed.

Thanks, keep the comments coming.

 

[johnwhelan]

Hmmmmmm . . .


johnwhelan,
If you don't mind, can you expand on "why" you think its easier to create in TC?

I suppose it doesn't hurt to try. But . . . I hate reading manuals. It should be very similar to 2006 except with some new features. Then there is the "download". Its my understanding that moving contents from 2006 that I already downloaded into TC is quite time consuming. Someone said it might just as fast to re-download. But . . . another purchase of a different version of 2006 is $30 or so . . . and after all, time IS money.

In either case, I think I'll wait until I get more response/comments.

I've been keeping my "Auto-Save" duty time to less than 1-1/2 hours . . . and so far it hasn't quit on me yet . . . . fingers crossed.

Thanks, keep the comments coming.

Basically I'd suggest waiting until TC3 then purchasing that one. TC and TRS2006 creation is much the same user experience if you are creating or reskinning rolling stock however Trainz is evolving if you look at the features page www.trainzclassics.co.uk you can see the bug list fix from TC to TC3. So if you are creating content it's easier in the one that has fewer undocumented system features for you to work around.

Cheerio John