For these would I be better off keeping the backgrounds one long whole image as is, or should I "cut" them up into smaller images (for example, making four 512 * 112 images) or even use tiles instead? I was thinking I could just take one object and use it to draw several sprites at once to save space, is there a way to do this in Unity?Ģ)In the case of sprites, is there any harm in having a separate sprite sheet for each unique enemy, or should I try to combine them all into a few HUGE sheets instead? In GM my experience was that using many 512 * 512 texture pages was WAY faster than using a few 2048*2048 ones, is that true in Unity too?ģ)In GM: studio we have something called surfaces they are basically blank views which you can use to create all kinds of gfx effects. I wanted to make sure that I got started the right way in Unity, am trying to figure out the best way to optimize this game, and had the following questions:ġ)When it comes to backgrounds, most of them will be about 2048 * 112 (back layer, uses parallax scrolling) or 2560 * 192 (front layer of backgrounds). I chose to use the old Arcade game Rygar for this, and make a minor remake to it. I figured I would do a more basic platformer which would give me a chance to learn Unity. The base size of the screen is 256 * 224.īefore trying to convert my project. For those who don't know, THIS IS A 2D PLATFORMER, that is almost all sprites with a handful of 3d objects (most of which are just flat primitives).
A blog with tons of updates and progress can be found here:.
The project I am working on is a remake of Castlevania: Symphony of the night. soooooooo overhwleming! But its great, because the potential for this thing just seems limitless. I've so far watched over 14 hours worth of videos, read countless articles on C# coding, along with the documentation for Unity. What's going on everyone? I'm new here, and trying to learn Unity so I can port my project over from gamemaker studio.
0 kommentar(er)
