Log in

View Full Version : gwx2.1 bug fix queery


flag4
05-06-08, 11:16 AM
i have downloaded the minor bug fix for 2.1.

it sits on my desk top and im wondering , does it find its own home or do i have to install it myself

thanks for your patience !:D

bigboywooly
05-06-08, 11:33 AM
lol
No tis a JSGME mod

flag4
05-06-08, 11:42 AM
im sorry bbw - but do you mean install it in JSGME

Yorktown_Class
05-06-08, 11:57 AM
im sorry bbw - but do you mean install it in JSGME

You got it:yep:

flag4
05-06-08, 12:05 PM
thank you :up:

Pisces
05-24-08, 04:59 PM
I had a look inside the filestructure of this GWX 2.1 'mod-fix'-mod and it confuses the hell out of me. When I enable this fix with JSGME it appearantly fixes some files in the data-folder and adds a readme file to the documents folder as it is expected to do. No confussion sofar. But it also contains another 2 additions to the MODS folder ( 'GWX - Late War Sensors Snorkel Antennas' and 'GWX_2.1_Location for Holtenau and Brunsbuettal locks' ) that (only) show up in JSGME when started a subsequent time. That is to say, since the 'Late War Sensors Snorkel Antennas'-fix has the same name it works as an update to the original optional late war sensors mod folder, so it really is invisible now. However when I try to enable the 'Holtenau brunsbuettal locks' update is says that it is in conflict wrt 'Locations.cfg' from the initially enabled 'GWX 2.1 Minor fix's 26th April'-fix. This kind of recursive mod enabling doesn't make sense to me and I suspect it is in conflict with JSGME modding rules.

What's going on or what am I doing wrong?

Pisces
05-26-08, 06:07 PM
***Bumpedy bump***

Also, I got this fix on the FileFront page of Bigboywooly. But the GWX Home site makes no mention of these fixes, not even a link to FF. You would think these are important for a correct working of GWX and everybody should have them. GWX people in the know, please respond. Those docks are boring me, I want to go 'Auslaufen' again.

Madox58
05-26-08, 06:14 PM
Sorry Mate,
BBW is unavailable at this time so
I'll check it out and get back to you.
Sorry I missed the posts!
:damn:

Pisces
05-27-08, 05:30 PM
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!!!