The second set of errors comes from using a Flixel version that's incompatible with Lime 7. Try updating to Flixel 4.5.0.

@agustín-pérez-fernández Could you try to disable vsync in your Project.xml?

@antwgames It does limit them to HTML5. Also, HaxeFlixel has no explicit support for this / no TS type definitions, so this is only really an option with pure OpenFL.

I don't have any experience with iOS / XCode myself, but this sort of question usually gets better results in the OpenFL forums, since this is not HaxeFlixel-specific.

@rafadelahoz You could try disabling particular "features" (text rendering, large sprites, etc) to try and isolate what exactly is making it slow. Not aware of anything in particular that would be slower with new OpenFL 8 right now.

I'd be curious to know what results you're getting with the Tilemap branch: https://github.com/HaxeFlixel/flixel/commits/Tilemap

It's rather experimental / unstable, but it uses a different renderer (Tilemap instead of drawQuads), so there's a chance you'd see an improvement.

@blaise_rascal Yes, what he meant is that for loops are not allowed after a class name / directly in the class body. They must be inside a function.

What OpenFL / Lime versions are you using? If not latest, could you try updating?

@sascha-west said in HaxeFlixel coding Language:

If I use HaxeFlixel can I use Javascript?

No, you will have to use Haxe (https://haxe.org/).

@ttt It's not, Neko is a virtual machine and it runs much slower than native HXCPP builds. It's most commonly used during development because it's quick to compile / test with, but for releases, people normally use HXCPP builds for the better performance.

Also note that you can just run lime test neko instead of lime test windows -neko.