Figuring out what is too slow.

[Jeru Sanders]

In the Flixel debugger I'm seeing this:

Obviously there's way too much time being spent updating, is there any way to figure out what exactly is taking up time? It seems like the only way of realistically figuring it out is to set "active = false" on items until you figure it out. :/

[Gama11]

Try a profiler like hxScout (or Adobe Scout for flash).

[Jeru Sanders]

Those aren't really reliable, Adobe Scout only works with swfs, and Flixel has pretty bad performance in high res swfs, I'm likely to not find the real problem because of the amount of noise to filter.

And hxScout needs it's own version of hxcpp, which relies on a separate version of openfl, lime, etc. It takes hours to set up properly and you're likely to get out of date data like that. It sucks that Haxe/OpenFL tooling is so poor. At some point I'll use FlxBasic IDs or something to count what's taking so long.

[Mixer]

Hey, I might be wrong here, but don't you just have to have the latest hxcpp, not event the dev version, and add a define? Like -DTelementary or something?