I was hoping someone here has managed to control the clipping plane of the perspective view in 3ds max via maxscript. We;re using a rather large unit scale and it makes working in a perspective view a pain. I know I can adjust it manually and save but I was hoping for something a little quicker. We’re learning a new pipeline and we’re combing through loads of assets so automation would be nice. I’ve run showproperties on viewport and I got 2 functions that are not documented viewport.getclipscale and viewport.setclipscale. Unfortunately they don’t solve my problem and I was hoping that someone would point out that I was using them incorrectly (For example using them in combination with other functions).
As a temporary fix I have a scripted callback that looks for changes in the perspective views FOV and then sets it to a desired number. However, this tends to flatten the view. Not a big deal but I am determined to find an answer
I’ve posted at CG Talk already and didn’t get a response but this forum always been money so here’s hoping!
Not really an answer to your question, but if your scene scale is giving you clipping plane problems then the files are almost certainly going to be hard to work with for lots of other reasons too. If these scenes need to be manipluated a lot by artists then rather than tackling each symptom as and when it causes a problem, it might be better to find a way to allow them to work at suitable scale instead. Writing something that changes the scene scale on export or as a separate conditioning stage will save your artists loads of frustration in the long run.
Yeah we’ve run into small issues with that unit size. Paint brush sizes for painting weights, default chamfer, weld, and bevel settings. I’m working on a startup script that sets these default user settings. This was mostly an annoyance issue, and I can’t believe that max doesn’t expose the viewport clipping plane to maxscript.
We’re learning a new pipeline and engine so the goal is to learn the system as-is and then make any modifications to the pipeline to meet our needs. With our last pipeline we worked at a different scale and converted at export.
