| 03-28-2004, 09:09 PM | #16 |
Suprising how much difference removing the brush list makes. I've found that I can run WE in the "High" priority with no choppiness (with 3-4 other programs open) on WE with just my slow 1.3GHz P4 and 256MB of PC800 RDRAM. (you do get just a bit of slowness when you load it up, but after that, it's nice.) Thanks for the tips man. |
| 03-29-2004, 12:28 AM | #17 | |
Quote:
The game already requires most of your resources to run... I don't think increasing the priority is beneficial, though increasing virtual RAM might be. |
| 03-29-2004, 02:59 AM | #18 |
You can go to Preferences and stop the editor from making a new map every time you start up the world editor to speed up the startup time. |
| 04-03-2004, 01:39 PM | #19 |
I find that lots of units really kill the processor... My system is fine with lots of doodads, but add a couple of units and it tries to commit suicide. |
| 04-16-2004, 03:59 PM | #20 |
When not using the main window, minimize it. Editing units and whatnot signifigantly improved on my aging machine. Macs could try doing the equivalent of minimizing, see if that helps. Obvious, but mentioned for completeness on the thread: Zoom in your clip plane (Ctrl+mousewheel) so you don't render more than you need. |
| 08-26-2004, 08:13 PM | #21 |
Does anyone else experience very brutal object editor lag? Anyone know a way to get around this? |
| 08-30-2004, 07:58 PM | #22 |
When you change object names and when you change editor suffix my machine trys to slit its wrists any ideas? |
| 11-10-2004, 10:34 AM | #23 |
One thing i use alot is the possibility to hide objects, i have an Highend PC, but still, i like it to run totally smoothly, also you can change the details in preferences, not recomended to set particles low, since it looks like crap... ;) Also one thing that cause tremendous lag on most computers is LAN, since it takes resources... Set your UL and DL lower to reduce overall lag on your computer.. |
| 01-10-2005, 12:00 PM | #24 | |
Guest | Quote:
|
| 02-02-2006, 05:52 PM | #25 |
I can't begin to say how useful this tutorial is, my text changing is instant now! I might start liking making units. Why shouldn't you use Realtime unless you have a superfast PC? Im using it, no trouble... Nevermind, found out why :(. |
| 02-02-2006, 09:22 PM | #26 |
Realtime means as far as I know, that process you set to Realtime never will run out of system resources, so for that process CPU and memory and disk too will be always ready to use, and that gets your system stuck easily. |
| 02-13-2006, 09:29 AM | #27 |
Trust me.. never set any program realtime. |
| 02-14-2006, 08:40 PM | #28 |
if you use realtime and the program is over your processor or ram & VM capabilities, your computer will most definatly crash, or go slow to the infinate power until its done with what it was doing, realtime is a HUGE risk, although i use it all the time my computer is very new and i have almost 6GB ram (6 1GB sticks) and a 4.7Ghz processor... |
| 03-29-2006, 08:57 PM | #29 | |
Quote:
Omg? ![]() You can also turn doodads/terrain/units on and off by pressing ctrl+d/+t or +u. |
| 04-12-2006, 11:32 AM | #30 |
I use realtime when unit editing, but for things like jass that dont require heavy resources, I just use high or even average. Dont use realtime if you have ANY other programs running. Msn/Google/Even antivirus programs. Generaly keeping theyse on with a realtime flagged program signs you up for a crash :P. |
