does anyone know about this ?

07/05/2017 06:47 andzia098#1
does any one know what ASSERT("MSGID:0x3019,R(39),W(39),T(1) stands for ?

it's the main problem that my arabian dungeon keeps crashing without a proper reason while everything is added perfectly, data and map do support arabia

here's the full dmp file :

[Only registered and activated users can see links. Click Here To Register...]

Update : im now 100% sure that the teleport is what causes the crash but no idea why as im sure it's added successfully both client and media side, anyway here are the lines of the teleport in both media, client side

Refobjcommon lines :



refobjstruct lines :


refteleport lines :





client side :

teleportbuilding lines :


teleportdata lines :



hope someone provides help as this problem has existed for almost 4 days now.

Thanks for reading and for any help trial

here's a screenshot from inside the dungeon where the teleport has no effect (can't crash me) while im far away from it but whenever i move towards it, an instant crash occurs.

[Only registered and activated users can see links. Click Here To Register...]
07/06/2017 21:57 guckguck#2
Hello,

In my eyes there is nothing to see within your dmp file. It is very hard to find your problem if you share only a minimum information.

My suggestion:
- upload all related media files to check for formating errors
- add missing dungeon information: dungeon based type <> overworld ?, world ID is 112 I guess?
- Do you crash on start_gate and/or end_gate?
- remove all teleport information out of your db/client and leave only the model (it is 0?) to check your data.pk2 information or use a working old type of teleport, because...
- in case your teleport information is wrong you should be able to see the model and talk with it, but you might crash during teleport
- you can also use a different (working) teleport model (Alexandria teleport, Qin-Shi teleport...)
- you can also try to add a different target for end_gate (e.g. jangan town teleport) to check your teleport information
- you can also try to "add" some wrong information to a known, working teleport to study crash behavior till you see something similar
- please create multiple dmp files and share them, sometimes you can see different stuff inside...
- teleportlink is (not) missing?
- SN_STORE_ARABIA_DUNGEON_START_GATE text file is right formatted too?

My personal experience with dungeon teleports:
- model missing/wrong -> crash on sight
- teleportdata wrong -> crash on teleport
- wrong dungeon start point and/or Z-height -> crash on spawn
- wrong world ID -> crash on teleport