dragorn421 / io_export_objex Goto Github PK

Thanks @turpaan64

A material A may branch to an object B that itself includes material A.
A material A may branch to an object D that has another material C branching to another object B which includes material A.
and so on

This causes a circular reference. objex2 should detect those and abort the export

In the mean time, z64convert 1.0.2 detects the issue

https://discord.com/channels/891705295640870922/891707377173266462/917707697858691072

HylianModding, #modding-help
https://discord.com/channels/388361645073629187/451783162859749386/920483912357146665

I found out the problem I had yesterday with z64convert giving me a "something went wrong" error! In blender when exporting the Objex2 file I changed the Path Mode to Copy

Investigate this, other path modes are intended to work

When I added the plugin it says it needs to be updated. Hopefully this can be addressed since blender 2.8 is vastly Superior then 2.7

The "not triangulated" warnings should be grouped in a single warning to reduce spam

"not triangulated" and color warnings could be automatically resolved by a dedicated operator

The "display device" warning in blender 3.0.1 (likely in 2.80+) is wrong, using None is not the way, or there are other things to tweak

The dedicated operator mentioned above could also automatically bake neutral scene lighting

Making several log files, one for all ERRORS and up, one all INFOS and up, and so on with DEBUG and TRACE, may be a good idea

Errors seem harder to look at or parse for end users if they are drowned in messages (understandable)

Also all INFO+ messages should be as user friendly as possible. If debug information should be put into them, just don't, and print it alongside at debug level