Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 29 7:57 am)
I've done a lot of test renders, but did not see this. Windows 7 here.
A ship in port is safe;
but that is not what ships are built for.
Sail out to sea and do new things.
-"Amazing
Grace" Hopper
Avatar image of me done by Chidori.
Basicwiz is right. I've seen this in 2010 but it's never happended to me if I started the render with the render screen on top.
Poser Pro 2012 SR3
Windows 7 Professional 64 bit
Intel Core I7 990x 3.46G 6 core
24G RAM
EVGA GTX580 R Video Card
Single HP LP2475 1920x1200 monitor
______________________________
Yeah, this bug didn't get it's wings pulled off till too late for release. Don't worry it's laying at the bottom of the kill jar and will be displayed for your enjoyment in our collection of dead bugs in a soon to come service release.
So you all know the exact trigger is actually was "No Lights with Map Shadows". If all the lights used reytrace or no shadows then this bug would happen. If you encounter the problem in a different situation (A scene using shadow maps) please report the problem. That's the only way it will get fixed.
OOooof. I thought it was just me ... I've been doing all my Renders In Background and I get a lot of renderer "hanging up" or the render window shows a previous render or whatever. Glad I did a search on this topic: so it's a known problem. It's not a show-stopper... making sure Render Window is visible seems to give me what I want, most of the time.
Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2
Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand]
I don't know if it's the same thing, but when I use SSS and simple lighting even with rendering, it passes the SSS and IDL and nothing happens. Some say it's a memory problem, which one time it was, then it may be a bug.
____________________________________________________________________________________________________________________________
Asus N50-600 - Intel Core i5-8400 CPU @ 2.80GHz · Windows 10 Home/11 upgrade 64-bit · 16GB DDR4 RAM · 1TB SSD and 1TB HDD; Graphics: NVIDIA Geforce GTX 1060 - 6GB GDDR5 VRAM; Software: Poser Pro 11x
Unless you bring up the Render window before you start your Render in Background all sorts of weird things happen: SSS pass doesn't happen, the previous images gets "re-rendered", freezes, yeah: stuff. Since I've made sure the render window was up before I started rendering, it hasn't done any of that.
Yet. :biggrin:
Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2
Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand]
Hmmm ... I have absolutely no idea what happens on my side: Every time I render an object (happens with every object, prop or character) I see that the image starts to render. I see every step of the render but as soon as the last part is finished, the render screen turns to grey. Also the image does not appear in the recent renders windows.
Everthing is o.k. if I render in background or do an area render or a render in Queue. In that cases the image if right - but nor if i render in foreground.
This only happens with Poser Pro 2012. I used to work with Poser Pro 2010 and never had this problem before.
Any ideas?
Quote - As there is no reaction anymore, I guess no one else has this problem, or knows the solution.Might mean we are doing something wrong, and SR1 will not solve this!
Not following what you mean... Nerd3D said:
"Yeah, this bug didn't get it's wings pulled off till too late for release. Don't worry it's laying at the bottom of the kill jar and will be displayed for your enjoyment in our collection of dead bugs in a soon to come service release.
So you all know the exact trigger is actually was "No Lights with Map Shadows". If all the lights used reytrace or no shadows then this bug would happen. If you encounter the problem in a different situation (A scene using shadow maps) please report the problem. That's the only way it will get fixed."
I'm confident that since it's been reported and noted, it'll get fixed.
Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2
Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand]
Nope - it doesn't depend on the lights. I tried an empty scene with different lights and different render settings: no matter what i tried and what i render: The scene renders normally (if there is nothing in the scene, the render window shows white) and as soon the render is finished the renderwindow gets grey. This grey is everytime the same: its not background or groundcolor.
Any idea is welcome ...
Report this to Smith Micro. If it is reproducable, it must be a bug. They will want to know about it.
Monterey/Mint21.x/Win10 - Blender3.x - PP11.3(cm) - Musescore3.6.2
Wir sind gewohnt, daß die Menschen verhöhnen was sie nicht verstehen
[it is clear that humans have contempt for that which they do not understand]
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.
Hi this may be me doing something wrong but I have noticed that sometimes the poser pro render engine does not deliver the render.
I am using V4 and have reloaded v4 into all the runtimes with all her morphs etc. I run a mac Pro with oddles of memory and ram.
Sometimes the model renders perfectly and the render appears in the render window and then without warning it will stop appearing... the render bar fills up and it "goes through the motions" but no render and in the render window is the previous render. The render history says the same as well and does not update.
If I reload a base v4 again it renders ok.
It seems entirely random.
Anyone else with this issue?