|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
How difficult would it be to be able to add an option to indicate which
blocks are currently being rendered? I often wonder where the render
threads are sitting, sometimes its obvious, sometimes its not.
Just an idea. Obviously, this should be a command line option, those
that don't want the current block to show can turn it off.
Thanks for the great effort to get the next version to this point guys.
My hats off to the POV-Team. 3.7 has been a long road to a new release.
I've often wondered if 3.7 would ever get to the stage its at now.
Thanks for the awesome work. Can't wait to see what's in store for the
future of our favorite raytracer.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 26.02.2011 04:23, schrieb Mike Raiford:
> How difficult would it be to be able to add an option to indicate which
> blocks are currently being rendered? I often wonder where the render
> threads are sitting, sometimes its obvious, sometimes its not.
Since December, 3.7.0 is essentially feature-frozen, and changes are
limited to bugfixes (the new SSLT syntax was an exception). There'll be
a 3.7.1 for sure though, and I'm pretty confident it won't take nearly
as long as 3.7.0.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 26/02/2011 04:23, Mike Raiford nous fit lire :
> How difficult would it be to be able to add an option to indicate which
> blocks are currently being rendered? I often wonder where the render
> threads are sitting, sometimes its obvious, sometimes its not.
>
> Just an idea. Obviously, this should be a command line option, those
> that don't want the current block to show can turn it off.
I second Clipka's anwser.
I have nevertheless a few questions: how would you highlight/indicate
the rendering blockS ?
(Yes, blocks, with an s, as there are many blocks rendered at the same
time (according to the number of threads))
On a preview picture, it's just another block of pixels... they start
black, but toggling them any other colour won't save you if the final
colour is the one chosen... (let's say it turn white when the render
starts for that block, how would you differentiate from the final white
from your picture ? the same issue will be happening whatever the colour
or pattern: sometime it will be invisible)
And it will really slowdown the rendering of the fast scene (double the
amount of data in the bottleneck: first to set it "White", later to set
it to final)
As a textual output, I guess that getting block number would be useless,
and displaying the two pair of coordinates (top-left, size ?) would be
competiting with pixels %, you would not be able to actually see it.
(the pixels % is for actually rendered pixels, it is always a bit late
when display) (and it might indeed corrupt the actual pixel %
indication, when toggling the block on the preview image)
Why do you need to know the rendering blocks ?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le_Forgeron <jgr### [at] freefr> wrote:
> I have nevertheless a few questions: how would you highlight/indicate
> the rendering blockS ?
In the preview window, draw a semi-transparent border around the blocks
being currently rendered.
> And it will really slowdown the rendering of the fast scene (double the
> amount of data in the bottleneck: first to set it "White", later to set
> it to final)
If the feature is an optional command-line option, it doesn't need to be
used for very fast renders.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> In the preview window, draw a semi-transparent border around the blocks
> being currently rendered.
Or toggle between normal and inverse video a couple times a second?
--
Darren New, San Diego CA, USA (PST)
"How did he die?" "He got shot in the hand."
"That was fatal?"
"He was holding a live grenade at the time."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New <dne### [at] sanrrcom> wrote:
> Warp wrote:
> > In the preview window, draw a semi-transparent border around the blocks
> > being currently rendered.
> Or toggle between normal and inverse video a couple times a second?
That would be really annoying.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 26.02.2011 20:07, schrieb Darren New:
> Or toggle between normal and inverse video a couple times a second?
Rather not.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> Warp wrote:
>>> In the preview window, draw a semi-transparent border around the blocks
>>> being currently rendered.
>
>> Or toggle between normal and inverse video a couple times a second?
>
> That would be really annoying.
Hmmm. Or maybe only while you're holding down a particular key? Or toggle it
by hitting the space bar while focus is on the preview page?
This is why they have the "crawling ants" boundaries for selections in
graphics packages: it's pretty obvious where it is regardless of what's
underneath.
Maybe toggling for each pixel updated, so you can see how fast each block is
rendering? :-)
--
Darren New, San Diego CA, USA (PST)
"How did he die?" "He got shot in the hand."
"That was fatal?"
"He was holding a live grenade at the time."
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 2011/02/26 14:07, Darren New a écrit :
> Warp wrote:
>> In the preview window, draw a semi-transparent border around the blocks
>> being currently rendered.
>
> Or toggle between normal and inverse video a couple times a second?
>
I vote against that one.
The border would probably be the best. It can be red, or the compliment
of the current tint displayed.
Anyway, it should be OFF by default.
Alain
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain <aze### [at] qwertyorg> wrote:
> Le 2011/02/26 14:07, Darren New a écrit :
> > Warp wrote:
> >> In the preview window, draw a semi-transparent border around the blocks
> >> being currently rendered.
> >
> > Or toggle between normal and inverse video a couple times a second?
> >
>
> I vote against that one.
>
> The border would probably be the best. It can be red, or the compliment
> of the current tint displayed.
>
> Anyway, it should be OFF by default.
>
>
>
> Alain
Yes, I don't care about how it will look as long as it's off by default.
-tgq
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |