LWAMI 3.09-3.10 bug advisory and request for help

[Molon Labe]

EDIT: The trigger compatibility issue that follows below has been fixed. There will not be a compatibility issue from 3.10 onwards.


--------------------------------

OK guys, I have some good news and bad news.

The good news is, the release of LWAMI 3.10 is imminent. And it's got a lot of new platforms and doctrines, and DB improvements that will hopefully make this the most complete DW experience we've had yet.

The bad news is the reason it's been delayed. There is a error in the indexing system that began in 3.09. The effect of this error is that triggers which specify particular platforms to complete a trigger have had their platform switched. The effect of this is that some missions written for stock DW and earlier mod versions will have some non-functioning triggers in 3.09 and 3.10. I've held up the release of 3.10 to try to fix this, but after playing with the object numbers, class numbers, and entity numbers, the problem persists. The unfortunate truth is that this issue has TLAM, LW, OneShot and I stumped. If anyone out there has any ideas (other than moving object/classes/entities around to make sure no new o/c/e's appear inside groups of stock o/c/e's and are all added in the back) we would be very happy to hear them.

But, short of getting help, it's time to bite the bullet and move forward. I hope the impact of this indexing error will be minimal, but in any case, the LWAMI project has always prided ourselves on reverse-compatibility, so we will treat this as a serious issue. I will personally take responsibility for mitigating the effects. So, I'm going to do two things: (1) Create and publish a list of any missions effected--PLEASE inform me if you become aware of any such missions. I'll coordinate with Bill and Oneshot to make sure the appropriate notices are displayed whereever these missions are available so users downloading them will know what versions they work with. (2) With the mission designers' permission, I will personally edit and re-release any effected missions to be compatible with LWAMI 3.09 and 3.10.

I don't think this is something most users will even notice, but just the same, it's important to make sure the product works like it's supposed to. Thanks for your support.

[Blacklight]

Thanks for all the work you guys are doing ! I wasn't even expecting a new LWAMI release !
Take your time. There's no rush. The sim isn't going anywhere and I'm sure that all of us subsimmers would like LWAMI to be the best that it can be ! Editing the missions for compatability is going above and beyond anything I've ever seen a modder do ! Usually it's just. "Here's the mod. Such and such isn't compatable. Good luck with that." Editing things to make them compatable can be quite a task and I'm really greatful that you're willing to go that extra mile. Your work is appreciated !

Perhaps you could collect the "fixed" missions into a single zip file that can be downloaded and put into DW with JGME along with the new LWAMI, overwriting what's already in the scenario folder. Then just update that zipped folder as new "fixed" missions become ready. Or maybe set up a "Mega-Missions Pack" or something like that.

[Molon Labe]

Originally Posted by Blacklight

Editing the missions for compatability is going above and beyond anything I've ever seen a modder do ! Usually it's just. "Here's the mod. Such and such isn't compatable. Good luck with that." Editing things to make them compatable can be quite a task and I'm really greatful that you're willing to go that extra mile. Your work is appreciated !

Thanks. I don't really think it's that big of a deal, it's just a few fields that need to be changed. It's a small bit of effort I can make to try to make this right. One way or another, the error is probably my fault so it's my responsibility to deal with. Luftwolf takes reverse compatibility seriously and I don't want to tarnish his legacy with a noob mistake.

Perhaps you could collect the "fixed" missions into a single zip file that can be downloaded and put into DW with JGME along with the new LWAMI, overwriting what's already in the scenario folder. Then just update that zipped folder as new "fixed" missions become ready. Or maybe set up a "Mega-Missions Pack" or something like that.

That's a pretty good idea, putting all the corrections in a single pack. I don't want to overwrite the old ones though--people may still want to play the same missions with stock DW.

[Hitman]

That's a pretty good idea, putting all the corrections in a single pack. I don't want to overwrite the old ones though--people may still want to play the same missions with stock DW.

Why not simply include them in 3-10? If the mod is enabled via JGSME, you play LWAMI and you get the correct missions. If you wanna play stock DW, fire up JGSME, disable LWAMI -and the fixed missions- and play again normally with the stock game.

[Molon Labe]

Originally Posted by Hitman

Why not simply include them in 3-10? If the mod is enabled via JGSME, you play LWAMI and you get the correct missions. If you wanna play stock DW, fire up JGSME, disable LWAMI -and the fixed missions- and play again normally with the stock game.

We could do that. But, the "list" will probably grow from week to week or month to month. So we'd have to re-release the mod every so often, I think. I'll ask OneShot about it. In any case, it wouldn't be too much trouble to have a single downloadable zip that is constantly being updated. The first line of the Mission Description will have version notes so people scrolling through missions will know right away which one they're browsing.

[Tarrasque]

Originally Posted by Molon Labe

So we'd have to re-release the mod every so often, I think.

Perhaps I'm being dumb but couldn't you just release the missions separately and just get the user to stick them in the relevant folder - much as (for example) Operation Monsun for SH4 has done with its hotfix.