[Rogurt]

Hi there,

just installed v3. Compared to v2 the material editor (mxed.exe) is very slow. The task manager shows that my 2 xeon cpus are in no way working at full speed. With material editor in v2 the task manager shows a quite constant 60-90% processor load. Identical materials render much slower in v3. Also it shows that the load is not the same over time but bounces up and down between 6% to 70%.

What´s up here? Has someone experienced the same?

[eric nixon]

For me the mw3 mxed is much slower, both opening and using it. I haven't explored the issue because I thought it was a temporary beta bug, but despite mentioning the issue I have seen no discussion about it, nor any improvement

Re. opening slowness which is variable, i suspect mxed is searching for file paths. Re. usage slowness, I think some bad code crept in as the ui became modular when procedurals were inroduced.

[Nova66]

Re. opening slowness which is variable

I'm seeing random opening slowness as well.

Andrew.

[Rogurt]

speaking of UI: I really feel that mxed UI suffered since I cannot have the colour picker left open while switching between Layers, BSDFs, Colour 0/90 etc. Now I have to click dozens of times more than before.

[dariolanza]

Hello Rogurt,

That impossibility of having the Color Picker opened while switching between layers and so is one of the known disadvantages of witching the MXED panels from non-modal to more rigid modal on Maxwell 3.0.
We discussed a lot about pros and cons, but switching them to non-modal was mandatory to host the new Procedural textures (demanded by many many users) so we evaluated pros and cons and decided to go to non-modal panels like what we have today.

We know those inconveniences (we knew that even before starting the development) but we still believe the gain is worth the change.
Unluckily, it is not possible to have the best of both words.

Greetings

Dario Lanza

[Rogurt]

so what about the slow speed of the v3 mxed? I really cant edit materials when waiting proximately 2-5 times longer compared to v2...

[eric nixon]

It seems NL are saying; We were always aware mxed UI would become painful to use, but we did it anyway for no actual gain (procedurals don't work and will be replaced in a future release). It sounds like they don't use MXED much, don't care about the users, and have no plans to rectify the situation. TBH It doesn't inspire confidence about future development. Maxwell2 was a polished professional product, obviously made by a proud team. MW3 not so much.

The benefits of MW3 IMO are Motion Blur, film response toning. (additive materials are still buggy, but a bonus also)

The benefit of MW2 are stability and a speedy UI, and a generally polished product.


If Dario had said something which suggested the problem was temporary I wouldn't be so pissed off.

[Rogurt]

Once more: what about the sluggish, slow mxed intern rendering? I just CANT edit materials like that!
Anyone: Do you experience the same or is mxed v3 comparable to v2 speed wise (I explicitely talk of rendering speed of the preview).

Cheers

[Rogurt]

Darn! Where is the "next preview" and "previous preview" button gone? How do I compare settings now!?
Are all UX Designers fired or dead at Next Limit?

[F. Tella]

Hi Rogur,

You have those options by right clicking in the preview image: Previews (list), Store and Remove.

Regarding the speed rendering the preview I'm answering through e-mail, but anyway, that's not my experience here.

Does it happen with all the preview scenes?

Are you using old preview scenes maybe?

Does something similar happen with FIRE or rendering with production engine (regarding the workload of processors)?

Please, let me know about this.

Regards,

Fernando

[Rogurt]

Hi Fernando,

I know about the right click preview option. This takes several clicks more than in v2. Changing back and forth between several states of a material becomes veeeery tedious like that.

I turned on "Production" as Preview Engine and the workload is up to 100% again. When changing back to "draft" it behaved similar to mxed v2 (60-80% load). Cant reproduce any more. I will have to look further into that (e.g testing with fire within c4d)...

Preview Scenes are just thev3 stock ones. But I plan to copy/paste my old v2 ones. Do you suggest that may cause problems?