LWAMI 3.09-3.10 bug advisory and request for help

Molon Labe · 09-02-09, 10:59 AM

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.

09-02-09, 10:59 AM	#1
Molon Labe Silent Hunter Join Date: Jun 2004 Location: Along the Watchtower Posts: 3,810 Downloads: 27 Uploads: 5	LWAMI 3.09-3.10 bug advisory---SOLVED 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. __________________ Last edited by Molon Labe; 04-07-10 at 03:05 PM.