[Effect] Shader Effect & Editor released. Create your shader

0 favourites
From the Asset Store
Fully commented source code/event sheet & sprites to create a space shooter game
  • If I add a sprite then your effect, it produces the correct flame effect - both halves.

    Your URL link to your editor shows only half of the effect for me.

  • This is like the NormalMap problem then.

    The people running my .capx not get working, but if they create a new document the effect shows good.. i not understand <img src="{SMILIES_PATH}/icon_e_sad.gif" alt=":(" title="Sad"> .

    zenox98 Can you send me your .capx where the shader effect works correct? is to see what are the differences between my document, maybe i have enabled some option or something, i don't know.


    I created this from a new document changing the size for 960x540 and Fullscreen from letterscale to OFF, works correct?:

    https://dl.dropboxusercontent.com/u/659 ... index.html

    This is the capx used:

    https://dl.dropboxusercontent.com/u/659 ... test1.capx

    Works correct on browsers and NW.JS?


    digitalsoapbox zenox98


    IF works corrects i guess the problem will be for the OffsetX that in all are at 0.5. Works well for me but seems for other cards have to be 0, test this version:

    https://dl.dropboxusercontent.com/u/659 ... r_v102.rar

    Or in the capx that shows wrong shaders edit the "OffsetX" variable and change the 0.5 for 0.0 to see if the shader appears correct.

  • matriax

    Sorry for late reply - lost track of this thread.

    I downloaded your .capx from last post and it works fine, as does the url link - looks the same as when I did it myself, i.e. both sides show correctly.

    The new effect files 'appear' to be working correctly now - both sides are visible, although not all effects are showing (some are just black). Tested in Firefox and NW.js.

    I'll attach a screenshot soon......

  • zenox98 Much thanks for test and for the screenshot.

    I see, then, one of the problems was the OffsetX, in my case works correct with 0.0 or 0.5 but for other people not, have to be 0.0 like you and i guess for the other guy :S . Why the hell are not all the shaders compatible with all the cards, even with the same developer, i also have NVIDIA. i hate this incompatibilities things

    I guess other of the errors can be the OffsetY that will explain we some shaders not appears, because they are in a -0 on Y coordinate instead move the shader in negative numbers.

    Also there is some shaders that works but not correct, i guess because the change of the OffsetX and other things.

    I don't know how to fix that to be compatible with all the cards sorry, hope Gigatron finds a way.

  • I think there is no errors in fx file..

    can someone test this example ... ?

    If there are no issue then it's shadercode preset problem on the .capx file.


  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Gigatron

    Your link displays shaders exactly the same as the pic I last uploaded - some work, some just black.

  • So there is no shader errors .. the problem is shadercode presets .

  • Then, simply some cards draw the shader different from others and there is nothing we can do?

  • If you can, remove offsetX and offsetY or declare them like ; const float offsetX=0.0;

    don't know why do you use them ?... if it's for moving flame... i prefer to move sprite x,y front of Picture instead using offsetX and Y variables.


    One of fire is now moving with mouse pointer x,y

  • Gigatron See the lava shader in the top-right. With the OffsetX at 0.5 works correct with 0.0 the right part not shows correct.

    See the original:

    https://dl.dropboxusercontent.com/u/659 ... index.html

    Also compare the original with your last test. You will find some lines at left/right up/down that looks weird is some shaders. With OffsetX and OffsetY i can fix that errors.

    Or how to fix that errors without OffsetX and Y ? For shader like the flames that are in the center all perfect, but for shader that get the entire size of the X/Y sprite sometimes to fix some problems i have to use Offset X/Y.

    But well, seems that if i want to get a shader compatible with all the cards i will have to sacrifice some ones or find another solution for that errors.


    So, first i will remove the OffsetX and OffsetY or as you said, instead of pass to C2 as variable simply set in the FX as 0.0 and see if that is the problem and with that all cards works in the same way. If that works then try to fix the error/glitchs in some shader or find another way to fix that. If not, sacrifice them. Correct?

  • matriax

    Thanks for trying to fix for us and feel free to give me a shout if you need me to test anything for you.

  • zenox98 Test this:

    https://dl.dropboxusercontent.com/u/659 ... r_v103.rar


    Changes: I removed the offsetX and FadeX Position.

    This is how looks in my side:


    Yes some shaders are not working, but now the objective is get the same output in both sides. After that see how get the maximun shaders compatibility.

  • Gigatron the .fx , .xml and .capx can be downloaded from the first post, this:

    https://dl.dropboxusercontent.com/u/659 ... editor.rar

    zenox98 digitalsoapbox Create a new document, add a sprite with my effect and run, still works wrong? How appears in the layout before run? also cutted in the half?.

    Also guys you tested the editor? this:

    https://dl.dropboxusercontent.com/u/659 ... index.html

    Also appears only a half part of tha shader?

    The same issue occurs in the editor, yes.

  • More effects are showing with the latest effect files. I'll put up a screen grab soon.....

  • zenox98 Is very weird that the lava/magma ones don't shows, they not have nothing special variables, Are the last two of the first row that are not showing in your screenshot.


    Looking better the original flame not have anything in negative, only one variable for the noise.

    The magma ones have a negative Y position and a negative Y fade. Mmm, maybe the problem is allow use negative numbers on some variables or coordinates that some cards process wrong.

    Edit2: I go to upload a new presets avoiding the negative X/Y values to see if this are the problems.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)