Grouping or Linking causes objects to flip out of position

[Anonymous]

Never had this problem before. After installing SP2 + EXT2 I cant use grouping or linking like i used to. For example, if im making something and i mirror it & then group it - or link both objects to a dummy - the object that was mirrored (after it is grouped or linked to another object) actually flips over - it does not retain the position where it should be. With lots of objects that need to be grouped (or for example linked to a dummy) this is a total nightmare. I would have to go to each object and find out the correct transform to get it back to its proper position.  Is this a bug or just some new plot to ruin my work ?  Anyone seen this happen ? 

ANy help much appreciated !

thx

Im using Max 2016 Win7 x64

[jens.diemer]

Maybe it's related to: http://forums.autodesk.com/t5/3ds-max-3ds-max-design-general/max2016-select-and-link-auto-inherit/m-... ?

[Anonymous]

Happening to me too, and its frustrating. I'm also finding it weird that there aren't loads more users reporting this! It seems broken to me.

[Anonymous]

Its also a problem if you try to merge an xref scene. If it remains as a link its OK - but if you merge it the geometry gets whacked out of position. This is really horrible & im also surprised there hasnt been an outcry. whats going on ?!?!

[Anonymous]

I can confirm this bug too.

Here's a screencast of the problem.

[Anonymous]

If you reset XForm, the problem is gone.

[Anonymous]

Thx for the workaround.

[georgecMAX]

Yes, Have same problem after installing SP2.

[Przemyslaw_Stachyra]

I have the same problem.

[georgecMAX]

It seems to happen when one of the objects in the group was mirrored.



Regards,

George Chianese
Office/fax: 215-254-6516
Cell: 443-655-6400
Philadelphia, PA
www.georgerenders.com
www.linkedin.com/in/georgerenders

[Przemyslaw_Stachyra]

Exactly

[renar-visuals]

Happens here too and I was tearing my hair out! That's just unacceptable! Uninstalling SP2 and EXT2...

[Przemyslaw_Stachyra]

Anyone from Autodesk here?!

Watch this problem here

https://youtu.be/gz5nooD3tPM

[FRANKSIBER7460]

Hello to all,

we can confirm this MASSIVE problem that cuts into our workflow.

NO official reaction from autodesk regarding this subject.

Incomprehensible.....

[Anonymous]

Same problem here after applying SP2 for 3Ds max 2016.

[jens.diemer]

SP2 can't fix it, because SP2 made this Bug, isn't it?

@everybody: Please report this bug in our subscription center, here:

https://autodesk.secure.force.com/Customer/apex/Case_CustomerPortalLandingPage

[Przemyslaw_Stachyra]

Yes. It's SP2 bug.

[spacefrog_]

There's already an older thread about that exact bug ....

http://forums.autodesk.com/t5/3ds-max-3ds-max-design-general/3ds-max-2016-sp2-bug-with-group-ungroup...

[Florian.Coenen]

Hello,

I can confirm the issue and wanted to inform you that this is already forwarded to the development with a high priority in order to fix that as soon as possible and the development is working hard to get that fixed.

In the meantime I would recommend to uninstall SP2.

I just wanted to let you know guys, that the issues with SP2 are really taken seriously here at Autodesk and we are doing our best to get that solved.

Best Regards,

[mhaZe23]

I´m wondering why it takes so long to fix this problem, which was reported early in mid-December.

Going back to SP1 isn´t quite a good solution, because when you reverse back you´d be faced with the "multiple groups massively slow down the viewport" problem. If you do the xform-modifer and collapse, you loose the stack and the instance.

You could save down to a former version, loose all the nested layer structure, do your thing, re-open in max2016 and continue. Not nice.

Best workaround somebody mentioned before: Select the mirrored object(s), go to the Hierarchy panel and press "Reset:Transform".

This is a serious bug which makes working with the program useless when you don´t know a workaround. After getting the second ServicePack months after release! Who is responsible for this?

And we´re in the second month this bug occured! Where is the fix? Is the programming team too busy with version 2017?

I do archviz work in a small studio, how are you supposed to work reliably with this tool under deadlines? It leeds to the question who takes care of proper beta testing the software under work conditions. Surely no serious workers in the customer business.

Autodesk-Shareholders, you think that´s good stock value?? And soon with version 2017, same procedure as last year?