Neko+Tilemap problem

[xerosugar]

• Flixel version: 4.0.0.
• OpenFL version: 3.6.0
• Lime version: 2.9.0
• Affected targets: Neko

When trying to "trace" a FlxTilemap the program crashes because it cannot "stringify" it for some reason. Win target works tho.

Observed behavior:
"$nargs
Called from Type::createInstance line 102
Called from flixel.util.FlxPool_flixel_util_LabelValuePair::get line 34
Called from flixel.util.LabelValuePair::weak line 603
Called from flixel.FlxObject::toString line 1088
..."

Expected behavior: To see something like: (x: 0 | y: 0 | w: 336 | h: 336 | visible: true | velocity: FlxPoint)

[Gama11]

Please provide some code to reproduce. Doing this in Mode works fine.

[xerosugar]

Hm, that's odd. I'm doing this with a TiledLevel also, if that could have something to do with it.
In the Tiled demo, try and add 'trace(tilemap);' under 'collidableTileLayers.push(tilemap);' on (row 94) to see what happens. That crashes it for me.

[Gama11]

That gets me this output, no crash:

TiledLevel.hx:92: (x: 0 | y: 0 | w: 7040 | h: 576 | visible: true | velocity: (x: 0 | y: 0))

What Haxe version are you on?

[xerosugar]

3.2.1

[Gama11]

No issues there either (I was on 3.2.0).

[xerosugar]

interesting
how do you generate a Tiled demo again?

[Gama11]

With flixel-tools you mean? flixel create <demo-name> (TiledEditor in this case).

[xerosugar]

ok, doing it from a fresh Tiled demo project worked

[xerosugar]

wonder if it's my .tmx file or something else that's messed up

[Gama11]

Try cleaning your export directory in the project where you have issues maybe?

Either way, seems like there isn't a bug here (with Flixel at least). Would still be interesting to know what's happening here.

[xerosugar]

nah, shouldn't be the tmx file. it works on win...
alright, thanks for the help!

[Gama11]

Do you have DCE enabled in the other project by chance?

[xerosugar]

I dunno, what's that?

[Gama11]

Dead code elimination, a Haxe feature that removes unused code. Can sometimes cause issues with code that isn't fully statically typed, like the Type.createInstance() call in your stacktrace. However, you would have to add that manually to your Project.xml, so I guess you're not using it. :)

http://haxe.org/manual/cr-dce.html

[Gama11]

Nevermind, that's actually exactly the stacktrace I get as well with <haxedef name="dce=full" />.

[xerosugar]

hehe, I had that in my project-file :)
ah, and I could trace the tilemap if I remove DCE, but it still crashes. same error message too.

[Gama11]

Are you sure it's the exact same error message?

[xerosugar]

the lines in my 1st message are the same at least

[Gama11]

Should be fixed.. can you try with DCE enabled and latest dev?

[xerosugar]

the error is gone, yay :)
but now something else happens; the 'widthInTiles' property on my map is always the same as the heightInTiles... that's... interesting. And I can change the map's width in Tiled and the height will always get the same value as the width :D

[xerosugar]

oh, wait. hold on

yeah, that was my fault! phew everything works now, thanks!

[Gama11]

👍