Yes, but how do I know if they are being delph checked? is there any option to set that per object?
or are all the objects ignoring the zbuffer when set to transparent by the Object.setTransparent()?

because I'm having the last behaviour instead of the first one, which would be expected, right?

Yes, thank you, it was missing that configuration

[Thread closed]

Mostly because I want to have a way of picking objects from the world using the cursor and this seems to be the only way.

furthermore, is there any way of picking a group of objects inside a view plane? like a rectangle selection?

Regards,
Jakes

By reading this thread https://stackoverflow.com/questions/16695874/why-does-the-jvm-full-gc-need-to-stop-the-world its easy to understand why it's normal to have short pauses on the threads in order to collect older data.

and this one https://plumbr.io/blog/garbage-collection/minor-gc-vs-major-gc-vs-full-gc to understand the differences.

And yes, I'm a bit of a performance geek, and want to try to give my best on any project, mosly because I'm aiming for low-end machines as well, and by low-end I mean 800s/900s Nvidia GPUs and dual cores CPUs, as well as older i5s and i7s.

Hello, I've been working around with Polylines and it seems that the method Polyline.setPercentage(float) is not working properly or might be something I am missing. For any value other than 1 the line turns fully invisible.

Is this an issue?

I know this might not be the best place to start this but, as this is something that requires a top performance execution, it could have something to do.

After some digging, tuning and playing around with the GC arguments to try to get some good configurations I ended up not having any success at solving its execution pauses.

We all know that the "Stop-the-world" issue while garbage collecting is real, but is there any way to overcome it in an elegant way? I mean, how do anyone here sets up their specs in order to have a nice experience without any lag or freezing every once in a while?

currently, this is what I'm using:

-XX:MaxGCPauseMillis=10 -XX:ParallelGCThreads=4 -Xmx1072M -Xms1072M -XX:+UseParallelGC -XX:NewRatio=4

but, even this, it will fill up the heap memory in a matter of minutes, and once its there, there will be a major sweep that will be noticeable to the simulation and the player.

Any tips or hints will be highly appreciated

Bu regarding this issue, isn't it possible to add a method to the engine that coudl be called staticly, such as TextureManager.preWarm(FrameBuffer), like this:

FrameBuffer.prewarmCompiledObjects(FrameBuffer)

or

Object3D.prewarmCompiledObjects(FrameBuffer)

(I would assume that for this I would need to pass an array of objects, or something similar?)

The reason I'm asking this is, does this method really needs to be a part of the world, beucause I could have the need to precompile every object into the buffer and I could not be using any world at this stage. for example, these objects could be in an asset container so that they could be sent out to the world afterwards. Furthermore, the only thing needed here is the FrameBuffer right?

You can configure the logger in the Logger class. Just set the log level to something higher (like http://www.jpct.net/doc/com/threed/jpct/Logger.html#LL_ERRORS_AND_WARNINGS) and the messages should disappear.

Thanks, I'll give it a go.

The compileAllObjects-method is still there, I've just renamed it so that it reflects better what it actually does. It's now called prewarmAllObject(<FrameBuffer>)

Regarding this, issue, I've tried a lot of scenarios so far:

1. Creating all of the objects hidden, starting the scene with only 1 or 2 simple objects, wait like 5 or 10 seconds, and show all of the 4000 hidden objects: and this way no hiccuping happens at all, it works as if all of them were already loaded.

2. Creating all of the objects visible, starting the scene with 4000+ objects: The scene freezes and has huge frame drops for like 3 or 4 seconds.

3. Used the World.prewarmAllObjects(FrameBuffer) combined with TextureManager.preWarm(FrameBuffer) and here is where the weird behaviour starts as I'm describing below:

- If everything is processed quick enough, then nothing different happens, it loads, and there will be a slowing down of the simulation for 2 or 3 seconds before everything starts running smoothly, so nothing seems to differ when using the World.prewarmAllObjects(FrameBuffer).

But

- if I take longer, after the TextureManager.preWarm(FrameBuffer) which outputs the message "Delayed pre-warming done!" then this shows up on the log afterwards: "Compiling object object6278/com.threed.jpct.Object3D@2d12a01f!
[ Sun Jan 19 22:54:28 GMT 2020 ] - WARNING: Object object6278 hasn't been build yet. Forcing build()!" and nothing happens, as if the application just stops its cycle. and it freezes here forever:


is there anything that I could be missing? As I said previously, If I hide all the objects for a while and then show them up, everything seems to flow normally, but if they start out visible from the start, there will always be some slowness and freezing.