 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
omniVERSE wrote:
> At first I thought you had posted to the wrong place.
> I figured out what you meant and looked around on the 'net. Ended up at a GNU
> RCS web page and bookmarked it. If it's what I think it is might be useful
> alright. I never "program" anything, only used to do some Basic language, but
> if I get what this RCS can do then it might be worthwhile to have around instead
> of trying to save a current file with a new name (I have many of those and often
> lose track of which is the best or latest). Really not sure, I'm filling my PC
> up so much all the time as it is the computer is slowing up on me, no harm in
> checking it out though.
>
> http://www.cs.purdue.edu/homes/trinkle/RCS/index.html is the one I came across.
>
> Thanks for that offer of help too.
>
> Bob
Here is one location you can get CVS and RCS from:
http://www.cyclic.com/pub/
Here is where RCS is on their servers:
http://www.cyclic.com/pub/rcs/
That includes Windows NT versions. (This also works for Windows 9X, since it's
really just a Win32 version)
Quickstart:
* make a C:\bin directory
* add it to your PATH
* go there
* extract rcs57nt.zip
* extract diff27nt.zip
* read some docs :-)
* go to where you are working on stuff
* create a 'RCS' directory (all caps, if you can)
* ci -l *.pov
Now each one should ask you to enter a description.
the "-l" option makes it check back out a locked version after the check-in is
done. A locked version is one that you can edit.
And whenever you finish editing a .pov file and are at a stage that you might want
to keep around, or just before you start doing strange experiments in it...
ci -l myfile.pov
voila! you have source control.
the command
rcsdiff myfile.pov
will show you what has changed since your last check-in.
the command
rcslog myfile.pov
will show you a history on that file.
--
"My new computer's got the clocks, it rocks
But it was obsolete before I opened the box" - W.A.Y.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Too late, I had already downloaded the RCS from the Cyclic site and just didn't
mention I did. Reason I went looking elsewhere was because they said no
document came with the zip files but that didn't stop me from doing the two
D/L's.
Thanks to your little tutorial here I might be able to use those zips after all.
I just didn't go looking for the reading material for them. Interesting concept
it is, now I'll end up wondering how this could be a good feature in POV-Ray
itself.
Bob
"Jon A. Cruz" <jon### [at] geocities com> wrote in message
news:388### [at] geocitiescom...
> Here is one location you can get CVS and RCS from:
>
> http://www.cyclic.com/pub/
>
> Here is where RCS is on their servers:
>
> http://www.cyclic.com/pub/rcs/
>
> That includes Windows NT versions. (This also works for Windows 9X, since it's
> really just a Win32 version)
>
>
> Quickstart:
> * make a C:\bin directory
> * add it to your PATH
> * go there
> * extract rcs57nt.zip
> * extract diff27nt.zip
> * read some docs :-)
> * go to where you are working on stuff
> * create a 'RCS' directory (all caps, if you can)
>
> * ci -l *.pov
>
> Now each one should ask you to enter a description.
> the "-l" option makes it check back out a locked version after the check-in is
> done. A locked version is one that you can edit.
>
> And whenever you finish editing a .pov file and are at a stage that you might
want
> to keep around, or just before you start doing strange experiments in it...
>
> ci -l myfile.pov
>
> voila! you have source control.
>
> the command
> rcsdiff myfile.pov
> will show you what has changed since your last check-in.
>
> the command
> rcslog myfile.pov
> will show you a history on that file.
>
>
> --
> "My new computer's got the clocks, it rocks
> But it was obsolete before I opened the box" - W.A.Y.
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Jon A. Cruz" wrote:
> Quickstart:
> * make a C:\bin directory
> * add it to your PATH
> * go there
> * extract rcs57nt.zip
> * extract diff27nt.zip
> * read some docs :-)
> * go to where you are working on stuff
> * create a 'RCS' directory (all caps, if you can)
>
> * ci -l *.pov
>
> Now each one should ask you to enter a description.
> the "-l" option makes it check back out a locked version after the check-in is
> done. A locked version is one that you can edit.
>
> And whenever you finish editing a .pov file and are at a stage that you might want
> to keep around, or just before you start doing strange experiments in it...
>
> ci -l myfile.pov
>
> voila! you have source control.
>
> the command
> rcsdiff myfile.pov
> will show you what has changed since your last check-in.
>
> the command
> rcslog myfile.pov
> will show you a history on that file.
That sounds like an aweful lot of work when you can just hit the "save as"
button once in a while to save your work. Source control in a pov file is
almost pointless unless you have an image to go with it to compare the
visual output differences between the two files. <g>
--
Ken Tyler - 1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Ken" <tyl### [at] pacbellnet> wrote in message
news:38838122.8ACABBF5@pacbell.net...
>
> "Jon A. Cruz" wrote:
>
> > And whenever you finish editing a .pov file and are at a stage that you
might want
> > to keep around, or just before you start doing strange experiments in it...
> >
> > ci -l myfile.pov
> >
> > the command
> > rcsdiff myfile.pov
> > will show you what has changed since your last check-in.
> >
> > the command
> > rcslog myfile.pov
> > will show you a history on that file.
>
> That sounds like an aweful lot of work when you can just hit the "save as"
> button once in a while to save your work. Source control in a pov file is
> almost pointless unless you have an image to go with it to compare the
> visual output differences between the two files. <g>
>
That was my point though, I have done the File/Save as... routine many times
before and get lot's of similar files that have to be deciphered at a later date
to tell which is which. Not easy to do, esp. when the rendered image alone
isn't altogether simple to compare. I may have deleted the good ones and kept
the bad ones trying to go by the most recent date.
Besides, there isn't a "Save as" button, would be a very good idea though.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Here it is again with a different perspective, the camera pans more and the dust
clouds have changed (for the worse? better?). Well, it's like I've been walking
backward as I try to improve this scene anyway.
The height field helps it I think. I know I'm going to need blobs or something
like that to use as container objects for the media, the CSG'd cylinders/spheres
are failing me here.
Btw, the clouds are a considerable distance away from the camera, just doesn't
look that way. The sun is behind them and to the right when the panning stops,
to give an idea about how the shadow is there. In POV units the hovercraft is
about 0.5 units across and the dust starts about 1000 units away then ends at
about 200 units away from the camera. So in reality (blurb) still very far off.
If the hovercraft object were 15 meters across that makes the cloud-front 6
kilometers away or approx. 4 miles, if I've figured this right. Ooooo, it's
vast...!
Without further ado, trial #3 (no one ever saw #2) and then back to work on it.
http://members.aol.com/persistenceofv/m_ds-hc2.mpg
440KB, 150 frames, 320X240 res. @ 24 fps Mpeg.
Happy viewing!
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> trial #3 (no one ever saw #2)
Mistaken... Very few people, one or two people probably, saw #1. #2 was the
animation you probably have seen, if at all, and it's still there at:
http://members.aol.com/persistenceofv/m_ds-ehc.mpg
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
omniVERSE schrieb:
>
> > trial #3 (no one ever saw #2)
>
> Mistaken... Very few people, one or two people probably, saw #1. #2 was the
> animation you probably have seen, if at all, and it's still there at:
> http://members.aol.com/persistenceofv/m_ds-ehc.mpg
>
> Bob
Yo Bob!
I just saw both versions of this incredible animation. There are two
things that I think are better in the first one.
First: the scene darkens slowly. This is very good seen on the ground
plane.
Second: also concerning the ground is the fact that shadows are forecast
which makes it more believable (I don't know if the shadows come from
the clouds (sky) or the storm)
The storm itself is better in the second version.
Waiting to see #3 ;-]
Karl
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
omniVERSE wrote:
>
> Here it is again with a different perspective, the camera pans more
> and the dust
> clouds have changed (for the worse? better?). Well, it's like I've
> been walking
> backward as I try to improve this scene anyway.
> The height field helps it I think. I know I'm going to need blobs or
> something
> like that to use as container objects for the media, the CSG'd
> cylinders/spheres
> are failing me here.
> Btw, the clouds are a considerable distance away from the camera, just
> doesn't
> look that way. The sun is behind them and to the right when the
> panning stops,
> to give an idea about how the shadow is there. In POV units the
> hovercraft is
> about 0.5 units across and the dust starts about 1000 units away then
> ends at
> about 200 units away from the camera. So in reality (blurb) still
> very far off.
> If the hovercraft object were 15 meters across that makes the
> cloud-front 6
> kilometers away or approx. 4 miles, if I've figured this right.
> Ooooo, it's
> vast...!
> Without further ado, trial #3 (no one ever saw #2) and then back to
> work on it.
>
> http://members.aol.com/persistenceofv/m_ds-hc2.mpg
>
> 440KB, 150 frames, 320X240 res. @ 24 fps Mpeg.
>
> Happy viewing!
> Bob
The dust in the storm is much better but in this version it seems the
containers are more visible which is a pity.
There's a quirk in the camera movement that is very distracting.
Remco
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Karl Pelzer" <Kar### [at] t-onlinede> wrote in message
news:3884C113.B56699A7@t-online.de...
> First: the scene darkens slowly. This is very good seen on the ground
> plane.
> Second: also concerning the ground is the fact that shadows are forecast
> which makes it more believable (I don't know if the shadows come from
> the clouds (sky) or the storm)
Dust cloud shadow, and it could use breaking up some I think. It became
apparent that it was going to mess up the whole thing when I wanted to have the
dust roll in slower, it had to be closer for a longer time then. That meant the
faked realism of it tends to lose credibility, or at least that's how I see it.
I had neglected to do anything about the dust trail of the hovercraft after
getting the height field in, it needs to follow the terrain better but I haven't
found a way to have puffs of dust showing only on the hilltops as it moves yet.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Remco de Korte" <rem### [at] xs4allnl> wrote in message
news:388### [at] xs4allnl...
> The dust in the storm is much better but in this version it seems the
> containers are more visible which is a pity.
> There's a quirk in the camera movement that is very distracting.
>
You don't like the camera panning either huh? :-) I'm going to smooth it out
more yet leave it generally the same. It's using the clockmod.inc deceleration
right now with a late start and early finish so it kind of jumps quickly into
motion at the beginning.
I've looked at using blobs for the dust containers now and it isn't pretty, even
more container edges than before. The attempt at improving the dust patterns
started showing the cylinder/sphere object a lot in m_ds-hc2.mpg. Not good...
Btw, I hope everyone who takes a look at these get the whole animation, when I
tested that the upload was okay the first time it chopped away the final part so
the hovercraft never passed by. On another click of the URL link it all came
through. It takes time anyway to view as you D/L of course but it had actually
quit too soon before.
Bob
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
