Bump version to v2.2.0

[Dragorn421]

Can also use this PR to discuss the release (e.g. if we should wait for anything)

Yanies mentioned it may be good to wait for f3dex3 preview, but since that's not anywhere near ready afaik I think it's fine to have a release in between

It's been 2 years since the previous release 😅

If you have permission (I'm not sure who does) there is a release draft for 2.2.0 on the releases page https://github.com/Fast-64/fast64/releases (not visible by everyone apparently)

[Lilaa3]

Sauren said the f3dex3 preview stuff is gonna take awhile.

[Lilaa3]

Change-log looks perfect too!

[ariahiro64]

there is a major bug with map importer for oot that applies the scene function to every single material causing almost guaranteed crashes. it is NOT ready for a release in this state.

2.2.0 should be stable first. Didn´t know about any big oot issues.

[ariahiro64]

#252 the work around is there for the issue so i guess you guys now know where to point people with issues

[Dragorn421]

there is a major bug with map importer for oot that applies the scene function to every single material causing almost guaranteed crashes. it is NOT ready for a release in this state.

Overlooking this because

• it is not a major bug (exporting imported stuff is inherently fragile, and also not the primary goal of fast64)
• though it's a pain you can fix the materials manually
• afaik this isn't a regression, the issue has existed since scene importing was implemented
• the 2.1.0 release already had scene importing (so, including the issue)

I am not trying to start an argument at all, just explaining why releasing despite this comment.

[ariahiro64]

there is a major bug with map importer for oot that applies the scene function to every single material causing almost guaranteed crashes. it is NOT ready for a release in this state.

Overlooking this because

* it is not a major bug (exporting imported stuff is inherently fragile, and also not the primary goal of fast64)

* though it's a pain you can fix the materials manually

* afaik this isn't a regression, the issue has existed since scene importing was implemented

* the 2.1.0 release already had scene importing (so, including the issue)

I am not trying to start an argument at all, just explaining why releasing despite this comment.

To add on we've also discussed it on the discord server and we feel just making people aware of the workaround is enough

[Lilaa3]

If its only an issue with imported scenes then I guess that is perfectly fine. Reverting my reverting of my approval!!

[Yanis002]

since we have an actual fix I'd like to see #275 merged before releasing 2.2.0, otherwise I don't have any objections

[Dragorn421]

since we have an actual fix I'd like to see #275 merged before releasing 2.2.0, otherwise I don't have any objections

I think it will take a bit more time to find a proper fix, so in agreement with Yanies we're going to release as is