Also consider this: if the asset you're referencing with AssetPaths has been renamed or deleted, you will get a compiler error. If you reference the asset via a String path, you will only notice at runtime.

4.3.0 has been released quite recently, there's just no support for latest OpenFL yet. ;)

There's currently two relevant open PRs:

• https://github.com/HaxeFlixel/flixel/pull/2099
• https://github.com/HaxeFlixel/flixel/pull/2068

Try FlxCamera.defaultCameras = [FlxG.camera], to render sprites only to the main camera by default. Then you can pick a few objects you want to render on custom camera(s) and set object.cameras = [customCamera] for each of those.

@starry-abyss Also, to add to that: off-screen sprites are not rendered, but they are still updated.

Does immersive mode work? That usually enables with a slight delay, maybe stageWidth is 1196 on startup but 1280 slightly later?

So you want to have a MenuState so you can follow the tutorial and delete it? :D

Jokes aside, MenuState is not part of the default template anymore. You can just duplicate PlayState.hx and replace the class name.

Flash debugging in FlashDevelop was always a pain to setup correctly for me. In my experience, it's much more straightforward with VSCode and the Haxe Debug extension.

You can put the HUD into a completely separate camera.

Can you check if you see any errors in the output panel with -v?

https://github.com/vshaxe/vshaxe/wiki/Troubleshooting

Is FlxTileFrames imported in that example?