Needing Help with W3 crashing whenever I quit from a Singleplayer Map (not World Edit)

Level 2
Joined
Sep 24, 2024
Messages
2
~If I am in the wrong forum, feel free to do anything with it, just let
someone solve my problem. Thank You~


New Member! Anyways, I am in the exact version of 1.29.2. I have upgraded from 1.24 to 1.27 to 1.29.2.
I have downloaded many maps that all work, no problem. However, I have been encountered a strange problem.
About a week ago, I encountered this: I was quitting from playing a map (a pretty large map), then all of a sudden,
the game black screens. After this, this behavior repeated when I was playing other smaller maps.

To connote,
This behavior does not appear on 2 of my other versions (I left them intact)

Thank you.
-Emperor of the Alliance, Gorrosh. :peasant-smile:
 
Last edited:
Level 34
Joined
May 14, 2021
Messages
1,598
New Member! Anyways, I am in the exact version of 1.29.2. I have upgraded from 1.24 to 1.27 to 1.29.2.
I'm pretty sure that you upgraded the game version in one way (from 1.24 to 1.27 to 1.29.2)? Or you've got all 3 of them separately?
There is no point in upgrading patches higher than 1.27b by normal way, since Blizzard removed this option to install older patches and forced you to use the "Classic" version of the latest patch.

I have downloaded many maps that all work, no problem. However, I have been encountered a strange problem.
About a week ago, I encountered this: I was quitting from playing a map (a pretty large map), then all of a sudden,
the game black screens. After this, this behavior repeated when I was playing other smaller maps.
What maps are you currently testing on? Melee or custom?
I played some custom melee maps on 1.29.2 and it worked without a problem when I resigned the game after clicking on "OK" during the post-game screen.
Some older maps (<2009) tend to bug if you are using the higher patches, so I think it might be the reason.
 
Level 2
Joined
Sep 24, 2024
Messages
2
I'm pretty sure that you upgraded the game version in one way (from 1.24 to 1.27 to 1.29.2)? Or you've got all 3 of them separately?
There is no point in upgrading patches higher than 1.27b by normal way, since Blizzard removed this option to install older patches and forced you to use the "Classic" version of the latest patch.
I've got all of them separately (I just copied my 1.27 directory then patched it so the installer just checks files (same with 1.24-1.27 change), change them and upgrades to 1.29.2, although, it was pretty hard, I had to resist and stand guard over the whole download to make sure Reforged doesn't download) - I got it from a post here. Hard to keep them intact. I also have no plan of upgrading 1.30 or .31 because of issues. (I got 1.29.2 early so it wont download Reforged)

What maps are you currently testing on? Melee or custom?
I played some custom melee maps on 1.29.2 and it worked without a problem when I resigned the game after clicking on "OK" during the post-game screen.
Some older maps (<2009) tend to bug if you are using the higher patches, so I think it might be the reason.
In every map it is almost the same situation, even those compatible with 1.29.2, idk why exactly, every time when i quit (press ok or quit mission/campaign/game). I does not happen with either 1.24 or 1.27 though.

Where I downloaded from -
WC3 Download Archive (1.00 - 1.31.1 + BETA & DEMO)
 
Last edited:
Level 34
Joined
May 14, 2021
Messages
1,598
I've got all of them separately (I just copied my 1.27 directory then patched it so the installer just checks files (same with 1.24-1.27 change), change them and upgrades to 1.29.2, although, it was pretty hard, I had to resist and stand guard over the whole download to make sure Reforged doesn't download) - I got it from a post here. Hard to keep them intact. I also have no plan of upgrading 1.30 or .31 because of issues. (I got 1.29.2 early so it wont download Reforged)


In every map it is almost the same situation, even those compatible with 1.29.2, idk why exactly, every time when i quit (press ok or quit mission/campaign/game). I does not happen with either 1.24 or 1.27 though.

Where I downloaded from -
WC3 Download Archive (1.00 - 1.31.1 + BETA & DEMO)
In my experiences, I had no problems with my maps on 1.29.2, though I only played a custom melee maps with triggers + modified AI scripts. I've also tested them on 1.26a. I think the map you are trying to play on will most likely have triggers that could cause memory leak-related issues, like the black screen you mentioned. You might need to do some research regarding this matter. It's extremely hard to find the source that's causing this memory leak problem considering you have to edit the map by yourself using World Editor, but there's a dedicated thread regarding this matter which can be found here. Events like "Unit Group" will always prone for the memory leak-related issues.

Of course, if you attempt to play regular maps on 1.31, the game will completely lock-up when you exited the game. Sadly, this is one of the bug that was present with the patch and was unfixed by Blizzard. I don't think if this problem still persists on the very latest patch (1.36). But since you are playing on the older patches, I can't give you an exact solution regarding this problem.
 
Top