• 0 Posts
  • 2.7K Comments
Joined 2 years ago
cake
Cake day: July 26th, 2023

help-circle

  • I mean I sort of agree, but I’ve both used custom engines and seen people trying use custom engines and you have this problem where the engine was designed for a game, rather than for any game. So if the original game didn’t have a particular feature the engine has no capacity to do that thing, so every time you want to make a new game in that engine, you basically have to rewrite the engine.

    It works if you build an engine to be an engine, but as you say that’s extremely expensive and time consuming and you probably am not going to get any benefit out of it. You could try selling the engine, but you’re unlikely to make much progress unless there is a significant improvement over the other options already available.















  • Well you can do that but then it isn’t going to run on a steam deck, whether or not you as a developer think that’s a problem depends on what hardware you are targeting.

    But you’ve still got the problem of file size. I’ve noticed that if the asset is really big you actually run into streaming issues when loading it in. It looks fantastic, but you probably don’t want your rock to take 10 seconds to load in. If you go look at the matrix demo you’ll see they have a lot of asset reuse because of that.

    Nanite isn’t magic it’s neither going to enable you to just throw in 16k resolution textures and just not worry about it there’s always going to be a trade-off. But it’s insane to say that it isn’t a useful feature or that you should never use it.