#Slice Command
12 messages in this thread
In playing with Imagine 1.0 I have had no luck getting the slice command to
work. I'm mainly referring to Tutorial 2(Page 33). After doing the slice
and waiting for the cancel gadget to disappear I have still have the same
thing. I think I understand how slice is suppose to work, but perhaps I'm
doing something wrong. I have tried it several times(10 at last count) and
no luck. I am extruding the A first just like it says. Has anyone else
run across this problem? Any help would be greatly appreciated.
Tim.. P.S. Imagine 1.0 is great and the Tutorial Guide is a huge
welcome!
Hi Tim! I too had that problem. It seems like most normal people, we both
glanced over a very important line about 3 words long. You must move the
plane to be in the middle of the extruded cookie cutter. Both from the top
front and right. That'll fix your problem and give you a covered face!
Hope this helps you out. I'm having problems making Imagine create glass.
No problem on mirrors, but I can't make an object to pass light at all.
Later,
Andrew
Aahh, so that's the problem. That thought jumped into my mind but got lost
I guess. Kinda makes more sense though that the object must actually be
through the plane to slice it. Thanks! Glass, Mirror. Hmm, I'm still
seeing what I can do with the object editors. Perhaps I'll be hitting you
up for some info on those in the near future. If there were only more hours
in the day.
Tim..
You could always do what I do… Lay out a mess of frames and let 'em
render overnight. Wake up, show 'em and keep the ones you like. So far I
managed to make a roundish spaceship and put it with a starfield and a
camera flyby. 60 frames rendered in HAM Interlaced overscan in just under
17 hours. Needs about 4 meg to play!
Later,
Andrew
Sounds pretty interesting. I would do my renderings at night but I run UUCP
in the early morning and it has a habit of locking the Amiga up. Rendering
with 030/FPU does make it a bit better though. I can let it go while I'm
at work. Hmm, getting close to the end of the tutorial book and the ideas
are flowing.
Tim..
You made it that far? 8) After the second tutorial, I threw out the book
and started playing. I love it! I'm actually learning by playing with
Imagine. Something I could never do with Imagine. Latest trick is using
VistaPro to create landscapes, then importing them into Imagine. It
produces some great stuff!
Andrew
Yea, I got most of the way through the tutorials then tossed the book to
the side at the last one. Though I didn't do that one, reading it over
helped me understand Make Path etc.. I've seen Vista, but not Vista Pro.
Is it worth the extra money?
Tim..
Yes, as a matter of fact, VistaPro is worth the money. If only to export
the landscapes as Turbo Silver objects for rendering in Imagine. I've been
doing some playing with it and it is a truely incredible program. I had
Vista and wasn't too pleased with the triangular shapes, that's fixed now.
Neat stuff you can do!
Later,
Andrew
Thanks, I'll be sure to add Vista Pro to my list. Getting back to the
origional subject. As you said I overlooked that one sentence and got it
to work. The only other area I had problems with was with IFF brush
wrapping. I imported a picture of ZZ TOP to the flag and when I rendered
it there was a gap in the middle. I decided to make the flag wave. When I
did this, the first frame still had a gap, but the rest of the frames
looked okay. Any ideas? The cycle editor tutorial was pretty good though
my cylinder man walk a little bull legged. Guess I could throw a hat on his
head and call him a cowboy. The stage tutorial was not bad though I
didn't do it all. I kinda wish there was a little more documentation on
stage. It seems powerful and easy to use, but it just seems like there is
something missing in the docs. I guess it's just a matter of playing
around with it and referring back to the reference guide.
Aloha
Tim..
Aloha?! 8) Yeah, the manuals do have a bit to be desired, but the overall
ease of use of the software is out of this world and more than makes up for
it.
I thought I'd bring up something interesting…. I've had the opertunity
(sic) to beta a bench mark program. The test went through several tests
and it seems that a 2500/30 beats out the 3000 slightly. Now I recently
had the chance to run Imagine on a 2500/30 and it was slugish compared to
the fluid use on the 3000. I wonder what gives?
Later,
Andrew
Andrew,
The reason the 3000 gives the appearnace of faster operation than the
2500/30 is that it is running the Kickstart in 32-bit RAM. You can
duplicate this on your 2500/30 with the program SETCPU and using the option
FASTROM. This will copy your 256k of OS into 32-bit memory causing a
drastic increase in screen i/o & other functions. Another point to
consider, the 3000's architecture from what I understand is full 32-bit –
that will cause some difference in itself.
I have an Amiga 500 with a CSA Mega Midget Racer , and using the benchmark
program AIB it rates as being slightly faster than the 3000 or 2500/30.
Joe
Is the 3000 set up with 2 megs of chip ram. If so that could be the
reason. I'm running Imagine on a GVP 030 at 28 Mhz and it seems to move
pretty good. I even tried the non-FPU version on a stock Amiga and it
wasn't as slow as I thought it would be(except for rendering of course). I
also have an ICD controller and a Quantum 105S. While I'll never get
enough speed, I feel that this combo should keep me happy for a while.(at
least till the 040's come out <grin>)
Tim..