{"id":13607,"date":"2020-07-05T15:19:05","date_gmt":"2020-07-05T15:19:05","guid":{"rendered":"https:\/\/www.jurn.link\/dazposer\/?p=13607"},"modified":"2023-02-13T21:51:55","modified_gmt":"2023-02-13T21:51:55","slug":"poser-how-to-toggle-all-scene-lights-when-making-preview-renders","status":"publish","type":"post","link":"https:\/\/jurn.link\/dazposer\/index.php\/2020\/07\/05\/poser-how-to-toggle-all-scene-lights-when-making-preview-renders\/","title":{"rendered":"Poser: how to toggle all scene lights when making Preview renders"},"content":{"rendered":"<p>Selecting GROUND in a Poser scene is a handy trick that does not, in every single instance, make the guide-wires of Lights invisible in a scene.  I&#8217;ve seen instances where spotlights don&#8217;t toggle off when GROUND is selected.<\/p>\n<p>Why would we want to toggle the lights? Well, when working with lights the last-selected light leaves &#8216;guide wires&#8217; showing in PREVIEW, and these will mess up a comic-book render. This picture of a live scene in OpenGL shows the problem&#8230;<\/p>\n<p><a href=\"https:\/\/www.jurn.link\/dazposer\/oldimages\/light-indicators.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.jurn.link\/dazposer\/oldimages\/light-indicators.jpg\" alt=\"\" width=\"640\" height=\"462\" class=\"alignnone size-large wp-image-13608\" \/><\/a><\/p>\n<p>If one were to render this in real-time, the picture would have the light&#8217;s &#8216;guide wires&#8217; arrows and circle on it.  Easy to miss, easy to forget until it&#8217;s too late and you&#8217;re dropping it into a panel on a comics page.<\/p>\n<p>Willyb53&#8217;s free <a href=\"https:\/\/sharecg.com\/v\/57963\/browse\/8\/Script\/Light-Toggle\">Light Toggle<\/a> script can be hacked to do this for us.  Willy&#8217;s script was set up to turn all the scene lights off and on, but a few simple tweaks <strong>keeps them shining<\/strong> while only their guide-wires are turned off in the scene. To do this we simply open his script with Notepad++ and change it to read&#8230;<\/p>\n<p><a href=\"https:\/\/jurn.link\/dazposer\/wp-content\/uploads\/2020\/07\/2022-07-14_232625.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/jurn.link\/dazposer\/wp-content\/uploads\/2020\/07\/2022-07-14_232625.jpg\" alt=\"\" width=\"514\" height=\"358\" class=\"aligncenter size-full wp-image-19209\" srcset=\"https:\/\/jurn.link\/dazposer\/wp-content\/uploads\/2020\/07\/2022-07-14_232625.jpg 514w, https:\/\/jurn.link\/dazposer\/wp-content\/uploads\/2020\/07\/2022-07-14_232625-300x209.jpg 300w\" sizes=\"auto, (max-width: 514px) 100vw, 514px\" \/><\/a><\/p>\n<p>&#8230; then save, rename <strong>Toggle_Visibility_All_Lights.py<\/strong> and place the new script wherever you keep your Python scripts.  Mine are in&#8230;<\/p>\n<p><em>C:\\Program Files\\Smith Micro\\Poser 11\\Runtime\\Python\\poserScripts\\ScriptsMenu\\FavoriteScripts<\/em><\/p>\n<p>You can then iconise the new script using Dimension3D\u2019s $10 eXtended Access. This runs fine so long as you have the <a href=\"https:\/\/www.jurn.link\/dazposer\/?p=12199\">AVFix for it<\/a>, and I load it at every Poser startup. Attached to a meaningful icon (here a red closed eye), the new script then becomes one-click and it can be handily positioned near the Poser lights control panel.<\/p>\n<p><a href=\"https:\/\/www.jurn.link\/dazposer\/oldimages\/iconise.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.jurn.link\/dazposer\/oldimages\/iconise.jpg\" alt=\"\" width=\"421\" height=\"295\" class=\"alignnone size-full wp-image-13610\" \/><\/a><\/p>\n<p><a href=\"https:\/\/www.jurn.link\/dazposer\/oldimages\/controls.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.jurn.link\/dazposer\/oldimages\/controls.jpg\" alt=\"\" width=\"571\" height=\"316\" class=\"alignnone size-full wp-image-13611\" \/><\/a><\/p>\n<p>If you have the neat and attractive <a href=\"https:\/\/www.jurn.link\/dazposer\/?p=12843\">Scene Toy<\/a> addon for Poser, and if all you mostly use the Hierarchy Editor for is to click on GROUND to get rid of the guide-wires, then this script lets you hide that window and reclaim a little more screen space in the Poser UI.  &#8220;Begone, &#8216;o great space-wasting panel of grey ugliness&#8221;&#8230;<\/p>\n<p><a href=\"https:\/\/www.jurn.link\/dazposer\/oldimages\/begone.jpg\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/www.jurn.link\/dazposer\/oldimages\/begone.jpg\" alt=\"\" width=\"150\" height=\"150\" class=\"alignnone size-thumbnail wp-image-13612\" \/><\/a><\/p>\n<p>Finally, the other thing to keep in mind, re: lights and Preview renders, is that OpenGL is limited to eight lights in a scene. This is an OpenGL limitation, not a Poser limitation. In practice, that &#8220;eight lights limit&#8221; may be even less, because your PCs&#8217; hardware may not be able to support that many interacting lights and their shadows.  For working in Comic Book Preview mode it&#8217;s probably best to try to stay at three or four lights in a scene. Sketch only supports three, in terms of having the strokes follow the light directions.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Selecting GROUND in a Poser scene is a handy trick that does not, in every single instance, make the guide-wires of Lights invisible in a scene. I&#8217;ve seen instances where spotlights don&#8217;t toggle off when GROUND is selected. Why would we want to toggle the lights? Well, when working with lights the last-selected light leaves [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23,9,3,12],"tags":[],"class_list":["post-13607","post","type-post","status-publish","format-standard","hentry","category-automation","category-freebies","category-poser","category-tutorials"],"_links":{"self":[{"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/posts\/13607","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/comments?post=13607"}],"version-history":[{"count":3,"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/posts\/13607\/revisions"}],"predecessor-version":[{"id":21093,"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/posts\/13607\/revisions\/21093"}],"wp:attachment":[{"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/media?parent=13607"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/categories?post=13607"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jurn.link\/dazposer\/index.php\/wp-json\/wp\/v2\/tags?post=13607"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}