Issue initalising PhysMember second issue with variable position

[linokl]

Hi Craig,

Me again, sorry I found another similar error after your last fix on PhysMember initialisation issue when trying to use the updated module.

I think there is a bug due to a mismatch in variable positions in the initialization call for PhysMember

In PhysMember, when you initialize the member the super init is called with "model" after the area (A) variable

In Member3D, in the initialization function, "model" variable after "material"

This is causing issue initalising PhysMember

Regards
Lino

[JWock82]

I just fixed this. Look for the fix in v0.0.93. Thanks for reporting!