Now let’s take a look at the code required to display this effect: package com. ![]() For this code example I am using particles.party. Save the file there, the extension doesn’t matter. If you have an Android project it will be located at /android-proj/assets otherwise it will be in core-proj/assets. We want to save the resulting file to our assets folder. Since our last release a little over a year ago, a great deal of work has been done libGDX 1.11.0 brings improvements and new features in various areas take a look below to find out more If you are upgrading from an older version, be sure to also check out the Ultimate Migration Guide (1.9.10 to 1.10.0). In this particular tutorial we are just going to go with the default as it is already configured, which is a flame looking effect. Now that you’ve got the particle editor open, let’s save an effect to work with. Select ParticleEditor – .particleeditor and click OK. It should now prompt you to select which Java Application to run: Then right click your desktop project, select Run As or Debug As->Java Application. Now click Run:Įclipse is actually much simpler… if it works, which is a big if. Really, all you need to do is set the Use classpath value to your desktop module. The first time you need to set some configuration values: Now right click ParticleEditor and select Run ParticleEditor… main(): Now in your Projects window, locate gdx-tools.jar ( there will be a version number too, currently 1.4.1 ).Įxpand it until you find particleeditor, then locate the class ParticleEditor. Once you’ve loaded your project into IntelliJ IDEA. I will cover each in turn below ( and also show both in the video above ): IntelliJ Fortunately there is a much easier option for running the particle editor if you use either Eclipse or IntelliJ IDEA. Obviously on your computer this will be somewhere else, and it will change with each version. On my computer on Windows its:Ĭ:\Users\Mike\.gradle\caches\modules-2\files-2.1\\gdx-tools\1.4.1\SOMEREALLYLONGGUID The actual directory it will be in is random thanks to a GUID key. Now LibGDX will be located somewhere in your Maven repository, which is a hidden folder. You can run it from the command line, but this presents a certain special challenge, since LibGDX moved to a Gradle based setup… so, where exactly is gdx.jar these days? That’s a good question, and the answer is very very well hidden.įirst make sure you’ve built your project at least once, so then all of the dependencies have been resolved ( AKA, Gradle downloaded LibGDX ). Now it’s a matter of running the ParticleEditor, which isn’t as obvious as you would think. ![]() This will result in the particle editor being included in your project dependencies. When you run the setup utility to create your project, make sure you set tools to true. Fortunately this is a pretty easy process. In order to follow along you need to install the gdx-tools in your project. In this tutorial we are going to use one of the tutorials included with LibGDX, the particle editor.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |