OP Monson problem

Newbytoo · 03-24-10, 07:07 PM

Hi,

ok I will play a few missions in OMV705 and make note of when and where the ctd's occur. Perhaps should of said but no problems with stock + UBM + RSRDC_SH15_V550. Thanks.

lurker_hlb3 · 03-24-10, 09:02 PM

Quote:

Originally Posted by Newbytoo

Hi,

ok I will play a few missions in OMV705 and make note of when and where the ctd's occur. Perhaps should of said but no problems with stock + UBM + RSRDC_SH15_V550. Thanks.

ensure you have the following "minimum" install

OM v705
OM v720
OM v720 Patch2

Newbytoo · 03-24-10, 10:19 PM

ok I tried the Scapa Flow mission tonight (a bit of an historical favourite of mine

) I ran it without any time compression.

At game time 8:35 pm, about 35 minutes in I get the standard Windows message = Silent Hunter IV has stopped working.

MODS

RSRDC_SH15_V550
OpsMonsun V705
OMV705 to V720
OMV720 Patch 2
OMEGU 300
OMEGU 300 Patch 5A

Thanks

lurker_hlb3 · 03-25-10, 06:42 AM

Quote:

Originally Posted by Newbytoo

ok I tried the Scapa Flow mission tonight (a bit of an historical favourite of mine

) I ran it without any time compression.

At game time 8:35 pm, about 35 minutes in I get the standard Windows message = Silent Hunter IV has stopped working.

MODS

RSRDC_SH15_V550
OpsMonsun V705
OMV705 to V720
OMV720 Patch 2
OMEGU 300
OMEGU 300 Patch 5A

Thanks

Unable to recreate your problem

ShadowWolf Kell · 03-25-10, 03:25 PM

This is something I've been trying to track down myself, and I think it might trace back to being an Nvidia issue with nHancer.

I've encountered CTDs with both sound mods and texture files (the german hats from RUIM for example), but I also noticed video might have something to do with it too.

Currently, the latest Nvidia driver 196.21 doesn't work with nHancer and AA. I've tried just about every setting you can think of to figure out how to get the sun halo while having AA enabled. Nothing worked. I don't even want to go into how many different combinations I tried.

Anyway I noticed some interesting things while doing this. After completely removing the nHancer profile for SH4, I noticed that on reloading the game it took much longer than normal. Like when you first install GWX. Battlefield 2 did something like this every time you made a major video option change and what it was doing was reconfiguring the graphics shaders and whatnot. I'm not sure if SH4 does this as well, but that's the impression I got.

Anyway to make long story short, by running with the standard Nvidia control panel settings set to automatic, things seemed to work much better. More importantly, if I disabled the gamma setting and set the in game settings to AAx4, AFx16, the sun halo effect worked.

Since making this change, the only time I've CTDed is one while approaching Kiel to dock. I've entered and left Scapa Flow on multiple occassions. Something I could never do due to CTDs in the past.

The problem with nHancer is that the EA Strategy Games option doesn't necessarily improve the look of graphics per se. I didn't know entirely how all this worked until I started playing around with the profile settings to get AA to work in Aliens vs Predator while not ruining the predator's heat vision mode. Normally you lose the whole heat gradients and only see blue blurs. I actually discovered a that enabled it, have smooth FPS (unlike the STALKER option) and didn't cause otgher issues or instability.

I think the EA Strategy Game option actually might lead to some instability issues since it's forcing the game to render it's graphics outside the limitations of how SH4 handles things. This can cause some major stability issues. The STALKER profile is an excellent example of this. For the vast majority of games it massively reduces FPS and can cause all sorts of weird behaviour, including CTDs. For STALKER, it actually runs rather well.

I tried every single combination for SH4 and noticed a great many cause all sorts of odd effects, especially when you start using Time Compression. I think this helps lead to random CTDs.

To expand upon this further, I started testing this out with SH5 as well. Quite a bit more obnoxious with the DRM, but something I've never had with SH5 are CTDs. Fiddling with the profile settings for AA compatibility actually introduced some CTDs to my game.

In summary, I really think that the AA compatibility options really have more to due with how it handles shaders than anything else. If you happen to have Aliens vs Predator (2010), you can verify this yourself by going through the AA compatibility options both for DX9 and DX10/11 for the beginning Predator mission and going through the landing cutscene on up to first contact (not the tutorial mission.) You'll see how it effects all sorts of stuff, including smoke, clouds, the cloaking shaders and whatnot.

Unfortunately I've about given up trying to get SH4 running in Combined 8xSQ mode.

McHibbins · 03-26-10, 05:57 AM

Two questions:

Doesn´t the museum work with OM ? CTD all the time while installed as ordered.

Which files do I need to tweak, to get the standard clothes for the crew back ?

Edit : Problem 2 solved

alexradu89 · 03-26-10, 06:11 AM

While having OM installed don't use the museum, as the creator stated it will CTD your game, sorry.

03-25-10, 03:25 PM	#5
ShadowWolf Kell Medic Join Date: Oct 2009 Posts: 163 Downloads: 123 Uploads: 0	This is something I've been trying to track down myself, and I think it might trace back to being an Nvidia issue with nHancer. I've encountered CTDs with both sound mods and texture files (the german hats from RUIM for example), but I also noticed video might have something to do with it too. Currently, the latest Nvidia driver 196.21 doesn't work with nHancer and AA. I've tried just about every setting you can think of to figure out how to get the sun halo while having AA enabled. Nothing worked. I don't even want to go into how many different combinations I tried. Anyway I noticed some interesting things while doing this. After completely removing the nHancer profile for SH4, I noticed that on reloading the game it took much longer than normal. Like when you first install GWX. Battlefield 2 did something like this every time you made a major video option change and what it was doing was reconfiguring the graphics shaders and whatnot. I'm not sure if SH4 does this as well, but that's the impression I got. Anyway to make long story short, by running with the standard Nvidia control panel settings set to automatic, things seemed to work much better. More importantly, if I disabled the gamma setting and set the in game settings to AAx4, AFx16, the sun halo effect worked. Since making this change, the only time I've CTDed is one while approaching Kiel to dock. I've entered and left Scapa Flow on multiple occassions. Something I could never do due to CTDs in the past. The problem with nHancer is that the EA Strategy Games option doesn't necessarily improve the look of graphics per se. I didn't know entirely how all this worked until I started playing around with the profile settings to get AA to work in Aliens vs Predator while not ruining the predator's heat vision mode. Normally you lose the whole heat gradients and only see blue blurs. I actually discovered a that enabled it, have smooth FPS (unlike the STALKER option) and didn't cause otgher issues or instability. I think the EA Strategy Game option actually might lead to some instability issues since it's forcing the game to render it's graphics outside the limitations of how SH4 handles things. This can cause some major stability issues. The STALKER profile is an excellent example of this. For the vast majority of games it massively reduces FPS and can cause all sorts of weird behaviour, including CTDs. For STALKER, it actually runs rather well. I tried every single combination for SH4 and noticed a great many cause all sorts of odd effects, especially when you start using Time Compression. I think this helps lead to random CTDs. To expand upon this further, I started testing this out with SH5 as well. Quite a bit more obnoxious with the DRM, but something I've never had with SH5 are CTDs. Fiddling with the profile settings for AA compatibility actually introduced some CTDs to my game. In summary, I really think that the AA compatibility options really have more to due with how it handles shaders than anything else. If you happen to have Aliens vs Predator (2010), you can verify this yourself by going through the AA compatibility options both for DX9 and DX10/11 for the beginning Predator mission and going through the landing cutscene on up to first contact (not the tutorial mission.) You'll see how it effects all sorts of stuff, including smoke, clouds, the cloaking shaders and whatnot. Unfortunately I've about given up trying to get SH4 running in Combined 8xSQ mode. Last edited by ShadowWolf Kell; 03-25-10 at 03:39 PM.

03-26-10, 05:57 AM	#6
McHibbins Seasoned Skipper Join Date: Feb 2008 Location: Good old Germany Posts: 739 Downloads: 80 Uploads: 0	Two questions: Doesn´t the museum work with OM ? CTD all the time while installed as ordered. Which files do I need to tweak, to get the standard clothes for the crew back ? Edit : Problem 2 solved __________________ Last edited by McHibbins; 03-26-10 at 06:55 AM.

03-24-10, 07:07 PM	#1
Newbytoo Nub Join Date: Apr 2005 Posts: 4 Downloads: 22 Uploads: 0	Hi, ok I will play a few missions in OMV705 and make note of when and where the ctd's occur. Perhaps should of said but no problems with stock + UBM + RSRDC_SH15_V550. Thanks.

03-24-10, 10:19 PM	#3
Newbytoo Nub Join Date: Apr 2005 Posts: 4 Downloads: 22 Uploads: 0	ok I tried the Scapa Flow mission tonight (a bit of an historical favourite of mine ) I ran it without any time compression. At game time 8:35 pm, about 35 minutes in I get the standard Windows message = Silent Hunter IV has stopped working. MODS RSRDC_SH15_V550 OpsMonsun V705 OMV705 to V720 OMV720 Patch 2 OMEGU 300 OMEGU 300 Patch 5A Thanks

03-26-10, 06:11 AM	#7
alexradu89 Lieutenant Join Date: May 2009 Location: Romania Posts: 259 Downloads: 94 Uploads: 0	While having OM installed don't use the museum, as the creator stated it will CTD your game, sorry.