jjroland opened this issue on Aug 28, 2012 · 16 posts
jjroland posted Tue, 28 August 2012 at 12:41 PM
I REALLY do not want to restore default settings.
Somehow I messed something up and I am rendering only the grey background. Even when I thought I had a background picture added and I selected to render the background image, nothing only the grey.
If I load V4, select the main camera and adjust it to where her head is smack in the middle of the screen and select to render the whole screen - I still get ONLY the grey.
It also takes an absurdly long time to render.. nothing.
Any ideas?
I am: aka Velocity3d
AmbientShade posted Tue, 28 August 2012 at 12:49 PM
that happened to me a couple of times not too long ago - i restarted poser and it hasn't happened since. I'm thinkin it may be a random display bug or something. Are your drivers updated?
~Shane
jjroland posted Tue, 28 August 2012 at 1:21 PM
Yup they are all up to date.
I am: aka Velocity3d
Winterclaw posted Tue, 28 August 2012 at 1:26 PM
What's the clipping distance on the camera or whatever its called (min draw?) and how far away is the camera compared to that?
I forget the setting off hand, but can't you have something display in the pose room (handles) but still be invisible in the render?
Do you only get this with V4? Try putting a primitive where her head is and see what happens.
WARK!
Thus Spoketh Winterclaw: a blog about a Winterclaw who speaks from time to time.
(using Poser Pro 2014 SR3, on 64 bit Win 7, poser units are inches.)
vilters posted Tue, 28 August 2012 at 3:04 PM
Is something between teh camera and the scene?
is the camera outside the BB sphere for example?
Poser 1, 2, 3, 4, 5, 7,
P8 and PPro2010, P9 and PP2012, P10 and PP2014 Game
Dev
"Do not drive
faster then your angel can fly"!
fivecat posted Tue, 28 August 2012 at 3:10 PM
Can you render with a camera other than the main camera, such as the posing camera? If you can, you need to check settings, such as clipping distance on the Main camera as Winterclaw suggested. Do you have "visible in camera" unticked in the figure properties tab perhaps?
Miss Nancy posted Tue, 28 August 2012 at 3:17 PM
do what the others said, and check if atmosphere is enabled.
Santel posted Tue, 28 August 2012 at 4:27 PM
Hi, I ran into that with an old file not too long ago, try entering the material room and select the background object and as it comes up the image is no doubt already loaded but will now magically appear in the pose room :)
jjroland posted Wed, 29 August 2012 at 8:41 AM
Had to go off to other duties yesterday after I asked this. I will try these suggestions and see if anything works. Thanks!
I am: aka Velocity3d
jjroland posted Wed, 29 August 2012 at 9:03 AM
After this I will post an image of the preview window from the main camera and then an image of what is rendering.
There seems to be nothing between V4 and the camera. Also it is catching her, it's just even if I have the camera pointed dead on her, it renders only her right arm. So it's like it's moving.
I am: aka Velocity3d
jjroland posted Wed, 29 August 2012 at 9:07 AM
I don't know if I have mentioned this before but I can be really simple sometimes..... I'm glad I asked because it kept me looking for the solution instead of restoring defaults but I did figure it out on my own.
I had the render dimensions set ridiculously high. So when I would see the finished render I would only see a small portion of it. 2560 x1920 - my moniter is not that big lol. Also explains why the renders were taking sooooo long.
smdh
I am: aka Velocity3d
fivecat posted Wed, 29 August 2012 at 10:30 AM
Glad you figured it out -- it never occurred to me that it might be render dimensions, lol.
jjroland posted Wed, 29 August 2012 at 10:43 AM
lol me either..
I am: aka Velocity3d
vilters posted Wed, 29 August 2012 at 11:04 AM
Ouch :-)
Poser 1, 2, 3, 4, 5, 7,
P8 and PPro2010, P9 and PP2012, P10 and PP2014 Game
Dev
"Do not drive
faster then your angel can fly"!
Gremalkyn posted Wed, 29 August 2012 at 11:50 AM
I forget the actual quote, but it goes something like this: 51% of all mistakes are caused by human error, with the other 51% being indirectly caused by people.
At least you figured it out, and it was something a) easy to fix and b) something to remember. :)
hornet3d posted Wed, 29 August 2012 at 3:27 PM
I have been caught out by this in the past. I reloaded an old scene and did some changes and then started a render which I abandoned as it the precalculating indirect light was clealy not running as it should. I did that three times until finally I let it complete the render. Only when I noticed the cursor changed when I hovered over the the completed render and I could pan across the image did I realise I had saved the orginal scene with the render dimensions way up for a special render.
I use Poser 13 on Windows 11 - For Scene set up I use a Geekcom A5 - Ryzen 9 5900HX, with 64 gig ram and 3 TB storage, mini PC with final rendering done on normal sized desktop using an AMD Ryzen Threadipper 1950X CPU, Corsair Hydro H100i CPU cooler, 3XS EVGA GTX 1080i SC with 11g Ram, 4 X 16gig Corsair DDR4 Ram and a Corsair RM 100 PSU . The desktop is in a remote location with rendering done via Queue Manager which gives me a clearer desktop and quieter computer room.