Defold 1.2.161 has been released

#35

Fantastic! Is this likely to fix the flickering and crashes?

0 Likes

#36

Yes

Maybe. Now that tilemap layers are interleaved with other things out could potentially result in z-fighting and flicker, but it could also be part of the bug.

0 Likes

#37

I was able to fix the z issue, but the flickering is tilemaps showing/disappearing seemingly randomly, so I don’t think it’s to do with z ordering (all visual objects should be within the -1 to 1 range).

For now, I’ve installed an older version, which works great without any issues.

2 Likes

#38

Hello again guys :wave:
@britzl
i would want to know if my issue was a real issue and if you are working on it, just to know… good work to all :slightly_smiling_face:

0 Likes

#39

I answered in the GitHub ticket

1 Like

#40

Here’s a bleeding edge alpha build of the Editor and engine, with fixes for the tilemap issues.
Please try it out and let us know if you have additional issues.

It’s a preview of the release that is scheduled for monday (1.2.162).

NOTE: Don’t replace your old installation. Install it with a different name,
e.g. “Defold_1.2.162_alpha” or similar.

NOTE: Don’t update it, since it will then replace the engine to the latest release one, and you’ll get the old issues back.

OSX
Win64
Linux64

3 Likes

Tilemap issues
#41

Ok, after adding another fix, we now have an alpha build you can test:

0 Likes

#42

@Mathias_Westerdahl
There is another bug with tilemap material… If you change the default material with a custom material, in tilemap preview nothing is shown; In main collection the tilemap is shown but is moved to another position. I attach a repro case, is the same project I posted for the previous issue:
https://github.com/defold/editor2-issues/files/3579596/DebugProject.zip

The tilemap with different material is called “anim” and it need to have the same position as “city1” tilemap.

1 Like

#43

For some components, the world matrix isn’t set (like tilemap), and you shouldn’t use it.
Change your vertex shader back to this, and it should work (it does for me)

gl_Position = view_proj * vec4(position.xyz, 1.0);
2 Likes

#44

@Mathias_Westerdahl
Yes, with this change it works, but now I have 2 other problems:
1. in tilemap preview if you change the z position of a layer, it results in grid not showing;
2. the game crashes randomly (sometimes doesn’t) without errors, and sometimes it shows in console this error:
Assertion failed: i < Size(), file C:\buildbot\slave\builds\engine-win32-64-dev\build\tmp\dynamo_home\sdk\include\dmsdk/dlib/array.h, line 410

0 Likes

#45

1. in tilemap preview if you change the z position of a layer, it results in grid not showing;

If that was working with the released editor, I’d say it’s because this alpha release doesn’t actually contain certain changes they’ve done in the Editor since the release of 1.2.161

the game crashes randomly (sometimes doesn’t) without errors, and sometimes it shows in console this error:
Assertion failed: i < Size(), file C:\buildbot\slave\builds\engine-win32-64-dev\build\tmp\dynamo_home\sdk\include\dmsdk/dlib/array.h, line 410

Do you get a _crash file? I’d very much like to see it :slight_smile:

Also do you have a small repro case for this?

3 Likes

#46

1. Yes in 1.2.161 there isn’t this error.
2. I have created the repro case… It was a little bit difficult because sometimes the game apparently works… Apperently because some tiles are changed or flipped at runtime for no reason. This is the repro case:
ReproCase.zip (72.3 KB)

W A S D for moving character :laughing:

Edit: I have also found that if I remove animated tilemaps, the game seems to not crash, so the problem it’s probably related to the animated tilemap material.

2 Likes

#47

Thanks for the repo case, but I couldn’t get it to crash.
Next time you get it, could you please provide the _crash file, it contains the callstack for the crash.

1 Like

#48

I have it:
_crash.zip (17.7 KB)
(is the crash file of the Repro Case)

I don’t know what is the default folder for _crush file on Windows, so I used crash.set_file_path("_crash") in order to generate it on root folder.

2 Likes

#49

It should be in the APPDATA path on Windows. in any case the output should say where the file was saved.

1 Like

#50

Copy and paste this to explorer and press enter

%APPDATA%/Defold

1 Like

#51

@NecroRayder Unfortunately, I couldn’t symbolicate using those files you sent me, so I added more debug info in the engine. Could you try reproducing the issue with this engine?
Win64

(I’ve added more verbose callstack info in the _crash file for Windows, and also we’ll be logging the callstack directly to the output console as well)

3 Likes

#52

Here 2 crash dumps:

defold-crash-1.zip (17.5 KB)

defold-crash-2.zip (35.7 KB)

I think they are different, in the second one there is a png showing what i got in that try.
I have got these results after different tries because sometimes it crashes without write crash file or log in console, sometimes i get this:
Assertion failed: i < Size(), file C:\buildbot\slave\builds\engine-win32-64-dev\build\tmp\dynamo_home\sdk\include\dmsdk/dlib/array.h, line 410
and with this new dmengine sometimes I get the error showed in png.

1 Like

#53

Btw, that first link doesn’t work?

EDIT:
The second link worked fine, and I can now debug the callstack.
I now know where it crashes, it’s just not clear cut as to why. (fyi, it’s another tilemap issue :confused: )

EDIT2:
There will be a fix for this in the next release 1.2.162 (monday)

5 Likes

#54

Nice :muscle: :raised_hands: :raised_hands:

1 Like