♥ PosetteForever ♥

<span style="font-family:Arial;"> </span><span style="font-size:12px;"> </span><span style="color: black;"> </span> <br /> <br /> Something frustrating happened to me today that I've never experienced before. I've been working on a spooky scene for Halloween in Poser 4 and made a lot of progress today by meticulously setting up the lighting which consisted of eight spotlights with various falloff zones and intensities. Earlier in the day I had added the monster character I wanted to use in the scene, the (free) Lemurtek Wolfgang werewolf. <br /> <br /> Normally as I'm working on a scene whenever I finish some significant aspect I'll save the scene as a slightly different name (file1a, file 1b, etc) because I have an old computer and I sometimes have troubles with Poser 4 and memory allocation. I had Poser open continuously for about 7 hours today working on this scene, though, and when I finally exited Poser and came back a little later my pz3 file wouldn't open. Poser just sat there showing an hourglass as it tried to open the scene, but this process never finished even after waiting a considerable amount of time. I was upset, but went back and tried to open the pz3 from 1 step earlier. It wouldn't open either (same behavior), and I was even more upset. <br /> <br /> After a lot of experimenting I determined that the problem was the werewolf character. I just downloaded it and never used it before, and it seems that it doesn't work for me; whenever I try to save a Poser scene containing this character, I can't open the pz3 file later (I verified this by making a blank scene with just the werewolf and the ground plane--I couldn't open that save file). The readme file for the werewolf suggests deleting the PoserGeometries rsr file if the creature won't load. I did this and it didn't matter. Since adding the werewolf was the first thing I did today in the scene, all my considerable work for the day seemed lost. <br /> <br /> The way I recovered most of my work was to start a blank Poser scene and import the faulty pz3 file into the new empty scene. Luckily almost everything imported properly, strangely including the werewolf (although if I saved the new scene with that character present the new pz3 wouldn't open). I deleted the problem character. <br /> <br /> Unfortunately not everything would import from the original/faulty pz3 file, namely the all the lights I had spent so much time on. The lights loaded all clumped together and were faulty somehow. When I selected any of them no parameter dials would appear, and although the lights appeared as black dots in the lighting globe thingy they were shining a bright white light that couldn't be adjusted. I deleted all the lights. <br /> <br /> With that lengthy preface I'll now get to my point in this thread. After briefly considering giving up on the whole scene rather than trying to reconstruct the lighting, I had a thought that the lighting info was stored in the faulty pz3 file so I opened it in a text editor. After deciphering what was going on with the way the info was stored, I was able to pretty quickly set up the lighting in my new non-werewolf scene by just looking at the parameters in the pz3 file. This was <i>much</i> faster than trying to manually do the lights over again. <br /> <br /> If anyone else ever has to do this, the way the lighting info is stored is a little confusing. After opening the pz3 file in a text editor, search for the word "light" and eventually you'll come to the section where the light info is stored. The start of it generally looks like this: <br /> <br /> <!-- no smilies start --><div class="code"><div class="code-header" id="codehdr2_4c32ee42" style="position:relative;">Code: [<a href="download_post.php?post=40638">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_4c32ee42','code2_4c32ee42',''); ShowHide('codehdr_4c32ee42', 'codehdr2_4c32ee42', '')">Hide</a>]</div><div class="code-header" id="codehdr_4c32ee42" style="position:relative;display:none;">Code: [<a href="download_post.php?post=40638">Download</a>] [<a href="javascript:void(0)" onclick="ShowHide('code_4c32ee42','code2_4c32ee42','');ShowHide('codehdr_4c32ee42','codehdr2_4c32ee42','')">Show</a>]</div><div class="code-content" id="code_4c32ee42" style="position:relative;"><ol class="code-list" start="1"><li class="code-row code-row-first"><span class="code-row-text">light spotLight 5  </span></li><li class="code-row"><span class="code-row-text">    {  </span></li><li class="code-row"><span class="code-row-text">    storageOffset 0 0.3487 0  </span></li><li class="code-row"><span class="code-row-text">    geomResource 7    </span></li><li class="code-row"><span class="code-row-text">    lightType 0  </span></li><li class="code-row"><span class="code-row-text">    name    LIGHT1  </span></li><li class="code-row"><span class="code-row-text">    off  </span></li><li class="code-row"><span class="code-row-text">    bend 1  </span></li><li class="code-row"><span class="code-row-text">    dynamicsLock        1  </span></li><li class="code-row"><span class="code-row-text">    hidden        0  </span></li><li class="code-row"><span class="code-row-text">    addToMenu    1  </span></li><li class="code-row"><span class="code-row-text">    castsShadow        1  </span></li><li class="code-row"><span class="code-row-text">    includeInDepthCue        1  </span></li><li class="code-row"><span class="code-row-text">    parent UNIVERSE  </span></li><li class="code-row"><span class="code-row-text">    channels  </span></li><li class="code-row"><span class="code-row-text">        {  </span></li><li class="code-row"><span class="code-row-text">        liteFalloffStart Angle Start  </span></li><li class="code-row"><span class="code-row-text">            {  </span></li><li class="code-row"><span class="code-row-text">            name Angle Start  </span></li><li class="code-row"><span class="code-row-text">            initValue 0  </span></li><li class="code-row"><span class="code-row-text">            hidden 1  </span></li><li class="code-row"><span class="code-row-text">            forceLimits 4  </span></li><li class="code-row"><span class="code-row-text">            min 0  </span></li><li class="code-row"><span class="code-row-text">            max 160  </span></li><li class="code-row"><span class="code-row-text">            trackingScale 0.25  </span></li><li class="code-row"><span class="code-row-text">            keys  </span></li><li class="code-row"><span class="code-row-text">                {  </span></li><li class="code-row"><span class="code-row-text">                static  0  </span></li><li class="code-row"><span class="code-row-text">                k  0  0  </span></li><li class="code-row"><span class="code-row-text">                sl  1  </span></li><li class="code-row"><span class="code-row-text">                spl  </span></li><li class="code-row"><span class="code-row-text">                sm  </span></li><li class="code-row"><span class="code-row-text">                }  </span></li><li class="code-row"><span class="code-row-text">            interpStyleLocked 0  </span></li><li class="code-row"><span class="code-row-text">            }  </span></li><li class="code-row"><span class="code-row-text">        liteFalloffEnd Angle End  </span></li><li class="code-row"><span class="code-row-text">            {  </span></li><li class="code-row"><span class="code-row-text">            name Angle End  </span></li><li class="code-row"><span class="code-row-text">            initValue 70  </span></li><li class="code-row"><span class="code-row-text">            hidden 1  </span></li><li class="code-row"><span class="code-row-text">            forceLimits 4  </span></li><li class="code-row"><span class="code-row-text">            min 0  </span></li><li class="code-row"><span class="code-row-text">            max 160  </span></li><li class="code-row"><span class="code-row-text">            trackingScale 0.25  </span></li><li class="code-row"><span class="code-row-text">            keys  </span></li><li class="code-row"><span class="code-row-text">                {  </span></li><li class="code-row"><span class="code-row-text">                static  0  </span></li><li class="code-row"><span class="code-row-text">                k  0  70  </span></li><li class="code-row"><span class="code-row-text">                sl  1  </span></li><li class="code-row"><span class="code-row-text">                spl  </span></li><li class="code-row"><span class="code-row-text">                sm  </span></li><li class="code-row"><span class="code-row-text">                }  </span></li><li class="code-row"><span class="code-row-text">            interpStyleLocked 0  </span></li><li class="code-row"><span class="code-row-text">            } </span></li></ol></div></div><!-- no smilies end --> <br /> <br /> The confusing part is that most of this info is not needed to reconstruct a light setting. For each of the light parameters/channels (Angle Start, Angle End, etc) the value you should set the light parameter dial in your scene is the second digit after the "k" value. For example in the pz3 clip above for liteFalloffEnd Angle End k is "0 70" so you'd set your "Angle End" parameter dial in Poser to 70. If the "rotateX xrot" parameter (not shown above) has "0 -22.6729" for k, you'd set your x rotation for the light on the parameter dial to -22.6729 degrees. <br /> <br /> One more confusing thing is that all lights, even infinite lights, are listed as spotlights in the pz3. The only way to tell that a light is infinite rather than a spotlight is that the k value for the one or more of the parameters "translateZ ztran," "translateX xtran," or "translateY ytran" is a huge number, in my case 95.2 ztran. Nonetheless to exactly restore infinite lights I found that I first had to set all the parameters as if it was a spotlight and only then go to the light properties in Poser and change the light from spotlight to infinite light. <br /> <br /> Using this technique I was able to pretty quickly reconstruct the lighting in my new/imported good scene by creating new lights, looking at the parameters in the faulty pz3, and putting in those settings on the new lights. <br /> <br /> Perhaps someone with more knowledge of text-editing pz3 files could help me with two questions that I wasn't able to resolve. <br /> <br /> 1) I wasn't able to exactly reconstruct my camera angles from the faulty pz3 by copying the camera info in the way I did with the lights. The cameras in the new scene were at similar but slightly different angles using the old info, and were way off place in the Z plane. Why would this be? <br /> <br /> 2) Would there have been a better way to handle the whole general situation? I was thinking that it might have been possible to edit the pz3 to remove just any references to the problem werewolf character but didn't feel comfortable trying this, especially with my text editor struggling and crawling through the 15 MB text of the pz3. Would this have been safe to try, and would it have worked effectively? Is everything for each 3d object in one continuous area of the pz3, or is the info spread out all over? <br /> <br /> So overall after some frustration and learning, my scene is mostly back to where it was without too much trouble except that I now need to find a new scary monster to terrorize poor Posette. Does anyone know of any good and free monster characters that would work in Poser 4? <br /> <br /> Thanks <br /> <br /> Endosphere

It is my fundamental purpose. How do I know that you were really "thinking"?

A good work, I can only suggest to try importing the fault pz3 in a scene where you've deleted all lights... About the werewolf problem, I don't know, if it is the P4 character I had no problems using it, I also remember a wolf/werewolf p4 character made combining two different figures, if it is the case, maybe it's because of it... What version of Poser are you using for this scene ?

I've got Metacreations Poser 4 with a Curious Labs patch taking it to version 4.03. I'm not sure why I'm having trouble with the werewolf. I've never had an item that would load fine from the Poser library, pose fine, render fine, but not save into a pz3 file. <br /> <br /> In the end I couldn't really find any other appropriate monsters to use in my scene (the only other actually menacing thing I have is the "Looks Like Alien" as in from the movie of the same name by SixPacWolf, but it wasn't really appropriate for this scene) so I decided to use the werewolf anyway. I brought it into the reconstructed scene, posed it, and did a bunch of renders since I couldn't save the pz3 to go back if anything was not quite right. Overall it worked out ok and I was satisfied with the results I got. <br /> <br /> Endosphere

Well, if the pz3 import is working simply save the light set and upload it after importing the pz3 file...

That's a good idea, Tormie. I didn't end up going that route since once I reconstructed the lights and reloaded the werewolf from the Poser library I was basically finished except for renderings, but your idea might have saved me the trouble of also starting over with the camera angles as they probably would have still been correct in the import. <br /> <br /> I forgot to mention earlier that I tried your idea about deleting all the lights from an empty scene and importing the faulty pz3 to get the lighting back. Unfortunately it didn't work (the lights were still in a big clump that couldn't be adjusted), but it was a good idea to try anyway. <br /> <br /> Although I reconstructed the scene in question and am finished with it now (actually I put a close-up render in the gallery area), I am still interested in hearing if anyone has ever tried to text edit a pz3 file to remove a scene element or character. When I get some time I will try this myself just to experiment, unless anyone already knows things just don't work that way. <br /> <br /> Endosphere

<a class="post-url" href="http://ultrawoman.fc2web.com/download.html" target="_blank">http://ultrawoman.fc2web.com/download.html</a> <br /> Ultrawoman monsters. One should fill the bill quickly enough. If you have time to edit a texture map, <a class="post-url" href="http://www.artist-3d.com" target="_blank">www.artist-3d.com</a> has a .3ds werewolf head that can prop-replace a dork head. <br /> Fang Morphs on Dork will make a quick vampire. <br /> <br /> <span style="color: #ff0019;">[Edited by Tormie: removed link to commercial product]</span>

Welcome back VRLowkey and thank you for the hints :). <br /> <br /> Just remember not to post links to commercial products on PF <img src="https://www.posetteforever.com/images/smiles/eusa_naughty.gif" alt="" />

Thanks for the suggestions, VRLowkey. Those Japanese robot ladies are pretty freaky, but there definitely are some neat (all free) creatures on that ultrawoman page and I thought the green fish-man thingy was pretty cool. I've been to that artist-3d site before a few times and they're especially good for some free furniture and household electronic item models, although unfortunately many of the files there are in .max format which is bad if, like me, a person has an older computer as I haven't been able to find any non-Windows XP freeware converters out there that will work with .max files. <br /> <br /> I still haven't had a chance to play around more with the text editor on the pz3 files but I'll hopefully get to it soon. <br /> <br /> Endosphere