ZGameEditor forum

Hej Ville, Ok then maybe it is TZApplication.Init method that is called too early on the problematic phone so that the initial value (via TGLDriverBase.InitGL) of GL_DEPTH_TEST is not properly set? Hmm .. hadn't thought of that. Seems kind of weird that only "TEST 1" and "TEST 2" as reported by Ats ...

Hej Ville,

But that's exactly what the test-project is doing .. reading out GL_CULL_FACE and GL_DEPTH_TEST using glGetIntegerv and toggling between TRUE and FALSE using glDisable and glEnable ( after the "PLEASE WAIT" period ), and all those things work just fine.

K

Hi Ats, So I had to double check because the result is weird: On the Xperia X (and on the Nexus 5 I'm testing right now) the donut is inside out with both parameters being FALSE during please wait, even though I removed the BitmapCombine component in DonutBitmap. Aha, so it's not caused by BitmapCom...

Hi Ats, Can that come from the compilation parameters of the libzgeandroid.so? Or is it a bug in the source code? Since it appears it's being caused by the BitmapCombine component that would mean it's probably a bug in the ZGameEditor source code. You could double-check this by deleting the BitmapCo...

Hi Ats, I had to add Pixel.A=1 to your BitmapExpression otherwise it appears white on API28 Ah sorry, forgot about that :oops: I noticed a interesting difference .. seems like on Nexus 5 both CULL and DEPTH start as false ( which is incorrect ) while on Galaxy S6 they start as true. On both phones t...

Hi Ats, I've updated the project code snippet ( see my previous post ) with a spinning donut in the background that uses a texture generated using BitmapCombine. Also, for the first 3 seconds the OpenGL cull_face and depth_test states aren't written, so it should use whatever state they are in after...

Hi guys, That should be pretty straight-forward to test though ... perhaps Ats can run the following project on a Android device that displays the problem and one that doesn't and see whether there's a difference? If not, the problem probably lies elsewhere. <?xml version="1.0" encoding="iso-8859-1"...

Hey, Yes I saw that but it saves and restores previous setting (via platform_android push/pop attrib). Ah right, the fakePushAttrib / fakePopAttrib procedures .. not sure what's going on then :-( @Ats, I tried to replicate the problem on a couple of Android devices, but no cigar. What Adreno chipset...

Hi guys,

BitmapCombine does seem to disable face culling inadvertently(?) on Android / ES ( using TBitmapCombine.ProduceOutput > GetCopyAsFloats > GLESPixelsFromTexture ) .. could have something to do with that.

K

Hej Ville, Based on this I would assume that on Android GL_BLEND is enabled by default somehow? That doesn't have anything to do with blending ( vertex colors mix with the material diffuse color without having to use blending ). It's because when you don't explicitly set certain components of the ve...

Hi guys, Keep in mind that currently when you do the following .. - Start a new project - Add a Mesh to App.Content - Add a MeshBox to the Mesh - Select the Mesh component ... the Mesh appears red in the preview window ( don't let that fool you ). Anyway, when you add a MeshExpression ( with VertexC...

Hi plygon,

Are you sure you're not getting any GLSL compilation errors in the log panel? Some GPU drivers are a bit particular when it comes to defining variables that don't actually get used for anything.

K

Hej Ville,

VilleK wrote: ↑

Thu Dec 13, 2018 8:32 am

do you think I should change so that ZApplication use the alpha value of ClearColor?

Yea, i don't see how it could hurt really .. besides, the default alpha value is 0 anyway.

K

Hi Ats, Then I made some tests with the OpenGL calls. If I put them in App.OnBeginRenderPass, nothing change. That's because when you use the OpenGL calls in OnBeginRenderPass, they get negated by the built-in clear calls shortly thereafter. But if I put them in App.OnRender (with App.RenderOrder = ...

Hi guys, Try clearing the screen using a alpha value of 1 ( instead of the default 0 ). Unfortunately you can't do this using App.ClearColor right now ( as the alpha value is ignored ), so you need to execute the following OpenGL calls ( after the screen is cleared by ZGE but before anything is rend...