Announcement

Collapse
No announcement yet.

3dsmax 2017

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • PIXELBOX_SRO
    replied
    interesting...downloading.
    no word about fixes in selections though :-/

    Leave a comment:


  • glorybound
    replied
    What the heck is 2017.1? Is that a first?

    Leave a comment:


  • Raph4
    replied
    2017.1 coming
    http://area.autodesk.com/blogs/the-3...x_2017_update1
    But I don't understand if MAXtoA is integrated into max ? for free ? or it's light version similar as NVIDIA Iray

    EDIT:
    Autodesk® 3ds Max® 2017.1
    Update 1 Readme
    http://up.autodesk.com/2017/3DSMAX/3...Readme_enu.htm

    Update 1 contains all previous Service Pack fixes for 3ds Max 2017.
    Service Packs and EXT's will no longer exist moving forward and will be simply called Updates.

    Same way from Adobe (2015 -> 2015.1 -> 2015.5... 2017, etc)
    Last edited by Raph4; 16-11-2016, 01:42 AM.

    Leave a comment:


  • bardo
    replied
    About the difficult with the selection I've found that when selection system goes crazy I do a "select all" (CTRL+A) and the objects come back selectable.

    It's not the best but, at the moment, it's the only quick way to workaround this problem.

    EDIT: I'm speaking for the 2016 version

    Leave a comment:


  • rikou
    replied
    It's totally crazy... How can it be possible ?
    Hey AD ?? are you sure to be able to release a true stable and full version of 3ds max 2017 before the (certainly) next buggy 3ds max 2018 ?
    AD, the baddest dev' in the world ! i'm so angry and tired....

    Leave a comment:


  • Deflaminis
    replied
    There is a problem with the selections currently. I can confirm this as I logged this issue myself.

    Leave a comment:


  • gandhics
    replied
    Originally posted by glorybound View Post
    A large percentage of MAX 2017 issues were not there in 2016, so they broke many working things. I guess that's what happens when you fire senior people and replace them with lesser paid interns.
    3dsMax 2017 utilize GPU a lot more than 2016 for mesh editing.
    That also means that 2017 is more sensitive to GPU and driver.
    That's probably why some problems are not happening for everyone.

    To have a bug fix, dev need a reproduction step or some clue about when the problem is happening.
    The more bug report will help to solve problem.

    Leave a comment:


  • gandhics
    replied
    Originally posted by glorybound View Post
    Yes, that is the problem. Toggling it on/off doesn't matter.
    May I get more information?
    I don't see that's happening here.

    Are you in object mode or sub-object mode?
    Perspective view or orthographic view or one of preset view?
    Could you tun this line in Listener? and revert setting and see if that helps?
    NitrousGraphicsManager.HardwareHitTestEnabled
    If you run the above line, it will tell you true or false.
    Then if it says "false", then run
    NitrousGraphicsManager.HardwareHitTestEnabled = true

    Leave a comment:


  • gandhics
    replied
    Originally posted by Recon442 View Post
    Always running latest nVidia one. I have some other lot more complex scenes, where it is not slower, but in this one particular, it is. It may be for example that there are high poly meshes that are just one element, or something like that. Too many smoothing groups... I don't really know, and it's easier for me to just not use 2017 than to dig into it and find what's wrong.

    EDIT: Actually, false alarm here. Surprisingly enough, it seems it is not Autodesk's mistake this time. I've measured GPU memory usage in that scene, which in 2017 fills all 4GB of my GPU memory, where as in 2016, it stays at around 2.8GB. The thing is that I am one of those who have fallen victim to nVidia's GTX970 3.5GB memory scam, so it's just my GPU dropping most of my performance due to that last 0.5GB being used in Max 2017. :/
    Glad to hear that you found the answer.

    Leave a comment:


  • jstrob
    replied
    Another bug that is there since ages and still there in max 2017 SP3 despite being reported everywhere is the gamma issue with the viewport canvas. When you use display gamma 2.2, the viewport canvas sitwches to 1.0 when you are painting...

    Please vote here for it to be corrected even though some think we should just submit it in the black box...
    http://3dsmaxfeedback.autodesk.com/f...-textures-does

    Leave a comment:


  • glorybound
    replied
    A large percentage of MAX 2017 issues were not there in 2016, so they broke many working things. I guess that's what happens when you fire senior people and replace them with lesser paid interns.

    Leave a comment:


  • pixelplume
    replied
    thought I was crazy.....me too with the selection....I gave up on 2017 and went back to 2016 for my last few projects

    Leave a comment:


  • jstrob
    replied
    Originally posted by Vizioen View Post
    I think he means the 3ds max settings themselves. This has been a major bug for all releases. Apparently its worse in 2017.
    Ok. About my render settings reverting to mental ray I just realized it's when I use GoZ. when I come back to max from zbrush the render settings are resetted. So might be a GoZ bug...

    Leave a comment:


  • glorybound
    replied
    Yes, that is the problem. Toggling it on/off doesn't matter.

    Leave a comment:


  • Syclone1
    replied
    Check to see if the window/crossing button next to the select and move isnt activated.

    Originally posted by glorybound View Post
    I am also having issues with the selection tool. Basically, I can't window select, unless I get the entire object in the window. So, the selection tool isn't seeing edges.

    Leave a comment:

Working...
X