Provide details on the proposal.
Physics data is currently hidden from the user, but it might be useful to expose it anyway until physics support is implemented.
This should take the form of one ListBox for each of the three physics data types, listing the raw data that appears in the binary, with the exception of bone indices (which should be converted to bone names).
Is your feature request related to a problem? Please describe.
Physics is useful to edit.
Additional context
Might need to have copy-and-paste options for copying physics data from one model to another - will not implement unless input is given on the exact form this should take and how feasible it is.
Basic implementation would be to have a "clipboard" in the global custom properties that holds a bytestring of a serialized physics chunk, that can then be deserialized and pasted onto a different model. The pasted physics will have incorrect bone names as an inevitability.
Provide details on the proposal. Physics data is currently hidden from the user, but it might be useful to expose it anyway until physics support is implemented.
This should take the form of one ListBox for each of the three physics data types, listing the raw data that appears in the binary, with the exception of bone indices (which should be converted to bone names).
Is your feature request related to a problem? Please describe. Physics is useful to edit.
Additional context Might need to have copy-and-paste options for copying physics data from one model to another - will not implement unless input is given on the exact form this should take and how feasible it is. Basic implementation would be to have a "clipboard" in the global custom properties that holds a bytestring of a serialized physics chunk, that can then be deserialized and pasted onto a different model. The pasted physics will have incorrect bone names as an inevitability.