libgdx | Unofficial libgdx svn clone | Game Engine library

LibGDX is not and game engine so don't expect any "generateTerrain()" method. You need to implement it yourself.

Here you can find general information about how to use libGDX for 3D.

And here you can find actual code that creates a height map.

You need to use an AssetManager. By loading the atlas in the assetManager you can easily get access to textures without the need to reload them every time you instantiate the screen. See https://www.gamedevelopment.blog/asset-manager-libgdx-tutorial/

I don't know if this will work but you can try this

You need to rename first. img3 looks like it serves the purpose of being the pointer to the currentTextureSet. so when you initialise in Player() you might want to rename img3 to currentTextureSet and then, instead of the duplicate load of herochar_idle_anim_strip_4.png, set currentTextureSet = img; after (you may also want to rename img, img1, img2 to idleTextureSet, runTextureSet and swordAttackTextureSet).

That aside, definitely get rid of Timer.schedule which you are calling from render will run in a background thread you don't want that.

Looking at the asset pack here https://o-lobster.itch.io/platformmetroidvania-pixel-art-asset-pack?download if this is the same one, the images should be selected left to right i.e. x should be incremented not y. However, it looks like you increment y... sprite.setRegion(regions[0][frame]); and the incorrect array access is swallowed because in a background timer task and the only textureRegion you can access is [0][0] i.e. you just see a single frame.

So dump this

In box2d, RayCasts should collide with static bodies, so your problem is probably somewhere else.

Keep in mind that the raycast callback is not reporting the fixtures in order of the distance to the start point. Instead the order is random and you have to handle that in you callback. If this is not the problem, you might want to add some code to the question.

Your code is calling the hashCode method on an instance of your Test class, a method inherited from Object.

Implementations of Java commonly implement that method by hashing the equivalent of a memory address of the object, or some such value. To quote the Javadoc of Object#hashCode.

The hashCode may or may not be implemented as some function of an object's memory address at some point in time.

While not necessarily so, if the implementation is using a memory-address scheme, one can imagine that successive runs of a console app might end up with the same hash code value on each run. But you certainly should not expect that. To quote the Javadoc:

Whenever it is invoked on the same object more than once during an execution of a Java application, the hashCode method must consistently return the same integer, provided no information used in equals comparisons on the object is modified. This integer need not remain consistent from one execution of an application to another execution of the same application.

In contrast to a console app, a GUI app is much more complicated, interacting with the host OS to establish windows, menus, and such. One can imagine here that the objects established on an execution run of the GUI app might result in somewhat different objects, enough so that hash codes calculated from something related to memory layout may well vary between runs.

You said:

If I launch the the simulation from a static main function, everything is deterministic and I get the same simulation each time I hit Run as -> Java application

As the last sentence of the above quoted Javadoc says: You may, or may not, get the same hash code on separate runs of your app.

➥ At the end of the day, none of this matters. You should not rely on the same value being returned from hashCode method between executions of your app. You can only rely on the same hash code during an execution of the app.

So your question, “How can I get the same behavior as the static main method?”, is moot. You should not be expecting the same hash code between runs. Why not? Because the documentation says so.

Reading between the lines, I guess you are trying to use the hash code value as a permanent unique identifier. That is not the purpose of a hash code.

Instead, consider using a universally unique identifier (UUID). Java bundles the UUID class to represent these 128-bit values.

If you want to specify a UUID value for your object, you can construct one using a factory method that parses the canonical textual presentation as a hex string with hyphen-delimited groupings of digits. You can manually generate a few values with a web site such as this. Or use software to manually generate UUID values.

Your assumptions are correct. GWT compiler works on Java sources. The error message it gives you is correct: There are no Java source code files to be found, you say it yourself that you used Kotlin.

If you want to use GWT, convert to correct Java source code.

In build.gradle change the first into the second block:

You need to use