|
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The images:
http://news.povray.org/povray.binaries.images/thread/%3Cweb.55cf44405a3a5488c6574dfe0%40news.povray.org%3E/
Post a reply to this message
Attachments:
Download 'bezier_spheresweep.inc.txt' (3 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"And" <49341109@ntnu.edu.tw> wrote:
> The images:
>
http://news.povray.org/povray.binaries.images/thread/%3Cweb.55cf44405a3a5488c6574dfe0%40news.povray.org%3E/
I want to add the bezier_spheresweep.inc and blending_polygon_circle_shape.inc
files to the exporter.
You can enter in them GPL LICENSE BLOCK and the authorship?
I can't violate your rights for authorship!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"LanuHum" <Lan### [at] yandexru> wrote:
> "And" <49341109@ntnu.edu.tw> wrote:
> > The images:
> >
http://news.povray.org/povray.binaries.images/thread/%3Cweb.55cf44405a3a5488c6574dfe0%40news.povray.org%3E/
>
> I want to add the bezier_spheresweep.inc and blending_polygon_circle_shape.inc
> files to the exporter.
> You can enter in them GPL LICENSE BLOCK and the authorship?
> I can't violate your rights for authorship!
Oh, I didn't see your message until today. Um... basically I'm willing to share
the macros to your exporter. It is also a good news for me. But in fact there
are still some minor bugs on the macros; and I have another version for the
'polygon to circle blending' macro. I would like to rearrange them and it will
need several weeks because I participate in a training about video producing
these days.
Okay, I will add an authorship and the GPL LICENSE BLOCK.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"And" <49341109@ntnu.edu.tw> wrote:
> "LanuHum" <Lan### [at] yandexru> wrote:
> > "And" <49341109@ntnu.edu.tw> wrote:
> > > The images:
> > >
http://news.povray.org/povray.binaries.images/thread/%3Cweb.55cf44405a3a5488c6574dfe0%40news.povray.org%3E/
> >
> > I want to add the bezier_spheresweep.inc and blending_polygon_circle_shape.inc
> > files to the exporter.
> > You can enter in them GPL LICENSE BLOCK and the authorship?
> > I can't violate your rights for authorship!
>
> Oh, I didn't see your message until today. Um... basically I'm willing to share
> the macros to your exporter. It is also a good news for me. But in fact there
> are still some minor bugs on the macros; and I have another version for the
> 'polygon to circle blending' macro. I would like to rearrange them and it will
> need several weeks because I participate in a training about video producing
> these days.
>
> Okay, I will add an authorship and the GPL LICENSE BLOCK.
Thanks!
GitHub allows to make changes to files. I will always update if you improve
them.
Now blending looks so:
Post a reply to this message
Attachments:
Download 'polygon_to_circle_blending.jpg' (57 KB)
Preview of image 'polygon_to_circle_blending.jpg'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"LanuHum" <Lan### [at] yandexru> wrote:
> "And" <49341109@ntnu.edu.tw> wrote:
> > "LanuHum" <Lan### [at] yandexru> wrote:
> > > "And" <49341109@ntnu.edu.tw> wrote:
> > > > The images:
> > > >
http://news.povray.org/povray.binaries.images/thread/%3Cweb.55cf44405a3a5488c6574dfe0%40news.povray.org%3E/
> > >
> > > I want to add the bezier_spheresweep.inc and blending_polygon_circle_shape.inc
> > > files to the exporter.
> > > You can enter in them GPL LICENSE BLOCK and the authorship?
> > > I can't violate your rights for authorship!
> >
> > Oh, I didn't see your message until today. Um... basically I'm willing to share
> > the macros to your exporter. It is also a good news for me. But in fact there
> > are still some minor bugs on the macros; and I have another version for the
> > 'polygon to circle blending' macro. I would like to rearrange them and it will
> > need several weeks because I participate in a training about video producing
> > these days.
> >
> > Okay, I will add an authorship and the GPL LICENSE BLOCK.
>
> Thanks!
> GitHub allows to make changes to files. I will always update if you improve
> them.
> Now blending looks so:
I will add the previous post:
https://github.com/Lanuhum/BlendPov-alternative/tree/master/povray/include
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
And, you watch my screenshots. I can create in the Blender everything, including
sphere sweep. Export and parsing is time. I consider that macros save time. I
hope that Povray will read and will calculate a macro quicker, than
blob {
object { sphere matrix }
object { sphere matrix }
and so on 100500 objects sphere
}
:):):)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 05.09.2015 um 21:35 schrieb LanuHum:
> And, you watch my screenshots. I can create in the Blender everything, including
> sphere sweep. Export and parsing is time. I consider that macros save time. I
> hope that Povray will read and will calculate a macro quicker, than
> blob {
> object { sphere matrix }
> object { sphere matrix }
> and so on 100500 objects sphere
> }
> :):):)
Actually, the current parser's macro and loop performance is rather
poor; if you want fast parsing, you're always better off just writing
one huge file without any loops or macros.
One of the worst things you can do is place a macro in an include file,
and call that macro a lot from the main file. This will cause POV-Ray to
repeatedly open and close that include file for each and every macro
invocation.
The only thing that can actually save time is functions.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 05.09.2015 um 21:35 schrieb LanuHum:
> > And, you watch my screenshots. I can create in the Blender everything, including
> > sphere sweep. Export and parsing is time. I consider that macros save time. I
> > hope that Povray will read and will calculate a macro quicker, than
> > blob {
> > object { sphere matrix }
> > object { sphere matrix }
> > and so on 100500 objects sphere
> > }
> > :):):)
>
> Actually, the current parser's macro and loop performance is rather
> poor; if you want fast parsing, you're always better off just writing
> one huge file without any loops or macros.
>
> One of the worst things you can do is place a macro in an include file,
> and call that macro a lot from the main file. This will cause POV-Ray to
> repeatedly open and close that include file for each and every macro
> invocation.
>
> The only thing that can actually save time is functions.
Thanks.
Sadly.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2015-09-06 08:47 AM (-4), clipka wrote:
> One of the worst things you can do is place a macro in an include file,
> and call that macro a lot from the main file. This will cause POV-Ray to
> repeatedly open and close that include file for each and every macro
> invocation.
And this is exactly how both And and I implemented sphere sweep unions
and merges (by calling Connect_Spheres() in shapes.inc). Still, the
parse times seem negligible, probably due to file caching.
Nevertheless, you have now persuaded me to write a substitute for VEq()
in SphereSweep, especially since, for that module's purposes, the
arguments needed preprocessing anyway before passing them to VEq().
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 05.09.2015 um 21:35 schrieb LanuHum:
> > And, you watch my screenshots. I can create in the Blender everything, including
> > sphere sweep. Export and parsing is time. I consider that macros save time. I
> > hope that Povray will read and will calculate a macro quicker, than
> > blob {
> > object { sphere matrix }
> > object { sphere matrix }
> > and so on 100500 objects sphere
> > }
> > :):):)
>
> Actually, the current parser's macro and loop performance is rather
> poor; if you want fast parsing, you're always better off just writing
> one huge file without any loops or macros.
>
> One of the worst things you can do is place a macro in an include file,
> and call that macro a lot from the main file. This will cause POV-Ray to
> repeatedly open and close that include file for each and every macro
> invocation.
>
I also think so. Although I'm not so professional on this working. Of course you
can save time on exporting the huge file.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |