Hm, you must have made that typo yourself accidentally , that issue doesn't exist in Haxelib release and on GitHub:

https://lib.haxe.org/p/flixel-demos/2.7.0/files/Arcade/Flixius/Project.xml
https://github.com/HaxeFlixel/flixel-demos/blob/dev/Arcade/Flixius/Project.xml

(it would have been noticed by Flixel's CI if one of the demos suddenly didn't build anymore)

The export folder can be rather big indeed, but it's mostly about the object files. The actual executable / bin subdirectory you would ship with releases is not very big.

There's a few fixed versions floating around, for instance https://github.com/Lythom/nape-build. Just run the following:

haxelib git nape https://github.com/Lythom/nape-build

I believe this has been fixed in Lime / OpenFL:

https://github.com/openfl/openfl/issues/2111

The fix might not have made it to Haxelib yet, so it might still require to install development builds of Lime and OpenFL.

Might be something for the OpenFL issue tracker, if you can reproduce with a pure OpenFL project / without Flixel.

@jvitoroc So what have you tried so far?

@sangress_ The initial worlbounds only cover a window-sized area. Based on the screenshot, this looks like the sort of game where you might move out of that area quickly?

I assume you installed Visual Studio 2017 including the C++ tools?

This is a fairly common error message that has come up in the Haxe/OpenFL/Flixel forums before, do any the solutions mentioned there help?

There's two things you need to watch out for:

• On state switches, destroy() is automatically called on display list members. So if those sprites have been add()ed, you'd need to remove() them before a switch to avoid that.
• Additionally, state switches dispose all FlxGraphic instances. This can be controlled via the persist property (sprite.graphic.persist = true).

Are you sure that FlxG.worldBounds includes this area? Collisions are only done in that rectangle.

https://marketplace.visualstudio.com/items?itemName=vshaxe.hxcpp-debugger