[giacob]

Studio is a mess, it crashes allll the time and the material assignment is poor followed with selection bugs and loads of other problems…

It's strange how widely all our collective experiences of using Studio differs, it never crashes for me and I find material assignment a joy.

u really mean that u find selecting a large numbers of items not very slow? at least 5-10 time slower than max for instance...? i dont beleive u at all unless u have a very good hardware .. but the fact is that on the same hardware max is faster .. very much faster than studio...
- another facts: when importing items to replace it many times crashes.. no doubt that is what a vast majority experiences
as we say " a single swallow doesnt means is spring"...

[smeggy]

Maxwell still crashes Max all the time, especially when hitting the render buton.. pop, all gone. It's flakey and not perticularly fun to use. I pretty much gave up using maxwell from frustration. After all this time I really don't care anymore and will probably find a different renderer to use though It's still fun to see what you guys are up to.

[giacob]

the plugin is stable in my experience....the studio is stable also but when trying to replace entities...and is slow...damm slow... i could use the max plugin and i do but max plugin has the difect that one cant see textures..whicc is the point in favour of studio
in the end the chance are 2:
- making the textures visible in the max plugin;
- making the studio work better
choise what u want Nl but do something....

[glebe digital]

u really mean that u find selecting a large numbers of items not very slow? at least 5-10 time slower than max for instance...? i dont beleive u at all unless u have a very good hardware .. but the fact is that on the same hardware max is faster .. very much faster than studio...
- another facts: when importing items to replace it many times crashes.. no doubt that is what a vast majority experiences
as we say " a single swallow doesnt means is spring"...

I run MWR on an athlonX2+4800 with 4gig ram, so I guess that makes a big difference.......I built that PC to specifically run MWR and it gives me no problems. In fact, large data-sets are handled much better in MWR than in Lightwave, selecting/grouping objects is not a problem.
Replacing objects is no problem if you've found your workaround, mine is to by-pass the plug-ins completely, but we use different software........

You're right about the swallows, but that point of view quickly leads to sophistry........how about 'the early bird catches the worm'......that's equally pertinent but equally pointless IMHO.

I've tried running MWR on my P4 and yes it is slow and stilted..........I think dual-cores are the only solution if you want to use MWR for production.

[jespi]

Hy mike. Could you help me? I know you are maya´s user and i´m a 3dsmax user, but maybe you know what am i doing wrong.

i´m trying make a brick wall with a grafity, i´ve thought that a way was make two layers, the first with a brick´s bitmap and the second with the grafity bitmap. First i´ve adjust the uvw maps(two uvwmaps)with standars materials to previsualize the scale of both materials.The next is change the standars materials to mxm materials. Now i have the mxm with uvwmap applied to the wall.But when i push render i have this error:
MXS file read successfully

>> Checking Data...

>> Loading Bitmaps & Preprocessing Data...

>> Error: UVW channels ( 2 ) on object "Box01" not enough for material "uvw"

>> Render Failed.

but if i do the same only with a uvwmap the render is done, but this way don´t permit me to fix tha grafiti where i want.

Thanks

[Mihai]

Make sure your brick texture uses projector 0 in the texture picker (the thing you use to load a texture), and the graffiti texture uses projector 1. It looks like you used projector 2 for one of the textures which would mean the object needs 3 uv maps, and that's why you get that error. Means there aren't enough uv projections on the object to render that material.

[jespi]

Thank you very much Mihai, problem solved . Another question, do you know why in the texture picker i only see a part of the bitmap when i load it?

[Mihai]

It's normal, it doesn't mean it crops the texture, it just shows it at full size, but doesn't show all of it. I'm not sure if this could be a problem for some, for me it isn't. I just need verification that it's the right texture, I don't really need to see all of it and if it speeds things up with loading very large textures, I'm fine with it.

[jespi]

No problem for me if in the render the image don´t look reduce.

Thanks and cheers Mihai

[ludenhud]

When I worked in studio for about 5-7h one day I got it to crash at Least 20 times.

What caused it to crash was render region, import object to an existing scene, save scene and much more. The fact that it's slower than working within maya is nothing that drives me as crazy as the crashes.

Without the crashing probs and the selection tool, importing methods and other small bugs and issues, I have to say I’m pretty cool with it. Even though I much rather would do everything via plugin.

[Mihai]

What graphics card do you have ludenhud?

[ludenhud]

RADEON X300

[lllab]

i find studio quite stable and fine beside the camera management,
and tht i cannot group other groups and that i cannot import grouped things from my host app. it seems studio only can group one level deep. thats bad.

a good thing would be support of layers and groups as they are in most apps,
and that gouping and layering stays when imported via plugin. also it should convert all cameras from the host app, not only the active one.

but i like the interface and overall impression of studio.

cheers
stefan

[Mihai]

Lots of crashes can be due to graphics card, and on top of that the drivers used by the card. I get the impression there a lot more problems when using ATI cards. I have a somewhat old Geforce and Studio is very stable, the viewport speed is even faster than in XSI.

[JDHill]

...I had a setting on my video card that would crash my entire machine whenever I turned on SkyDome...fixed it early on, and no more problems from there on out. I don't think Studio is unstable...just yesterday, I was moving around, grouping, hiding, assigning materials, etc...on a 12.6m polygon scene...it obviously didn't move too fast, but it didn't crash even once.

~JD