Page 1 of 1

CTD

Posted: Thu Jun 27, 2013 11:59 pm
by Tzar007
I think I have an interesting crash for you here.

Load the attached save file. It's the First Clash at Veve scenario, D1 at 16h55. Just run it, and at 17h00 it will crash. It does that 100% of the time, I cannot go further than 17h00 without crashing.

That's with the latest 4.4.264 beta build, but it will also doing this with the previous build.

RE: CTD

Posted: Fri Jun 28, 2013 1:07 am
by BletchleyGeek
Acknowledged. I'll take a look at your save later today.

RE: CTD

Posted: Fri Jun 28, 2013 6:23 am
by BletchleyGeek
Tzar, I can confirm the crash. It has to do with Reinforcements entering the map. Is anyone else running across this?

In any case, the problem has been found and fixed for the next build.

EDIT: This has been lingering around for quite some time, and I'm surprised nobody before you with a BfG scenario has experienced it (and that includes myself).

RE: CTD

Posted: Fri Jun 28, 2013 10:30 am
by Tzar007
I'm glad you fixed it for the next build! If i restart the scenario from scratch, will I stumble across it again, or it is more random?

RE: CTD

Posted: Fri Jun 28, 2013 1:54 pm
by jimcarravall
ORIGINAL: Bletchley_Geek

Tzar, I can confirm the crash. It has to do with Reinforcements entering the map. Is anyone else running across this?

In any case, the problem has been found and fixed for the next build.

EDIT: This has been lingering around for quite some time, and I'm surprised nobody before you with a BfG scenario has experienced it (and that includes myself).

I get the CTD if I load the saved file.

I've done two quick run throughs with the Public Beta v4.4.264, first as Allies, and next as Axis. Issued no orders to the "human" player, and ran through with no orders delay setting.

Don't get the CTD.

I'm running Windows 7 on a Dell XPS 8300 Intel Core i5-2320 operating at 3 GhZ with 8 Gig of RAM using an AMD Radeon HD 6450 adaptor.

RE: CTD

Posted: Sun Jun 30, 2013 4:14 am
by BletchleyGeek
ORIGINAL: Tzar007

I'm glad you fixed it for the next build! If i restart the scenario from scratch, will I stumble across it again, or it is more random?

I can't say exactly: with a different organization (i.e. detachments, etc.) maybe it's not happening. If you can try to start from scratch to see if you run into it, it would be appreciated.