[Rodo]

yes that's it

Spoiler:

first lost ftl.
then everything else.

on my second playthrough I get the dialogue in a different order, if that's intentional then there's no error.

[Ace]

What hull percent does the Theseus start the mission with?

The event trigger has been fixed, but I want to know if you're starting with very low hull % or there's some other issue.

[karajorma]

http://www.hard-light.net/forums/index.php?topic=82014

[Rodo]

starts on 75%, but I'm guessing it's fixed on the patch. Will test now.

Edit: It's fixed, dialogue plays ok and as far as I could get in the mission it's not crashing anymore. There was a minute right after the arrival of the third baseship when it all went downhill and FPS dropped to 0 for like two seconds (previously this happened and then the mission would crash sometimes, some others it did not), then it all came back to normal.

I have to go, will make two more runs tonight to see if the mission crashes.

[VPR]

Following on from my post in the patch release thread it's now crashing all the time in M6 at the same point for me as it was pre-patch even after restarting the game in-between attempts. I'll try from a new pilot file first and restart the campaign.

I can't generate a debug log for the mission in-game either as it won't load the mission if I try to go to it from the main menu briefing using the debug exe. I've attached screenshots of the two errors before it crashes and a debug.log (third attachment shows the exit code in the launcher if that's any use?).

[attachment removed and sold on the black market]

[Swifty]

those are just warnings, not errors. Just click No for those so you can actually get into the mission.

[VPR]

The game crashes out after the second warning when I click No.

I've tried using the old collisions setting but this doesn't help. Unless there's anything else I can try first I'll reinstall the whole game from scratch as so far no one else seems to be having issues after the patch.

[Solver]

I also just crashed post-patch in M6, during the dialogue line "we're going to give those toasters a bloody nose", and then crash.

[borizz]

Yeah, I'm also still crashing after the patch. If you want I could probably get you a debug log.

[Swifty]

Debug log would help a lot.

[borizz]

It's getting late and I'm getting frustrated, so I'll probably do this tomorrow. I keep getting killed by

Spoiler:

nuke shockwaves from theseus.

I also had to dial down difficulty to Very Easy because it's not fun at all playing at 12 FPS.

[MikeRoz]

Patch appears to have rectified my crashes. If it helps, I was (and still am) using the old collision code and I have plenty of RAM.

[Swifty]

If the game works for you using old collision code, it would be preferable if you can use the new collision code so we can start finding bugs from that. Chances are if the game was crashing for you even with the old collision code, then it's likely the new collision code wasn't the problem.

[Rodo]

Just played the mission again with the new collision (never used the old so far) and the mission crashed on the first attempt.

I'll try the Debug now.
Edit: no crash with debug, but It got pretty close to that (I presume from the massive lag) when the third baseship arrived and started shooting the civi's

[Nemesis6]

No luck for me with the new patch. Gonna see if I can get  myself to play with the debug version.

[Da-Fort]

The patch fixed the mission for me. Three for three. I also noticed the dialogue plays correctly now.

[NoSpin]

Hey guys, first thing....AMAZING GAME!

Second, even after the patch I am still crashing on Mission 6. Usually I would be able to play the mission fine, but after I died once I would repeatedly crash each subsequent time. However earlier today I crashed on my first run, so I'm not sure if that trend is correct.

I believe I have the log of a crash I had while in debug mode, but I will continue testing and post more logs later today (hopefully).

System specs- Intel i7, Nvidia 540M, Windows 7 64bit

Code: [Select]

7478: Could not create debris, no more slots left
Frame 7478: Could not create debris, no more slots left
Frame 7478: Could not create debris, no more slots left
Frame 7478: Could not create debris, no more slots left
Frame 7478: Could not create debris, no more slots left
Frame 10235: Could not create debris, no more slots left
Frame 10673: Could not create debris, no more slots left
Frame 10696: Could not create debris, no more slots left
Frame 10696: Could not create debris, no more slots left
Frame 10696: Could not create debris, no more slots left
Frame 10696: Could not create debris, no more slots left
Frame 10696: Could not create debris, no more slots left
Frame 10696: Could not create debris, no more slots left
ASSERTION: "snd->info.n_channels == 1" at sound.cpp:666
 Sound should be mono! Sound file: Engines_AB_Col_Viper_MK7.ogg
Int3(): From d:\c++\freespace\diaspora build\code\globalincs\windebug.cpp at line 1034


[Anjelus]

I'm crashing too I'm afraid, probably for the same reason everyone else is. This last go it happened right after the first mention of the Raptors.

Windows 7
i5-2500k @ 3.30Ghz
8GB RAM
GTX 560 Ti

[Ace]

Debris slots? Could we be hitting a debris object count limit?

[crizza]

Applied patch, created new pilot file, deleted the old and now my... controls, key bindings etc are completly screwed...
like not dumping countermeasures on X, gliding no longer on W and so on...*sigh*