Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Chunk Models - Unknown/Invalid Poly Type #18

Closed
ItsEasyActually opened this issue Jun 24, 2024 · 1 comment
Closed

Chunk Models - Unknown/Invalid Poly Type #18

ItsEasyActually opened this issue Jun 24, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@ItsEasyActually
Copy link
Contributor

ItsEasyActually commented Jun 24, 2024

The Ninja file found here produces the following error when imported:

An error occured while importing 013_fldManshipD_00.nj
Traceback (most recent call last):
  File "C:\Users\iea\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\SonicAdventureBlenderIO\source\register\operators\base.py", line 26, in execute
    return self._execute(context)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\iea\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\SonicAdventureBlenderIO\source\register\operators\import_operators.py", line 110, in _execute
    raise error
  File "C:\Users\iea\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\addons\SonicAdventureBlenderIO\source\register\operators\import_operators.py", line 106, in _execute
    import_data = SAIO_NET.MODEL.Import(
                  ^^^^^^^^^^^^^^^^^^^^^^
System.FormatException: Poly chunk type is invalid: 205

The data is able to be opened in SAMDL, so it does not appear to be an unknown poly type from the documentation. It's unclear if the error is a result of actually being an invalid poly type or if there may be a read error occurring when attempting to parse the Poly chunks in the file.

@ItsEasyActually ItsEasyActually added the bug Something isn't working label Jun 24, 2024
@Justin113D Justin113D mentioned this issue Aug 6, 2024
Justin113D added a commit that referenced this issue Aug 6, 2024
## Additions
- Model and level can now be imported via drag & drop
- Model and level exporters added to collection exporters
- Setup batch to work around issues with current VSCode blender extension

## Changes
- Removed `Write Specular` option, as it leaving specular colors out was seemingly never needed in the first place (#24)
- `Automatic Node Attributes` changed to `Automatic Node Attribute mode`; Now a dropdown, defaults to "Missing", which fills in missing node attributes, instead of overriding them.
- Linking entire template scene now, instead of scene elements (#17)
- Auto updater dropped in favor of updating via repository
- PythonNET no longer gets installed via PIP, but shipped as a wheel
- improved addon reloading
- Updated setup batch
- Organized importer and exporter settings into panels

## Fixed issues
- #23
  - This is a bug on blenders end, and has only been worked around so far. As a consequence, normals may be messed up on exporting. This will be fixed once blender 4.2.1 releases
- Auto node attribute evaluation now comparing vectors with 0.0001 wiggleroom (#14)
- Optimizing polygons was able to result in strip-join sections getting lost (#21 & #22)
- Reading `MaterialBumpChunk` was broken (#18)
- #16
- #20
- LandEntrys from very old addon not migrating properly
- Models with too many polygons (not limited) but fitting vertex count (limited) crashed the exporter
- Color-only models with shape animations would break on export
@Justin113D
Copy link
Member

Fixed in release 2.2.0

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants