 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think it could be a good idea to support multiple render jobs running
in parallel in a single instance of POV-Ray. You could manage them like
downloads in a download manager or bittorrent.
Why, do you ask? Because when running multiple instances it can get
confusing as to which instance is currently running. Over the last week
I've accidentally stopped a long render a few times because I clicked on
the wrong icon in the taskbar.
Also, it resolves the issue where some files are open in one instance
but not another, and POV-Ray does not correctly remember which files
were open when starting a new instance.
Lastly, the "recent files" list at the bottom of the File menu may get
messed up with all the separate instances.
I don't think this is a high priority, but I thought I'd throw the idea
out there.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Why, do you ask? Because when running multiple instances it can get
> confusing as to which instance is currently running. Over the last week
> I've accidentally stopped a long render a few times because I clicked on
> the wrong icon in the taskbar.
Don't you get a warning if you try to stop a long render?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Le 22/01/2016 02:46, Mike Horvath a écrit :
> I think it could be a good idea to support multiple render jobs
> running in parallel in a single instance of POV-Ray. You could
> manage them like downloads in a download manager or bittorrent.
>
> Why, do you ask? Because when running multiple instances it can
> get confusing as to which instance is currently running. Over the
> last week I've accidentally stopped a long render a few times
> because I clicked on the wrong icon in the taskbar.
>
> Also, it resolves the issue where some files are open in one
> instance but not another, and POV-Ray does not correctly remember
> which files were open when starting a new instance.
>
> Lastly, the "recent files" list at the bottom of the File menu may
> get messed up with all the separate instances.
>
> I don't think this is a high priority, but I thought I'd throw the
> idea out there.
You know, of course, that the windows version has a render-queue, in
which you can put the different jobs.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iJwEAQEIAAYFAlaimlkACgkQhKAm8mTpkW2XnAQAsgiFdbSqd6tKlPBH2WWK6dwS
HgMkZsJw2RbRdwrVPqzUlWKI81e0eQXUxxfXa1rn+sVfz+HMOLl+dk/GhWYV8hCR
5SX6X5G2R17r3zJK+ANRJUQp2e2l8b5/KePMJretpZtxm+bWBIzLR2R/Gf8urzdV
CuTv6PAZiKUgB8o4fcc=
=9JCZ
-----END PGP SIGNATURE-----
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/22/2016 4:08 PM, Le_Forgeron wrote:
> You know, of course, that the windows version has a render-queue, in
> which you can put the different jobs.
I did know that, actually.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/22/2016 2:40 AM, scott wrote:
>> Why, do you ask? Because when running multiple instances it can get
>> confusing as to which instance is currently running. Over the last week
>> I've accidentally stopped a long render a few times because I clicked on
>> the wrong icon in the taskbar.
>
> Don't you get a warning if you try to stop a long render?
Unfortunately, I still get confused sometimes and click through the warning.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Ok, Mike thinks of a Render-Que ahere multiple "Scripts" render at the same
time,
and where you can give each of the renderings more or less priority.
In my experience this will only make sense, if it will survive a computer-reboot
without big problems.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/23/2016 9:45 AM, Theogott wrote:
> Ok, Mike thinks of a Render-Que ahere multiple "Scripts" render at the same
> time,
> and where you can give each of the renderings more or less priority.
> In my experience this will only make sense, if it will survive a computer-reboot
> without big problems.
>
>
That is true. You should be able to continue where you left off after a
reboot.
(Currently you can use POV-Ray's +C switch. But does this work with
multiple scenes?)
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Horvath <mik### [at] gmail com> wrote:
> On 1/23/2016 9:45 AM, Theogott wrote:
> > Ok, Mike thinks of a Render-Que ahere multiple "Scripts" render at the same
> > time,
> > and where you can give each of the renderings more or less priority.
> > In my experience this will only make sense, if it will survive a computer-reboot
> > without big problems.
>
> That is true. You should be able to continue where you left off after a
> reboot.
>
> (Currently you can use POV-Ray's +C switch. But does this work with
> multiple scenes?)
Internally POV-Ray 3.7 can render multiple scenes at the same time. There is
just no user interface to make use of this feature.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> Internally POV-Ray 3.7 can render multiple scenes at the same time. There is
> just no user interface to make use of this feature.
Possibly there is some "Overhead" in doing trhese switches often, unless it
would definitely dedicate CPU-Cores to each Task?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Theogott" <nomail@nomail> wrote:
> > Internally POV-Ray 3.7 can render multiple scenes at the same time. There is
> > just no user interface to make use of this feature.
>
> Possibly there is some "Overhead" in doing trhese switches often, unless it
> would definitely dedicate CPU-Cores to each Task?
The overhead of rendering multiple scenes in a single instance is less than
running multiple instances and rendering in each.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
