[REL] SH5 Starshells patch

[Mikemike47]

Originally Posted by TheDarkWraith

;Modified by TheDarkWraith
[DistressFlareWarship]
Effect2=Distress_Flare_Red, 75

[DistressFlareMerchant]
Effect2=Distress_Flare_Red, 75

@TDW
A fix is ";Effect2=Distress_Flare_Red, 75" for both entries.

Have you noticed the [TEC] Silent CTD Hunter thread? It discusses the distress flare red issue. Another issue in this thread talks about FX update 22 and .zon files.

[TheDarkWraith]

Originally Posted by Mikemike47

@TDW
A fix is ";Effect2=Distress_Flare_Red, 75" for both entries.

Have you noticed the [TEC] Silent CTD Hunter thread? It discusses the distress flare red issue. Another issue in this thread talks about FX update 22 and .zon files.

FX_Update does not cause CTDs. Users cause CTDs. I have been using FX Update ever since I made it and I have no CTDs.

Distress flares cause no problems on my system. Starshells also cause no issues on my system. If you are getting CTDs from the flares or starshells then it's not FX_Update or IRAI it's something else.

Try playing the game with just IRAI or FX_Update enabled and you'll see that the flares/starshells do not cause CTDs.

That Silent CTD Hunter thread is severely flawed in how you are determining CTDs. In order to properly chase down CTDs you need to be running the game in a debugger. Thus when an exception is thrown by the game the debugger will catch it and break at the code that is causing the exception. Then you begin the investigation as to why the exception is being thrown. That's the only way to properly diagnose CTDs. I recommend Olly Debug v2.01