 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have a couple questions regarding the POV-Ray with Subdivision project
(http://www.cise.ufl.edu/~xwu/Pov-Sub/).
1) Is this program made obsolete by any recent beta versions of POV-Ray 3.7?
2) Is there a way I can add conditional checks to my pov file to check
whether I am running the modified executable?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>I have a couple questions regarding the POV-Ray with Subdivision project
> (http://www.cise.ufl.edu/~xwu/Pov-Sub/).
>
> 1) Is this program made obsolete by any recent beta versions of POV-Ray
> 3.7?
No. That is, it should still execute fine.
However, it's a modified version, the improvements in the 3.7 betas
are not in that code... I'm unsure if the authors will update POV-sub
when 3.7 comes out of beta. Note: the standard POV mesh code
is highly optimized, so IMHO it's unlikely that such extended syntax
will be adopted as standard.
> 2) Is there a way I can add conditional checks to my pov file to check
> whether I am running the modified executable?
Well, I guess it depends. You could write a batch file to swap the
standard executable with the modified one, and have it swap
an include file at the same time, then #include it and test the
variable you declare there.
-- file subdivision.inc
#declare SUBDIVISION = on;
-- file subdivision.bak
#declare SUBDIVISION = off;
-- file somefile.pov
#include "subdivision.inc"
#if (SUBDIVISION = on)
// non-standard code
#else
// standard code
#end
-- file swap_pov.bat (for DOS)
cd **povdirectory**
ren pvengine.exe pvengine.tmp
ren pvengine.bak pvengine.exe
ren pvengine.tmp pvengine.bak
ren subdivision.inc subdivision.tmp
ren subdivision.bak subdivision.inc
ren subdivision.tmp subdivision.bak
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Tim Attwood wrote, regarding POV-Sub:
> However, it's a modified version, the improvements in the 3.7 betas
> are not in that code... I'm unsure if the authors will update POV-sub
> when 3.7 comes out of beta.
Man, I hope they do. The subdivision patch is extremely useful!
> Note: the standard POV mesh code
> is highly optimized, so IMHO it's unlikely that such extended syntax
> will be adopted as standard.
Meaning the subdivision patch? I hope that isn't true :( I want to see
it become part of the official version. It would make POV-Ray more
useful as a modeler >> hint hint :)
~Sam
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I just tested the patch with the beta version. Unfortunately, the
combination is buggy. I'm unable to open files, though I am able to render
whatever file the program loads automatically.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
SharkD <nomail@nomail> wrote:
> I just tested the patch with the beta version.
Beta version of what?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The beta version of POV-Ray.
Warp <war### [at] tag povrayorg> wrote:
> SharkD <nomail@nomail> wrote:
> > I just tested the patch with the beta version.
>
> Beta version of what?
>
> --
> - Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
SharkD <nomail@nomail> wrote:
> The beta version of POV-Ray.
I don't understand how you can apply a patch to a verion of POV-Ray with
no source code.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
It's a sekrit.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think most of this patch resides in it's own
executable... but a modified pvengine (3.6) is
modified to link it, I think. Don't get those files
with the same names too confused =P
MD5 of version 3.6.1c.icl8.win32
57ABA6087FB8F96289026F4E6F403469 *pvengine.exe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
SharkD <nomail@nomail> wrote:
> It's a sekrit.
What does that mean?
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
