Indeed there was mate, and an enormous help it was even if I do say so myself. Unfortunately it has long since disappeared beneath the waves :wah:

A new wiki? A bloody marvellous idea, however most questions these days appear to be mod (compatibility)/starforce/win 7, related. Now if someone could really crack this blasted screenshot voodoo ............... !

If you do decide to continue with the new (revised) wiki. I would certainly like to contribute what little knowledge I have.

Best regards.

Fubar2Niner

Well I don't suppose that it would hurt to add some tips-n-tricks to get mods working properly, as that can be a hassle at times... :hmmm:

I am beginning to suspect that the source code will need to be modified to use possibly changed Windows 7 library calls and recompiled on an Windows 7 machine.

Here is a thought, I don't know if it has been tried yet, but does Windows 7 have compatibility modes? Would changing the compatibility mode of the sh3.exe to Windows XP make the res fix work?

I'll give anything a shot once, will report my findings later. Thanks for the input mate :salute:

Best regards.

Fubar2Niner

Give it a go and report back but, sorry to say, I think I tried comp modes as far back as Win7 would allow as well as disabling a bunch of stuff entirely (Aero, etc.) and none of that ever worked either.

I wonder if it would be worthwhile setting up a poll thread for people who have the Res Fix CTD issue to report what OS they are on... I've always suspected that it's Vista/Win7 related somehow but have nothing except my own experience to back up that suspicion. :hmmm:

Surely if it could be narrowed down to one or two versions of Windows that might make finding a fix a lot easier.

See below kaleun

Read on mien frau

Certainly couldn't do any harm in my book :up:.........

@krashkart thanks for the interest mate:salute:

OK on to my findings so far.

1) I followed Kafka's train of thought and enabled compat mode (XPSP3) on an already 4GB patched SH3.exe, no dice CTD after my first screenshot attempt :damn:

2) I tried again but this time using Gamebooster, before luanching SH3 thru Commander........ again no dice :hmmm:

3) This time before anything I reverted the .exe back from compat mode, applied Osmium Steele's little workaround, (mentioned in first post), re-enabled compat mode on the SH3.exe. Launched Gamebooster and started SH3 from Commander..........

I have so far succsesfully taken 17 screen shots without any mishap :rock:
This is early days people, so I don't want to raise too many hopes yet. All 17 shots were tagged in quick succsession, normally instant death for me, using a combination of Ctrl+PrtSc and plain PrtSc. I am getting no black screens in shots so far...............


Things may be looking up. More to follow.........................:salute:

Best regards.

Fubar2Niner

@all


Despite a promising start things just took a downward turn. I restarted SH3 using the same procedure as in 3) in post above. Tried taking a screenie and this time crash. However not a CTD, just a total freeze, never had this before.......

Ideas anyone?

Best regards.

Fubar2Niner

Drat!!! That is very discouraging, so close and then so far.

I'm sorry mate, I got nothing else to help you with. :cry:

This might be useful to someone, it is how I get Full Screen Antialiasing (FSAA) in Silent Hunter III with my NVidia video card. nHancer and other tools don't work for me.

I am using Windows XP and my video card is an 8600GT with drivers version 197.13, so I don't know if it would apply to Vista or windows 7 or the later NVidia drivers or control panel.

1. Find the NvApps.xml file in your C:\WINDOWS\system32 folder and make a backup copy just in case this this dosn't work for you.

2. Open the NvApps.xml file with Notepad and search for "Silent Hunter III" to find the profile settings.

3. Paste this line:

<PROPERTY Label="aa_feature_bits" Value="0x20000000" Default="0x20000000" Itemtype="predefined"/>

right after this line:

<PROPERTY Label="multichip_rendering_mode" Value="0x02000001" Default="0x02000001" Itemtype="predefined"/>

as in this example below

http://img15.imageshack.us/img15/117...pssettings.jpg

Doing this ensures that FSAA gets applied to the entire scene and has greatly improved my overall scene quality. Until I learned how to do this things just looked terrible in the distance.

This setting was taken from the settings for the "Most EA Strategy Games" and the "Command and Conquer 3" series of games settings in the NvApps.xml file. There are other "aa_feature_bits" values in the file, but I haven't tried them yet as this seems to work fine.

PS. The lines in the profile after the pasted line will probably be different than in the image above, depending on what settings you have in the NVidia control panel.

@Kafka - Added to the opening post. :salute:


@Fubar - Good effort, mate. Hopefully that nut can be cracked... :salute: