Resume

My work is done :-)
Step by step with fabulous description.
Two questions stay. First the image below. The edges in the middle ( red arrow ) couldn't be used with fillets. I don't know why, because there are the same edges like in PaQ's Turtorial.
I've a suspicion. My workstation
(Computer Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz 2.05 GHz, 2,00 GB RAM with Winxp seems to be overstrained. Is MoI developed for dual core processor? Any activity with bigger meshes work very slow. If I compare my MoI and the application from PaQ there are many differences.





Regards

Michael

Hi Apophis,

First for you performance problem, check this in the options settings :



- Unchecking the 'add detail to inflections' will boost MoI.

I don't think MoI is multithreaded for the moment, so you should have mostly the same speed as in the video (quad 3.0 here).

For the fillet problem, it's a question of sequence to respect :



The edge you're pointing should be filleted before the side surface.
(You can still correct it, I can create an other quick video this evening)

For the offline video, I have to check how I can do that using the screencast service.

Thanks Pilou, Wink seems to create nice video too. I Will have a look at this this evening, I hope it's possible to edit the movie after recording (I moslty need some cutting tool).

Of course yes you can edit anything ;)
Key delete is your friend :)

Right click and "save target as"... Play with browser on local machine.

http://www.exeink.com/caps/rip/full_pump.swf

Screen cast pumps it out as a "50 MB" file. Trying to re-encode it now to bring the size down.

[EDIT]
Gave up on trying to re-encode it. If you want it locally download the 50 mb file.
It wont be there forever! at least a few weeks.

Some browsers wont play the native flash file. I've attached an html file that will play the flash video. It must be in the same place as the flash file.
[EDIT]

Thanks a lot for the hosting BurrMan, my screencast bandwidth limit is allready over.
I definively have to find a better compression solution.

I think that the jing screencast thing doesnt give much control of that. thats what the paid versions give is more control of the output. The original capture could be much smaller, but to "grab" what screencast pushes down was not an acceptable solution.

Looks that jing project it's just an advertising for screencast service, since yesterday I allready get 5 mails about bandwidth limit :S