SUBSIM Radio Room Forums - View Single Post

Molon Labe · 04-06-10, 11:12 AM

Actually, the trigger-compatibility issue arose in LWAMI 3.09, not 3.10.

Here's the short version on LWAMI compatibility. The general rule is that stock missions are compatible with LWAMI and vice-versa. Those missions may play differently because of different capabilities in the two sim versions. By now, most people know that the Oscar II in the first stock campaign mission can detect the player 688I at mission start in some instances, because LWAMI gives the Oscar a towed array that it doesn't have in stock DW.

[strikethrough]LWAMI versions 3.09 and later also have an issue with trigger compatibility. Some triggers that name a specific class or ship that is supposed to complete a trigger may reference the incorrect ship/class. We'll be working on the mission list/fixes after release. [/strikethrough] I'm even going to revisit trying to fix the issue outright, maybe the time away from the issue will allow me to tackle it from another angle. (EDIT: turns out that was a good idea, the issue is indeed solved! So just ignore this paragraph.)

04-06-10, 11:12 AM	#5
Molon Labe Silent Hunter Join Date: Jun 2004 Location: Along the Watchtower Posts: 3,810 Downloads: 27 Uploads: 5	Actually, the trigger-compatibility issue arose in LWAMI 3.09, not 3.10. Here's the short version on LWAMI compatibility. The general rule is that stock missions are compatible with LWAMI and vice-versa. Those missions may play differently because of different capabilities in the two sim versions. By now, most people know that the Oscar II in the first stock campaign mission can detect the player 688I at mission start in some instances, because LWAMI gives the Oscar a towed array that it doesn't have in stock DW. [strikethrough]LWAMI versions 3.09 and later also have an issue with trigger compatibility. Some triggers that name a specific class or ship that is supposed to complete a trigger may reference the incorrect ship/class. We'll be working on the mission list/fixes after release. [/strikethrough] I'm even going to revisit trying to fix the issue outright, maybe the time away from the issue will allow me to tackle it from another angle. (EDIT: turns out that was a good idea, the issue is indeed solved! So just ignore this paragraph.) __________________ Last edited by Molon Labe; 04-07-10 at 03:09 PM.