Well Gee I just checked my account at Autodesk and the last update for 3ds Max as part of the Building design Suite Premium is SP3; thanks Autodesk. Of course I'm surprised I can still access the account since the subscription has lapsed. I'm just going to live with it and be thankful I can legally use 3ds Max 2014 and 2017 till the day I die without giving Autodesk another penny. I have the 2014 version because when I migrated to the Building Design Suite Premium from just AutoCAD and 3ds Max Design subscriptions to save about $500 on my subscription costs Autodesk wouldn't give me any kind of price break so I let one subscription lapse and migrated one. My son's happy though; he gets to use my 2014 version.

I do run a few older scripts like TexTools but the shutdown problem occurred on a clean, fresh install of Max 2017 when I had to install it instead of 2016; which by License I can't use anymore. Blast those hard drive failures!

I'm running 2017, Version 19.0 SP3 commercial with a PERPETUAL license; I absolutely hate the monthly or yearly "rental" garbage which Autodesk and Adobe migrated to. I let my Autodesk Building Design Suite Premium Subscription lapse this year when they tried to force the rental agreement on me; had been on subscription with perpetual license since 2009 for AutoCAD and 3ds Max then the Building Design Suite Premium. I'll be honest a lot of the crashes I experience are due to operator error; I learned how to use 3ds Max on my own and I am still learning every time I use it. Back in 2009 it was a toss up between 3ds Max and Maya for me (Maya wasn't owned by Autodesk back then) but since I had AutoCAD Max won. Yes Autodesk is aware of the problem but I don't expect them to resolve it for me but they will probably resolve it in the 2018 version. My solution is to run the script provided to me and SAVE OFTEN.

I'm running a Quadro K5000 with latest drivers, 32g ram, Windows 7 Pro, i7 3930K 3.8Ghz hex core processor all in a box I built myself. I've checked the Autodesk forums and there are quite a few people complaining about 2017. especially the shut down issue. The max script was provided to me by an Autodesk representative who acknowledged the problem. They have some illegal callbacks in their C++ 2015 as the error thrown is not an Autodesk error but a Windows error and they know the issue exists. After a day of troubleshooting the issue I traced it to the 2015 C++ redistributable. A reinstall of that redistributable will fix it for one shut down cycle but the next shutdown throws the error. Therefore the script "get process-KILL process", Well it's not as bad as disappearing verts which I experienced quite a few versions ago and their support response was "we know it exists but we will fix it in a later version".

3ds Max User since 2009 and 2017 is my last upgrade since Autodesk went the subscription route with non-perpetual licenses; just like Adobe with their Creative Cloud. 2017 will not shut down clean without a script to kill process and tends to crash on me at the least opportune times; often when doing some of the simplest things. Like their improvements to UVWunwrap but in general I thought 2016 was more stable, it shut down without needing a get process, kill process script and filling my error log with errors every time I'd close it without that script.

Excellent work. I can't even imagine unwrapping those surfaces. I just have to ask: how often did Max crash on you during all that work? You just made me feel like an absolute noob looking at this, but hey they are still excellent.

Click display origin in the props properties window; open the joint editor: move the GREEN crosshair to the point that you want the prop to rotate from; use front, top, and a side view to rough it in; use the numerical boxes in the joint editor to fine tune. Make sure that the red crosshair is also aligned with the point of rotation, not on the point of rotation but aligned with it

Bagginsbill my drivers for my Quadro K5000 are current according to NVidia but I did figure out what was going on last night. By adding additional geometry the preview render cleaned up and renders the surfaces correctly. Apparently the preview renderer doesn't like long polys before a directional change by simply doing a ring and connect 1 line in Max on the long edge the preview renderer no longer stretches the textures,

Can't get more accurate than numerical input,

When V4/M4 are first initialized numerous absolute references are written in the morph channels which are valid as long as the original directory structure is maintained. If the install directory changes the morphs will no longer work. The references are absolute and not relative so any change to the original install location will "break" the figure. If this is a reinstall simply put them in a directory structure which matches the original. Use notepad++ (or notepad) to open the file in your RuntimeLibraries!DAZVictoria 4V4BODYChnnls.pz2 to verify the original installation directory structure; do not try and edit this file to correct the directory structures unless you want to spend a long and frustrating time editing because this is not the only place this method of referencing is used by DAZ. After you know where the files need to go simply place them there; that's why I still have an old Smith Micro Poser runtime on my "C" drive after numerous computer rebuilds, It was easier to do this then a reinstall of V4/M4 since the version which I have uses the old installer which throws errors after every install and doesn't even recognize Poser Pro.exe as a valid Poser executable.