Pissed off........ctd

Originally Posted by danlisa

SH3 Commander is 100% stable.
GWX is 100% stable.
SH3 Rez Fix SP2 is 100% stable.

PROVIDED you use them as instructed.

What I find amusing about these threads is the lack of details.

OMGZ!!! CTD arggggghhhhh! Does not help!

In an attempt to diagnose the OP's problem.

1) Was this a 100% clean installation of SH3 1.4b and then GWX 3.0?
2) Was the SH3 folder in My Documents deleted?
3) Are you using previous Game save files?
4) Did you install the GWX specific SH3 Commander Files?
5) Did you activate any mods without rolling back Sh3 Commander first?

Seriously, there are lots of areas where you can balls up your game if things are not done correctly.

Just don't tell me you never had a CTD yourself, well unless u don't play at all.

Copy from event viewer below.

Faulting application sh3.exe, version 1.4.0.1, faulting module sh3.exe, version 1.4.0.1, fault address 0x00090038.

I redownloaded rez fix just to check if I have the very same version of it and that was true. Since I'm using XP SP3 I use only d3d9.dll and d3d9.cfg files to make a 1280x1024.

Answering your 5 questions:

1. Of course it was clean
2. It was not since after the intallation of sh3 there followed GWX intallation immediatly.
3. Not sure what you mean.
4. Yes, the same you have to do for OLCG2 (I think it's only for salvo torpedo switch numbers to be visible)
5. It's always on AutoRollback.

Now I will be extreme datafull and show you my JSGME stuff:



Now go figure why da hell I'm getting CTDs mister wise arse!

[danlisa]

Originally Posted by Contact

Just don't tell me you never had a CTD yourself, well unless u don't play at all.

I have never had a CTD using any final release version of GWX, used in conjunction with SH3 Commander and/or the Res Fix.

Plenty of CTD's during development & testing though.

Since I'm using XP SP3 I use only d3d9.dll and d3d9.cfg files to make a 1280x1024.

Why? Even using SP3 you need all the Rez Fix files. I have an install under SP3 and all the Rez Fix files are installed and the game is working correctly.

Now I will be extreme datafull and show you my JSGME stuff:

Now go figure why da hell I'm getting CTDs mister wise arse!

I'll do you one better. Disable EVERYTHING that is not an Official GWX Verified Mod and then try your game. As this 'Wise Arse' already stated, GWX and it's MODS are 100% stable. Any instability caused by the addition 3rd party mods is the owners own dumb ass fault.

Because the rez fix is working fine with these two files only. You set the desireble resolution in .cfg via notepad and .dll does the rest of a job.

Blame my ignorance but I have no idea why I have to run SP2 Rez fix.bat then ? Or what does SHIII.sdb do ?

[TarJak]

I'm with Danlisa on this. The only time I experience CTD's is with the introduction of untested mods on top of my GWX3.0, SH3Commander, Resfix install. I find if I remove said mods, the problems disappears.

I use the method Contact uses for Resfix. DLL installed to SH3 folder, edit the config and make sure that the res is the same as your desktop res. Any differences between the two will cause CTD's.

If you say Rez fix is 100% stable then could it be somewhere incompatible with OLCG2 ? Guess no one knows that..

[JScones]

Originally Posted by StarLion45

there you ' re wrong Contact . If you die , and decide that you want to start the patrol you died in , you must never start SH3Cmdr right away , it crashing to desktop at ONCE . YOU MUST START IN THE GWX GAME , OR STOCK sh3

I don't even understand what you are trying to articulate, but it sounds to me that you are doing something screwy.

I mean, if you die, SH3Cmdr will no longer let you load the dead career. Thus for you to use it, you must be interfering manually. As soon as you interfere manually, and THIS INCLUDES REVERTING TO A PREVIOUS SAVE POINT IN ANY CAREER, you potentially break SH3, which in turn breaks SH3Cmdr.

But I'm sure you would know this, having no doubt read the FAQ in the SH3Cmdr User Guide.

Unfortunately SH3Cmdr usually ends up blamed for CTDs because of:
a) some interesting user belief that SH3 is perfectly coded thus couldn't be at fault
b) some interesting user belief that it couldn't possibly be anything they've done (like add conflicting mods, incorrectly edit files etc etc)
c) some interesting user belief that searching forums for possible answers before ranting is a waste of time, you know, like finding instances of similar problems occurring *before* SH3Cmdr and mods like GWX even existed (I know SH3Cmdr and GWX are mighty good, but I don't think they're good enough to create CTD's before they even existed!)
d) some interesting user belief that as SH3Cmdr is the last thing they see before SH3 loads, *anything* that goes wrong in SH3 must be attributed to it.

But as anyone who has read the SH3Cmdr User Guide will know, SH3Cmdr is very particular in what it changes, especially when you are mid patrol (hence why it recognises such careers). It limits changes to those proven not to cause CTDs under normal usage (through repeated scenario testing).

I will state categorically that outside of testing I have never had a CTD while playing SH3 + GWX (all versions), ever. Call me a smartarse or whatever you like, but the reason is simple: basic housekeeping and knowing what I am doing (ie following "manufacturer's" instructions and taking no shortcuts because "they seem right"). Much like maintaining a car. It can be done.

I'm not pointing fingers at anyone in this thread (indeed, any defensiveness may be an indication of guilt), but that's simply how it is.

[TarJak]

Originally Posted by Contact

If you say Rez fix is 100% stable then could it be somewhere incompatible with OLCG2 ? Guess no one knows that..

I can't comment on OLCG2 because I don't use it. I've installed it an tried it but prefer not to use manual targeting because I'm a lazy Kaleun.

Looking at your list of mods there are possibly 3 or 4 potential candidates for causing CTD's.

Originally Posted by TarJak

I can't comment on OLCG2 because I don't use it. I've installed it an tried it but prefer not to use manual targeting because I'm a lazy Kaleun.

Looking at your list of mods there are possibly 3 or 4 potential candidates for causing CTD's.

Name them please.

[TarJak]

It's probably one mod that is not compatible with something else you have running so naming them is not really for me to say. Doing so may offend the modder and the people who did the testing of that mod.

I should have said there are 3-4 candidates for causing incompatibilities which may cause CTD's. It is most likely the mix of mods you have rather than any single mod, however that may also be the case.

Usually mods are well tested against a base install without other mods in the way.

The only way to diagnose a combination of mods is to remove them all then add them back one by one then run several tests across a number of scenarios. If you still get CTD's then take that mod out and try the next one and so on until you don't get anymore CTD's.

It's a pain in the rear but then so was testing my GWX set of mods for months until I settled on a group that is stable and provides me with some enjoyment.

[Hanzberger]

Well a lot has gone on in a couple of days of being away. OK maybe I am a big dummy but help me understand some things:

First off I did search the forums (not extensivly) and found some threads on CTD's. Everything I read was either old or didn't have anything to do with what happened to my CTD.

I am using a clean install with GWX3.0 and no additional mods. And yes I followed the instructions and installed all the files needed to run that and CMDer per the directions.

I made sure I was on the surface, no other ships around, not raining so it seemed like a good time to quit and save.

Yes I was angry cuz I don't have a lot of time to play this game let alone finally have a good career going and then have it lost.

Now I still have some questions:
This I did not know or missed but are we suppose to delete the folder SH3 from "my documents"?????

2)when you leave the game it doesn't allow you to just quit it always puts you back in base so when you go to restart, cmder has you starting back in base. Once in the game I go back to where I was at "in mission"
What am I missing here? What I am thinking is that cmder and the game don't jive all the time by doing this since when you start thru cmder, and I just checked, it has me at home base. The only option it gives me to change that is to start at another base. I wanna start where I left off, at sea. I hope this makes some sense I am on 5hrs sleep in 2 days.

And this CTD happened on my 5th try. (career wise) so everything was fine up until this happened.

[TarJak]

Originally Posted by Hanzberger

This I did not know or missed but are we suppose to delete the folder SH3 from "my documents"?????

Before installing GWX you must remove the SH3 Folder from My Documents.

[Melonfish]

Originally Posted by TarJak

Before installing GWX you must remove the SH3 Folder from My Documents.

Actually i didn't do this and i've only ever had one CTD and that was a duff save file.
otherwise no issues.

[Jimbuna]

Originally Posted by Melonfish

Actually i didn't do this and i've only ever had one CTD and that was a duff save file.
otherwise no issues.

Then you are luckier than many other people who have done similarly.

The installation instructions for GWX3.0 strongly advise against that course of action.

[Hanomag]

Originally Posted by JScones

I don't even understand what you are trying to articulate, but it sounds to me that you are doing something screwy.

I mean, if you die, SH3Cmdr will no longer let you load the dead career. Thus for you to use it, you must be interfering manually. As soon as you interfere manually, and THIS INCLUDES REVERTING TO A PREVIOUS SAVE POINT IN ANY CAREER, you potentially break SH3, which in turn breaks SH3Cmdr.

But I'm sure you would know this, having no doubt read the FAQ in the SH3Cmdr User Guide.

Unfortunately SH3Cmdr usually ends up blamed for CTDs because of:
a) some interesting user belief that SH3 is perfectly coded thus couldn't be at fault
b) some interesting user belief that it couldn't possibly be anything they've done (like add conflicting mods, incorrectly edit files etc etc)
c) some interesting user belief that searching forums for possible answers before ranting is a waste of time, you know, like finding instances of similar problems occurring *before* SH3Cmdr and mods like GWX even existed (I know SH3Cmdr and GWX are mighty good, but I don't think they're good enough to create CTD's before they even existed!)
d) some interesting user belief that as SH3Cmdr is the last thing they see before SH3 loads, *anything* that goes wrong in SH3 must be attributed to it.

But as anyone who has read the SH3Cmdr User Guide will know, SH3Cmdr is very particular in what it changes, especially when you are mid patrol (hence why it recognises such careers). It limits changes to those proven not to cause CTDs under normal usage (through repeated scenario testing).

I will state categorically that outside of testing I have never had a CTD while playing SH3 + GWX (all versions), ever. Call me a smartarse or whatever you like, but the reason is simple: basic housekeeping and knowing what I am doing (ie following "manufacturer's" instructions and taking no shortcuts because "they seem right"). Much like maintaining a car. It can be done.

I'm not pointing fingers at anyone in this thread (indeed, any defensiveness may be an indication of guilt), but that's simply how it is.

SH3 COMMANDER IS OPERATING AS INTENDED!!

[Hanzberger]

Originally Posted by TarJak

Before installing GWX you must remove the SH3 Folder from My Documents.

So is it too late to do it now or do I have to reinstall everything again?