MoI discussion forum
MoI discussion forum

Full Version: Hidden line removal progress

Show messages:  1-8  …  229-248  249-268  269-288  289-296

From: Bard (BFM)
21 Nov 2013   [#289] In reply to [#46]
Hello Mike K4ICY, beau bee, bee, buzz, balèze (hulk, huge) in the MoI galery.
From: Michael Gibson
21 Nov 2013   [#290] In reply to [#288]
Hi Max, I think that Rhino's one is based on intersecting curves with one another, while MoI's one is based on following a curve and using a pixel depth buffer to determine whether things are hidden or not.

So yeah they use a different approach and that's part of why they have different abilities too, like Rhino's one does not have any method for generating an outline or silhouette lines out to AI or PDF format like MoI's does.

I think it could be possible for me to increase the accuracy of MoI's one in the future, by incorporating some more detailed analysis of things when a curve is entering or exiting from the hidden state.

- Michael
From: wastzzz
21 Nov 2013   [#291] In reply to [#290]
Thanks for the explanation.
I like the idea of increasing the accuracy, if possible. Otherwise, for some technical drawings I am sticking to Rhino at the moment. It's not a problem. But the silhouettes+outlines output is really great for presenting a product quickly and clear.
From: Marc (TELLIER)
28 Nov 2013   [#292]
Hi,

Thanks again for this amazing feature!

I also use it to extract renders only, having the alpha channel is a very productive asset.
I'm getting used to the megapixel concept, so for a squarish viewport, 4 mp gives me about 2000px which is often quite enough for my needs.

Marc
From: Michael Gibson
28 Nov 2013   [#293] In reply to [#292]
You're welcome Marc, I'm glad that you're putting it to good use!

- Michael
From: Mike K4ICY (MAJIKMIKE)
30 Nov 2013   [#294]
...And another reason why I'm loving this new PDF-writer feature more and more!




I had to write a short article for our local ham club newsletter: http://k4tlh.net/tars-newsletter/

So last night I came up with an idea to break down the anatomy of one of the type of Morse code (CW) key I use which is called a "Bug" by Amateur radio operators.

This is a WWII "J-36" "Bug" (Vibroplex type) key manufactured by J.H. Bunnell in 1942. The base is a heavy piece of solid cast iron, and the rest is nickel coated brass.
The swing arm is moved one way to act as a way to make manually sent dashes "dah's" and moving the arm the other way causes a pendulum to reverberated a spring-loaded contact to produce exact dots "dit's".
The weight on the reed determines the frequency and will give you about 150 dits if needed with the default configuration yielding dots at about 40 word-per-minute speeds.
I have an added weight called a "Bug Tamer" which brings it down to 18 wpm.

This type of key was mostly perfected and mass-marketed by a company called Vibroplex starting in 1904 and is still in business today, though the concept goes back to the old telegraph days in the 1800's.

Go to this site to see a nifty Flash animation of how this key works::: http://www.ae4rv.com/tn/education/bug.htm


Armed with only a small engineer's ruler, I transposed the measurements into a MoI model, outputted it to a PDF, then used Corel to do the rest.

Though I could have just used the PDF result, I tend to develop certain niches with styling, and after spending two decades of hand-drawing, scanning and tracing to vector - I'm partial to the results.

Nothing too noteworthy, but a very basic result that did the job when needed.
From: Martin (MARTIN3D)
1 Dec 2013   [#295] In reply to [#294]
Hi Mike, I love your Bug illustration!
From: Mike K4ICY (MAJIKMIKE)
2 Dec 2013   [#296]
Thanks Martin!!!


Hi Michael,

Did anyone forget to mention that this new PDF feature essentially gives MoI the long sought after "PRINT" button option?

I know it's obvious.

;-)

Show messages:  1-8  …  229-248  249-268  269-288  289-296