1923

Creators of Slay the Spire will migrate their next game to a new engine if Unity doesn't completely revert their changes (nitter.net)

submitted 1 year ago by simple@lemm.ee to c/games@lemmy.world

154 comments fedilink hide all child comments

Picture taken from their Twitter

you are viewing a single comment's thread
view the rest of the comments

[-] dog@suppo.fi 2 points 1 year ago

This is true, and I vouch for gamedevs to first test other engines to see the differences.

Calculating for the future is extremely important in pretty much everything.

Also I wouldn't say there would be performance issues, unless you somehow completely screw up coding and compiling said code.

Projects should work on top of a bottom layer, or translation layer as it's sometimes called; game logic calls for functions from there, instead of directly from the engine. This is also important for code security.

_move_entity might be calling the proprietary unity_move_object with a different reg stack, but when compiled the performance should be +/- 0.

[-] bane_killgrind@lemmy.ml 4 points 1 year ago

The things you are suggesting are adding complexity and therefore cost.

It does take a higher level of expertise to adequately abstract away engine specific limitations and requirements.

It's again an even higher level of expertise and therefore expenditure to account for performance issues with these abstractions.

[-] dog@suppo.fi 1 points 1 year ago

Not untrue, but it helps to adapt your future projects if done in such a way.

It does require more expertise, and it takes more time, thus it'd have to be the first thing done for the project, not something you do after everything's done already.