Reply With QuoteQuick question. Will this version work on win7 ?
note: i can't get Temple of Tides to work at all.
made my day... thank youOriginally Posted by Daraan
Easier way without script(thanks to 1.19)
New Tweqs CurveC -> Pendulum
that really looks a bit more realistic
X in swings per second, Y,Z like normal
only bad thing Y/Z must be between[-31..0]/[0...31]
(so it should work for your clock
lol, there are so many new features that i almost forgot to look what's new
Quick question. Will this version work on win7 ?
note: i can't get Temple of Tides to work at all.
I never had any trouble with it in Windows 7.
If you're having trouble with The Temple of the Tides, try putting the latest version on NVScript.osm in place of the Mayan.osm in the package. (Mayan.osm is just a renamed older version of NVScript.osm.)
Added a newly-built version of NVDebug.
No changes to functionality, but it should fix the issue with the script module sometimes failing to load.
Saw a "NVScriptFX.osm" recently. What's that? Was that a beta version that eventually became incorporated into NVScript? The mission had both NVScript and NVScriptFX loaded.
No idea, I've never heard of NVScriptFX.
What mission was this? Maybe NVScriptFX was some private build that I made for someone, but then it doesn't make sense to have both modules loaded, since all private builds contain all the usual scripts, too...
To actually build a new module would involve playing around with the makefiles, I'm generally not too eager to do that.
Last edited by Nameless Voice; 5th Jan 2013 at 04:41.
This was Sliptip's FXDemo. It seems odd to me too, which is why I asked. But these are the scripts loaded:
I guess it's just nvscript renamed then to make sure the correct version is used, and Sliptip forgot to drop nvscript.Code:Script modules in mission: 'nvscriptfx' 'nvscript' 'convict' 'gen'
Updated to v.1.2.4.
This is mostly to make an official version with all the recent fixes that I've given to various people privately, though it also has a few new scripts and features since v.1.2.3.
Note that the System Shock 2 version of NVScript may require NewDark 2.4.4 or higher (specifically, using NVPlayerScript from it will crash older versions.)
NV: You don't mention the fix to NVSafeDoor. Should I assume that fix is NOT included or is that in the "various fixes" category?
That's included, just not specifically mentioned.
For reference: NVSafeDoor was buggy in various ways, and it is now fixed.
Thanks NV!
A few errors in the documentation:
The internal link of NVWakePhysicsTrap goes to #NVWatchMeTrap
The description of NVWatchMeTrap is written twice.
The list at the top says NVTrapSetQVar doesn't work in T2.
For those who want a fixed version of the NVScript.html documentation before NV gets around to it.
I vaguely recall there are some documentation items to fix other than the ones that R Soul mentions, but I can't find them now, so I only corrected the ones he pointed out.
Thanks, Larry!
Should we update the thread title, then?
I don't get it. Exactly how would you use it for that?As of v1.2.4, you can use <kbd style="font-family: 'Courier New', Courier, mono; font-weight: bold; color: rgb(0, 0, 102); font-size: small;">NVLinkBuilderModifyExistingLink=1</kbd> to modify the data of existing link (if it exists), instead of creating a new one. The first matching link is used. Note that modifying the data (instead of removing and adding a new link) allows you to avoid behaviour such as attached objects automatically being deleted when the attachment link is removed.
If the link you were going to create (to, from, flavour) already exists, then the data on that will be set instead of creating a new link.
Yes please. Changing the first-post title used to do that, but it doesn't seem to do so anymore.
Yeah, I'm not sure when that changed. But it's done now.
This might explain why I have a different 1.2.4. Was wondering why the new(the one larry posted few posts above) was only roughly half the size. Old one was 1.11MB.
So i kept both for 'savety'.
--
And instantly a problem popped up:
I have a setup with
NVMetaTrapTarget="^physical"
which results in the following crash
Reverting back to the other 1.2.4 or to 1.2.3 it's working as it did earlier.Code:Crash message: Link to invalid source or dest. ( 0 --> MetaID
After a lot of testing it seems the problem is fixed when I use "^:physical".
But I'm not sure if you changed something there and this is now the correct way to do? Maybe that's one of the missing documentations Larry talked about?
-------------------------------------------------------------
Secondly I would like to ask if you could modify the NVTrigOBB to behave like the TrigOBBSpec script. So that you can actually choose the archetypes which triggers it. (best would be with a choosable MetaProp (instead/additionally to M-NotifyRegion).
Until now I have a setup which triggers at PhysEnter, but to get a hold on the target to add a metaprop and links I need the .target=^physical
But it's not a 100% save method but it works as intended but can fails when other elements like decoration are to close.
EDIT:
Maybe better alternative: If you could target the first/last object linked with a specific type like "^&Population" this would be a great and could be used elsewhere as well since sometimes only one object is linked.
Last edited by Daraan; 1st May 2016 at 10:07.
It's smaller because it was compiled in a different IDE. The same scripts should all still be there.
What's ^:Physical even supposed to do? Wouldn't that try to find the nearest object that descends from some non-existent ":Physical" archetype?
Well it needs to find the closest physical(-7) object. Yah
Since ^physical somehow doesn't work anymore I tried ^: similar to range detection ^<4:
All I can say with ^: it works
Try the new version of NVTrigOBB (see first post.)
Splendid!
That is definitely neither a trouchuss nor a greejus!
Splendid, indeed. I will check it out. Thanks a lot.
I'm not getting that.
Sorry, it's a reference to a certain thread in CommChat, and not important.
It's a genius bonus. Or possibly a genious bonus!
Posting Permissions