 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Kenneth" <kdw### [at] earthlink net> wrote:
> Here's the link...
>
http://news.povray.org/povray.general/thread/%3Cweb.45125ba9d84b4b77cc29cf380@news.povray.org%3E/
>
> and the link to the associated image...
>
http://news.povray.org/povray.binaries.images/thread/%3Cweb.45125e6ed84b4b77cc29cf380%40news.povray.org%3E/?ttop=2674
26
> &toff=900
>
Sorry, the link to my original post brings up a "bad request." But the image
link still works (which will refer you back to the original post.)
Ken
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
OK...here's a WORKING link back to my original post. (I must have missed
something while cutting and pasting...) Sorry!
http://news.povray.org/povray.general/thread/%3Cweb.45125ba9d84b4b77cc29cf380%40news.povray.org%3E/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Kenneth" <kdw### [at] earthlinknet> wrote:
> "s.day" <s.d### [at] uelacuk> wrote:
> > Wow! thanks for all the replies.
> >
> > No media in the scene to be causing any issues...
> >
>
> A beautiful scene, and very complex (which makes it difficult to nail down the
> problem, I'm sure.)
>
> In looking at your scene code, I see that there are lots of spotlights that
> actually DO make use of media in some way. In the current version of POV-Ray,
> there are *multiple* problems associated when using media, radiosity and
> spotlights, which can cause really strange visual aberrations to appear in
> places you wouldn't expect. So far, I've only posted info about one such
> problem (not using radiosity). But there are others.
>
> Here's the link...
>
http://news.povray.org/povray.general/thread/%3Cweb.45125ba9d84b4b77cc29cf380@news.povray.org%3E/
>
> and the link to the associated image...
>
http://news.povray.org/povray.binaries.images/thread/%3Cweb.45125e6ed84b4b77cc29cf380%40news.povray.org%3E/?ttop=2674
26
> &toff=900
>
> Another problem is that radiosity illumination from media does not show up on
> any objects (or parts of objects) that are inside a media-filled spotlight
> cone. Said another way, the media IN the cone doesn't generate radiosity
> illumination on objects that are embedded in it. I think that's a problem with
> the spotlight itself.
>
> My suggestion would be to run your complete scene--radiosity and all-- with
> UseTestTex=1 rather than 0 (which will turn off your media) and see if the
> black spots still appear. A long and laborious testing process, to be sure!
>
> Ken W.
Hi Ken,
Thanks for taking the time to download/read the code, it must be almost as much
of a challenge as finding the cause of this problem with my lack of comments. I
had forgotten about the media used with the spotlights (that's the problem with
re-rendering 3 year old scenes). However, for the renders I have posted I was
using useTestTex=1 so media would not have been used/affected this.
I have done several more tests but so far have not found the cause. My first
tests were to revert to the default radiosity settings then go through and
adjust each item one at a time to the settings that caused the problem. All
these renders were OK (and much quicker).
I have also managed to complete a render with reasonably high quality settings:
pretrace_start 0.08
pretrace_end 0.01
count 500
nearest_count 10 // was 20
error_bound 1 // was 0.08
recursion_limit 4
low_error_factor .5 // was 0.9
gray_threshold 0.0
minimum_reuse 0.015
brightness 0.8
adc_bailout 0.01/2
which rendered fine, I am using the saved data from this trace to render at
5250x3500 with focal blur/isosurfaces and spotlights with media etc.. So far
the estimate for this render is about 5 months so I hope I am happy with it at
the end!!
As the PC still has several cores sitting their idle I am trying a smaller
render with the settings that caused the problem to see if image size has an
effect. I am still hoping to track down the cause of this even if the current
render is OK (I can't stand a mystery) I just wonder if I will manage to find
the cause before the other render has finished..
Sean
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Eero Ahonen <aer### [at] removethiszbxtnetinvalid> wrote:
> s.day wrote:
> > I forgot to add that the machine is only running XP 32 bit and 32 bit POV which
> > is why I wondered if approaching the 2GB memory limit may be causing the
> > problem.
> >
> > Sean
> >
>
> Start XP with /3GB -switch and it'll be able to allocate 3G for one process.
>
> --
> Eero "Aero" Ahonen
> http://www.zbxt.net
> aer### [at] removethiszbxtnetinvalid
Thanks Eero,
I will add this to my list of things to try.
Sean
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"s.day" <s.d### [at] uelacuk> wrote:
> Eero Ahonen <aer### [at] removethiszbxtnetinvalid> wrote:
> > Start XP with /3GB -switch and it'll be able to allocate 3G for one process.
> >
> > --
> > Eero "Aero" Ahonen
> > http://www.zbxt.net
> > aer### [at] removethiszbxtnetinvalid
>
> Thanks Eero,
>
> I will add this to my list of things to try.
>
> Sean
That's a really interesting work-around to the 2GB limit, that I didn't even
know about until this post. Thanks.
In researching this, the Microsoft website doesn't specifically mention that it
will work with Windows XP Home Edition SP2 (which is what I use.) They list
others, but not this particular version of the OS. But hey, it's worth a try.
Now, if I could only figure out what a /3GB-switch is and how to implement it...
Ken
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Kenneth nous apporta ses lumieres en ce 2008/03/20 09:05:
> "s.day" <s.d### [at] uelacuk> wrote:
>> Eero Ahonen <aer### [at] removethiszbxtnetinvalid> wrote:
>
>>> Start XP with /3GB -switch and it'll be able to allocate 3G for one process.
>>>
>>> --
>>> Eero "Aero" Ahonen
>>> http://www.zbxt.net
>>> aer### [at] removethiszbxtnetinvalid
>> Thanks Eero,
>>
>> I will add this to my list of things to try.
>>
>> Sean
>
> That's a really interesting work-around to the 2GB limit, that I didn't even
> know about until this post. Thanks.
>
> In researching this, the Microsoft website doesn't specifically mention that it
> will work with Windows XP Home Edition SP2 (which is what I use.) They list
> others, but not this particular version of the OS. But hey, it's worth a try.
>
> Now, if I could only figure out what a /3GB-switch is and how to implement it...
>
> Ken
>
>
>
Open the "boot.ini" file in the root of the drive where windows is installed.
Find this:
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=...
Add " /3GB" at the end of the first line, and ONLY that line.
If you encounter a problem when booting, restart in safe mode and undo the change.
--
Alain
-------------------------------------------------
Scientology: If shit happens, see "Dianetics", p.157.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain wrote:
> If you encounter a problem when booting, restart in safe mode and undo
> the change.
Or easier, duplicate the first line pre-change and give it a different
label, so you can pick whether to boot with that flag when you start. :-)
--
Darren New / San Diego, CA, USA (PST)
"That's pretty. Where's that?"
"It's the Age of Channelwood."
"We should go there on vacation some time."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain wrote:
> Open the "boot.ini" file in the root of the drive where windows is
> installed.
> Find this:
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=...
>
> Add " /3GB" at the end of the first line, and ONLY that line.
>
> If you encounter a problem when booting, restart in safe mode and undo
> the change.
You'll have to un-hide "protected operating system files" first to see boot.ini:
In Windows Explorer, uncheck the box:
Tools>Folder Options>View>Hide protected....
When I installed XP Pro (SP2) on machines with 4GB of memory, the /3GB switch
was automatically added to boot.ini. You should only have to add it if you
increase your memory after installation.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tim Riley nous apporta ses lumieres en ce 2008/03/21 14:12:
> Alain wrote:
>> Open the "boot.ini" file in the root of the drive where windows is
>> installed.
>> Find this:
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=...
>>
>> Add " /3GB" at the end of the first line, and ONLY that line.
>>
>> If you encounter a problem when booting, restart in safe mode and undo
>> the change.
>
> You'll have to un-hide "protected operating system files" first to see
> boot.ini:
> In Windows Explorer, uncheck the box:
> Tools>Folder Options>View>Hide protected....
>
> When I installed XP Pro (SP2) on machines with 4GB of memory, the /3GB
> switch was automatically added to boot.ini. You should only have to add
> it if you increase your memory after installation.
Forgot that. One of the first things I do after installing Windows it to unhide
all files.
--
Alain
-------------------------------------------------
Agnostic: Did someone shit?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks to everyone for the memory switch tips! That's what I like about the
newsgroups: "Ask and ye shall receive." ;-)
Ken W.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
