Difference between revisions of "Causes of CTDs"
no edit summary
imported>Odessa |
imported>Odessa |
||
| Line 4: | Line 4: | ||
===Debugging=== | ===Debugging=== | ||
The console command [[SetConsoleOuputFile|SCOF]] can be used in game, or via a script with [[Con_SCOF]] to write all console output to a text file in the fallout game directory. This is very useful as it allows you trace output to the point of CTD back in Windows. | The console command [[SetConsoleOuputFile|SCOF]] can be used in game, or via a script with [[Con_SCOF]] to write all console output to a text file in the fallout game directory. This is very useful as it allows you to trace output to the point of CTD back in Windows. | ||
<pre> | <pre> | ||
; within game console, type: | ; within game console, type: | ||
| Line 37: | Line 37: | ||
FirstRef.MarkForDelete | FirstRef.MarkForDelete | ||
</pre> | </pre> | ||
===Unexpected returns during immediate game start up=== | |||
It has been observed on a few occasions where scripts running in early game startup, or sometimes just on their first scan return <NULL> for an actor. With all the DLC's booting up, I've experienced such failures up to 10 seconds after gamestart, things like a female player returning zero for [[GetIsSex]] Female. | |||
===Invalid string formatting=== | ===Invalid string formatting=== | ||
| Line 60: | Line 63: | ||
===Nested function calls=== | ===Nested function calls=== | ||
If using the [[Script Compiler Override]], it is possible to nest multiple function calls on a single line, rather than use | If using the [[Script Compiler Override]], it is possible to nest multiple function calls on a single line, rather than use intermediary variables. Sometimes this causes a CTD, which is avoidable by using multiple lines. | ||
===Single line And/Or conditions=== | ===Single line And/Or conditions=== | ||