my new game: Sokoban2018

oleg · January 2018

https://play.google.com/Sokoban2018

My experiment is a way to control the game by a non-standard method

totebo · January 2018

Cool! How do you do the shine on the boxes?

antix · January 2018

@totebo that effect could be as simple as the example shader that uses normal maps

antix · January 2018

@oleg really nice

On my Pixel-C...
On the main menu the play button.. it seems there is a circular object being moved across this and it reveals empty grey areas of the underlying image.

Apollo14 · January 2018

Good game! Rated it 5

oleg · January 2018

antix said:
@oleg really nice

On my Pixel-C...
On the main menu the play button.. it seems there is a circular object being moved across this and it reveals empty grey areas of the underlying image.

you can make a screenshot?

oleg · January 2018

totebo said:
Cool! How do you do the shine on the boxes?

a shader from an example that goes with Gideros

SinisterSoft · January 2018

Nice control system.

pie · January 2018

I like the responsive environment in the level menu (the one with the 4 doors) but I noticed that pressing back device button won't get you anywhere here.

Cool game though, really smooth

keszegh · January 2018

nice responsiveness, indeed.
one comment: in the list of levels i'd number them to ease keeping track of them.

oleg · January 2018

pie said:
but I noticed that pressing back device button won't get you anywhere here.

Thanks, in the next update I will fix this error

oleg · January 2018

keszegh said:

one comment: in the list of levels i'd number them to ease keeping track of them.

I decided not to do numbering
it's a psychological factor
so that the players are not distracted by the number of levels they have gone through

keszegh · January 2018

@oleg, if there are no numbers then probably i would not allow to cycle around the level sets (now you can go to left from first to get to last and vice versa, these are somehow confusing).

oleg · January 2018

@keszegh ok I will do page numbering

keszegh · January 2018

sounds like a good compromise.

antix · January 2018

oleg · January 2018

@antix with the project "normal maping" - the same mistake ??

antix · January 2018

@oleg, yes!

I did a test on the Pixel C with OS 8.1.0 and it has the same issue. However Google Nexus 4 with Android 5.5.1 works fine.

oleg · January 2018

specially for @keszegh

antix · March 2018

So can anyone shed any light on the issue with shaders I'm experiencing? I've started experimenting with them again and the same issue is there.

hgy29 · March 2018

@antix, typically differences in shader results between devices will be because they don't have the same float precision. GLSL defines three precision classes: lowp, mediump and highp. Devices are free to use any higher precision than specified. Also highp precision is mandatory only for vertex shaders, some devices may treat highp as mediump in fragment shaders.

There is an API in gideros to check actual device precisions for shaders: http://docs.giderosmobile.com/reference/gideros/Shader/getProperties#Shader:getProperties

antix · March 2018

@hgy29 I see. I ran a test...

Google Nexus 4
version OpenGL ES 3.0 V@104.0 AU@ (GIT@Id3510ff6dc)
vendor Qualcomm
renderer Adreno (TM) 320
glsl_version OpenGL ES GLSL ES 3.00
shader_compiler 1
fragment_float_high_precision 23
vertex_float_high_precision 23
vertex_float_medium_precision 23
fragment_float_medium_precision 10
max_texture_size 4096

Google Pixel-C
version OpenGL ES 3.2 NVIDIA 361.00
vendor NVIDIA Corporation
renderer NVIDIA Tegra
glsl_version OpenGL ES GLSL ES 3.20
shader_compiler 1
fragment_float_high_precision 23
vertex_float_high_precision 23
vertex_float_medium_precision 10
fragment_float_medium_precision 10
max_texture_size 16384

I'm scratching my head to fathom how my new tablet has a lesser vertex_float_medium_precision than my very old phone!

I changed the code to use high precision which works. However performance on the Nexus 4 is very bad ()even with medium precision) so I think I will not bother with shaders for my upcoming projects

antix · March 2018

Further tests reveal that only one line needs to be changed for this example to work on devices with inferior medium_vertex_precision

uniform highp vec4 lightPos;

The Normal Mapping example also still contains a reference to a non existing texture so that needs to be changed also

antix · March 2018

One other question would be.. how do you make this shader work with images that have transparent areas? Currently it makes all transparent areas solid black in color

oleg · March 2018

local JigsawVShader=
[[
attribute vec4 POSITION0;
attribute vec2 TEXCOORD0;
 
uniform mat4 g_MVPMatrix;
 
varying mediump vec2 texCoord;
 
void main()
{
        gl_Position = g_MVPMatrix * POSITION0;
        texCoord = TEXCOORD0;
}
]]
 
local JigsawFShader=[[
uniform lowp sampler2D gMask;
uniform lowp sampler2D gJig;
uniform mediump vec4 jigRect;
uniform mediump vec4 maskInfo;
 
varying mediump vec2 texCoord;
 
#ifdef GLES2
precision mediump float;
#endif
 
void main()
{
        vec4 mask= texture2D(gMask, texCoord);
        if (mask.r<0.5)
                discard;
        vec4 jig=texture2D(gJig, texCoord*jigRect.zw+jigRect.xy);
 
        gl_FragColor = jig;
}
]]
 
local JigsawShaderAttrs=
{
{name="POSITION0",type=Shader.DFLOAT,mult=3,slot=0,offset=0},
{name="vColor",type=Shader.DUBYTE,mult=0,slot=1,offset=0},
{name="TEXCOORD0",type=Shader.DFLOAT,mult=2,slot=2,offset=0}
}
 
local JigsawShaderConstants={
{name="g_MVPMatrix",type=Shader.CMATRIX,sys=Shader.SYS_WVP, vertex=true},
{name="gMask",type=Shader.CTEXTURE,mult=1,vertex=false},
{name="gJig",type=Shader.CTEXTURE,mult=1,vertex=false},
{name="jigRect",type=Shader.CFLOAT4,mult=1,vertex=false},
}
 
 
local JigsawShader= Shader.new(
JigsawVShader,JigsawFShader,
Shader.FLAG_FROM_CODE,JigsawShaderConstants,JigsawShaderAttrs) 
 
local jigsaw=Texture.new("1.jpg",true) --картинка
local piece=Pixel.new(Texture.new("2.jpg",true),200,200) --маска  (чорне видаляє)
piece:setTexture(jigsaw,1)
piece:setShader(JigsawShader)
piece:setShaderConstant("jigRect",Shader.CFLOAT4,1,0.1,0.1,0.3,0.3)
 
application:setBackgroundColor(150)
 
stage:addChild(piece) 
piece:setPosition(50,50)</pre>

2.jpg mask

antix · March 2018

@oleg, thanks, I'll try to mash that into the current shader. Do you have the jpg images I could test with please?

oleg · March 2018

antix · March 2018

@oleg thanks.

So it seems that i require three textures, the actual image, the normal map, and the mask. This won;t be very feasible for projects with hundreds of Sprites

It is interesting to see that Pixels can have multiple textures, that's not very well documented.

antix · March 2018

If I have 3 textures (texture, normal, mask) how does the shader know which texture to reference? Can you assign textures to shader variables?

oleg · March 2018

I do not know

antix · March 2018

@oleg no problem, thanks for all your help. I now have it working just using two textures (the image and the normal map)

Howdy, Stranger!

Categories

In this Discussion

Top Posters

my new game: Sokoban2018

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

Top Posters

my new game: Sokoban2018

Comments