[QUESTION] Unknown Crash

[Смердокрыл]

Hey!
I downported the Wandering Isle from early MoP to Cata (well, I just copy-pasted it). When I log in a character that is flying above the isle, he obviously starts falling down. At that moment, I can see stuff below like trees, a bridge, etc. And then wow crashes with a #132 error. Problem is: there are so many files I copied (all the wmos, objects, etc) that I cant possibly guess what causes the crash. And the error log is written in elvish.

Could anyone help, please?

P.S. I attach the error log in case there is a nathrezim here, since their race is known for the ability to understand any language.
[attachment=0:13rqloft]2015-10-16 20.01.09 Crash.txt[/attachment:13rqloft]

[Смердокрыл]

Its not the map itself, since when I only had the wdt, wdl and adt files, nothing crashed. Has to be something smaller, like a wmo.

[Amaroth]

The only idea I have is making gameobjects of all models you have and spawning them somewhere in map which works. You can test by this which model works and which not. I have Python script which can do that model to gamobject conversion part, and I also know a way how to spawn like 50 gobs with different entries at once, so you don't have to check downported models one by one.

If interrested, you should probably contact me via Skype striker159753. Or we can solve it here, but that will be unneccerily slow.

[Смердокрыл]

Surprisingly enough, I dont have skype. Besides, if we do it here, other people with a similar problem can follow.

[Amaroth]

*sigh*
I will need your GameObjectDisplayInfo.dbc. If you haven't modded this DBC yet, just let me know and I will use blizzlike one. I also need (listfile) file(s?) extracted from your MPQ(s?) where you keep your down-ported models from newer datadiscs. I also need some gameobject entry from which I can start and where you have space. For instance, if you have no gameobjects with entry 600 000 and higher in gameobject_template table in database, let me know that I can safely place my generated gobs there.

I will send you SQL file to add gameobejcts into database and modded DBC which will contain new gameobject displayIDs. You will need to update that DBC in both your client's MPQs and in server data folder.

If you don't want to spawn test gobs one by one to check if they work, you can use following command by placing it into chat box ingame:
[code]/run for i=55000,55149 do SendChatMessage(".gob add "..i) end;/code]
Just edit those 2 values for i. This command would spawn all gobs with entry 55000-55149, so 150 different gobs would be spawned on place where you stand. Btw, you can modify command in "", so you can use this statement for whatever else you might want to use it, for instance for quickly filling NPC vendor with custom-made items or such tasks. With this method, you can easily check which models in path are giving you crashes. This is btw useful also for spawning gobs, because with a little modification will my gob-generating method lead to possibility to search for gobs in WMV while my gobs have the same name as their models have.

Buut before we do all this, just make sure your ADTs are alright. I have no experience with retro-porting entire maps, so if problem occured there, you will be the one who will have to deal with it. I can't help you with that particular matter. In fact, I will just help you find out what is giving crashes. Fixing model itself might need either help from someone more familiar with WoW 3D models or replacing/deleting that model from map.

[Смердокрыл]

Before I send you all the required files, is it not possible to find the reason of the crash in the crash log? If it isnt, why even have crash logs?

[Amaroth]

To find out what type of crash you have. If you know exceptions (yours is 0xC0000005 (ACCESS_VIOLATION) at 0023:00E06EC9), you can just see wth went wrong. Check this thread for more info:
http://modcraft.io/viewtopic.php?f=12&t=2971

You can also find something out in the rest of log if you are more experienced, but thats not for instance my case. Anyway, it may or may not help you, it really depends on situation. Most of crashes tend to be already known exceptions for us. There are also a few exceptions which are not described in that topic, but they are generally known as "the ones which appear when your retro-porting process isn't finished/is messed up". Most common are particle errors.

[Смердокрыл]

I am terribly sorry that you had to write that giant message.
There is nothing wrong with the wmos. I just had to change a single value in the wdt via 010 editor.
I am, again, sorry, and thankful for your help.

[Amaroth]

Nvm, it still might server someone else.