I meant Blender's internal python console, sorry wasn't clear. It seemed like an import issue since it was failing due to functions "not existing", but if I'm understanding you right that code doesn't need to be used anyway, when running test_mesh_parms does the job instead.What console do you mean? if OS' cmd interface, then it won't run there because import script relies on bpy module which is strictly blender-specific. If in blender's python console, then it should run if all script is copy-pasted there, including imports etc (IIRC "Run Script" button and blender console run in different scopes, i.e. they don't share imports or variables). Hitting "Run Script" is actually the way to go.
Examining Mesh class I can see a fair bit of WIP in there. If I wanted to print out a mesh header to view, is that accommodated for?
Attempting to parse files unpacked by the Delutto unpacker throws a decode error:
- File "S:\Tools\Blender\2.82\python\lib\site-packages\r6s\common.py", line 8, in __init__
self.name = r.read(name_len).decode('utf8')
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x95 in position 8: invalid start byte
I got the same outbreak .forge from comword's dropbox and extracted and processed a mesh file that was the same as one I already had from your dropbox, all I could tell was the contents of the two were not the same. Guessing it's either output bad data, or ins't compatible in some other way. Not much incentive to continue with that path as you've solved unpacking separately, unless you got some simple idea that fixes it.