Announcement

Collapse
No announcement yet.

max 2016 flakiness

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

  • max 2016 flakiness

    ive just made the jump to 2016 for a job where client is using the new physcam.. doesnt come back to 2014 very well ( my chosen version..) i also noticed a massive viewport speedup when scrubbing the timeline on my animated scene with 2016, so i thought id jump in.. i mean, its at sp3 so it should be pretty solid eh?



    anyway im getting wierdness with window selection of scene objects in the viewport.. sometimes selects nothing, even if im trying to select 5000 objects.. then i try again..crash to desktop..

    also, (although i didnt try since installing sp3) i noticed the scene explorer text selection seems broken? i have 1000 objects in my scene called "lamppost_xxx" so i go to the text selector and type "lamp" it filters down to 0 objects.


    this is in the space of an hour or so of work.. i dread to think what other surprises are lurking in there.

    back to 2014 for me!



    -p.s. is there a script to convert standard max cams to the new physcam? if so i can give my scenes to client with standard cams and they can deal with the conversion without cursing me.

  • #2
    For mostly the same reasons, I'm still on 2014. Each time I dare to use 2016 I end up regretting it ! A bit of a crazy situation imho (hopefully 2017 will be better )
    Last edited by JezUK; 16-03-2016, 05:47 AM.
    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


    • #3
      I've been saying that to myself since 2009

      Originally posted by JezUK View Post
      hopefully 2017 will be better

      Comment


      • #4
        I was using 2014 but made the jump to 2016 quite some time ago and for the most part I really like it, the only major thing that's a PITA for me is a problem with the sliders other than that no real problems at all.
        Cheers,
        -dave
        ■ ASUS ROG STRIX X399-E - 1950X ■ ASUS ROG STRIX X399-E - 2990WX ■ ASUS PRIME X399 - 2990WX ■ GIGABYTE AORUS X399 - 2990WX ■ ASUS Maximus Extreme XI with i9-9900k ■

        Comment


        • #5
          youre not having any selection issues (in viewport or via text filter?) odd that id have such an issue but others would not.. unlesss its scene specific.. although i cannot see how.

          Comment


          • #6
            Originally posted by super gnu View Post
            youre not having any selection issues (in viewport or via text filter?) odd that id have such an issue but others would not.. unlesss its scene specific.. although i cannot see how.
            I do have an issue with trying to select objects in a scene that has sliders in it, where if the sliders are not hidden or frozen then it seems like they have an invisible selection area that spans the viewport horizontally making it very hard to select anything besides sliders. Ive reported this to AD a while back but no response at all yet from them. Also in scene explorer when using the text search as soon as I start typing the object list seems to just go blank but Ive noticed that I have to scroll up in the SE and my selection is there, which is also kind of annoying why it would do that.

            ok so other than that haha no "major" problems

            Here is a SS of the slider isssue, might help explain it better...

            Click image for larger version

Name:	slider problems 01.jpg
Views:	1
Size:	494.9 KB
ID:	860145
            Cheers,
            -dave
            ■ ASUS ROG STRIX X399-E - 1950X ■ ASUS ROG STRIX X399-E - 2990WX ■ ASUS PRIME X399 - 2990WX ■ GIGABYTE AORUS X399 - 2990WX ■ ASUS Maximus Extreme XI with i9-9900k ■

            Comment


            • #7
              Hmm... I have been on 2016 since last august. I have not seen the problem either.
              For selection issue, you can try this

              NitrousGraphicsManager.HardwareHitTestEnabled = false

              Comment

              Working...
              X