I have this terrain with some planes scattered on it. About 2000 planes. when the camera faces many of them, the terrain and my player model stop being rendered. I have to make the camera look at where they aren't in order to be able to see the terrain and the player model again. Any tips?
Also, the planes were cloned using the cloneObject() method. I don't really know what to do now.

few planes on camera:
https://imgur.com/k3PNGug

many planes on camera:
https://imgur.com/T18Kh3r

update:
It seems to be a limit of objects on screen; when I move the camera some planes disappear e others appear, for some reason my player model and the terrain are not a priority and are ignored when there are many planes on screen. I removed some of the copies and this no longer happens. But I still would like to place many of them around my map.

Hi, i have worked on the new project for some time, i think it can work, but it's not finished yet. here is a quick demo of what it would look like.

Thanks Egon,
i found that setUniform(float array) can be used to set boolean uniform too, if the uniform in glsl program is written as 'bool'.

to AeroShark333:
i tried gles3.0 and i am quite sure the app was in es3, but i still can't use bitwise operation (shader doesn't compile if '&' is used).
i just used 3 as the argument when calling the setglesclientversion() method.

Quote from: MichaelJPCT on April 24, 2024, 05:53:52 AM
another question , can there be uniform short array?

You can't specify different integers (byte, short, integer, long, etc.) but you can set the overall integer precision (but this is device specific...).
As of OpenGLES 3.0, you can do more with integers such as bit manipulation. So I could imagine you could store two shorts in a 32-bit integer variable. (idea can be extended to arrays, of course)
You'll need to make sure your renderer supports OpenGLES3.0 and the device also supports it (as well as bit manipulation).

Quote from: MichaelJPCT on April 24, 2024, 05:53:52 AM
another question , can a uniform array be longer than 1024 elements?

From my experience this is very device specific. Modern devices usually have allow for more than 256 uniform values.
That means that you should take around 240 as your uniform array size limit. (as other uniform variables are also counted for the device limit).

Should be doable. You can implement an IRenderHook and attach it to the objects in question. In it, implement the https://www.jpct.net/jpct-ae/doc/com/threed/jpct/IRenderHook.html#setCurrentShader-com.threed.jpct.GLSLShader--method and then do something like:


int handle = GLES20.glGetUniformLocation(shader.getProgram(), "your_uniforms_name");
GLES20.glUniform1iv(handle, intArray.length, intArray, 0);


in it...that should work...I guess...

i was thinking about more flexibilities of data format.
for example, since 'short' is not possible, i may use 1 int to store 2 short values. i could save some ram in this way.

but now i found a bigger problem:
i can't use bitwise operation in shader(like int&2 ). so i can't use 1 int to store 32 boolean values. and jpct-ae doesn't provide setUniform(string,bool val). i guess i could use 1 int to store 4 booleans by some calculation, but it's not convenient.

can i call GL functions directly so jpct-ae doesn't need to provide all possible signatures of setUniform?

Thanks.

No, there isn't. I guess, I never saw the need for it so I somehow overlooked it. Do you need support for this?

Internally, it's used (as you've noticed) for setting the blending modes, but that's the only part that uses it.

About the other questions:

• There's no setter for short-arrays in the API, so I guess not...
• I'm not limiting this, so I guess it depends on the GPU/driver what the limit is.

hello Egon,
it seems that there is no setUniform(string,int[] val). but in java doc of glsl shader there is: uniform int blendingmode[4].
is that right?

another question , can there be uniform short array?
another question , can a uniform array be longer than 1024 elements?

thanks.

Quote from: AeroShark333 on January 28, 2024, 02:23:59 PM
It's a cool game but some things I noticed:

-> Is the game supposed to be played in landscape mode; I believe portrait mode might work as well
-> I found the controls a bit hard (on my Samsung Galaxy Note 9 (Android 11) the button hitboxes seem a bit too small that it doesn't always register my presses when I try to press a button)
-> Additionally, I think it would be nice to have gyroscope controls maybe for left and right movement (it would also reduce the amount of buttons on screen; or allow the remaining buttons to be enlarged)
-> Lastly, I am not sure about this but it feels like the ball speed does not reset to a slower speed once one of both players has scored... (this has lead to sometimes 3 goals in a row because there is not much time to react after a goal has been scored)
-> Another suggestion might be to let the ball start closer to the opponent instead of from the center of the screen (so that the ball travels a bit further and allows for a better reaction)

Hello. I made this application to study neural networks (although I didn't implement in app), and if the game suddenly becomes popular, I'll make your recommendations, thank you)))

Quote from: EgonOlsen on January 28, 2024, 01:19:19 PM
What's the minimum requirement for this game? I can't install it on any of my devices (granted, they are all a bit older now... )...

Hi Egon, android 11+