edit: this issue is now fully patched, github.com/tildearrow/furnace/commit/f68249f52bdbe677ed4c7465eba4a71fb107e84f I'd ask everyone to remain calm about the issue regarding s3m import, as it's a very new feature. There was a lot happening all at once, furnace localization, TIA updates. And dramas. instead of coulda/shoulda done it anyways, it's time to heal, time to lend a hand. You can do that by wait a few days for a emergency hotfix, then try all the s3m you can find see if it's fixed. if not, after a well thought outs, perhaps submit a Issues. I should point out that even OpenMPT, whose doing this for soolong, didn't hack it, even now there's still some files that don't play well. Furnace just started, and it's a very big project. I believe more consideration should be paid, as it's unreasonable to ask every release being perfect LTS quality from project this size. Thank you for reading this.
tildearrow was not smart here. The whole import was pushes from very initial state (in which it was for several months) to the current state in just 5 or so days, that's why it does not work properly. Tildearrow better either not include it in this release or postpone release until it works properly.
yeah...it coulda done better... but there's a lot happening at once, translation, TIA pitch patches. Idk.. one thing to know is that even OpenMPT not hack it completely, there's still some modules don't work well on OpenMPT who's been at it for very long. Just my primitive view, that's it.
@@wheatenclient3623 I will use OpenMPT to improve s3m/xm/it import when tildearrow finishes working on it. I will also probably create a separate system to support IT filters abd bew note actions properly.
@@ltva8781 thanks! that would really helps with this situation. You I both know it's too late for blaming and coulda done betters, it's time to do things really helps. I've submitted numours issues in furnace/issues, hope they would help some.
