SFX no longer visible

[RiotZ]

Special Effect - Create a special effect at (Position of (Triggering unit)) using war3mapImported\NewDirtEXNofire.mdx


This doesn't do anything.

Using TempLoc for the location also doesn't do anything.

However attaching it to a unit still shows the special effect.

Excuse my language but what the fuck? I've never seen this bug before and it's extremely unsettling.

Edit: This doesn't work so it's not the custom model.
Special Effect - Create a special effect at (Position of (Triggering unit)) using Abilities\Spells\Human\Thunderclap\ThunderClapCaster.mdl

I'm checking if there's a broken trigger that runs on "A Unit Dies" since that's what these triggers run on. However I believe I've already done this check and found that in triggers where I assess damage using the position of a dying unit, the damage STILL works, the special effects just don't show up.

 

[A]mun]

Well please post your trigger, maybe it's just a small oversight.

 

[RiotZ]

Everything works BUT the special effect.

 

[Jampion]

I don't see any obvious mistake, so I would recommend doing some debug steps.

Use "game text message" to verify that the trigger runs. You could display the x and y coordinates of temp loc.
Do something else at TempLoc to see where it is, for example creating a unit.
Remove "Destroy Special Effect" to see if the special effect is removed immediatly.

 

[RiotZ]

I don't see any obvious mistake, so I would recommend doing some debug steps.

Use "game text message" to verify that the trigger runs. You could display the x and y coordinates of temp loc.
Do something else at TempLoc to see where it is, for example creating a unit.
Remove "Destroy Special Effect" to see if the special effect is removed immediatly.

I did all of this. The loc returned is correct, even when using TempLoc, I am positive as I used multiple debug methods. I removed the destroy sfx function, still does not show up.

I am lost.

 

[Jampion]

Have you tried different models?
Make sure spell detail is set to high in the options. I don't know if that could cause this, but rather check it.
I am pretty sure I used this special effect and had no problem. The only thing I can think of is something model related, so either graphic settings or imported models/skins changing the special effect.

 

[RiotZ]

I checked Blizzard generic SFX, none of them show up. When I make the a dummy unit have a SFX for its model, that doesn't show up either.

 

[Jampion]

First try this:
make a custom script below the destroy sfx: set bj_lastCreatedEffect = null

I quickly tested it and it works fine for me.
I would try it on a new map to get it work there. If it works there something in your map is wrong or the map is somehow corrupted, but I doubt a corruption would cause this.
Try to disable all your triggers except this one (duplicate your map before that) and see if it works.

If you say the models don't work at all (even if you set a unit to have this model), it's not trigger related of course.

 

[RiotZ]

First try this:
make a custom script below the destroy sfx: set bj_lastCreatedEffect = null

I quickly tested it and it works fine for me.
I would try it on a new map to get it work there. If it works there something in your map is wrong or the map is somehow corrupted, but I doubt a corruption would cause this.
Try to disable all your triggers except this one (duplicate your map before that) and see if it works.

If you say the models don't work at all (even if you set a unit to have this model), it's not trigger related of course.

I tested some other maps, seems to be a WC3-engine-related bug.

 

[Halo7568]

Has your computer been on for a long time? Alternatively, I think with some newer Windows versions, you might be setup in such a way that your computer is not doing a full shutdown when going through the typical menus. There is some bug with effects being invisible due to, what I imagine is, some clock value not being reset. This happens in, but may not be limited to, the two cases I mentioned above.

Anyway, one way to check if this is the cause is to turn off your computer through the command prompt like so:
- Press the Windows key + R to bring up the run dialog
- type "cmd" (without quotes) and press enter
- in the resulting command prompt, type: shutdown /s /t 0
- press enter
- the above command should do a full shutdown, so just turn the computer back on afterwards and see if the bug is still there

 

[RiotZ]

Cold booting my computer fixed it. Weird.

 

[Dr Super Good]

For anyone coming across this...

This problem is caused by the graphic drivers getting into some kind of buggy state. At the time of posting there is no known direct cause however it is associated with the driver having a very long life time. Be aware that the graphic drivers are only loaded on computer start up. Resuming from hybrid sleep (Windows 8 and 10 standard shutdown mode) will not restart the graphic drivers. Easiest way to restart them is to restart the computer.

 

[A]mun]

Yep, that's another one for the archive - never stop learning.