Maxwell Render | Official public forum

Never came to grips with this, but often I want to move or scale an object or a texture interactively (where you grab the xyz arrows in the viewport) and it just doesn't work. Sometimes it does, sometimes it doesn't.

I'm sure there's a simple reason but I can't seem to figure out what the difference is between times it works and times it doesn't.

Thanks!

Same here.... just restarting the program helps....sometimes

Q!

+1 lately

I've had this issue a lot too. I sometimes find it happens when I'm in my fixed camera angle view or if the perspective view is a bit too crazy. If you check out the object properties while moving them, you may sometimes notice it is actually moving, just in really tiny increments.

Ah, ok. Glad I asked, it seems like more of a glitch then, I thought it was something that was supposed to happen and I couldn't grasp the reason.

Better to know.

+1

I always have to restart MR in order for the xyz and rotate gizmos to become usable again :(

Must be a bug!

+1
XYZ pivot is killing me.
Plus, when scaling a texture with it, instead of fine scaling, the texture is being scaled by miles...

I must admit I gave up trying to use the viewport tools directly years ago -- my rule has been: when you work in Studio don't work in the viewport, work in the interface.

Ever since I made that change it's been smooth sailing.

Best,
Jason.

Direct mouse-based manipulation of 3D data in perspective viewports has been around and working well since I first encountered it in commercial software way back in 1989 - so it should work flawlessly in 2012, no?

I'm not saying it's right -- I guess I'm just interested in how to work around the issue so I can get my work done... sorry to bother you with helpful advice.

Hej Jason, easy, my comment was not aimed at what you pointed out; but, see, if even you - with many years of Maxwell Render work experience - had to resort to using input fields only, it makes me wonder even more why viewport manipulation handles (not really an Open GL secret) have not been correctly implemented in the meantime.

If one is cloning, let's say, some chairs (instancing groups unfortunately also does not work - yet?) and just clicking on the X gizmo shoots them all over the 3D worldspace, frustration sets in. Having to arrange six chairs around a table (so their placement looks casual and convincing) numerically is just painful.

Here, this bug occurs after the viewport is changed from 3D to any of F, B, L and the like. As long as the viewport is not changed from 3D to any other, the gizmos do work.

Yup, that's at least a workaround. Unfortunately I do a lot of changing views in the viewport.

I also have a lot of frustration trying to manipulate maps m-Que, but when it's working it's ok. I swear, I'll never understand the scaling of textures in this sucker. I wish it was like MAX and real scale would be a godsend but even that only occasionally works as I would expect.

I'm sure these are just things in the pipeline at nextlimit, right?

You have two ways in Studio basically. I guess it's the same in all other applications: either changing the tiling, or manipulating the UV set directly.

http://support.nextlimit.com/display/ma ... +in+Studio

I think the problems I have are related to dealing with textures in models that come in from the plugins of the various modelling software I use, Rhino, Max, & Sketchup. The maps come in locked, but when you try to unlock and manipulate them is is a giant cluster^&%(%. The normalize doesn't work with real scale, the scale itself for the mapping makes no sense whatsoever, (why would a square bitmap have wildly different scales in the X, Y, or Z axis in order to be mapped correctly instead of stretched and warped), etc.

If there's a way to do this more effectively, I'm all ears. I've read the documentation and I find nothing. It's not such a big deal, I just have to do it by eye, but real scale textures working as expected would save me a lot of time.