![]() ![]() You should be able to find the right conf by googling it or on the Unity forums. Luckily for you, this has nothing to do with the TopDown Engine, and is really a general Unity matter. Obviously including support for every gamepad/configuration would be impossible, so I just went with the most common conf. The asset is not working with my gamepad!Ĭontrols have been set up for keyboard and xbox pc gamepad. They contain, as the name implies, the only assets you need to get started. I get that one a lot actually, so I’ve included two “minimal demo” scenes in the assets. What are the minimum prefabs I need to start a level from scratch ? Very specific (like a grappling hook or a portal gun - although I reckon that’d be pretty fun), it probably won’t make it. My goal is to create a strong yet generic basis for all kinds of top-down games. You can of course express your interest in a new feature, but in the end I’m the one whoĭecides what I do with the Engine. Can you develop that feature that I really need ? Updates get released when they’re done and properly tested. When will you release the update X or feature Y ? Plus, the code is heavily commented, so understanding it shouldn’t be too hard. Well you’re reading the documentation right now, so it’s a good start! There are also video tutorials over on YouTube.įurthermore, the asset includes a complete documentation of all the classes of the TopDown Engine. In the meantime, please try the steps above if you run into issues. I’m working with Unity right now to change that, and have a native solution. Of course, this is not as robust as it could be if it was native to Unity. So the TopDown Engine implements an auto downloader that, once the asset’s been imported, runs a check, downloads the packages, and makes sure everything works. If that fails, make sure you imported at least v1.0.2 (you can check at the bottom of the readme what version you got) in an EMPTY project.Īnd if all that fails, please use the support email, I’ll be happy to help you.Ī bit of info about why this may happen : Unity allows (for now) an asset on the Asset Store to upload its Project Settings folder (which includes input, quality, etc), but not the Packages’ manifest.json, which describes what packages the asset uses (such as, in this case, PostProcessing and Cincemachine). ![]() If despite that, you still get errors mentioning Cinemachine or PostProcessing, or if the camera doesn’t follow the player, you can try to go to the Tools Menu at the top of your screen, then More Mountains, then Welcome To The TopDown Engine. If you’ve imported the asset in a blank project, the Engine should automatically handle that for you, and install the required dependencies. This asset relies on a few Unity packages to function. ⚠️ I get errors after importing the package / the camera doesn’t move! ⚠️ You can check what the requirements for each engine’s version are on the Releases page. That’s normal, that’s how the Asset Store works. Each version of the engine requires a specific Unity version, and if your version doesn’t match, you’ll get an old version. FAQ ⚠️ I downloaded the asset and it’s not working / I don’t have all the files ⚠️įirst, start by making sure you’re running the latest current version of Unity. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |