this post was submitted on 23 Sep 2023
762 points (99.1% liked)

Games

16950 readers
901 users here now

Video game news oriented community. No NanoUFO is not a bot :)

Posts.

  1. News oriented content (general reviews, previews or retrospectives allowed).
  2. Broad discussion posts (preferably not only about a specific game).
  3. No humor/memes etc..
  4. No affiliate links
  5. No advertising.
  6. No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
  7. No self promotion.
  8. No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
  9. No politics.

Comments.

  1. No personal attacks.
  2. Obey instance rules.
  3. No low effort comments(one or two words, emoji etc..)
  4. Please use spoiler tags for spoilers.

My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.

Other communities:

Beehaw.org gaming

Lemmy.ml gaming

lemmy.ca pcgaming

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments

Switching engines also depends on how portable your work from the old engine is with regard to the new engine. It may not be impossible but can still be a lot of work. The earlier that decision is made, the better.

Not to mention I'm guessing a good amount of indie devs are not abstracting every detail of interacting with the engine from the getgo in the chance they want to swap engines down the line. I'm sure some more experienced studios due for that just incase measure or to make migrating past breaking changes a bit easier when they crop up. But generally speaking I can't imagine that's a common tactic. But even if it did your still going to have to recreate every new implementation for your interfaces and there are bound to be differences here that are gonna take some time.