Visibility/Weather Random Number Problems

This is from the battle.net thread I posted:

Ok, so these things SHOULD be pretty streight-forward. Visibility mods and weather effects.

Create a visibility modifier over a region. Assign the mod to a variable. Later in the game, I try to destroy the modifier. NOT WORKING. Turn the mod off. Still not working (well, fog of war covers the region for a split second, and then visibility appears again). GRRR!!!

Same with timers. SOMETIMES they work, and SOMETIMES they don't.

Weather Effects: When I first made my map I had a weather effect over a region. Worked perfectly. Now, the effect stopped working, and I can't get IT NOR any other effect to work.

WHY ME!?!?

Also, it seems now that Random isn't quite so random anymore, either.

Variable is initialized to 0 at start of map.

Later on, it is given a random value between 1 and 8. ALWAYS (Without Fail) it's first value returns 7. (Same with Random unit from unit group-- It ALWAYS picks a unit owned by player 1.)

Not quite so random to me.

Any ideas? I think World Edit is related to Forrest Gump or something, I'm sensing some serious lack of IQ on behalf of it. And some serious frustration on my side.

Thanks in advance...

If you have a cinematic of any kind, I believe that makes all random numbers the same. I think their is a custom-text trigger to fix this however.

I can confirm Draco's comment: entering cinematic mode turns off the ability to have random numbers. Two ways around this:

1) Use custum text to restore the random number seed (not easy, if you don't know jass)

2) instead of entering cinematic mode, manually enter letterbox mode and remove user control. This is a good approximation of cinematic mode.

Create a visibility modifier over a region. Assign the mod to a variable. Later in the game, I try to destroy the modifier. NOT WORKING. Turn the mod off. Still not working (well, fog of war covers the region for a split second, and then visibility appears again). GRRR!!!

Strange... it works here...
See if you are not creating multiple Visibility modifiers (i.e.: verify if the trigger that creates it and assign the variable can only be run once), because you may be creating several of them and assign only the last one to the variable.

Same with timers. SOMETIMES they work, and SOMETIMES they don't.

Look above. It may be the same problem.

Weather Effects: When I first made my map I had a weather effect over a region. Worked perfectly. Now, the effect stopped working, and I can't get IT NOR any other effect to work.

See if Particles in the video settings is set to at least Medium. Low Particles won't allow you to see Weather effects.

UPDATE:

I can now confirm that "Test Map" caused all of the problems that I mentioned (the only problem that i've not tested yet is the visibility modifiers).

I uninstalled and then reinstalled Warcraft 3, and now everything works pretty much perfectly.

So a word of advice from another victim (this is probably redundant to all of you, but I guess I can just confirm it): DO NOT USE THE "TEST MAP" FUNCTION! NEVER!

As for the random numbers: Seems to me that "Test map" screwed up the first random number seed for every trigger where one is run. If you have EVER pressed "test map," I'd highly suggest and recommend that you uninstall Warcraft 3, and then reinstall it. I can't believe how many permanent damages (to warcraft, the game itself!) were caused because of it.

Thanx for all the replies, and look for my map online soon :D

I always use it :)

I keep forgetting to tell ppl not to use test map, because I thought everyone knew now why NOT to use it. Oh well.

EEK! I used the test map and now Im having problems with random (units wont spawn at random location)!! Do i really have to uninstal WC3 and reinstal???

I would advise it, since I couldn't find any other way to fix it.

"Test Map" even caused some of the single-player campaign missions to stop working properly for me.

Reinstalling isn't going to fix anyone's map editor problems.

Both cinematic mode AND test map stop random numbers.

80% of the time if it's doing something funky, it's your triggers, not the editor $!@#ing up. (The other 20% of the time the editor is doing wierd, undocumented stuff, like giving your buildings blue colored lighting if you give them a flying height of 5000)