More input needed on CS update!

[Patrik]

Hey again, everyone.
In testing the coming update we ran into a bit of an issue. The old collada importer would not take the up_axis set in a model into consideration, something the AMFP's importer does.
This means few TDD models that had a custom up_axis set (even though it had no effect) are now rotated incorrectly in the game, something that completely breaks the main campaign and probably some custom stories as well. This is of course not acceptable.

We have two possible solutions to the issue, but since they will affect the modding community it seems like a good idea to ask for input here first.

1) Patch the old TDD models to have the correct up_axis
New models will work correctly out-of-the-box. However, this will potentially break any mods using custom models with the wrong up_axis set! Should not affect that many mods, and it would be easy for the modder to patch.

2) Keep the handling of up_axis the same way it was in TDD
New models with a custom up_axis will need to be rotated manually by the modders, which might get annoying. This means all old mods will keep working just like they did before.

Which solution would you prefer, and why?

[Adrianis]

2) Keep the handling of up_axis the same way it was in TDD
New models with a custom up_axis will need to be rotated manually by the modders

When you say 'New models', do you mean new models that modders are making or the new models from AMFP?

In either case would probably say go with option 2, it might mean a lot of trouble initially but, potentially breaking a bunch of old mods where the author may have moved on would be a shame

[PutraenusAlivius]

OPTION 2. Also, is that why AAMFP assets that I imported for my Custom Story rotated wrong?

Wow. Just wrote this with just one hand and finger.

[Patrik]

Also, is that why AAMFP assets that I imported for my Custom Story rotated wrong?

Yeah, that's probably the reason. It should affect some, if not all of the AMFP dae files.

[Unearthlybrutal]

I prefer the second solution because of this:

This means all old mods will keep working just like they did before.

[Your Computer]

First one.

Any mods that break as a result but are not updated to reflect the update should die. The closer things work out-of-the-box, the better. Retail version requires manually updating the game, so if they wish to play mods that become outdated after the patch, they can just choose not to upgrade. But for this to be possible, you would need to release the update as an update and not part of the full game.

[Javist]

I'm for first one.

p.s Can't there be both variants?
Maybe, a checkbox in the launcher/options.. bool in cfg or something like that?
Probably the task is too complex for such switching, just guessing.

[Robby]

I am sticking with Option #1. Old custom stories will have to be reupdated, but that's something common.

[Fatalist]

Second.
Because first one will potentially break any mods using custom models.
And my mod uses too much custom stuff...

[Alex Ros]

1) Patch the old TDD models to have the correct up_axisNew models will work correctly out-of-the-box. However, this will potentially break any mods using custom models with the wrong up_axis set! Should not affect that many mods, and it would be easy for the modder to patch.

The first one option. Because it's truly not a pain in the ass to patch old mods or mods in production. And if you guys agree to update all of the TDD models, then it's just a piggishness on the part of modders do not agree to do the same, it's unfair. The fair decision - you have to update TDD assets, modders too have to update their assets. IMO of course.