Issue - Ensure primitive attributes are updated correctly.
Many (probably most) current modifiers that create new geometry fail to update primitive attributes, meaning that those modifiers will fail when applied to primitives with attributes. Since it's really easy to write code that doesn't take attributes into account, we need a way to consistently catch such errors. One heavy-handed way to do it would be to simply update every mesh source to generate output with attributes - then, current tests would automatically start failing in an obvious way. On the down-side, this means increasing memory usage for everyone for what is basically a test case. Second alternative would be to do something in the test layer that automatically adds attributes to sources.
Details
- Id:
- 38ed366c277ad6ad3cbf7113a50c73ab0dc6ecb9
- Type:
- Bugfix
- Creation Time:
- 2009-12-26 17:27 UTC
- Reporter:
- Timothy M. Shead <tshead@k-3d.com>
- Release:
- 0.8.0.0
- Status:
- Closed
Issue Log
| 2009-12-26 17:27 UTC | Timothy M. Shead <tshead@k-3d.com> | created | |
| 2010-01-09 17:50 UTC | Timothy M. Shead <tshead@k-3d.com> | closed with disposition fixed | Enabled aggressive testing of primitive attributes on the dashboard - all mesh-related tests now generate attributes and enforce the validity of their output tests, so it should be impossible for a plugin to pass a regression test without generating valid attributes." |