@gama11
Meaning that normal gl_ attributes are not set?
So any stolen shaders have to be altered to openfl_ style?

Also the flip bug had to do with me applying the shader to both the camera and game. Why it flips then I don't understand but removing one of them solves it.

@gama11
Sorry for being tired and unclear. "other" = gl_ prefixed variables that you just informed me are set by openfl. Thank you! :)

Many thanks,

What I meant with "style" is the "openfl_" variables such as "openfl_TextureCoordv" and "bitmap".
Should they be used instead of other GLSL alternatives?

As an example I just simply took the game from the HaxeFlixel book and replaced the post processing with the scanline example from the Filters demo. It feels like UV is not starting at the same point as haxeflixel thinks it does... or I am just not doing it right ;).

Best
J

I am new to shaders and I keep googling and finding all kinds of contradicting answers and examples from varying years back like:
https://github.com/HaxeFlixel/flixel-demos/tree/dev/Effects/Filters
and references to how to use GLSL shaders using -Dnext but only for desktop targets.

What is the state now?

• Should I use GLSL shaders (should work with webgl?) or OpenFLs special own style?
• Where can I learn that OpenFL style if that is recommended?
• I tried to implement the scanline example (using openfl style) but it flipped my screen up-side-down. Should I somehow tell it to start UV from top or something?
• Are filtershaders and per-sprite shaders different things or just applied differently?

EDIT:

• is it possible to load a say .frag file to a FlxShader instead of using @:glFragmentSource and a string?

Many thanks
J

Hi,
I was trying to follow all pages on how to install version 4.4.0 with openfl 8 and lime (6.2?) etc.
And I am failing.
What is the perfered way?

• Compiling everything from source?
• haxelib git all the way?
• git and npm install and then what?

Please list how you did it.
Many thanks.

@gama11
Excellent. Adding break on load solved the problem. Your template should probably have that too.

I guess we first have to get Lime to work on haxe 4 first. I got lots of errors when trying to compile some very simple code from the "Discover HaxeFlixel" book using preview 3.

@gama11 Have you tried the hashlink debugging?
https://github.com/vshaxe/hashlink-debugger

If this works it feels like a better choice than neko. Or?

I assume that just pressed is async with respect to html events which then will not work. Perhaps you can call addEventListener on window and catch Enter or F11. That should count as user initiated as well.

I am new to haxe so here is the js code that works.

window.addEventListener("keydown", function(ev) {
    if(ev.key=="F11" /* or Enter if you want */) {
       var thing = document.getElementById("mything");
       thing.webkitRequestFullscreen();
       ev.preventDefault();
       ev.stopPropagation();
    } 
});

Awesome!

I just couldn't breakpoint in my create function but in update it worked fine. Do you know the reason for this?

Many thanks!

Hi,
I am just setting up everything to get started with haxeflixel and settled for vscode.
My question is: has anyone set up Debugger for Chrome to work with the "lime test html5 -debug" command that is outputed by the build command?

It seem that this should be possible and would imo greatly improve the integrated feel of developing with haxeflixel.

Are there roadblocks that I am not aware of for doing this?