PBR Sheen value export is breaking import in Babylon 4.0.3

[babylonjs]

PBR Sheen value export is breaking import in Babylon 4.0.3

[Palmer-JC]

Thanks for documenting this. If you would notice in your proposed solution, there is already the writing out isEnabled twice. This change occurred right after 4.0 went out, and I pointed out I needed to write private members to JSON, so they made them public. It is easy to write small stuff twice. I just need to remember to delete that after 4.2 comes out.

Not writing stuff is not easy at a repo level. It is also a transitory problem that goes away on it own. For non npm is already has. I suggest for your work, just delete the section which exports it, or maybe just edit the babylon files. Which ever is easier.

I really think this is more of a problem that the npm is only published periodically.

[osmanzeki]

Indeed no worries, I just wanted to document this behaviour as you mentioned as I had a hard time figuring out what was going on when upgrading to Blender 2.8x for my workflows (I have a lot of automated exports to Babylon in python and Blender).

I fixed it exactly as you proposed, by commenting out the section that writes the sheen stuff for the moment. Indeed when 4.2 is released and npm is all synced, I will reinstate the latest Babylon Blender exporter in my workflow. :)

Thank you!