Black Screen on startup
#626
Posté 21 mars 2012 - 05:43
Maybe one of you could get in touch with that Ryan fellow from the other thread, seems like you have the problem nailed down.
#627
Posté 21 mars 2012 - 05:53
Resante wrote...
*Sorry my formatting is jacked up, I typed up part of this in Notepad to avoid losing it.*Word_Bearer wrote...
Its a problem with EA and the Gamertags. No home remedies. Sorry.
Muhaha but there IS a home remedy! I just figured out what the problem is.
As we have all suspected, it is related to the gamertag and a file that ME3
creates to go along with it. Each profile has a directory on whatever your
storage media is (hdd, usb, etc.) Your profile has multiple subdirectories
with saves, and also a location with a .gpd files containing info on all of
the games you have played. This ME3 .gpd file is the problem. When you
redownload your profile it redownloads all of the .gpd files from MS.
1) I removed my hdd, downloaded my profile to internal memory and copied the
profile to a USB stick. I tried loading ME3 after this and got the frozen black screen. On to step 2.
2) Moved USB stick to my pc to look at the files. (If you know how to use USB Xtaf Xplorer I'd suggest using it to extract the profile and make a backup of it before messing around on the stick.)
2) Now, I wasn't able to find a way to get to the contents of this file
directly. You will need a profile editor like the Horizon tool (google it.)
3) Open Horizon, go to Tools > Device Explorer. It should find your flash drive. Expand Gamer Profiles, select your profile, then click the little gear to the upper right of the window (Open in Package Manager).
4) This will show your profile details. Do NOT change anything here. Click contents to display all of the package files specific to the profile. We're looking for the Mass Effect 3 package, which is 4541095D.gpd. Right click this, extract, and back it up somewhere. Now right click it and delete it.
5) Click Save, Rehash, and Resign. Skipping this may result in a corrupt profile. YOu'll get a confirmation once the profile is saved.
6) Place flash drive back in Xbox, REMOVE NETWORK CABLE, and power up. You should be able to play ME3 with your profile. It will create a new package file on your profile, and if you move your save from your HDD to the flash drive you can even load your gamesaves.
7) Enjoy Mass Effect 3 single player.
***Problems***
I connected to Xbox Live and the game downloaded the 4 MB update. I then got the message that I had played the game on a different console and it immediately locked up. I believe BW checks the contents of the .gpd file or attempts to write values to it right after the omni-tool scene, because after the first lockup I deleted the .gpd file again, disconnected from the Internet and was able to play again (game creates a new .gpd). I connected the ethernet cable, rebooted the xbox, and got the dreaded black screen right after the omni-tool scene. Unfortunately this means MP is still out of the question right now. I will send all of this info to Bioware, I like to hope that if I figured this out in one night they certainly already had it figured out and are working on finding out what their game is doing to this .gpd file. I will keep investigating myself. If anyone else wants to attempt this, let us know if you're successful.
I forwarded this to Kenny, thanks for posting this Resante.
#628
Posté 21 mars 2012 - 05:57
it's what I miss about having a gaming pc, great guys that get stuff fixed before the companies even look at it.
#629
Posté 21 mars 2012 - 06:08
#630
Posté 21 mars 2012 - 06:09
MalSkyblade wrote...
I've got this same issue, but I'm afraid of Microsoft banning my Live account if they catch me altering my profile save. It just seems like something they would do, and then I might never get my profile back. I guess I'll just not play till BioWare fixes.
Oh yah that's not a bad point. MS are bastards like that. I'm not mucking around with it myself....but bro just basically showed the QA team what the problem is so +1000
#631
Posté 21 mars 2012 - 06:17
#632
Posté 21 mars 2012 - 06:50
I'd be fine with that, as long as they say, hey patch in 2 weeks.
Well.....we'll see if they can take this ball and run with it now
#633
Posté 21 mars 2012 - 07:22
1 call bioware have them edit your profile saved to origin to erase me3 .gpd.
2. Call Microsoft and have them edit your profile on their server to delete me3 .gpd
3. Erase and recover gamertag with me3 .gpd deleted
4. Put ME3 in should make a brand new .gpd w/o any corruption thus allowing it to work as intended
You would probably lose all saves,achievements and multiplayer stats but should work I would think
#634
Posté 21 mars 2012 - 07:25
Godof360 wrote...
This is what I'm thinking but I don't know how possible it is.
1 call bioware have them edit your profile saved to origin to erase me3 .gpd.
2. Call Microsoft and have them edit your profile on their server to delete me3 .gpd
3. Erase and recover gamertag with me3 .gpd deleted
4. Put ME3 in should make a brand new .gpd w/o any corruption thus allowing it to work as intended
You would probably lose all saves,achievements and multiplayer stats but should work I would think
Except that it doesn't fix the under lying issue that caused this. Allowing it to possibly happen again. This needs to be fixed at the source, whatever that may be.
#635
Posté 21 mars 2012 - 07:25
#636
Posté 21 mars 2012 - 07:27
#637
Posté 21 mars 2012 - 07:51
Godof360 wrote...
Maybe only need bioware to edit your profile on origin to erase .gpd thus essentially like you never played me3 before thus when u load game it would imprint a new non corrupt .gpd on to your profile
Hey doesn't my Non-tech ass suggest this like 7 days ago.
And I've no idea what I'm talking about.
#638
Posté 21 mars 2012 - 08:43
nickel25 wrote...
This crap started happening to me a day after I got the game. Wrote an article to try and spread the word.www.screwattack.com/news/mass-effect-3-has-game-breaking-bug-xbox
Good to know. Nice to see a SA writer coming here to spread the word. The video is getting more hits as a result.
#639
Posté 21 mars 2012 - 10:08
#640
Posté 21 mars 2012 - 12:03
Sit down, have a drink, it may be a WHILE. I'm thinking about punching someone in the face while they sit in their office, using their computer, and try to speed things up...
#641
Posté 21 mars 2012 - 12:18
Hope we hear something good today on the issue at hand
#642
Posté 21 mars 2012 - 12:27
Btw. Godof, the Black screen vid is yours right? The one being spread around now? Cuz I did leave a comment and you replied to it. If thats you lol.
#643
Posté 21 mars 2012 - 12:30
#644
Posté 21 mars 2012 - 12:35
Is there a way to increase war readiness if you dont have iOS and dont play multiplayer?
#645
Posté 21 mars 2012 - 12:47
#646
Posté 21 mars 2012 - 02:02
Godof360 wrote...
Maybe only need bioware to edit your profile on origin to erase .gpd thus essentially like you never played me3 before thus when u load game it would imprint a new non corrupt .gpd on to your profile
The thing is, who knows at what other points in the game the .gpd gets modified. From what I can tell it could get changed by a lot of things. Getting an achievement, saving your game, going online... only BW knows for sure. When my game first froze, it was at an autosave point at the end of a cutscene near the end of the game. I was able to load that save after moving it to my flash drive during this testing.
I was tired when I did this last night so I don't remember if I did this particular step (and am not in a position to try it right now) - has anyone tried redownloading the profile to a new source without ME3 in the drive, disconnecting from Xbox Live, then playing ME3? I know I was online when I first tried playing it after downloading the profile.
#647
Posté 21 mars 2012 - 02:04
#648
Posté 21 mars 2012 - 02:18
Resante wrote...
Godof360 wrote...
Maybe only need bioware to edit your profile on origin to erase .gpd thus essentially like you never played me3 before thus when u load game it would imprint a new non corrupt .gpd on to your profile
The thing is, who knows at what other points in the game the .gpd gets modified. From what I can tell it could get changed by a lot of things. Getting an achievement, saving your game, going online... only BW knows for sure. When my game first froze, it was at an autosave point at the end of a cutscene near the end of the game. I was able to load that save after moving it to my flash drive during this testing.
I was tired when I did this last night so I don't remember if I did this particular step (and am not in a position to try it right now) - has anyone tried redownloading the profile to a new source without ME3 in the drive, disconnecting from Xbox Live, then playing ME3? I know I was online when I first tried playing it after downloading the profile.
I'm not a tech person really. But what worries me is that like when you get this in a corrupted save....they always say the fix is to delete the save.
#649
Posté 21 mars 2012 - 02:34
In this case none of my gamesaves were affected at all. I was able to load the last autosave and start exactly where I left off. If someone else wants to test this and verify your saves workDemGeth wrote...
I'm not a tech person really. But what worries me is that like when you get this in a corrupted save....they always say the fix is to delete the save.
#650
Posté 21 mars 2012 - 02:40
DemGeth wrote...
I'm not a tech person really. But what worries me is that like when you get this in a corrupted save....they always say the fix is to delete the save.
Well I think resante proved the saved game is fine, as you can play single player ok.
The issue is clearly status information that is added on top. ME3 is now multiplayer for the first time, AND its free with paid transactions so its important for bioware to have some kind of status info to track purchases, points etc AND make it difficult for people to "trick" eg adding unlimited credits to buy expensive packs in game currency vs microsoft points.
if they encrypt the file (which is likely), its possible for the file to be corrupted by just a single bit wrong. This could easily happen if the "update file" process is interrupted mid process eg from a freeze. if the devs didnt make the "modify file" atomic (ie a commit or rollback entire change) a freeze could easily corrupt the file by only overwriting a subset of the entire file for example.





Retour en haut




