{"id":1317,"date":"2017-11-27T05:51:20","date_gmt":"2017-11-27T12:51:20","guid":{"rendered":"http:\/\/artistedancediva.co.uk\/wp\/?page_id=1317"},"modified":"2018-04-07T15:58:40","modified_gmt":"2018-04-07T21:58:40","slug":"bk13-the-artiste-book-set-rezzer-v3-1","status":"publish","type":"page","link":"https:\/\/artistedancediva.co.uk\/wp\/?page_id=1317","title":{"rendered":"BK13 &#8211; The Artiste &#8211; Book &#8211; Set Rezzer &#8211; v3.1"},"content":{"rendered":"<p>Nov. 27, 2017 &#8211; NEW! On *setrezzer a new entry called FastReRez.\u00a0 It will default to &#8220;on&#8221; and was implemented to address slow rerezzing after a MasterReset. The caveat is that you will always need to save (copy child-object back into MasterRezzer replacing any existing) in order for it to work.<\/p>\n<p>It appears everyone always saves their latest moves permanently. If so then this aids in rezzes as fast as the Initial rez.<\/p>\n<p>&nbsp;<\/p>\n<p>There is also a FastReRezOn\/FastReRezOff toggle button on the main menu of the MasterRezzer.<\/p>\n<p>Turn this ON for fast rezzes after the initial rez after a MasterReset.\u00a0 After the initial rez, the <strong>RezDelay<\/strong> kicks in and can annoy those in a hurry. The caveat is that the <strong>MasterRezzer<\/strong> wont remember moves or rotations after the initial rez.\u00a0 So you would need to copy objects into the MasterRezzer if you move or rotate them after the initial rez upon MasterReset.<\/p>\n<p>So remember to turn this OFF before going to the show venue\u00a0 because you probably want to rez the MasterRezzer and Rotate your sets BEFORE you lock them.<\/p>\n<p>Note that this button only works if <strong>FastReRez<\/strong>,on in the *<strong>setmaster<\/strong>.<\/p>\n<p>***********<\/p>\n<p>There is another feature implemented that uses a new <strong>*rezdelays nc<\/strong> in the MasterRezzer<\/p>\n<p><strong>ChildName<\/strong>, <strong>seconds-to-delay<\/strong> after rez-at-master before moving and rotation.<\/p>\n<p>Ex:<\/p>\n<p><strong>*rezdelays<\/strong><br \/>\n<strong><span style=\"color: #0000ff;\">FaderScreen<\/span>,<span style=\"color: #ff0000;\">4.0<\/span><\/strong><\/p>\n<p>This value will <strong>OVERRIDE<\/strong> the <strong>RezDelay<\/strong>\u00a0 value in the <strong>MasterRezzer<\/strong>. This is meant to be used for troubling children that are complex with mesh or that contains a lot of prims on an individual level and not force every child to delay a long time when only those who need it are impacted.\u00a0 This <strong>RezDelay<\/strong> value on the *<strong>setmaster<\/strong> applies to ALL objects in ALL sets.\u00a0 This is why its preferred that you use the *<strong>rezdelays<\/strong> nc entries instead.<\/p>\n<p>There is also a new entry on the <strong>*setchild nc<\/strong> called <strong>DelayAfterRez. <\/strong>It should always have a value of at least <span style=\"color: #ff0000;\"><strong>1.0<\/strong> <\/span>seconds.\u00a0 In cases where a child-object is <span style=\"color: #0000ff;\"><strong>duplicated<\/strong><\/span> or is <strong><span style=\"color: #0000ff;\">left inside the MasterRezzer<\/span><\/strong> but <strong>rezzed<\/strong>, bump this value up to <strong><span style=\"color: #ff0000;\">2.0<\/span> <\/strong>or <strong><span style=\"color: #ff0000;\">3.0<\/span><\/strong>.\u00a0 What happens is with a lot\u00a0 objects that want to rez farther away than 10m from the MasterRezzer, you may get a <span style=\"color: #ff0000;\"><strong>troubled rez<\/strong><\/span>.\u00a0 The MasterRezzer moves to where the child-object needs to be rezzed at and then rezzes the child-object in place with a zero-offset.\u00a0 This gets around the maximum of 10m.\u00a0 But if the object tries to rezz before the MasterRezzer can move into position, you will get a failed anomaly as discussed above.\u00a0 This new entry <span style=\"color: #0000ff;\"><strong>delays<\/strong> <\/span>the rez-in-place until the MasterRezzer has had a chance to complete its move into position.<\/p>\n<p>&nbsp;<\/p>\n<p>I replaced <strong>DblExposure<\/strong> with <strong>KillAll<\/strong>&#8230;..this will kill all sets rezzed instead of only the last set selected.\u00a0 You can still execute <strong>DblExposure<\/strong> by using a local chat command using.\u00a0using the <strong>RemoteChatChannel<\/strong>.<\/p>\n<p>Also I replaced <strong>ComeHome<\/strong> with <strong>FastReRezOn\/Off.\u00a0 \u00a0<\/strong>You can still execute <strong>ComeHome \u00a0<\/strong>by using a local chat using the <strong>RemoteChatChannel<\/strong>.<\/p>\n<p><span style=\"color: #ff0000;\"><strong>NEW Set Rezzer 3.79 Released on April 7th, 2018<\/strong><\/span><\/p>\n<p>&nbsp;<\/p>\n<p>If you have a monster set that is big as in lots of objects and\/or very high in LI (land impact) there are options when using the ArtisteSet Rezzer.<\/p>\n<p>1 Pre-Cache your set seems to help the most<\/p>\n<p>2 Use the new DelayAfterRez entry in the *setchild to allow more time for the rezzer to move<\/p>\n<p>3 Use the RezDelay entry in the *setmaster. There is NEVER a reason to rez fast. You can rez a set hidden then fade or show it when needed.<\/p>\n<p>4 Use the *rezdelays nc<\/p>\n<p>5 Break big set into multiple sets<\/p>\n<p>6 Use Set-Rezzer Chaining by making one of your sets a rez of a setrezzer.<\/p>\n<p><span style=\"color: #ff0000;\"><strong>\u00a0<\/strong><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Nov. 27, 2017 &#8211; NEW! On *setrezzer a new entry called FastReRez.\u00a0 It will default to &#8220;on&#8221; and was implemented to address slow rerezzing after a MasterReset. The caveat is that you will always need to save (copy child-object back into MasterRezzer replacing any existing) in order for it to work. It appears everyone always &hellip; <a href=\"https:\/\/artistedancediva.co.uk\/wp\/?page_id=1317\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">BK13 &#8211; The Artiste &#8211; Book &#8211; Set Rezzer &#8211; v3.1<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"parent":1313,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"_links":{"self":[{"href":"https:\/\/artistedancediva.co.uk\/wp\/index.php?rest_route=\/wp\/v2\/pages\/1317"}],"collection":[{"href":"https:\/\/artistedancediva.co.uk\/wp\/index.php?rest_route=\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/artistedancediva.co.uk\/wp\/index.php?rest_route=\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/artistedancediva.co.uk\/wp\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/artistedancediva.co.uk\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1317"}],"version-history":[{"count":8,"href":"https:\/\/artistedancediva.co.uk\/wp\/index.php?rest_route=\/wp\/v2\/pages\/1317\/revisions"}],"predecessor-version":[{"id":1732,"href":"https:\/\/artistedancediva.co.uk\/wp\/index.php?rest_route=\/wp\/v2\/pages\/1317\/revisions\/1732"}],"up":[{"embeddable":true,"href":"https:\/\/artistedancediva.co.uk\/wp\/index.php?rest_route=\/wp\/v2\/pages\/1313"}],"wp:attachment":[{"href":"https:\/\/artistedancediva.co.uk\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1317"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}