Closed 514boy closed 11 years ago
Could you upload your profile so I can take a look at it?
I've emailed you the link and password.
It turns out that in one of the GPDs in your profile, 454108C0.gpd, the header was screwed up. It said that there were no free memory table entries, but that's actually impossible so Velocity didn't know what to do. I added checks so this will be fixed in the next update, but if you want it to work now just extract that GPD, and put a 01 at the address 0x17.
Thank you very much. I really appreciate you looking at it. Unfortunately, with 0x1 at 0x17, profile editor won't even open. I get "XDBF: Error reading setting entry. Invalid setting entry type."
I have not been able to use the profile editor function of Velocity, at all, on Windows 7 x64 running as admin. After ~1 second of opening my profile in the editor, Velocity crashes with:
"The instruction at 0x75b9c120 referenced memory at 0xfffffff4. The memory could not be read." or "The instruction at 0x75bcc120 referenced memory at 0xfffffff4. The memory could not be read."
If I let Windows handle the crash, I can see that the faulting module is msvcrt.dll. Exception Code: c0000005 Exception Offset: 0000c120 This PC that I'm using has the runtimes for VS 2008 x86 SP1, VS2010 x86 & x64, and VS2012 x86. I can use the profile that crashes Velocity on multiple dashboards, with no problems of editing avatars, or adding GPDs by loading games while logged in. On the PC side, every single 360 tool going back years are able to open and edit it, so I don't think it's some kind of corruption in my profile, which is currently at 4.50MB.