didnt recognize the god rays. Pretty neat. Im very interested in how that works :ONormalmaps as itself can be done inside a normal shader as you can use a normal map uniform _t_normal inside the callback(object)Oh, is there already a functional Normalmap-Lighting-Shader available online for Use in Visionaire? If so, I must have totally missed that -- and, where could I find that? (I think it could easily be combined with automatic Normalmap-Generation as I have started to work on.)The Godrays in that Screenshot are unfortunately rather expensive -- primarily because I have no Downsampling and therefore must use too many Samples (48 Iterations of Textures offset against the Light-Vector), so I have alternatively started to play around with a simpler Concept which uses only 3 Samples of Textures being bent/stretched and clamped at different Points (see Image, also with a Shadow using only 1 Sample -- I consider offering Graphings Settings with different Levels of Complexity).

why dont you use a normalmap for the light stuff?The reflection shader however looks neat. You need to share some scripts ;)...I thought you want to get the top/left position of the actual sprite and calculate it by substracting the AnimationSize from the actual players position. This however doesnt contain the offset from the sprite to the actual center.Thanks. :)The Mechanics are still a Bit faulty though, only the Reflection works without any Problems, because that is such a simple Technique... except for the Positioning/Scaling, as that is the big Problem discussed here.I actually started out writing a Shader that would automatically generate a Normalmap for my Character that could be used for Lighting (see Image -- though that is a WIP-Shot), but then I had to admit to myself that I just don't understand the necessary Normal-Vector-Dotproduct-Etc.-Calculations necessary to actually actually use the Normalmap (but I might keep trying), so I instead settled with the much easier Mechanic of using an offset inverted Alphamask blurred across the Character according to the Lightvector (as seen on the multiple Images I have already posted), and I think the Results are neat enough, and run fast enough as well. :)However, I never said that that the "Lighting-Stuff" -- i.e. the Character-Lighting -- is problematic in any Way, my Problem is with getting a properly positioned Mask for the shown Effects. I don't see how a Normalmap (on my Character) could possibly produce Godrays, Reflections, or Shadows cast across the Background in Pseudo-3D. Normalmaps don't help with that.Concerning this: I thought you want to get the top/left position of the actual sprite and calculate it by substracting the AnimationSize from the actual players position. This however doesnt contain the offset from the sprite to the actual center.I am currently using the Character's Position (and the upper-left Corner of the Duplicate would be there), which is at the Animation-Center and therefore have to offset the Duplicate by the Position of the Animation-Center, which usually is half the Width of the Character-Sprite, and ca. 0.94 of its Height. If, however, I could load the Animation-Sprite's upper-left Corner's Onscreen-Position directly, I would not have to shift it by any such Offset (which changes with each Angle) and could most probably directly place it where the current Sprite is. But you might be right, I should try and do the Calculation with the AnimationSize or AnimationInnerSize and see if that might make any beneficial Difference. :) (Problem still being that the AnimationSize does such weird Things when being loaded into the Shader.)

getAnimationSize() should work.At least as i tried it last time, i got the sprite size incl. its zoom calculated in. the problem is that the sprite position is mostly not exactly the point where the sprite ends or exactly centeres. So you need to consider that you need to substract also the spriteSize-"distance to position.x/y"Yes, it is very strange though. I seemingly can load the AnimationSize (divided by the Screen-Dimensions or not):  graphics.shaderUniform(shader_effects[eff].num.num, "AnimationSize",     {      graphics.getAnimationSize(Erlene).x / 1920,      graphics.getAnimationSize(Erlene).y / 1080    } )But then, the Duplicate weirdly has very different Scaling-Dimensions compared to if I put in the Values of the usual Animation-Size manually inside the Shader -- as you can see in the Image with the three differently scaled Duplicates.(I also tried making the Screen-Dimension-Division inside the Shader when using the Uniform loaded via getAnimationSize(), but that strangely did not work at all then.)I am not 100% sure what you mean by substract also the spriteSize-"distance to position.x/y". Right now, the UV-Coordinate for the Mask gets a manually inserted Offset "+vec2(0.5,0.94)" to approximate the Position according to the Animation-Center. Did you mean something different? If so, then maybe that could be something I have been entirely missing so far. :)@ Machtnix:Yes, after loading the Sprite into the Shader and scaling/positioning the Sprite to somewhat fit the Player-Character, I use the Alpha-Mask to get a Mask for Effects like Shadowcasting and Crepuscular Rays (as you can see on one of the Images, though I will have to use a different Rays-Technique due to a Lack of Downscaling (or does Visionaire have that??)), or the RGB-Values for a Reflection (as seen one another one of the Images). Yes, the Alpha-Mask has the same Dimensions as the Sprite, but Positioning and Scaling the Sprite in the Shader (automatically and exactly) is the Problem. :)

Ich bin raus... Ich verstehe nur Bahnhof. und wenn ich den Übersetzer nutze (wie jetzt), kommt nur Müll raus.Warum die Figur doppelt erscheint, kann ich mir nicht erklären. Ist wohl wirklich ein Shader-Problem. Ich hatte es anfangs auch völlig falsch interpretiert, dank der Bilder sehe ich erst, was los ist.I'm out ... I understand only station. And if I use the translator (like now), only garbage comes out. :) :)Why the character appears double, I can not explain. Is really a shader problem. At the beginning I interpreted it completely wrong, thanks to the pictures I see what's going on.

Ah yes, it might make Sense to explain that Problem: The Character.Position is centered on the manually set Point where the Character's Feet touch the Ground, but if a Sprite is being loaded into a Shader as a Texture, the Center-Point will be the upper left Corner of the Sprite, so the Character-Sprite loaded into the Shader would have its upper left Corner centered on the Point where the actual Character's Feet touch the Ground (and the loaded Sprite would be displayed to the bottom right of the actual Character). So, the Sprite loaded into the Shader should have its upper left Corner placed where the actual Character's Sprite has its upper left Corner placed on Screen.The Problem is similar to scaling or rotating an Object via Lua, in which Case the Sprite's "RotationCenter" can and should be set as well, but since "graphics.shaderUniform" wants me to load in a Sprite via Filepath, I seemingly cannot just make it load a specificly defined Sprite that has been definied to have its RotationCenter at a specific Point (if that would even help me here).So, I am afraid the Character.Position is not what I am looking for in this particular Case, though I am currently using that (and Character.Size) to place and scale the Sprite in the Shader, but that needs anadditional Correction, and depending on my Character's current Animation, that Approximation (which necessarily includes Values which make no Sense to me) can sometimes fit perfectly and sometimes have a slight but noticeable Offset, possibly (but I can only speculate) because the Character's current Sprite might be cut down to only its visible Pixels (which would be the Difference between "graphics.getAnimationSize" and "graphics.getAnimationInnerSize", which I might be able to use for Scaling (not sure, I tried, it did not work, but maybe I just coded it wrongly), but that still would not help me with the Sprite's Positioning, I think).