| 08-19-2002, 05:23 AM | #1 |
Guest | I was fiddling around with a test map which I made at the smallest possible scale: 32x32. When I happened to import my unit mod and begin to edit, I noticed that instead of the usual 5 second delays after every change I made, there was only a 2 second delay. Apparently the size of the map directly affects the delays experienced when changing unit data in the WE. So then, when editing your units do all your work on a tiny test map and you'll save tons of time per entry. Hope this is useful to someone. Take care. |
| 08-19-2002, 07:34 AM | #2 |
sweet thanks! oh and by the way, are you gonna update your LOTR mod anytime soon? |
| 08-19-2002, 08:08 AM | #3 | |
Guest | Quote:
Been working lots on 3.0 changes last several days, as well as a 224x448 Isengard and Helm's Deep map. Basic Orc units are in place. Working on Rohan units now. After that I plan on working on the Ents of Fangorn. The map itself is taking forever. 224x448 is *big*! It takes a Rohirrim mounted unit moving at 480 ages to go from one long end to the other. Got Isengard in place with surrounding Wizard's Vale (Nan Curunir). Need to do some detail work on Fangorn. The Isen River is in place as well, along with Isen Ford. Got to begin work on southern mountains and Helm's Deep. Back to work. Care. |
| 08-19-2002, 09:09 AM | #4 |
Guest | well, I KNOW that at that size, the map is very hard to edit fast =). was creating a 256x256 map and boy, it took a while before I finished about 1/4 of the map because editor is lagging |
| 08-19-2002, 04:42 PM | #5 |
Closing the pallete may help a bit as it will reset the palete each time you change something (I checked (don't leave it on nuetral if you ahve every unit unlocked)> |
| 08-19-2002, 07:22 PM | #6 | |
Guest | Quote:
There we go! That's good advice. I've noticed that it does that. It would be nice if they made it so we can open up the Unit Module all by itself. Thanks. |