![]() |
SUBSIM: The Web's #1 resource for all submarine & naval simulations since 1997 |
![]() |
#9 |
Silent Hunter
![]() Join Date: Dec 2004
Location: AN9771
Posts: 4,904
Downloads: 304
Uploads: 0
|
![]()
Well, I had another look at this issue and did some deeper digging in the forum. I found posts late april where people respond the same thing I did. I gathered the only thing I did wrong was trying to enable the 'Holtenau/Brunsbutel Lock'-Fix when I don't have that mod installed at all. So I made a fuss about it for nothing.
However, I still disagree with the choice for having made this a JSGME-fix. This second start-up of JSGME required to make the 'Late War Sensor'-fix to actually get applied (and 'Holt./Brunsb. Locks Location'-fix added) would easily be circumvented when users would have been required to temporarily dissable ALL mods (to make a virgin GWX 2.1 again), and then simply extract the 'data', 'documentation', and 'MODS' folder directly into the SH3 base folder (simply over-write files like any patch does). And after that re-enable their choice of mods (Holt./Brunsb. Location fix after the original mod) and play a fixed GWX2.1. Otherwise I think it's a dirty way to fix because the need to start JSGME twice (recursive nature). The only reason I can think of for applying the fix through JSGME is if this is not a definitive fix and needs to make place for a future update. If so, the readme should have stated to enable the fix before anything else (to properly update/add the folders to Sh3/MODS) and restart JSGME before further enabling. So I guess I'll be able to leave port now. Brittain, beware!!! |
![]() |
![]() |
|
|