HomeUser Control Panel (unavailable in archive)ForumsTutorialsArt GalleryResourcesMaps

Windows XP Nightmare!

09-10-2002, 05:06 AM#1
FM_TertiaryEye
Hello,

Im using worldedit under windows XP and everything was running smooth until i started really adding trees. I have a map thats only 160 x 160, and i only have a bit over 200 of them. But all of a sudden everytime i try to add a tree, im waiting for 5-7 seconds for a tree to appear.

This map isnt overly detailed, its only 128kb and it doesnt have much that every other map has, its basically run of the mill in terms of complexity.

Another huge problem is changing values in the unit editor, evertime i set something as simlple as an int, it takes at lest 4-5 seconds for it to show up during which the editor completely freezes of course. That wouldnt be so bad IF I didnt have to change the values of 28 creeps :P

I sent this to a buddy who had Win Xp as well and he had the exact same bug, i think it has something to do with machines with higher memory, (other programs have claimed that they would run poorly in winXP on machines with over 512MB ram). Here's my system specs.

1.5 Gig Ram
AthalonXP 1.2 GHZ
WindowsXP Pro
Geforce4 ti4400

Does anyone else have this problem? Is there a workaround for systems with this problem? If anyone can help it would be appriceated, its gotten to be so bad that i can't even complete my map.

Thanks,
Jason
09-10-2002, 06:02 AM#2
Guest
its not your system the WE is just slow like that, no matter what.
09-10-2002, 08:56 AM#3
Guest
The unit editor is just slow. Nothing you can do about it.

It shouldn't be taking that long for a tree to appear though, but it does slow down the more thats on your map. Try turning some of the details off like Lighting, Shadows etc to see if that helps. If you're zoomed out a long ways, try zooming in a bit, don't have the game running in the background, and make sure you don't have multiple maps open at the same time.
09-10-2002, 11:31 PM#4
Guest
Yeah, it does that. Did you put down structures or units before you started placing trees? That could also be a problem. At least thats better than actually going over the destructible doodad limit and not being able to save (DOH!:( ).
09-10-2002, 11:55 PM#5
FM_TertiaryEye
Hmmm, no unfortunately i have been making terrain changes, adding doodads, placing triggers, making custom units, and placing units all on a region-by-region basis.

So thats one of the problems eh? Well i will certainly try to remember that next time.

Thanks again everyone for your advice, im glad there are peeps online who apply their knowledge in a helpful way.

Gracias!
jason
09-12-2002, 02:51 AM#6
Guest
I have that problem with XP too, I never played this game on anything else though. Start positions make my editor lag like crazy, so get rid of them until you save.
09-12-2002, 06:33 AM#7
Guest
just remember, world editor is the BIGGEST system resources hogger you have on your system. ;)
09-12-2002, 05:06 PM#8
Guest
I had this problem too.
My map Odin's Rage RPG has more than 6000 doodads, about a thousand units, and it's 192x192...I didn't have problems with the triggers but it was a hell to design the map properly. I had 10-20 secs delay to design large areas of water, and about 20-30 secs delay to design high mountains and ramps..
I hope Blizzard fix this bug, this is the worst nightmare for mappers..
10-23-2002, 12:45 PM#9
iceslushee
i thought this is sorta in the veign of winxp im just doing RIS at the moment and am trying to do an unatended install of xp on a client machine im hoping someone in here knows what im talkin about and knows that it cant be done cos of the asms error but there is a way around it... so please tell me!?
10-24-2002, 06:11 AM#10
Guest
Try running WE just after startup, before you do a lot of other things and see if it makes a difference.

Maclu - You should not even have that much memory in a computer. Thats practically a sin. Get a faster Athlon if you have that much memory. hehe. Trying to access massive amounts of ram is a draw back. Unless you need it for something very important. :)