Tainz Railroad Simulator 2026

I find the common complaint that they should remove "the bugs" (always unspecified number and identities) first before adding new features or releasing new versions to be showing an ignorance of how software development works.
If I was N3V I'd be more concerned that my customers have a common complaint which apparently I'm failing to address.
 
Newer technology when first introduced always is. But the price drops as production scales up and more competitors release alternative (and often better) products.

I just checked the price of the RTX5050/5060 cards and they are cheaper than what I was looking at for my current RTX3050/3060 cards when they came out.

I don't think it's gonna happen atm as A"I" is draining components from final customers. Just look how Micron "killed" Crucial because it wasn't profitable enough compared to B2B sales.
 
I don't think it's gonna happen atm as A"I" is draining components from final customers.
You may be correct. NVidia, for example, "seems to be" making more money selling its products to big business "AI wannabes" than selling its GPUs to computer manufacturers and end users (like us). The AI boom may turn out to be a bubble, like the ".com bubble" of the late 1990's which crashed in March 2000. Or it may not - who knows?
 
Already assets that don't use LMs (LODs for bogies and traincar assets) are already being flagged with warnings. At some point in the future, those warnings may become errors.

Regardlesss of whenever this is done, it would always be too late!
 
If I was N3V I'd be more concerned that my customers have a common complaint which apparently I'm failing to address.
Another prediction of doom if they don't fix what I want fixed.

N3V has been around for about 19 years now and we have heard that same general complaint almost every year. I for one would prefer to see a steady stream of new features added as opposed to the stagnation and eventual death of waiting to fix everyone's personal list of problems before anything new is introduced.
it would always be too late!
Too late for some, too soon for others while some would prefer never.
 
Last edited:
many of those were built with TRS2006-Ts2009/10 standards, and I doubt that many of the authors fix them.
Perhaps the solution, as has sometimes been posted here, is to terminate the current Trainz product and start a completely new one that will not accept any of the previous assets and whose assets will be incompatible with Trainz. That could be a big commercial risk.
 
Too late for some, too soon for others while some would prefer never.

What I really would like, since N3V still allows uploading build 3.7 assets to the DLS is having some indication of their LOD-less status in Content Manager (since having a dedicated warning seems to be an impossible task, marking them with a warning would be enough).
 
What I really would like, since N3V still allows uploading build 3.7 assets to the DLS is having some indication of their LOD-less status in Content Manager (since having a dedicated warning seems to be an impossible task, marking them with a warning would be enough).
The issue we're seeing now is people use build 3.7 as a way to avoid the stricter requirements for newer versions of assets. This becomes another problem due to a build 3.7 asset referencing build 4.6 dependencies. I've run into this a few times when testing some older assets in TS12 for someone. It took me a bit to figure out what was going on because the dependencies are not compatible with TS12.
 
No thank you, I'd rather have a new Trainz product that is mostly backward compatible with old stuff. A new product from scratch would be like starting over from the beginning. Some guys like John above and I have been with Trainz since the beginning. I bought almost every version of Trainz over the past 23 years.
 
Back
Top