Why 2D might deserve more attention than it is getting

[anonymous_user_8c6e3ac71 (anonymous_user_8c6e3ac7)]

@Achilleon;582616

You can check the game called Wasabi Horizon in Work in Progress tab of forums. They have a top down 2D game going on and they have massive progress, not to mention they have no problem on the collision system that you mention. You might be right about the fact that 2D could be more welcoming, but those guys prove that it is quite possible when you work on it.

It is also hard to give a proper answer against that graphical “bug” without any visual. It can be your mistake, or a bug on the Engine that needs to be reported, or maybe it’s easy to fix. I have been working heavily on 2D stuff and I never had such problems myself.

About the size, I feel 50 MB is quite good enough. I got the feeling that we are pass the point of games being 5 MBs. Unreal is a big engine. Those engines you worked before that you mentioned as “feature lacking” are low on size, because… well… they lack feattures.

My 2 cents, yet again.

Actually, you will find that they appear to have run into the exact same problems, or at least similar ones, as this sounds a lot like it.

Yes, this is being put together with paper 2D. We have been hitting some obstacles with z rendering. The only solution we’ve come up with to getting the desired effect of the character moving behind items, but over that same item when in front of them was the biggest hurdle. We are looking for a better way to do it.

Also, keep in mind that this is still in the early stages. It is well possible that they will run into new issues as it progresses, although it is certainly worth keeping an eye on. The game I was working on made it quite far as well, before things started falling apart more and more because of nasty hacks related to 2D.

The graphic artifacts will become more apparent the more sprites you are using. For my game I was using 32x32 tiles, which is why it was noticeable. That being said, the tilesets are not of extremely high quality, so that might be playing into it, or perhaps I am just seeing things after I went through so much trial and error in order to get the graphics to render correctly, I just do not trust it to ever be perfect anymore. Then again, I have read from other people experiencing trouble with the 2D rendering as well. The easiest solution would simply be providing a default setup for 2D so it is clear whether it is caused by incorrect settings or is indeed a bug. Wasabi Horizon is using a very artsy style where you will not notice a few pixels being off, so that might be why it works for them.

50MB can still be quite relevant on mobile or when downloading on a slow connection. At most 30MB in an uncompressed state would be nice. I disagree that the other engines are able to output smaller executables due to a lack of features. A tile editor will increase the output size by exactly 0kb, as it is an editor feature, rather than included in the game itself. UE is a big engine, but if features are not being used, they do not need to be included in the executable. I can only imagine how much bean counting that will be just for a little bit of improvement, especially for an engine of this size. That is why I put it at the very end of the list. Once everything else about 2D is running perfectly and only then, I think it would make sense to try and improve that.