Here's an other render test, with a generic shader .... again to validate the workflow and see how textures can hide some modeling details. I have a better idea where to put details and where it's not needed.

So now I just have to finish the modeling .. See you in one month :P

The textures are looking fantastic in the test, can't wait to see the whole thing done! :)

re: display speed - if you'd like to send me the model that is bogging down, I could try using it to do some profiling over here to try and narrow down what is causing the most slowdown. But I've actually done quite a lot of work on that already in v1. However maybe I'll see that there are some particular kinds of surfaces that are getting too heavily meshed and that might give me an idea on how to compensate for that.

One thing you might also try in addition to the meshing settings is to turn the hidden-line display off - the hidden lines display does a second pass through curves, so turning it off will reduce the amount of curve drawing by half.

- Michael

Hi Petr,

You wrote:
> On the other hand, the gears in clock, it isn't about the power or torque.
> It is just matter of silent and patient cogwheels motion

Yes I agree, practically, you wouldn't use such gears in a power torque situation, I was referring to to the visual aspect of Pascal's project.
If we were going to build this thing literally (which would be so cool) :) yeah, you would have to engineer it properly.

Cheers

Hi Michael,

I've mail you the object.

The 'problem' in fact it's not exactly the display speed, I'm quite happy with it, but I get problem to do transformation, like moving or rotation of the whole object ... it's nearly impossible :S. No way to place the mirror line too.

Btw a little smoke test :)

Hi PaQ, cool smoke test!

re: Transformation speed instead of display speed - that is an area that I can more easily improve.

Currently it creates a complete copied object for every transformation result, and especially mirror does a bunch of work that tends to make it slow on larger objects.

It should be possible for me to improve this quite a bit to kind of redraw the existing object during the dynamic part of transformations instead of making actual duplicates until you are finished.

- Michael

Hi Michael.

That sounds really great.

I dont' know if it's the same 'redrawing' problem that also slow down the extrude function. It's probably less critical, but I also fell some huge slow down when extruding complex shape, like for example an 60 teethes gear created with the spur gear script.

Whatever, can't wait to see the improvement !

Have a good Siggraph :)

Hi PaQ - the basic problem is that a very complex object that takes up a really big chunk of memory (like your objects in the file you sent me take up about 0.5 GB) can take some time to process.

For extrude, it is just taking that long to create the object and also the object's mesh.

Improving extrude will be a lot more difficult, because there is not an already existing equivalent object that can just be drawn in a new location like it is possible to do with transforms.

In the future to improve things like extrude it will pretty much require doing a kind of wireframe mode instead of shaded mode, a wireframe mode will avoid the mesh calculation step which will be the most time consuming part for something like extrude. But I also want to make the mesh calculation multi-core capable which should help out as well.

- Michael

Sure a wireframe view will help a lot ... Can't wait for the multi-core meshing too :)