| 08-19-2002, 07:44 AM | #1 |
Guest | Are there any limits on triggers in wc3? Im making a map, and it seems that wc3 suddenly crashes at periodic times depending on the amount of triggers that i have executed. It spits out an error that it cant read memory. Any suggestions for me to fix this problem would be appreciated. Note: it has under 50 triggers >_< |
| 08-19-2002, 07:50 AM | #2 |
No there are no limits but obviously you need to delete a few items off your computer, like programs or games you dont use, the reboot your computer, if you have you desktop even half full that causes a problem also. And maby if you havn't recently emptied your recycle bin that might be a good idea. |
| 08-19-2002, 07:52 AM | #3 |
Wait I just re read that, cant read memory, hmm if thats exact then i can't help you there, iv never run into that problem. well your a SupahGenious you'll figure it out. sorry couldn't help it. |
| 08-19-2002, 07:54 AM | #4 |
Guest | lol trust me.. its not my computers fault.. brought it ot battle.net and everyone crashes at the same time (+ i have 512 mb of sdram, and when i boot, i run explorer, and systray :) ) Edit: ive been trying to figure it out for days now >_< |
| 08-19-2002, 02:37 PM | #5 |
Guest | I got the same thing last night... my partner and I were playing a creeping map (Look at infoceptor's front page) and both got a could not read memory and crashed out. Then my whole PC crashed about five minutes after. |
| 08-19-2002, 03:43 PM | #6 |
Guest | I never had any problem since the retail version, but it would be interesting to know what kind of triggers crash the game (or maybe it is due to your computer), especially in multiplayer maps. I don't think this is due to the number of triggers you used, unless they all happened at the same time and overloaded your memory (but I doubt about this since W3 seems to have a good control of concurrency). |