Sun, Dec 1, 7:16 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 29 7:57 am)



Subject: Problems in P6


dogor ( ) posted Thu, 02 June 2005 at 1:26 AM · edited Sun, 01 December 2024 at 7:10 PM

file_249081.jpg

Notice that in this render the bottom is missing a bar of render. Can't get P6 to render it on this scene. Also I tried to change the background color and it aleays changes itself back to gray again no matter what color I try to change it to in any scene I do. Any thoughts?


nerd ( ) posted Thu, 02 June 2005 at 1:51 AM
Forum Moderator

There's a cahnce your preferred stat is messed up. Try changing your prefs to to launch Poser to Factory UI and State. Restart Poser and create a simple test scene. Nerd3D


svdl ( ) posted Thu, 02 June 2005 at 2:53 AM

There also may be some files called poserTemp.xxxxx left in your Poser folder. Those are scratch files that didn't get deleted. And they can really mess with the program. If they're there, delete them. (I regularly run "del poserTemp* /s" to kill those files off. Sometimes makes the difference between a failed and a successful render).

The pen is mightier than the sword. But if you literally want to have some impact, use a typewriter

My gallery   My freestuff


hauksdottir ( ) posted Thu, 02 June 2005 at 3:25 PM

But, aren't the cached renders also a temp file?


nerd ( ) posted Thu, 02 June 2005 at 4:38 PM
Forum Moderator

Yes and no, they will be there the next session, but will ecentually rotate out as new renders are made. But I don't see how they could cause this problem. Nerd3D


Dizzi ( ) posted Thu, 02 June 2005 at 5:07 PM

Cached renders are not stored in the poser directory. Maybe reducing bucket size solves the render problem.



hauksdottir ( ) posted Thu, 02 June 2005 at 9:43 PM

I doubt if they are causing the problem, but deleting the cached renders might bring a further question if you didn't realize they were also temp files. So exporting any that you want before deleting all temp files is a good idea. It used to be that temp files were mostly the detritus left after a crash, so deleting them on sight was a good idea. As for the background color... do you have the SR1 installed? Are you clicking on the sphere next to the working window which controls the background color? Are you using the dots to save the UI? Carolly


dogor ( ) posted Thu, 02 June 2005 at 10:25 PM

I'm trying to post replies here, but they ain't posting I'll send you a message if this one doesn't post.


dogor ( ) posted Thu, 02 June 2005 at 10:38 PM

It worked. Yes, I have SR1 installed, I did it again to make sure. :) Reseting start up back to factory fixed the render problem however I have not created a new render fresh since I did to check and see if that fixed the color problem. The pz3 could have stored settings from before that don't allow me to change the color. No UI's just saving to pz3 and I have saved again since and I still cannot change the color in the background. At startup with factory I can change the color. I need to figure out what is different about the room other than characters and textures in this one and others I made with the same problem.


dogor ( ) posted Thu, 02 June 2005 at 11:07 PM

file_249082.jpg

I launched P6 factory stat and deleted James and installed a new figure. I can still change the forground color. I cannot with the old pz3 with the same character. All I can see is the ground plane is different.


hauksdottir ( ) posted Thu, 02 June 2005 at 11:27 PM

There may indeed be something with that pz3 which is wacky. But you can now change and set the color and render her completely, which are both good steps. After you get your preferences the way you want be sure to set them in the menu and also set one of the UI dots. That will give you two ways to get back to your favorite setup. If you do discover what the problem is with the pz3, and it is with other pz3s, drop a line to efrontier. There is a place to attach a buggy pz3 in the form if you need it examined. Carolly


dogor ( ) posted Thu, 02 June 2005 at 11:56 PM

Alright, that sounds like a winner, but I'm sure the ground is the problem in the earlier render. It cannot be changed to the new P6 factory start up ground either because I tried. It's a different ground plane from earlier P6 or the P5 ground and it does not work for me in P6 properly and there is no way to fix it. P6 would have to except it. Thanks everyone! Later,


nerd ( ) posted Fri, 03 June 2005 at 12:46 AM
Forum Moderator

If you open a P5 file in P6 the ground will be a P5 style ground. The P6 ground plane is scalled up from the P5 one. It's also set to diplay in wireframe view. In materials you would also have to change it to a Shadow Catcher and disconnect the texture node. Nerd3D


dogor ( ) posted Fri, 03 June 2005 at 1:40 AM

Is a P5 pose room 100% compatible with P6? They come in P5 pz3's I have left over from P5. I didn't know that if it's true, but may be in the SR1 readme.


nerd ( ) posted Fri, 03 June 2005 at 1:58 AM
Forum Moderator

Most P5 scenes will open in P6 just fine. (I tried hundreds during beta) One difference is the Skin shader node. The way it works was changed between P5 and P6 so senes that use it may need to be reworked a bit. Nerd3D


dogor ( ) posted Fri, 03 June 2005 at 2:11 AM

It might not be possible to change the background color either, but yes they will open. I wish the P6 room was installed if it's re saved in P6.


dogor ( ) posted Fri, 03 June 2005 at 2:26 AM

I tried changing the background color in a P5 pz3. It worked. I guess the room I trouble with was an early P6 room or something strange. Got it working right now though thanks "nerd" for your first post it really fixed both.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.