|
|
|
Tell us what you think of the site.
|
Autodesk Media & Entertainment User Community
|
Autodesk® 3ds Max®
|
|
Autodesk® Maya®
|
|
Autodesk® Softimage®
|
|
Autodesk® MotionBuilder®
|
|
Autodesk® Mudbox™
|
|
Autodesk® ImageModeler™
|
|
Autodesk® Sketchbook® Pro
|
|
Autodesk® Smoke on Mac®
|
|
Autodesk® Entertainment Creation Suite Ultimate®
|
| sp5 - bugs still not fixed
|
|
|
this can´t be true, five servicepacks in short time, still existential bugs! it feels like nitrous is playing games with autodesk. bitmap quality in viewport, ha! leaving isolate mode and loosing the camera view, urgh! we rendered hundreds of perspective views now instead of camera views. very disappointing.
Matthias
|
|
|
|
|
Are you using the fancy new viewport arrangement switching buttons on the lower left?
I just had a problem like that...If you open your scene and it is not arranged how you saved it you might have a problem because that is how the render servers are going to open the job.
I have started submitting jobs ONLY based on closing the scene, open the scene, select the viewport/camera I want and sending the job.
Author: Doughboy12
|
| Replied: 13 September 2012 05:21 AM
|
|
|
|
|
|
|
You should use state sets and record the camera/viewport to be assigned. This should ensure that the proper camera is used. Personally I never have this problem, but that is because I make sure stuff like that is take care of ahead of time.
-Eric
Author: PiXeL_MoNKeY
|
| Replied: 13 September 2012 07:28 AM
|
|
|
|
|
|
|
|
Yes Eric, we should all always make sure that the things we take for granted are no longer taken for granted...Glad it ALWAYS works for you.
Author: Doughboy12
|
| Replied: 13 September 2012 07:58 AM
|
|
|
|
|
|
|
I got your back Eric. This sounds just like careless behavior to me. Change to what is essentially a different camera, isolation mode, then expect it will take it back to where you were before without checking it?
You don’t even really have to use state sets. Just name the cameras and double check before rendering. Never render perspective view. You can accidentally bump it, it is constantly destroyed by switching viewports, it can’t be exported to other files, the list goes on.
Name your cameras, name your layers, files and materials. It takes a bit of extra thought and work up front, but it saves your life in crunch time.
Author: Andy Engelkemier
|
| Replied: 14 September 2012 07:06 AM
|
|
|
|
|
Yep. Not to mention the clipping planes bug. It’s horrendous. I use clipping planes daily in my workflow and this just drives me crazy when they keep resetting and I need to readjust them all the time. Why did you have to break something that worked perfectly well? And then 5 product updates later it’s still not fixed??? It boggles my mind.
|
|
|
sasho90 13 September 2012 09:02 PM
Yep. Not to mention the clipping planes bug. It’s horrendous. I use clipping planes daily in my workflow and this just drives me crazy when they keep resetting and I need to readjust them all the time. Why did you have to break something that worked perfectly well? And then 5 product updates later it’s still not fixed??? It boggles my mind.
can you post a scene where you have this occuring ?
Don’t know if it was you on cgsociety, but as i posted there i fail trying to reproduce this issue ...
Are you using some kind of viewport switching script ?
------------------------------------------------------------------------------
Free Tools (Scriptspot):
PowerPreview: Quality Previews from Nitrous Viewports - Download
EditPolyNC: Caddieless Editable Poly/Edit Poly recompiles Download
PowerSwitcher: Enhanced Viewport Switching in 3ds Max - Download
------------------------------------------------------------------------------
Home of The Frogs | Online Portfolio
|
|
|
|
Yes, that’s me on CG Society. You can find a scene attached. It’s an empty scene but that doesn’t really mater since this happens on every scene and even after resetting.
I don’t use any viewport scripts. I’ve tried both Nitrous and Direct3D display modes. I have even tested this on a 2nd computer and it still doesn’t work.
By the way, I just found a thread through search where another guy has exactly the same problem so it’s not just me:
http://area.autodesk.com/for...pping-and-uv-unwrap-bugs/
|
|
|
|
Thanks - stiill - i can’t reproduce
a few ideas to test:
* rename your 3ds max.ini and restart Max, that should give you the plain default settings
and test without changing any setting
* disable the viewcube plugins completely by moving “stdplugs\AutoCamMax.gup” to a save place
somewhere and test again. Though i tried to reproduce the bug with and without them, still no luck
* are you on standard 3ds Max or on the 3ds Max Design version ?
Other than that, i’m quite clueless why this happens to you ( and other people apparently ... )
------------------------------------------------------------------------------
Free Tools (Scriptspot):
PowerPreview: Quality Previews from Nitrous Viewports - Download
EditPolyNC: Caddieless Editable Poly/Edit Poly recompiles Download
PowerSwitcher: Enhanced Viewport Switching in 3ds Max - Download
------------------------------------------------------------------------------
Home of The Frogs | Online Portfolio
|
|
|
|
sasho90, my guess is some sort of startup script, plugin, or maxstart.max thing. Opened your file, Front View had Viewport Clipping enabled (moved full top/bottom), moved the mark closer to each other, saved, reset (no clipping in reset scene), open filed, clipping where I had it. So not sure what is going on in your case.
Doughboy, stuff like that doesn’t happen to me, because once it happens one time I make sure it doesn’t happen again. Get burned by Iterative Rendering with State Sets, now all my state sets have a script to always push it to production rendering. I think it should be fixed, and have asked for it since I first tested state sets. Has it changed? Nope. Have I been bitten by that since it first happened? Nope. Do I think it is a top priority issue that should be fixed immediately? Nope. I wish it was a top priority issue as that means that means that everything else has been fixed. I learn from my own flaws and those of the software and work around them. The is certain accountability that comes from the software developers, but the users need to take some accountability too. To priority issues are those that have no workaround and can only be fixed by the developer.
-Eric
Eric Craft
“The Evil Monkey hiding in your closet.”
|
|
|
|
|
|
|
Yes, only happened to me once also...but it IS a new behavior, that is what sucks.
Author: Doughboy12
|
| Replied: 17 September 2012 02:09 AM
|
|
|
|
|
|
|
