Been thinking about this myself for my own project, so when Tom said the following, he had it coming! =D

[…]

Which engine to use for a game is for sure an interesting topic and I would love to see a pro / con discussion about that in the forums!

Best,
Tom

 

Unreal Engine pros:

• Possibly the best graphics in a game engine today. Many, especially within architectural visualization, a script to make the light simulation much better, and it’s easy. Unreal Engine supports anything from ultra-low poly games to this. It’s simply very future proof.
• Very good distant shadows, with relatively low performance hit. Was implemented after The Kite animated short.
• The Blueprint system there for scripting/ programming is genius!
• In-engine monitoring of what type of calculations that is heaviest on the performance. Brilliant for optimization.
• Free to develop on.
• In-engine modding gives the modder good feedback and lets him/ her instance parts, and create more dynamic LODs.
• Epic (no pun intended) procedural vegetation generating.
• Allows for full C++ editing.

Unreal Engine cons:

• No good system for roads or water out of the box.
• Modding may be more complicated for some, and may require installation of Unreal Engine.

Unity pros (I know little about the last two engines, so I am not going to base this on my experience with an outdated release):

• Two Unity based games have shown a very interesting and dynamic water system: Cities: Skylines and Roller Coaster Tycoon World.
• Well established market.

Unity cons:

• Probably not as future proof in terms of graphics as Unreal Engine.
• Not quite ‘free’. May require its own official modding kit.

What do I personally hope? I’m hoping for Unreal Engine, as long as Urban Games can get what is needed into the engine. What made Train Fever unique is primarily the city generating, and without features such as this, Train Fever would not be Train Fever.

I also hope it could speed up the development, while also giving us, modders, the ability to implement more complication custom features through the Blueprint system in Unreal Engine. I believe the engine also would be the best at allowing a wide specter of graphic options, meaning that it would allow people without much computer power to play with low enough settings, and still allow room for epic graphics for those with flagship graphics.

Merry Christmas!
Cheers,
PaTrond

I personally find the original TF engine to be very well designed for the first game Urban Games has made and is one of my favorite custom game engines I’ve seen so far.

“If it aint too broke, patch it till you run out of duct tape…”- Jason M.

I say stick with the current TF engine and improve the performance, though if I had to pick a new engine I’d select Unity5 for compatibility and performance over features.

I’d love to see what Train Fever could be with an engine such as the two in question. Especially Unreal because of the graphics.

I can only imagine what entire forests with trees, bushes and ferns would look like, using something like SpeedTree which react to wind and trains passing by. Details. But very appealing details. SpeedTree plugs directly in Unity and Unreal. Bring it on!!

I’m not favoring one engine over another, as long as modding support will come first hand from the developers. I love the effort the modders have done to make it possible for the rest of us who don’t know programming, to make mods. But it’s always been sort of a guessing game or jumping through hoops just to make the mesh alone import perfectly. Endless hours of trial and error have gone by just to get a working mod going. I’d like to skip half of that time of failure, and rather be productive!

Another advantage of having an engine with something like Unreal Engine’s Blueprint system, is that it’s very easy to instance almost everything, meaning everything from calculations to textures and geometry. (Almost) every modern game engine has decent or good solutions for this, so this is not Unreal Engine exclusive. This would lower load times, performance hit, and it would also make it easy for modders to make multiple textures/ liveries for the same object. The way I see it – there might be a way I don’t know of – is that the texture path has to be defined in the geometry file, meaning that if I want another asset that has the exact same geometry, but different texture, I still have to duplicate the geometry file.

for example, in C++ you can easily get block level parallelism by openmp, in c#, you need to create task and dispatch them and sync them and manage them…

In my last project in work there is a train kinematic engine, I did the first version in C++, then 1 year later, the project manager want it written in C# like other parts of the project, so he asked another team member did it. it seems the c# version is far slower than mine c++ version.

Does anyone know what language Train Fever is written in and which engine it uses?