![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
So, I've read somewhere here that someone somewhere else wanted that all
the folks here to just show what they're working on, even if it's
somehow far from being finished... ;-)
Anyways, since I've had a long streak of no inspiration and finally got
one, I've begun working on it right away. It's a little tedious, as I
have to get used to the new Silo (my subdivision surface modeller of
choice) Beta, and I haven't used POV-Ray to this extent for some time
now. I've made a couple of commissions, but mostly, that was tweaking
existing scenes, not starting a wholly new one.
This is the robot as it is right now. I'm still working on just about
all the parts, but have begun scripting the skeleton, so that I just
need to define angles to bend and twist the body parts. I'm not striving
for realism, but rather just a simple robotish feel. A fundamental (but
not yet visible) part of the image is an idea from a close friend of
mine (that's also where the robot idea stems from).
Even though it doesn't look like it, the final image will be much more
dramatic than this nice "sunny day" version, I'll probably post another
WIP when I'm posing the robot.
Regards,
Tim
--
aka "Tim Nikias"
Homepage: <http://www.nolights.de>
Post a reply to this message
Attachments:
Download 'robot.jpg' (55 KB)
Preview of image 'robot.jpg'
![robot.jpg](/povray.binaries.images/attachment/%3C4586ce4e%40news.povray.org%3E/robot.jpg?ttop=443866&toff=4100&preview=1)
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Tim Nikias wrote:
> It's a little tedious, as I have to get used to the new Silo (my
> subdivision surface modeller of choice) Beta...
Every time I hear of a new subdivision modelling program out there, I go
and check to see if it does posable models, partly because if it does,
and the learning curve isn't as horrid as Blender's, I can forget about
my own modeler and work on something else.
Regards,
John
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
John VanSickle wrote:
> Every time I hear of a new subdivision modelling program out there, I go
> and check to see if it does posable models, partly because if it does,
> and the learning curve isn't as horrid as Blender's, I can forget about
> my own modeler and work on something else.
Eh, why? Silo isn't that new actually, AFAIK it's been around 2 years...
Still, why would you forget about your own? I have fun writing scripts,
and if I'd be more inclined and much more motivated, I wouldn't mind
writing my own applications or at least add-ons to existing ones (e.g.
Silo, once 2.0 is out and plug-ins are supported).
And it's never bad to have a couple of different solutions to pick from,
only one choice for a workflow is pretty limiting...
Regards,
Tim
--
aka "Tim Nikias"
Homepage: <http://www.nolights.de>
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Tim Nikias wrote:
> John VanSickle wrote:
>
>> Every time I hear of a new subdivision modelling program out there, I
>> go and check to see if it does posable models, partly because if it
>> does, and the learning curve isn't as horrid as Blender's, I can
>> forget about my own modeler and work on something else.
>
> Eh, why?
I don't want to re-invent the wheel.
My primary desire in developing this app is to give the POV-Ray
community a tool for making posable models that can be animated by SDL
code. A lot of CSG models in .INC files can be posed based on #declares
that are set prior to calling the file; I wanted to have uv-mapped
subdivision surface models that can be used in the same way. This isn't
something that seems to be covered by any app out there (I may be
wrong), so for the moment I don't have any competition.
> And it's never bad to have a couple of different solutions to pick from,
> only one choice for a workflow is pretty limiting...
Probably true. But as things stand, my app doesn't play well with others.
Regards,
John
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |