Xbox 360 Bug : Dunkirk Evacuation

There is a bug in BA:SWWII on the Xbox 360. After you sink the second ship, a cut scene kicks in and your plane changes to a bi-plane that is uncontrollable. The bi-plane goes over the city and then does circles until the mission times out. If anyone can figure out a way to get past this bug, please post the solution. This all happens right when I started having fun.

Carl the Cat

Thank you and excellent catch!

Our testing team has managed to reproduce this 100% and it will be slated for patching. The cause is that during the cut-scene which plays (and checkpoint save) after destroying the second Battleship, you were set on a course of certain death. This kamikaze crash landing into either the ground, water, or the third Battleship is carried out during the cut-scene and out of your control, and the checkpoint saves during your death throes.

There is an easy work-around though. First, you must completely re-start the mission. Second, shortly after launching the weapons needed to destroy the second Battleship, tilt your plane skyward to ensure no collisions for the next minute or two while the cut-scene plays.

He is right. The ability to get around the bug is easily doable. When you bomb the 2nd ship, bomb it from high altitude. While your bombs are dropping, pull back on the stick a little to get your nose above the horizon. The cut scene will play and the game will continue without hiccups. Thanks for the advice on getting around this problem.

Carl the Cat

i've been re doing this mission over and over again.. and i can't seem to pass the dumb plane looping over and over and over again.. i tried everything but can't seem to pass this level. after the second ship is bombed.. the plane cut scene comes in and that's all.. any help please?

I've played this game through twice and have never had this happen. Must be luck on my part. Glad to see you Polecat, I was under the impression that all of us 360 gamers were abandoned here.

Ive played this whole level 3 times now, doing exactly as described above and get the bug every time. What a **** game, and what a waste of money. Why advertise it as having 18 levels when it wont even play 2 ?!?

Maybe you shouldn't try so hard to recreate the glitch. As I have said, I have not encountered this glitch and have played through the game at least 2 time from begining to end.

All you have to do to see that it is possible is click on my gamer card and compare games.

Pretty simple really... Don't try to recreate the glitch and it's entirely possible that you won't glitch out.

Erm, I wasn't trying to recreate the glitch, I was trying to 'complete' the level. Note the use of speech marks. The glitch was preventing full completion of the level. Read and understand before posting in future eh?

quote:

doing exactly as described above and get the bug every time

You state in your own words that you are recreating the glitch. If you change your approach then you just may get past the level. If not, trade your game and move on, brightboy.

I state no such thing. What I did state was that I had done exactly as described, as it is supposed to AVOID the glitch.

If you dont understand the post, dont reply.

Easy boys!!! When I get home tonight, I will redo the level and tell you exactly what to do. I will have the results in this thread by 9pm EST. Anyway, after getting past Dunkirk Evacuation, I have had no other problems. Trust me when I tell you, getting past the bug and not giving up on the game is well worth it. This game is the best game I have played in quite a long time. I just wish someone will make a game that uses ultra-modern planes in war situations. A game that allows you to fly a stelth bomber, stealth fighter, SR-71 blackbird, YF-22 raptor, apache hellicopter, all other current military planes, and then make up some future military aircraft would be AWESOME.

Carl the Cat

Thanks Carl, but have managed to get around the problem now by resetting the cache on the Xbox.

Re your comments on a modern plane version, Over G is out at the end of May. Try the following link:

http://shop.gameplay.co.uk/webstore/productpage.asp?pro...=XT0091&title=over_g

Yeah, but what does that have to do with people that already own the game and need to get around the bug by using the game controls in a squence that allows them to continue the Dunkirk Evacuation mission? How can a current owner of BA:SWWII apply a patch that clears the cache on their xbox 360? Is there a way?

Sorry for the delay in posting this info. I did the Dunkirk Evacuation again and it worked fine for me. Bomb the small ship that is closest to shore. After that, from high altitude, bomb the second small ship from the other side. When flying your bombing line, fly over the small ship (while dropping your bombs) and then the big ship (not over the big ship, then small ship). Drop your bombs from high altitude and then immeidately point your nose up so all you see are clouds. This should get you past the bug and let you continue the mission. If it doesnt work, let me know and I will try to take screen shots, although that will be very painstaking.

well i was finally able to finish this level after like 3 tries... even if you bomb at high altitude and put your nose up sometimes that glitch occurs.. but luckily on my 3rd try or so it finally went to the correct cut scene... but yeah.. that nose up and high altitude works great... but if you don't get it the first try.. keep on trying it and eventually it will go to the right cut scene.

keep trying??? this is miserable. I restart the level do everything, drop dombs and put the plane in safe trajectory and all I get is the bi-plane. probably 5 times now :-(

Any more hints/fix for this?

Thanks!

Is it the bi-plane that flies over the city and then does circles until the mission times out or is it the bi-plane that drops the "special" torpedo on the big ship?

If the "times out" bi-plane, try from a higher altitude.

Also, check Xbox Live. I think there is a patch to download. You can access patches by puting the game in the DVD tray and then going to Xbox Live. I think all you need is a Silver Membership to get connected.

Let me know how it worked out for you.

Carl the Cat

Just for grins, posting another "me too". I have perhaps a little more light to shine on this bug.

It seems that once you've been caught, simply setting the plane on a safe course isn't good enough. I've read and fully understand what everyone here is saying, so just trust me when I say that's not sufficient to get past this.

After going through the level 5, 10, lost count at 12 times - I gave up and turned the unit off. The first time I ran this level after that (maybe a day later), I cleared the level. I did nothing different than any other time, except for the system reboot.

I was then able to repeat the mission and either recreate the bug or end victoriously.

However, after I turned the machine off, I found I could end it the wrong way, and again, restarting the mission was not sufficient to avoid the bug. Yes, even pointing the plane in a "safe" direction.

I think rebooting the machine plays a role in this, somehow. Despite the encouragement folks have been offering others, once you're caught in the loop, simply restarting the mission and setting the plane in a "safe" direction doesn't ensure a good ending. At least not 100% certain.

I don't even know how many times I've played this level now. Terrible program.

Hi all,
Just got the game and loved it for the first 20 minutes, until hitting this bug. PolecatXXX mentioned awhile back that this was slated for patching, so I'm hoping this is now fixed?

I don't have the capability to hook my xbox 360 up to the internet right now, but would gladly do so if it let me continue to enjoy the game.

Thanks!

*BTW I've tried the suggested "nose up" and "high altitude" workarounds, but after about 10 tries with no success I'm about at wits end.

I just encountered this problem myself. My XBox360 is connected to the internet, and no patch appears to be available as of yet.

I haven't tried the suggestions above yet to see if I can get around this bug - but good to know that I wasn't the only one to experience it, and that there seems to be a work around (although I'm surprised this wasn't caught in testing - seems to be happening to a lot of people).