Resolution fix, help needed

[bybyx]

Hello everyone.
I decided to go back to SH3 after a very long time. I am not an expert in subsim games, but I played the SH2, SH3 and SH4 for fun and because these games have an unique feeling that you can not find in any other game. I used automatic targeting but now I decided to use manual.
I already played SH4 at 100% reality settings thanks to an amazing tutorial from Werner Sobe. I played SH3 when the game first came out, then with GWX1 an now with GWX 2.1 + OLC's mods for visuals and manual targeting and a few more. The thing is that I never completed the game an now I am keen to do it.
I want to use " The resolution fix" because I have an LCD monitor with a resolution of 1280/1024 an at 1024/768 the game looks rather...well not quite good.
Have you people encountered problems with this resolution?
Thanks!

[Castout]

If you're using OLC mod resolution fix will make the OLC part becomes inaccurate.

I tried it and all my OLC calculations were wrong. I got rid of the resolution fix mod and the calculation became accurate again.

[bybyx]

I see
thanks

[Stev1]

You could try this if you have the Microsoft Application Compatibility Toolkit Installed

On Windows' Start menu, select "All Programs/Microsoft Application Compatibility Toolkit 4.0/Tools" and run the Compatibility Administrator.
When the program opens, make sure "New Database" is highlighted under "Custom Databases", and click the "Fix" button.
In the "Name of program to be fixed" box, type "SH3". Now, click the browse button, and select the sh3.exe in your SH3 install directory. Then click on the "Next" button.
Under "Operating System Modes" select "None" and click the "Next" button.
In the "Compatibility Fixes" box, check DelayDLLInit, and click the "Parameters" button.
In the "Command Line" box, type "d3d9.dll" and click "OK". (You can click the "Test Run" button to make sure it is working). Click the "Next" button.
Click on the "Finish" button. Then click the "Save" button, name it "SH3", and click OK.
On the "File" menu, select "Install".
Close the Compatibilty Administrator.
Enjoy SH3 in high display resolution.

[Castout]

Yes that Stev1 will ruin the OLC mechanism

[bybyx]

Could the developers have provided a patch that could enable higher resolutions?

[Castout]

Well no instead they have successfully ruined SH title by releasing the current SH4 . SH3 is waaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaay

better.

SH4 is sugar coated rubbish. Eek.

[Wolfehunter]

Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: sh3.exe
Application Version: 1.4.0.1
Application Timestamp: 00000000
Hang Signature: e8f4
Hang Type: 2048
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 4105
Additional Hang Signature 1: 780001ff5bed2f1a4cf54573e6aa0ad0
Additional Hang Signature 2: 1665
Additional Hang Signature 3: 50981315c1b209a09b5e8ed5acdf24ae
Additional Hang Signature 4: e8f4
Additional Hang Signature 5: 780001ff5bed2f1a4cf54573e6aa0ad0
Additional Hang Signature 6: 1665
Additional Hang Signature 7: 50981315c1b209a09b5e8ed5acdf24ae

I get this error when trying to use PrtScr and take some shots.

I'm using 64Bit software but it hangs or crashes. I can only get the first pic. When I try again I get this hanging error.

I've tweak the d3d9.cfg,

;
; DX9res Settings
; by Kegetys <kegetys@dnainternet.net>
;
; Note that this config is reloaded on device reset, so you can task switch out
; of the game, change settings from this file and then return
;
[config]
; ResX: Horizontal resolution setting
; ResY: Vertical resolution setting
; useFiltering: Use linear filtering for UI elements
; enableScreenshots: Hook printscreen keypress to save TGA screenshot
resX=1680
resY=1050
useFiltering=1
enableScreenshots=1
screenshotPath=C:\****\Pictures\SilentHunter3 Pics
[gamma]
; setGamma: Override gamma ramp
; gammaRed: Red channel gamma (1.0 = normal, decrease to add brightess, increase to darken)
; gammaGreen: Green channel gamma (1.0 = normal, decrease to add brightess, increase to darken)
; gammaBlue: Blue channel gamma (1.0 = normal, decrease to add brightess, increase to darken)
setGamma=0
gammaRed=1.0
gammaGreen=1.0
gammaBlue=1.0


Anybody have any idea what is causing this crash? It happen with my old rig on a rare blue moon it would CTD but this uber rig it shouldn't be an issue? :hmm:

Can't be hardware.

Here is the last shot before it froze.

http://i240.photobucket.com/albums/f...r/Hangshot.jpg

[denis_469]

Apparantly not enough videomemory in you comp. So if you up reholution you need have reserve videomemory before up resolution.

[Wolfehunter]

Originally Posted by denis_469

Apparantly not enough videomemory in you comp. So if you up reholution you need have reserve videomemory before up resolution.

I have 2 gigs of video memory? 1gig from my GTX280 and 1gig shared memory?

It doesn't make sense.

My old rig had 500megs give or take a few and it worked mostly.

256megs from my GeForce 7800GTX and few extra megs from shared.

New rig uses vista ultimate 64bit

Old used vista ultimate 32bit.

Only does this when using Resolution fix.

If I use default SH3 rez no crash and I can record Fraps videos without a CTD.

Also forgot to add I need Vsync on for the pics to work properly or I get some funky shots...

I also wanted to add this line found in the Event Viewer,

Binary data:

In Words
0000: 006E0055 006E006B 0077006F 0000006E
0008: 0000

In Bytes
0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n.
0008: 6F 00 77 00 6E 00 00 00 o.w.n...
0010: 00 00 ..

[Commander Gizmo]

Sounds like it could possibly be a bad memory address. Try ditching the shared memory and see if it works better. Shared+onboard memory doesn't always work as well as we'd like.

I suspect that D3D or SH3 is having trouble addressing the memory due to the large size and split setup.

[Wolfehunter]

Originally Posted by Commander Gizmo

Sounds like it could possibly be a bad memory address. Try ditching the shared memory and see if it works better. Shared+onboard memory doesn't always work as well as we'd like.

I suspect that D3D or SH3 is having trouble addressing the memory due to the large size and split setup.

I wish I could remove the shared memory from Vista but I think you can't.

I don't remember where I read it because it was about a year ago when I first got vista 32. I hated the shared memory but I think it can't be turned off.

I've check the Vista forum on this hang issue and many programs hang especially explorer...

Funny thing is that the tech guys from MS say well you need a clean install.

RIGHT! Sure I have a clean install. Jezz..

Or did you make sure its compatible with vista first.

RIGHT! What is really compatible with vista? Please anyone... :rotfl:

I mean what the hell.

I know there is a conflict but what..:hmm:

It can't be bad memory because it works with SH3 Vanilla without the Resolution fix.

So something is wrong with rez fix mod...

Hmm I'm going to try to contact the maker.. Maybe he or she knows.

Thanks for your help guys.

I still like to hear other idea and solution if any.

[jaxa]

Originally Posted by Castout

If you're using OLC mod resolution fix will make the OLC part becomes inaccurate.

I tried it and all my OLC calculations were wrong. I got rid of the resolution fix mod and the calculation became accurate again.

Does it mean that better not enable resolution fix using OLC? :hmm:
I use GWX 2.1 with resolution fix (1280x1024) and want to test OLCU. Will it be compatible?

[Commander Gizmo]

One possible reason that vanilla SH3 would run but not GWX+OLCE2 is that the latter has a vastly larger amount of textures, thus using all that memory. A lot of games have a hard time addressing higher memory addresses.

You don't change shared memory in Windows, you do it in BIOS. Not all systems let you control it there either.

You can test your system memory using a program called Memtest86. You download the CD image and burn it to disc. Then you boot your system and run test 7. I think the key strokes are C, 1, 3, 7, ENTER, C or something like that. Test 7 catches most problems.

I am not saying that is your problem, just that it is likely.

Originally Posted by jaxa

Does it mean that better not enable resolution fix using OLC? :hmm:
I use GWX 2.1 with resolution fix (1280x1024) and want to test OLCU. Will it be compatible?

It means if u do a manual targeting, your fire solution might be wrong under the use of OLCE2+ res fix. I personally used OLCE2 v.2.4.2 (without GUI) with res fix and it looked pretty normal if not mentioning oddly small sun.