The folder containing the neko binary, as well as std.ndll (and other .ndll files). On Windows, that's a separate directory next to the Haxe directory (C:\HaxeToolkit\neko vs C:\HaxeToolkit\haxe), not sure what the directory structure would look like on a Mac.

Is NEKOPATH set correctly? Seems relevant to that error message, according to what I linked earlier:

NEKOPATH - path to the neko installation. I believe it's needed for loading standard .ndll files.

Hm... flixel-tools calls haxelib, and it sounds like something is wrong with running the latter. What happens when you run haxelib list / haxelib path flixel?

I don't think HAXE_PATH and NEKO_PATH are a thing btw - it's HAXEPATH and NEKOPATH (source).

The ApplicationMain not found error happens when you haven't built for the selected target yet (see https://github.com/openfl/lime-vscode-extension/issues/44). As the warning says, it doesn't meant that completion won't work, just that it will be slower than it could be.

I think the black screen when building through VSCode and the "invalid field access" error were since fixed in Lime by this commit. However, it hasn't made it into a release yet. So to avoid that, you could either downgrade to the previous Lime / OpenFL versions or update to a dev version of Lime. Adding this to your settings.json should work as a workaround as well:

"haxe.enableCompilationServer": false

Perhaps you need to set the HAXE_STD_PATH environment variable since you have it in a non-standard location. It should point to the std folder next to the Haxe binary.

This happens if you haven't compiled the game yet (for the currently selected target). See also https://github.com/openfl/lime-vscode-extension/issues/44.

No, that's currently not possible (without modifying flixel-tools sources).

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.