[Crash] WE crashing on launch after having a imported model

[TheJassy]

As the title of this thread states... All my other maps that dont have an import of some sort are fine. The map is fine in game just World Editor that hates me.

 

[Ravager16829]

You might want to check out this thread. Someone had already encountered the similar problem before:

My map keeps crashing and its so bizzare..

Hey everyone , i hoped maybe some could help me because i cant figure it out.. Just like many other ppl , my maps started crashing after 1.33.. (fuck 1.33) But i could usually save them , even my 500mb+ map. I had tried to troubleshoot and find the models which would cause the crash , but it...

www.hiveworkshop.com

Usually, this happens because there are several imported files that made in BLP format, which is now corrupted.
Others said, you don't have memory to fit enough for World Editor. Current version of WE can consume a lot of RAM (up to 16 GB).

 

[HankHell69]

I can’t open any of my maps I’ve worked on but I can play it in WC3 and everything works... but I’m not done and I can’t work on it and it bugs me. When I had Quenching Mod I couldn’t even get to the main menu and it crashes. 1.33 is a disaster.

 

[Ravager16829]

I can’t open any of my maps I’ve worked on but I can play it in WC3 and everything works... but I’m not done and I can’t work on it and it bugs me. When I had Quenching Mod I couldn’t even get to the main menu and it crashes. 1.33 is a disaster.

You are right. The August 17, 2022 Patch is still buggy for now, even having a high consumption of RAM usage which can led to memory leak issues (game crashing).

The only possible thing you can do to is by using the older versions of WC3. If you have already backed up 1.32 (you can also get it from any websites, but I couldn't post the link due to the piracy rule), then you should be fine.

 

[TheJassy]

I can’t open any of my maps I’ve worked on but I can play it in WC3 and everything works... but I’m not done and I can’t work on it and it bugs me. When I had Quenching Mod I couldn’t even get to the main menu and it crashes. 1.33 is a disaster.

A temporary solution I found after posting this thread was to:

1. Open up the editor (not the map but just a new map)
2. Change the HD graphics to SD graphics (It wont fuck up the map)
3. Load your map that you can't open and delete the imported models
4. Change back from SD to HD

It's not really the best solution but I'll work for now.

 

[TheJassy]

You might want to check out this thread. Someone had already encountered the similar problem before:

My map keeps crashing and its so bizzare..

Hey everyone , i hoped maybe some could help me because i cant figure it out.. Just like many other ppl , my maps started crashing after 1.33.. (fuck 1.33) But i could usually save them , even my 500mb+ map. I had tried to troubleshoot and find the models which would cause the crash , but it...

www.hiveworkshop.com

Usually, this happens because there are several imported files that made in BLP format, which is now corrupted.
Others said, you don't have memory to fit enough for World Editor. Current version of WE can consume a lot of RAM (up to 16 GB).

I will check it out, Thank you so much

 

[Shandium]

I can’t open any of my maps I’ve worked on but I can play it in WC3 and everything works... but I’m not done and I can’t work on it and it bugs me. When I had Quenching Mod I couldn’t even get to the main menu and it crashes. 1.33 is a disaster.

Open your map with the MPQ editor and delete the models (usually the skins are the issue).

Once done , re-import them one by one , set them and reopen your map after every new model until you find which one of them is cursed (thats how i call it lol) and give up on that one.

I made a thread on whether there is a way to use a cursed model despite making your map crash but no luck until now..

Also technically , you could 99% run them without skins without any issue. They will just look white. Once finished , you can import your skin for one last time and then play your map without any issues , but you wont be able to reopen the map anymore until you delete the skin of the cursed model again with the MPQ editor..

Im hoping that a PC upgrade might be the solution but ill buy my parts in 1-2 months so i cant give an answer yet.

Your quenching mode issue probably is an issue of being outdated. Just uninstall it and reinstall 2.0 which was made for 1.33.

 

[HankHell69]

Open your map with the MPQ editor and delete the models (usually the skins are the issue).

Once done , re-import them one by one , set them and reopen your map after every new model until you find which one of them is cursed (thats how i call it lol) and give up on that one.

I made a thread on whether there is a way to use a cursed model despite making your map crash but no luck until now..

Also technically , you could 99% run them without skins without any issue. They will just look white. Once finished , you can import your skin for one last time and then play your map without any issues , but you wont be able to reopen the map anymore until you delete the skin of the cursed model again with the MPQ editor..

Im hoping that a PC upgrade might be the solution but ill buy my parts in 1-2 months so i cant give an answer yet.

Your quenching mode issue probably is an issue of being outdated. Just uninstall it and reinstall 2.0 which was made for 1.33.

The map I'm working on all the models, skins, etc. work just fine tested it out in WC3R. I just can't finish my map up until this issue is resolved. I have had that issue before where one skin texture messes up the entire map and corrupts all the models/skins I imported. When that happens a lot of the time I give up on that map because I hate having to reimport everything one by one and then retype the correct path for each... lol

 

[TheJassy]

The map I'm working on all the models, skins, etc. work just fine tested it out in WC3R. I just can't finish my map up until this issue is resolved. I have had that issue before where one skin texture messes up the entire map and corrupts all the models/skins I imported. When that happens a lot of the time I give up on that map because I hate having to reimport everything one by one and then retype the correct path for each... lol

Sadly for now I guess we'll have to stick to to only the things that can be found in the editor.

 

[Dreamshock]

Same issue for me, new patch totally screwed up my map. I was making map for 2 months around May but had to stop and recently i decided to reopen it only to find out that the map is bugged and cannot load half of the custom models i imported along with several scripts, cant even playtest the map, its ridicolous how blizzard managed to screw it all over again.

 

[TheJassy]

Same issue for me, new patch totally screwed up my map. I was making map for 2 months around May but had to stop and recently i decided to reopen it only to find out that the map is bugged and cannot load half of the custom models i imported along with several scripts, cant even playtest the map, its ridicolous how blizzard managed to screw it all over aga

Same issue for me, new patch totally screwed up my map. I was making map for 2 months around May but had to stop and recently i decided to reopen it only to find out that the map is bugged and cannot load half of the custom models i imported along with several scripts, cant even playtest the map, its ridicolous how blizzard managed to screw it all over again.

From what I've seen my method works till there is some proper resolved issue. All needed now is if you have the patience of removing and adding all the units onto the map