Announcement

Collapse
No announcement yet.

3dsmax 2017

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

  • #16
    It might very well be a plugin. Do you have Walls & Tiles installed? Sometimes I think my problem start whenever I install it.
    Bobby Parker
    www.bobby-parker.com
    e-mail: info@bobby-parker.com
    phone: 2188206812

    My current hardware setup:
    • Ryzen 9 5900x CPU
    • 128gb Vengeance RGB Pro RAM
    • NVIDIA GeForce RTX 4090
    • ​Windows 11 Pro

    Comment


    • #17
      Dont using it. I have Vray, Forest Pack and Relink Bitmaps. And 2016 works fine.
      AMD TR 7980X, 256GB DDR5, GeForce RTX 4090 24GB, Win 10 Pro
      ---------------------------
      2D | 3D | web | video
      jiri.matys@gmail.com
      ---------------------------
      https://gumroad.com/jirimatys
      https://www.artstation.com/jiri_matys
      https://www.youtube.com/channel/UCAv...Rq9X_wxwPX-0tg
      https://www.instagram.com/jiri.matys_cgi/
      https://www.behance.net/Jiri_Matys
      https://cz.linkedin.com/in/jiří-matys-195a41a0

      Comment


      • #18
        Originally posted by Jiri.Matys View Post
        Dont using it. I have Vray, Forest Pack and Relink Bitmaps. And 2016 works fine.
        I'm not 100% sure that, that's the culprit. However, that's the only thing, other than what you have listed, I have installed. I install it, to use it, and before I know it the scene gets to slow to use. I'll have to experiment. I'm wondering if anyone else has the same issues when Walls&Tiles is installed.

        Bobby Parker www.bobby-parker.com
        Bobby Parker
        www.bobby-parker.com
        e-mail: info@bobby-parker.com
        phone: 2188206812

        My current hardware setup:
        • Ryzen 9 5900x CPU
        • 128gb Vengeance RGB Pro RAM
        • NVIDIA GeForce RTX 4090
        • ​Windows 11 Pro

        Comment


        • #19
          I just watched a "What's new in 2017" and, although it is one man's opinion, he said that it was riddled with bugs and crashes 4/5 times a day. Basically, do not use it in a production environment.

          Sent from my iPad using Forum Runner
          Bobby Parker
          www.bobby-parker.com
          e-mail: info@bobby-parker.com
          phone: 2188206812

          My current hardware setup:
          • Ryzen 9 5900x CPU
          • 128gb Vengeance RGB Pro RAM
          • NVIDIA GeForce RTX 4090
          • ​Windows 11 Pro

          Comment


          • #20
            I will try and see for myself. Everyone have different experiences. I think it wont crash at all for me.
            AMD TR 7980X, 256GB DDR5, GeForce RTX 4090 24GB, Win 10 Pro
            ---------------------------
            2D | 3D | web | video
            jiri.matys@gmail.com
            ---------------------------
            https://gumroad.com/jirimatys
            https://www.artstation.com/jiri_matys
            https://www.youtube.com/channel/UCAv...Rq9X_wxwPX-0tg
            https://www.instagram.com/jiri.matys_cgi/
            https://www.behance.net/Jiri_Matys
            https://cz.linkedin.com/in/jiří-matys-195a41a0

            Comment


            • #21
              Originally posted by Jiri.Matys View Post
              I will try and see for myself. Everyone have different experiences. I think it wont crash at all for me.
              let us know how it goes.

              Sent from my iPad using Forum Runner
              Bobby Parker
              www.bobby-parker.com
              e-mail: info@bobby-parker.com
              phone: 2188206812

              My current hardware setup:
              • Ryzen 9 5900x CPU
              • 128gb Vengeance RGB Pro RAM
              • NVIDIA GeForce RTX 4090
              • ​Windows 11 Pro

              Comment


              • #22
                I used to have 2016 installed at the same time 2014 as I (foolishly) decided it *must* be safe to make the jump (after all, why else pay the maintenance fee...)..... each time I tried using 2016 for production work it let me down (badly) and I'd end up reverting back to using trusty ole 2014.

                I then had to do a reformat of my OS hard-disk and reinstall all my software - 2016 didn't make the cut

                Surely it'll be safe to jump to 2017, I mean, 3 years later (or am I paying maintenance for nothing here.....) ?
                Jez

                ------------------------------------
                3DS Max 2023.3.4 | V-Ray 6.10.08 | Phoenix FD 4.40.00 | PD Player 64 1.0.7.32 | Forest Pack Pro 8.2.2 | RailClone 6.1.3
                Windows 11 Pro 22H2 | NVidia Drivers 535.98 (Game Drivers)

                Asus X299 Sage (Bios 4001), i9-7980xe, 128Gb, 1TB m.2 OS, 2 x NVidia RTX 3090 FE
                ---- Updated 06/09/23 -------

                Comment


                • #23
                  I was skeptical at first but 2016 works fine for us. Still on SP1 out of fear of breaking things that work, after hearing to much bad things about SP2 and 3.
                  Had high hopes for 2015, but went back to 2014 for production work. The layer manager/scene explorer was a nice idea, but turned out to be a nightmare. At least it works in 2016, even though it isn't exactly smooth and comfortable to rename or move things - it renames the things you want to. Also had loads of trouble with snapping and viewport graphics in 2015.

                  The pattern is pretty obvious: 2011, 2013, 2015 are versions that we skipped or reverted from. AFAIK they change/break the SDK every other year, and sadly it seems that it comes at a cost. So hopes are very low for 2017. Maybe that is ok though. I mean, I wouldn't mind if they didn't come out with a new version every year. I'd rather have a production safe release every other year. Which is sort of what they are doing, if one chooses to see it that way, it's just not marketed as that way?

                  Comment


                  • #24
                    Originally posted by tzaar View Post
                    I was skeptical at first but 2016 works fine for us. Still on SP1 out of fear of breaking things that work, after hearing to much bad things about SP2 and 3.
                    Had high hopes for 2015, but went back to 2014 for production work. The layer manager/scene explorer was a nice idea, but turned out to be a nightmare. At least it works in 2016, even though it isn't exactly smooth and comfortable to rename or move things - it renames the things you want to. Also had loads of trouble with snapping and viewport graphics in 2015.

                    The pattern is pretty obvious: 2011, 2013, 2015 are versions that we skipped or reverted from. AFAIK they change/break the SDK every other year, and sadly it seems that it comes at a cost. So hopes are very low for 2017. Maybe that is ok though. I mean, I wouldn't mind if they didn't come out with a new version every year. I'd rather have a production safe release every other year. Which is sort of what they are doing, if one chooses to see it that way, it's just not marketed as that way?
                    The subscription is going to make things awful expensive. Let's say a company has 10 stations of 3DS MAX, it'll cost them $18,000 a year, just to use. If you skip every release because you find no benefit in upgrading, it'll basically cost $36,000 to upgrade. Crazy!
                    Bobby Parker
                    www.bobby-parker.com
                    e-mail: info@bobby-parker.com
                    phone: 2188206812

                    My current hardware setup:
                    • Ryzen 9 5900x CPU
                    • 128gb Vengeance RGB Pro RAM
                    • NVIDIA GeForce RTX 4090
                    • ​Windows 11 Pro

                    Comment


                    • #25
                      hii!

                      well that pattern with "uneven suxxs" is like windows versions.
                      the 2016 works """"ok"""" for me but its still "mehh".
                      So 2017 cant do anything worse ..

                      large scenes are of course a total joke with 3dsmax.. 4000+ objects and its dead.

                      since i will reinstall my workstation with a fresh windows 10 i will try 3smax2017 before wiping it.
                      Daniel Krassnig / http://www.vistral-3d-visualisierung.de/ / Architektur Visualisierungen

                      Comment


                      • #26
                        If it doesn't fix things, there really isn't a point to upgrade. I remember paying the subscription on an AD product for 3 years, without any patches, SP, or upgrades. AD eventually pulled the plug on it, so I paid 3 years for absolutely nothing.
                        Bobby Parker
                        www.bobby-parker.com
                        e-mail: info@bobby-parker.com
                        phone: 2188206812

                        My current hardware setup:
                        • Ryzen 9 5900x CPU
                        • 128gb Vengeance RGB Pro RAM
                        • NVIDIA GeForce RTX 4090
                        • ​Windows 11 Pro

                        Comment


                        • #27
                          Originally posted by glorybound View Post
                          The subscription is going to make things awful expensive. Let's say a company has 10 stations of 3DS MAX, it'll cost them $18,000 a year, just to use. If you skip every release because you find no benefit in upgrading, it'll basically cost $36,000 to upgrade. Crazy!
                          Your operating costs in staff, rent and taxes will be hitting $750k a year with that setup. Not to mention the accounts people you'd need to have on staff at that size.
                          It would also cost significantly more in a city like NYC, where you'd be spending at least 10k a month on rent (and thats a good deal). 18k isnt a lot for the tools.
                          Last edited by Neilg; 25-04-2016, 10:37 AM.

                          Comment


                          • #28
                            Interesting all this about Max and to know how everyone else feels about it. We are using 3DS Max 2013 STILL!!!! We used to be on a subscription and always paying that late, etc., so I decided to pull the plug at 2013 and use that money on VRay and brand new workstations as well as servers and GPUs. IMO this has worked to benefit us. Unfortunately, if AD decides to make 2017 and up not be able to save below 2014 versions (knock on wood), then I'll be out of sink with any other units that use 2017 (that would be the only inconvenience). But there you have my 2cents. Soon we'll have to make a decision to stay with 3DS Max and their unrelenting push to make you pay yearly for a subscription or change to another program that will not give me that problem.

                            Comment


                            • #29
                              The beauty is, it was your decision. AD is taking our ability to chose what's best for us away, this is what is insane.
                              Bobby Parker
                              www.bobby-parker.com
                              e-mail: info@bobby-parker.com
                              phone: 2188206812

                              My current hardware setup:
                              • Ryzen 9 5900x CPU
                              • 128gb Vengeance RGB Pro RAM
                              • NVIDIA GeForce RTX 4090
                              • ​Windows 11 Pro

                              Comment


                              • #30
                                Originally posted by glorybound View Post
                                The beauty is, it was your decision. AD is taking our ability to chose what's best for us away, this is what is insane.
                                Thanks Bobby! Spot on.... Maybe the Blender Foundation will make files from 3DS Max openable in their future versions of Blender and thus interchangable at which point AD will better be looking for new customers. As a matter of fact, I'll talk to the Blender guys at this year's Sigraph, I touched upon this last year and they seemed to be into the idea of doing it, they just needed more resources to go ahead. Anyhow, we will see.

                                Comment

                                Working...
                                X