Zontik on 12/4/2016 at 10:51
There is a problem I noticed. When turned off, the object with NVPhantomTrap on it dissolves and finally stops at unknown value about 0.01. It isn't zero, because I still can see the object if the light is bright enough.
My Design Note is:
Quote:
NVPhantomAlphaMax=1; NVPhantomAlphaMin=0; NVPhantomFadeOn=4000; NVPhantomFadeOff=1
What I do wrong?
New Dark, version 1.23.
I tried to set Transparency property to 0 - is works good at mission start, but after single cycle on/off the object returns to its visibility.
I tried also to set 0.00 in NVPhantomAlphaMin parameter, with no luck.
Nameless Voice on 12/4/2016 at 21:39
Oh, that's a regression. NVPhantomTrap used to have an option to set Render Type to None when the alpha reached zero, it looks like that functionality was lost when I rewrote the script back in v1.2.0.
I've re-added (and documented) those options.
LarryG on 13/4/2016 at 00:23
Quote Posted by R Soul
NVPhantomTrap sends PhantomOn and PhantomOff messages to itself ...
Please add the documentation for these messages as well. They are very handy for triggering other events and without documentation most won't know that they exist.
Zontik on 13/4/2016 at 06:06
I'm one of the most.
Having the documentation is great, but I always suspected that it was not full.
Thank you for help!
Nameless Voice on 13/4/2016 at 18:24
The documentation does mention that it sends a message to all affected objects when they finish fading, but it's a bit hard to find because it's in the documentation for the parent script (NVGenericScalarTrap) instead, and doesn't actually specify what the messages are for the child scripts, or that the parameters to set it change to match the name of the child script.
I've copied and adjusted the line for both NVGlowTrap and NVPhantomTrap now.
LarryG on 14/4/2016 at 02:31
Thank you.
