Hello,
Currently we're using 5.0.3.
On each engine update, we need to resave the assets in the Content folder (usually two times in a row until there are no more changes).
Not doing so means that our own assets, depending on HoudiniNiagara ones, will systematically be resaved by the ResavePackages commandlet.
Is that something you're aware of, and could you take it into account in your release process ? I guess it means having a branch/tag by version of the engine.
Hello,
Currently we're using 5.0.3.
On each engine update, we need to resave the assets in the Content folder (usually two times in a row until there are no more changes).
Not doing so means that our own assets, depending on HoudiniNiagara ones, will systematically be resaved by the ResavePackages commandlet.
Is that something you're aware of, and could you take it into account in your release process ? I guess it means having a branch/tag by version of the engine.