I dont think thats a cigar. :shifty: :rotfl:

It's not a cigar?? Well it that case, thanks, but it's been a while. I don't think I'll need that much. :|\\

No, but it'll still smoke for a while......:rotfl:

Maybe its a fat cuban? I dunno, i just did a google image search for Cigar, and that one just stood out :D

Only a few weeks to go till i can raid ports in my country of residence :rock:

Say if i wanted a list of new ports that will be in GWX.... who would be the person to beg? :oops:




* lol im now a seaman *

hmm...
Gibs maybe. Or rubini. That is, if their willing to tell you before GWX is released ;)

I have a pretty good idea, but you coudlnt pry it out of me with a crowbar.

New Ports List:

Very Long!

Enjoy! ;)

Oh ok, even if there was just one port in Australia, like Sydney or Darwin id live happily with that :up: ill try and reframe from greedy thoughts :nope:

OK, there appears to be a simple misunderstanding which I will now clarify for all.

The auto-installer DOES NOT automatically install into any path. Yuck. My professional peers would ostracise me. Actually, I would ostracise myself.

The installer (perhaps we'll drop the "auto" to avoid further confusion) works like most other installers - you have total control over where you want to install it. Indeed, you can select ANY path on your computer.

However, it will only CONTINUE the installation process if the path YOU HAVE SELECTED is verified as a clean, unmodded SH3 patched to v1.4b. The installer is smart enough to identify this. If your clean install is at "C:\SH3\MyCleanInstall\" or "C:\SH3\MyGWXInstall\", then so be it. Yes, it *defaults* to the registry path (to suit most players), but it certainly does not *force* this path. Here's a screenshot to demonstrate...

http://www.users.on.net/~jscones/tmp/GWXInst1.gif

Notice the folder I selected? Well, here's the next screen...

http://www.users.on.net/~jscones/tmp/GWXInst2.gif

Oops, silly me. Better select a different path (no point showing a screenshot of a suitable path as the installer just moves to the next page).

FWIW my clean SH3 is at "C:\Games\SilentHunterIII- Clean v1.4b". The installer will happily install to it, even though my "default" path is "C:\Games\SilentHunterIII".

Please guys, the installer is nothing to stress over. Its intent is to avoid installation "accidents" caused by forgetting to patch SH3 or forgetting to remove mods from your SH3 prior to installing GWX. It's aimed to help the majority of players that just want to play GWX, not jump through 100 hoops to get it installed and running correctly. Indeed, a scan of the current GW threads demonstrates that these two "accidents" are perhaps the main cause of GW running problems. The installer is simply one of many examples of the GWX team listening to the community.

And let's be logical here - GWX is meant to be *played*, and the only way it can be played is for it to be installed over a clean, unmodded SH3 patched to v1.4b (regardless of where it is installed). So it's silly not to cater for this fact when installing.

I'll also point out here that to make GWX installation even easier still for many players, the installer will include German, Spanish and hopefully French translations.

Now, to address another question, "why can't GWX be installed into/via JSGME?". Well, a number of reasons. Fundamentally, what's the point of having an installer that doesn't do the full job?

Primarily though, GWX modifies OVER 5,000 files. Players must remember that GWX is not a simple tweaking of a few files or the addition of a pretty image or two; GWX totally overhauls SH3. The file interdependancies and such are mind boggling alone. Thus the potential for mistakes if manually installing are far greater.

Players could prolly liken GWX to the v1.4b patch - you install the patch and it becomes your base for all subsequent modifications. GWX is meant to be the same - you install it over v1.4b and it becomes your base for any subsequent modifications. And as you can imagine, with a stable base, subsequent mod problems are less likely, or indeed easier to fault-find and fix.

Plus, GWX makes other changes that JSGME does not natively support - in other words, players would need to follow further instructions to install GWX correctly. Not very user friendly. I certainly do not think that it is appropriate to expect players, no matter how competent they may be, to undertake file manipulation to get GWX to work on their computer where with one click it's all done for them, correctly. See my above comment re mistake potential. ;)

Of course, *after* GWX is installed, you can use JSGME to your heart's content.

If only I hadn't gone interstate for two days...

Thank you JScones
We all happy now?
Good
Can we move along now please!

Well put, JS.

Guys, read the above quote again ;) ;) ;)

...

Von

Nobody satisfy everybody.
I prefer auto installer (better to say semi-auto installer). It's probably stabler and looks more professional than install GWX via jsgme.

<Sound Trumpet> JScones to the rescue.....

That'll teach you for neglecting your GWX duties;)

It is a shame that we have spent so much time/effort concentrating on one minor issue when there is so much that needs to be praised/applauded.

Now back to work the lot of you:D

WW2 Newsreel : U-boat in the indian ocean :D
http://www.youtube.com/watch?v=rg_LJQu2B2s

edit: Figures, has to be U-177 in that newsreel. ANY view or picture of an IXD2, is freaking rare.
http://www.uboat.net/men/gysae.htm

A sub forum isn't the place for debate jargon.

Awesome.

Thanks for building that bridge JScones, now everybody can get over it.:up:

You play Panzer Elite!!:rock:

Another heavily modded game.

Thank you for this clarification. It seems we were indeed misinformed, hence the confusion. As one of your professional peers I approve.
It's an important distinction. The use of "autoinstaller" set off one of my internal alarms which is why I was concerned enough to ask for clarification. "Autoinstaller" and "installer" are not the same thing.
This accords with something I said right at the beginning: if the 1.4b verification process is truly effective then the path is irrelevant.

I'm pleased with everything you've said. The installation procedure you describe follows standard practices and meets the aim of simplifying the installation without unnecessarily inconveniencing some users at the expense of others. Furthermore, and here I confess to a selfish interest, it won't inconvenience or confuse users of MultiSH3 which means I don't expect to be bombarded with emails or PMs requesting assistance.

One quick question: does the 1.4b verifier require the installation to be absolutely clean or does it ignore the presence of things like jsgme.exe or multish3.exe in the game's default folder? If you want to talk about this in detail via email then that's fine with me.

Yeah right, get a dunny roll, your dribbling.

Your stamp of approval is not required nor desired.

Well unless clean now means dirty an full of crap, then I'd say no.

That's not for you to say. This is between professionals.