The games becoming unplayable, in the last 1/2 hour I have restarted 6 times while playing the Zaria mission! Anyone else having problems? Could it be they are setting the minimum specs for our computers to high? :mad:
The games becoming unplayable, in the last 1/2 hour I have restarted 6 times while playing the Zaria mission! Anyone else having problems? Could it be they are setting the minimum specs for our computers to high? :mad:
It's actually a known issue that the team has been working on. Last I heard, they had a fix that will be going in.
For me the crashing started with a patch a few weeks ago.
I start up the program in safe mode now. I don't know if that'll help. It's not a perfect solution (can't load keybinds or parse if you start in safe mode) but it might be something.
The games becoming unplayable, in the last 1/2 hour I have restarted 6 times while playing the Zaria mission! Anyone else having problems? Could it be they are setting the minimum specs for our computers to high? :mad:
Yes. Yes. It's a mess. bendalek offer the best solution for that crashing mission.
Three threads were merged into one so the thread's info was pushed all over the place, but BD was kind enough to repeat himself at the end of page four.
For me the first crash always happens just after entering the large oval room ( circled in yellow ).
On way to get through the whole mess is...
1) Run into the room and Disable the 2nd of the Transporter Inhibitors
2) After the system crash, re-booted your game immediately and do not do the file verification step the launcher offers so that you can continue the mission nearest to point you just left.
3) This time, try to make a mad dash through the room then turn south to stop in the corridor away from the door. Don't move west, because that last group of Breen will cause another crash. Save them for last.
4) After you team has cleaned up the last of Breen in the oval room, you will need to run back in and Disable the 3rd and last of the Transporter Inhibitors. Your system may crash again to accomplish this, it's okay, just skip the file verification step again.
5) Once you are back in you should appear in the south corridor not the beam in location. Move to fight the last of the Breen, but back off the moment your team starts to fight them. If your system does not crash during the fight, it still might crash one more time when you move through the area to get to the room where your party beamed down. If it does...
6) Re-boot. Run into room. Watch as Defer get beamed up. Fight last big fight. "Beam up" (before any other crashes can happen).
It's actually a known issue that the team has been working on. Last I heard, they had a fix that will be going in.
FYI, it's not just the Zaria mission. In STFs and the like it occurs too: screen suddenly freezes, then game crashes. As I keep pressing that 'Send Report' button, someone should know about it by now.
This was happening to a friend last night so we started a proces of elimination, one of our processes was to play as many missions with Breen in as we could and try to find a common denominator, what we found was it was happening every single time the Breen fired off an aoe freeze, that seems to point towards a graphics issue with certain effects. Anyway long story short we tried a few things to stop it happening and eventually found that forcing the game into Direct3D 9ex completely got rid of the crashes for him.
just been having serial SNR's. tried exiting and going back in.
Can't get back in. here's the probable reason
tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 79 ms 97 ms 97 ms BigPond.BigPond [10.0.0.138]
2 23 ms 23 ms 23 ms 172.18.217.104
3 23 ms 24 ms 23 ms 172.18.74.173
4 23 ms 23 ms 23 ms bundle-ether4.wel-edge902.perth.telstra.net [203
.50.112.56]
5 23 ms 26 ms 25 ms bundle-ether7.wel-core3.perth.telstra.net [203.5
0.6.190]
6 57 ms 57 ms 58 ms bundle-ether7.fli-core1.adelaide.telstra.net [20
3.50.11.18]
7 68 ms 65 ms 65 ms bundle-ether9.win-core10.melbourne.telstra.net [
203.50.11.91]
8 79 ms 79 ms 80 ms bundle-ether12.ken-core10.sydney.telstra.net [20
3.50.11.122]
9 81 ms 78 ms 82 ms Bundle-ether18.pad-gw2.sydney.telstra.net [203.5
0.13.82]
10 78 ms 77 ms 77 ms bundle-ether1.sydp-core01.sydney.reach.com [203.
50.13.46]
11 218 ms 217 ms 217 ms i-0-3-0-6.paix-core01.bx.telstraglobal.net [202.
84.140.194]
12 215 ms 215 ms 214 ms i-0-4-0-6.paix02.bi.telstraglobal.net [202.40.14
9.58]
13 * * 260 ms te0-0-0-3.ccr21.sjc04.atlas.cogentco.com [154.54
.11.157]
14 261 ms 261 ms 261 ms be2015.ccr21.sfo01.atlas.cogentco.com [154.54.7.
173]
15 958 ms * 978 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30
.54]
16 311 ms * 310 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
86]
17 * 319 ms 319 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44
.86]
18 330 ms 329 ms 330 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25
.89]
19 333 ms 335 ms 334 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43
.9]
20 * 333 ms 333 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
21 334 ms 338 ms * 38.111.40.114
22
333 ms 333 ms *
xboxpatchserver.crypticstudios.com [208.95.185.4
1]
23 332 ms 333 ms 332 ms xboxpatchserver.crypticstudios.com [208.95.185.4
1]
Still getting the crash on loading screen. Nothing seems to fix it on my end. even the alter a file so it only uses DX 9.
Now after a crash and it asks me to supply a crash report it requests a ticket number. Which comes up as unknown and the crash report closes. Just to add insult to injury there.
Originally Posted by pwlaughingtrendy
Network engineers are not ship designers.
Nor should they be. Their ships would look weird.
Comments
I start up the program in safe mode now. I don't know if that'll help. It's not a perfect solution (can't load keybinds or parse if you start in safe mode) but it might be something.
Yes. Yes. It's a mess. bendalek offer the best solution for that crashing mission.
http://sto-forum.perfectworld.com/showthread.php?t=1456991
Three threads were merged into one so the thread's info was pushed all over the place, but BD was kind enough to repeat himself at the end of page four.
The gist is , you need to do a speed run. Here's a map of the problem mission.
For me the first crash always happens just after entering the large oval room ( circled in yellow ).
On way to get through the whole mess is...
1) Run into the room and Disable the 2nd of the Transporter Inhibitors
2) After the system crash, re-booted your game immediately and do not do the file verification step the launcher offers so that you can continue the mission nearest to point you just left.
3) This time, try to make a mad dash through the room then turn south to stop in the corridor away from the door. Don't move west, because that last group of Breen will cause another crash. Save them for last.
4) After you team has cleaned up the last of Breen in the oval room, you will need to run back in and Disable the 3rd and last of the Transporter Inhibitors. Your system may crash again to accomplish this, it's okay, just skip the file verification step again.
5) Once you are back in you should appear in the south corridor not the beam in location. Move to fight the last of the Breen, but back off the moment your team starts to fight them. If your system does not crash during the fight, it still might crash one more time when you move through the area to get to the room where your party beamed down. If it does...
6) Re-boot. Run into room. Watch as Defer get beamed up. Fight last big fight. "Beam up" (before any other crashes can happen).
Hope that helps.
FYI, it's not just the Zaria mission. In STFs and the like it occurs too: screen suddenly freezes, then game crashes. As I keep pressing that 'Send Report' button, someone should know about it by now.
Can't get back in. here's the probable reason
tracert patchserver.crypticstudios.com
Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:
1 79 ms 97 ms 97 ms BigPond.BigPond [10.0.0.138]
2 23 ms 23 ms 23 ms 172.18.217.104
3 23 ms 24 ms 23 ms 172.18.74.173
4 23 ms 23 ms 23 ms bundle-ether4.wel-edge902.perth.telstra.net [203
.50.112.56]
5 23 ms 26 ms 25 ms bundle-ether7.wel-core3.perth.telstra.net [203.5
0.6.190]
6 57 ms 57 ms 58 ms bundle-ether7.fli-core1.adelaide.telstra.net [20
3.50.11.18]
7 68 ms 65 ms 65 ms bundle-ether9.win-core10.melbourne.telstra.net [
203.50.11.91]
8 79 ms 79 ms 80 ms bundle-ether12.ken-core10.sydney.telstra.net [20
3.50.11.122]
9 81 ms 78 ms 82 ms Bundle-ether18.pad-gw2.sydney.telstra.net [203.5
0.13.82]
10 78 ms 77 ms 77 ms bundle-ether1.sydp-core01.sydney.reach.com [203.
50.13.46]
11 218 ms 217 ms 217 ms i-0-3-0-6.paix-core01.bx.telstraglobal.net [202.
84.140.194]
12 215 ms 215 ms 214 ms i-0-4-0-6.paix02.bi.telstraglobal.net [202.40.14
9.58]
13 * * 260 ms te0-0-0-3.ccr21.sjc04.atlas.cogentco.com [154.54
.11.157]
14 261 ms 261 ms 261 ms be2015.ccr21.sfo01.atlas.cogentco.com [154.54.7.
173]
15 958 ms * 978 ms be2132.ccr21.mci01.atlas.cogentco.com [154.54.30
.54]
16 311 ms * 310 ms be2156.ccr41.ord01.atlas.cogentco.com [154.54.6.
86]
17 * 319 ms 319 ms be2351.ccr21.cle04.atlas.cogentco.com [154.54.44
.86]
18 330 ms 329 ms 330 ms be2009.ccr21.alb02.atlas.cogentco.com [154.54.25
.89]
19 333 ms 335 ms 334 ms be2299.ccr21.bos01.atlas.cogentco.com [154.54.43
.9]
20 * 333 ms 333 ms te0-0-1-0.rcr11.b002133-1.bos01.atlas.cogentco.c
om [154.54.46.134]
21 334 ms 338 ms * 38.111.40.114
22
- 333 ms 333 ms *
xboxpatchserver.crypticstudios.com [208.95.185.41]
23 332 ms 333 ms 332 ms xboxpatchserver.crypticstudios.com [208.95.185.4
1]
Trace complete.
C:\Users\Felicity>
Get the Forums Enhancement Extension!
Now after a crash and it asks me to supply a crash report it requests a ticket number. Which comes up as unknown and the crash report closes. Just to add insult to injury there.
Originally Posted by pwlaughingtrendy
Network engineers are not ship designers.
Nor should they be. Their ships would look weird.