| 06-10-2003, 06:59 PM | #1 |
Hey, if you dont know, im making turret wars, almost finished with it, hope to have it done within the next few weeks. Ive been privately beta testing lately, and running into the same problem over and over. PROBLEM: After about an hour of gameplay, my computer starts to lag like a |3*^(#. Then about 10 minutes after the lag starts, WC3 crashes, and it says that i ran out of memory. Im using my brothers computer, and its fairly new, and really good, so i know its not the fact i have a bad computer. Solution needed: Is there anything that i can do to cut down on the memory intake the game uses? I was thinking maybe if i paused everything for like 2-3 minutes, and then unpaused everything, that might help give a sorta intermission. But, if there is anything anybody knows of what i can do, or, what it is that takes up alot of memory, please Email me at: [email protected] Thank you. If you can figure this little problem of mine out, or lead me on the path to fixing it, i will definately add you to the credits. thank you. |
| 06-10-2003, 07:23 PM | #2 |
Sounds weird. Maybe an infinite loop going on somewhere too fast doing too many things. Can I see the triggers on the map? Could also be hardware related though. Check if your power supply is good enough, and if your computer isnt getting too hot, or is infected with a virus. |
| 06-10-2003, 07:30 PM | #3 |
I'm thinking it's one of the following... 1. Too many units are present on screen and are given rders/commands around the same time. This can cause confusion in your system and the queu limit can be overrun. Make a mentla note by looking at the screen at how many units and buildings are present at the time and what they are all doing. Might be the special effects for the projectile they are using also. 2. Too many tirggers trying to function. Could have a problem with your trigger system also. Maybe too many lines of code being executed over a set amount of time.. Periodic Event triggers can cause this if there are too many or if the task they are performing every second or so is too large to handle. 3. Terrain and doodads with the units.. Also when checking your units.. Make sure you note your terrain.. the size of the map and how many doodads you placed.. See if you can skimp here and there from it... 4. Too long of game? I'm trying to think about what turret wars would be like.. I'm thinking of the old starcraft game if it is that.. you shouldn't be having problems at all.. And it shouldn't be that long... You can send the map to me via [email protected] and I can check through the triggers and everything and perform a couple of tests for you if you'd like. My best guess is number 2 though. But I could be wrong... |
| 06-10-2003, 07:39 PM | #4 |
How much RAM does your brother's comp have? if less then 256 that could be your problem.although wc3 is said to run with 128 it cant really well...also u might want to close any processes that are working in the background on your comp...the easiest way would be to just go out and by 64 mb of ram stick for like 30-40$ not much....If u dont want to do that just make sure all other programs are closed....and also too many variables being overused at one time can cause memory errors... |
