7 replies to this topic

[BellatorMonk]

So I CTD fairly often 1 out 5 matches when in an 8 man, 1 out 10 in a 4 man and 1 out 10-20 solo.

So far as I can tell every CTD is with a mech using modules. Going to start driving w/o modules to confirm.

[Banditman]

Totally empirical evidence here, but, you know what? Since I took the (disappointing) Advanced Zoom module out of my mech, I can't remember a flat CTD. I still CTD when I forget to shut off FRAPs movie capture before exiting a match, but that's not new.

I'll try to pay more attention.

[Snib]

I CTD more often with certain mechs than with others, but it's irrelevant whether they got modules or not (actually my COM-2D is the only mech I have with a module and I never CTD on that one).

[BLUPRNT]

Hmmmm! Now you got me wondering. CTD is new to me lately as well as playing with modules. Do some investigating tonight.

[Elder Thorn]

i bought my first Module today after open beta start and i had several crashes before

[Gradrock]

I run a comm 2d myself and this mech for whatever reason CTDs same as yours 1 in5 easily. Other mechs not so much1 in 10ish maybe, and it has happened on every map. So I also thought well maybe its the modules, so took those off no help, well then maybe its the weapon load out, took those off, nope still the same, tried changing armor points, engines and heatsinks. Still the issue persists.

[Glucose]

I still think these CTDs are related to the HUD becoming all mangled. There seems to be some sort of memory corruption / race condition going on during the initialization of each map. I've noticed more CTDs if something has gone funky.

The advanced zoom module *could* be another shader resource that has to be loaded at initialization, which would change the rate at which things initialize and possibly make the problem worse?

*theories*

[knight-of-ni]

Been running sensor modules in my three Jenners and have never had a CTD. I guess I'm fortunate.