Hi Burr,

> Nvidia quadro card. Just tried to turn off thread optimization witgh no change in result.

Hmmm, well that's disappointing!

Can you test what happens if you set DisplayThreadLimit=1 in MoI.ini (in the [View] section), does it then only show one actual core active when rotating the view or is the driver still using some itself then?

You also might try setting DisplayThreadLimit=6 or so and see if that produces some better results. It's possible with too many threads to actually have things degrade somewhat in areas where they need to be coordinated.

- Michael

Hi Michael,

Thanks for the new Beta!
I like the icons you used for deform tools

The enlarged pdf support will surely be handy.

Marc

Hmmm... no luck here either. :-/

I've tried it both with the "Global" setting as well as with one keyed for moi.exe.

I again tried different combos of thread levels.

It seems that "2" is still the fastest.
I also see four cores working, but that's because 2 cores are hyper-threaded to four.




And Triple Buffering seems to have no effect either way.

Setting a thread limit actually does limit the cpu's being used, but no real change... It appears maybe I see a 50ms change when going to something other than no limit, but I'm not sure.

I'll fool around a bit more with some of the other driver settings later. Any suggestions on those other than the thread optimization off?

Hi Mike,

> I also see four cores working, but that's because 2 cores are hyper-threaded to four.

Hmm but when you set the limit in MoI to 2 that should mean only 2 threads (so 2 entries in the task manager) are crunching away with possibly some amount on a third thread where it is talking to the driver on the main thread.

If you still see 4 cores going, that sounds like the driver is still using multiple threads itself despite that particular "Threaded optimization" setting being turned off. I was going to say try the global setting instead of the per-app one but I just saw that you tried that already.

Is it possible that there is a separate Direct3D and OpenGL sections for driver settings? You would want to be in the Direct3D one if so.

Otherwise, some generic advice might be to upgrade to the latest video driver if you are on an older version, maybe there was a problem at some point with it not paying attention to the threaded optimization setting...

- Michael

Hi Burr,

> I'll fool around a bit more with some of the other driver settings later. Any suggestions on
> those other than the thread optimization off?

Nope, I'd leave everything else other than "threaded optimization" to be at the defaults. Also make sure not to force anti-aliasing on with the driver settings or else it can mess up how selection works in MoI.

But also now that I see what your test file is like, a "sphere grid" is actually a particular kind of case since each sphere only has a single edge in it. So your test file happens to be heavy on surface drawing and light on edge drawing, and it's actually edge drawing that consumes the most CPU and also therefore has the most to benefit from the multi-core use as well.

On a more real model you would tend to have more than just one edge for each surface, especially with areas that have been cut and booleaned.

- Michael

Thanks,

I shall try to get in contact with my brother and see what he's got set up in this thing...
But I'll do some snooping myself to see what I can break. ;-)

Since the weekend is upon me, maybe I can concentrate on souping up the system that really needs it (at home.)
It's only got two cores. Maybe I'll be pleasantly surprised. :-)

Fun, fun!

Hi Ditto - re: flickering on spheres, I haven't seen anything like that over here so far.

Can you please post a 3DM model file for a simple case where it is happening for you just so I can make sure I can have the same test case over here for looking at?

Also do you have any custom settings set under Options > View > Meshing parameters - are your settings there the default Mesh angle = 10 degrees and "Add detail to inflections" enabled?

- Michael

Nice Job Michael! The new Isocurves will be very useful!

I tested the benchmarks & saw a substantial speed-up.

I'm running with mesh angle @ 6 deg. & used AutoRotate2 to get an average speed:

April Beta = 53 ms.
July Beta = 17 ms.

got a dumb question. Where might I find my license key?

>Michael

Can you look in your nVidia driver settings to see if there is any option like "Threaded optimization" which can be turned off? Do you see any change in MoI after that?




In the Nvidia control panel,on advanced 3D settings i tried ON-OFF-AUTO,global settings and also -MOI V3 July-dedicated settings




GPU-Z screenshot about my card



during thread optimization turned -OFF- i ran windows task manager and i saw all four threads working(maybe they didn't run?..forgive me if i have misunderstood what you mean)

see below attached screenshots with all options:no great changes

good night Michael (here is midnight) see you tomorrow

Hi beanworks,

> got a dumb question. Where might I find my license key?

Well, it's sent to you by e-mail originally. Right now it is not displayed in the actual program UI anywhere but it is written as a text file which you can open up in a text editor (like notepad on Windows or TextEdit.app on Mac) to see.

The text file is in the same location as moi.ini, and will be named moi_v2_license.key - you can find out where your moi.ini file is at by going to Options > General , and push the "Edit .ini file" button. In the dialog that pops up, it will tell you where the ini file is located at and your moi_v2_license.key file should be in that same directory.

- Michael

Hi danperk, that is a great speedup, and cool twisty model too!

What video card are you using on that machine?

- Michael

Thanks! I'm running an ATI 5870 - 1GB & Intel 930 Quad.

awesome, found it. thank you for everything!

Okay!

I tried a model on my home PC.

I have a Pentium 4 (2 core), 1 g. ram
NVIDIA GeForce4 Ti 4800 SE


I see one core taking the brunt in the older version, and two cores working just as hard in the new one.

MoI's timing with this particular model:

116 ms and 100 ms. %14 (?)

""""""""""""But also now that I see what your test file is like, a "sphere grid" is actually a particular kind of case since each sphere only has a single edge in it. So your test file happens to be heavy on surface drawing and light on edge drawing, and it's actually edge drawing that consumes the most CPU and also therefore has the most to benefit from the multi-core use as well.""""""""""

Rat's... We already talked about that... Shouldve known.... Never mind.

Re-tested on an edgy model.

V2 = 220 ms
V3 = 120 ms

Much better. my bad.

Hi Burr, yup that's more like it... Also an edgy model with Hidden line display enabled will probably see the biggest difference.

With this edgy model, do you see any difference if setting DisplayThreadLimit=6 or DisplayThreadLimit=8 on your dual-quad-core ? I'm still not so sure that one thread per "virtual" core is the best way to go on a hyperthreaded machine or not.

- Michael

Hi Mike,

> I have a Pentium 4 (2 core), 1 g. ram
> NVIDIA GeForce4 Ti 4800 SE

Not really too surprising there isn't much gain there, because the GeForce4 Ti 4800 SE is basically an antique at this point - it comes from the 4th generation nVidia wave, they are on the 15th generation right now...

Especially if it's in an AGP 1x or 2x slot probably the card is the bottleneck. Multi-core CPU use can only help things out if the video card and bus is speedy enough that the card can handle more stuff than what one CPU can chug out. If the card is not able to keep much ahead of just 1 CPU then having more than 1 CPU also going won't really do much.

However recent trends have been that video cards have become faster at a greater pace than CPUs - for various reasons CPUs are basically stuck at around their current speed and the focus is more on having several cores available, so this new system in MoI is pretty good for the direction that things are going.

Your GeForce4 card though is nearly 10 years old at this point, as far as GPUs go that's like an eternity, it's basically a nice feature that MoI is able to run at all on these kinds of old generation cards (MoI actually does run on the 1st generation GeForce and Radeons!), but you're probably not going to get much benefit for things that are tuned more for current generation stuff.

I would have expected a better result on your work machine though definitely... From what you were describing it kind of sounds like the multi-core use of the driver is still on despite changing that setting, I don't know if possibly that is a driver problem that has been fixed in a newer driver version, but that could be possible.

- Michael