Dev:Ref/Requests/Physics2.6

Physics Features

Particles

Option to display particle emitter in a different mode than the particle dupliobjects

As a user I'd like to have an option in the 'Display' area of the 'Particles' tab of the 'Properties' panel, which would allow me to set the display method of the emitter (excluding the particle dupliobjects) to 'Textures', 'Solid', 'Wired' or 'Bounds'. (The drop down menu would look the same as in the 'Display' area of the 'Object Tab' of the 'Properties' panel, but would only effect the emitter, not the particle dupliobjects.) This option should basically be an equivalent to the 'Emitter' option from the 'Render' Area of the 'Particles' tab of the 'Properties' panel, but for display in viewport.

With this option, by setting the display method for the emitters to 'Wired' or 'Bounds', while leaving all other display modes to 'Solid' or above, it would be possible to clearly see (in the viewport) the particle dupliobjects of several particle emitters which are stacked one on top of the other and would otherwise obstruct each other. Currently, afaik, it would only be possible to see through the emitters by setting the display mode from the 'Object' tab to 'Wired' or 'Bounds' which displays both particle dupliobjects and emitters in wired mode. However with a sufficient large amount of particle dupliobjects it becomes impossible to distinguish individual wireframed dupliobjects, and therefore it's not possible to get a good impression of the position, rotation and scale of the particle dupliobects. --Fabian Hernandez 22:39, 15 May 2013 (CEST)

RigidBody Simulation

Per-object Trigger Activation Settings

With the new activation options added in the 2013 GSOC, the trigger activation system has two settings; Trigger to set an object as a trigger object, and Use Trigger to set any objects to be activated when touched by an object with Trigger enabled.

I personally think It would be more effective to have one setting on the object being triggered, which would define both what object(s) are being used as trigger objects for that object, and whether or not trigger activation is enabled.

This would work by having an object or group selector when Trigger activation is enabled:

This would allow things that are impossible (to my knowledge) with the current system, such as allowing objectA using a different trigger object than objectB, and allowing objectB to not react to the trigger object used for objectA. In addition, this way it uses one less setting. --Gandalf3 Tuesday, October 15, 2013 at 5:55 AM CEST