# 3DSMax 2026 viewport hit detection / poor selection accuracy

**URL:** <https://forums.chaos.com/t/3dsmax-2026-viewport-hit-detection-poor-selection-accuracy/123994>\
**Category:** Off-topic\
**Created:** [December 1, 2025, 12:36pm UTC](https://forums.chaos.com/t/3dsmax-2026-viewport-hit-detection-poor-selection-accuracy/123994 "2025-12-01T12:36:39Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pixelcon](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/pixelcon/32/22319_2.png) [@Pixelcon](https://forums.chaos.com/u/Pixelcon)\
**Post date:** [December 1, 2025, 12:36pm UTC](https://forums.chaos.com/t/3dsmax-2026-viewport-hit-detection-poor-selection-accuracy/123994/1 "2025-12-01T12:36:39Z")

</div>

Has anyone else noticed selecting objects in max 2026 in a shaded viewport requires many many more clicks than it did in previous versions?  
For me it seems like the Z values are back-to-front in the viewport meaning the farthest items are selected first. Even very large items very close to the camera are ignored…

---

<div class="post-metadata">

**Author:** ![bruce\_hart\_1](https://avatars.discourse-cdn.com/v4/letter/b/5f9b8f/32.png) [@bruce\_hart\_1](https://forums.chaos.com/u/bruce_hart_1)\
**Post date:** [December 2, 2025, 12:15am UTC](https://forums.chaos.com/t/3dsmax-2026-viewport-hit-detection-poor-selection-accuracy/123994/2 "2025-12-02T00:15:08Z")

</div>

Yes - I’ve noticed the same. I’ve been using 3DS Max since 3D Studio for DOS, and this release seemes to have the most broken tools, in terms of existing features no longer working. Been meaning to compile a list and post on The Area (with some highly optimistic notion that Autodesk would take notice.) Some things may be to do with my Video card/drivers, so I’m interested if other people have had the same issues…

- The Layer manager has numerous problems: can’t Rename layers (except via Properties), can’t hide/unhide multiple selected layers with the Eye icon  
- The Walk Through tool does not allow movement speed change via the [] bracket keys, but instead moves the viewpoint backwards  
- Filleting spline verts is a joke, resulting all kinds of wonky results. It seemed broken back in 2024  
- The Tile map in the Compact Editor does not allow you to click on the swatch button to add a custom map  
- I’ve had many occasions where a window selection around a group of objects, selects other objects not even visible in the viewport. I constantly need to do an isolate zoom extents, just to make sure nothing off screen has been selected.  
- some objects get mysteriously renamed to other objects in the scene (never quite figured out when or how this happens)  
- sometimes objects get “stuck” to the cursor during a move opertion, needing Esc to stop it.

That’s all I can think of right now.

---

<div class="post-metadata">

**Author:** ![Vizioen](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/vizioen/32/59355_2.png) [@Vizioen](https://forums.chaos.com/u/Vizioen)\
**Post date:** [December 2, 2025, 12:41pm UTC](https://forums.chaos.com/t/3dsmax-2026-viewport-hit-detection-poor-selection-accuracy/123994/3 "2025-12-02T12:41:25Z")

</div>

> [@Pixelcon](#):
>
> Has anyone else noticed selecting objects in max 2026 in a shaded viewport requires many many more clicks than it did in previous versions?  
> For me it seems like the Z values are back-to-front in the viewport meaning the farthest items are selected first. Even very large items very close to the camera are ignored…

What happens if you use GPU hittesting?

nitrousgraphicsmanager.HardwareHitTestEnabled=true

I have this enabled by default. It’s miles better to select and viewport responsiveness (orbit / pan) is also a LOT better. Downside is selecting camera objects (or forestpack/raiclones icons, forces, etc) or splines overlapping other geometry isn’t as good as CPU but having no delayed viewport interaction and less problems selecting geometries is a big plus. I have it as a script to turn on or off if I can’t select something properly.

---

<div class="post-metadata">

**Author:** ![Pixelcon](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/pixelcon/32/22319_2.png) [@Pixelcon](https://forums.chaos.com/u/Pixelcon)\
**Post date:** [December 2, 2025, 2:49pm UTC](https://forums.chaos.com/t/3dsmax-2026-viewport-hit-detection-poor-selection-accuracy/123994/4 "2025-12-02T14:49:10Z")

</div>

> [@Vizioen](#):
>
> What happens if you use GPU hittesting?
> 
> nitrousgraphicsmanager.HardwareHitTestEnabled=true
> 
> I have this enabled by default. It’s miles better to select and viewport responsiveness (orbit / pan) is also a LOT better. Downside is selecting camera objects (or forestpack/raiclones icons, forces, etc) or splines overlapping other geometry isn’t as good as CPU but having no delayed viewport interaction and less problems selecting geometries is a big plus. I have it as a script to turn on or off if I can’t select something properly.

Bam! This is muchhhh better. I think I had that enabled for previous versions… It’s hard to keep track of all these little hacks we learn over the years…  
Forestpack is almost impossible for me to select without using the layer manager or Itoo tools so this cannot be any worse.

Thanks!!

---

<div class="post-metadata">

**Author:** ![Vizioen](https://dub1.discourse-cdn.com/chaosprd/user_avatar/forums.chaos.com/vizioen/32/59355_2.png) [@Vizioen](https://forums.chaos.com/u/Vizioen)\
**Post date:** [December 2, 2025, 3:48pm UTC](https://forums.chaos.com/t/3dsmax-2026-viewport-hit-detection-poor-selection-accuracy/123994/5 "2025-12-02T15:48:11Z")

</div>

> [@Pixelcon](#):
>
> Bam! This is muchhhh better. I think I had that enabled for previous versions… It’s hard to keep track of all these little hacks we learn over the years…  
> Forestpack is almost impossible for me to select without using the layer manager or Itoo tools so this cannot be any worse.
> 
> Thanks!!

Yeah I know, I use the forest / railclone lister to select them.

I made it a habit to put these into a little script that I copy every time I reinstall, in the scripts - startup folder. Don’t have to keep track of it that way. Another handy one I put in there is PlacementTool.UseBase=true which enables the Base as Pivot option for the placement tool (Y).
