Mapping Operator makes simulation very slow
#1
In the file i have attached you can see 1000 instanced animated shapes working in realtime, but if you switch off the fast sim and turn on the slow sim that contains the mapping operator things begin to get very slow.

This is a simple recreation of something i am trying to apply to more complex objects, and with that scene its impossible to get any kind of playback. from 40 fps to 3fps

Is there any way to improve the speed when using a texture map to drive a property?

Thanks


Attached Files
.max   shimmer-effect-test.max (Size: 848 KB / Downloads: 25)
  Reply
#2
Mapping overrides disabling instancing by default. In your Display operator(s) you can see options at the bottom to re-enable instancing. It's a little clunky like this due to Max viewport limitations, some of which were improved in Max 2024+.
  Reply
#3
(03-06-2025, 07:38 PM)tyFlow Wrote: Mapping overrides disabling instancing by default. In your Display operator(s) you can see options at the bottom to re-enable instancing. It's a little clunky like this due to Max viewport limitations, some of which were improved in Max 2024+.

Thank you so much i never knew about that. Completely fixed the problem. 

What is the reason it disables it by default?
  Reply
#4
Because Max's viewport instancing system only supports 1 mapping override at a time....so to avoid "why aren't my mapping overrides working" questions (for scenes with multi-channel overrides), I have instancing disabled if mapping overrides are applied by default, so users can at least see their overrides, even if things run slower due to no instancing.

If the Max devs eventually allow multiple mapping overrides per instance, then I would switch that to the default.
  Reply


Forum Jump: