hi @nlrobson

Maybe stamp() would be a better way to go?
https://api.haxeflixel.com/flixel/FlxSprite.html#stamp

You can make a brush. private var _brush = new FlxSprite().makeGraphic(2, 2, 0xFFFF0000);

canvas.stamp(_brush, Std.int(totalTime % 128), Std.int(totalTime / 128));

I know it's just to test, but the math you're doing limits the x, y to 0, 0 the first 2 seconds, and 0, 1 until 5 seconds, then 0, 2 after 5 seconds, etc. Std.int() floors it. So it takes over 10 seconds to get to 4 px. Over 1 minute to get to 28 px, so not so rapid, and only the left edge. The modulus % always returns the remainder, so that one is always going to be 0 since Std.int() floors it.

@Gama11 @Agustín-Pérez-Fernández

For windows build I only notice lag when full screen. For full screen vsync="false" does help, but I notice artifacts in my game. I think my laptop with onboard video is part of the problem. I also notice that moving the game to my other monitor, connected via HDMI, it's worse. Another thing I tried that helped was to set FlxG.drawFrameRate = 40 but the movement is a bit choppy.

Still, Android is terribly laggy even if I set drawFrameRate to 30, unless it's a very basic game.

@felgs said in Hello world not compiling:

super.create(
var text = new flixel.text.FlxText(0, 0, 0, "Hello World", 64);
text.screenCenter();
add(text);
);

the problem is that you have a misplaced ). It should be:

super.create();
var text = new flixel.text.FlxText(0, 0, 0, "Hello World", 64);
text.screenCenter();
add(text);

sorry, I didn't notice that you tried -Dwebgl

@geokureli

If you must use old lime/openfl try building with lime test html5 -Dwebgl but there are a few things that won't be correct. Colors are tinted wrong, red is blue, etc. Slice9 doesn't work, stamp needs a workaround.

Have you tried HF 4.4 with openfl 8?

You need to get the angle of direction, so if you have the start x/y you can add -1, 0 or 1 to get the dx/dy (direction) you want it to go. To go UP, dx is the same as x, dy is y - 1. That's the point straight up from starting point.

something like this.

public function shoot(x:Int, y:Int, direction:String, speed:Int):Void
{
	var dx = x;
	var dy = y;
	
	switch(direction)
	{
		case "left":
			dx += -1;
			dy +=  0;
		case "up":
			dx +=  0;
			dy += -1;
		case "right":
			dx +=  1;
			dy +=  0;
	}
	
	var rangle = radianAngle(x, y, dx, dy);
	
	velocity.set(Math.cos(rangle) * speed, Math.sin(rangle) * speed);		
}

private function radianAngle(x1:Float, y1:Float, x2:Float, y2:Float):Float
{
	return Math.atan2(y2 - y1, x2 - x1);
}

This is just to give you the math needed for the getting the angle. You should change the code to work with your code.

@ttt said in Why does my sprite loop keeps blinking every time loops:

loadGraphic(AssetPaths.player__png, true, 16, 16);
setFacingFlip(FlxObject.LEFT, false, false);
setFacingFlip(FlxObject.RIGHT, true, false);
animation.add("d", [0, 1, 0, 2], 6, true);
animation.play("d");

Can you post the image you're using? It sounds like there's a problem with how you locate the frames of your sprite sheet.

If you make it a 48x16 strip with each frame being 16x16, it should work. Like so:
|0|1|2|

Or, if you make the image 32x32 like this it should work too
|0|1|
|2| |
where frame 3 is a blank area.

If you have a blank area in your image it will show nothing for that frame of the animation and blink.
|0|1|
| |3|
So, in this case frame 2 is a blank area and will show nothing when animation frame 2 is drawn.

@ttt

not much to go on. The only time I ever have a FlxSprite blink, or flicker, is if I use FlxSpriteUtil.flicker(mySprite) but that would be intentional.

I'm not sure if this is a possible reason, but I noticed with cpp builds when running full screen I get lag, too. This is with latest libs.

Just a hunch here, but maybe it's something to do with the full screen implementation??

For simple games with simple collision, I was able to set fps to 30 for reasonable game play. For my bigger game with lots of collision action, it's not able to handle the collisions without missing sometimes.

I hope someone can figure this out. I wish I knew more so I could.

@fried

Maybe you are mixing up the 2 map options shown in the tutorial?

http://haxeflixel.com/documentation/loading-the-tilemap/

Look at 4. and 5. and notice the changes you need to make depending on the map choice you're using.

Maybe it will help to view the source of the demo to see what's going on.
The source link is on the Conclusion page of the tutorial.

Hope it helps