Post by: Xbox-Scene on January 30, 2010, 02:48:00 PM
| Team XeDev released a new version of XM360: Quote
Official Site: http://xedev.xbins.org Download: n/a (built with XDK) |
Post by: BulletMag on January 30, 2010, 03:10:00 PM
................ hope so
Post by: whelixw on January 30, 2010, 03:10:00 PM
Post by: darkdude on January 30, 2010, 03:39:00 PM
EDIT: nvm .. it is there now (IMG:style_emoticons/default/smile.gif)
This post has been edited by darkdude: Jan 30 2010, 11:41 PM
Post by: node21 on January 30, 2010, 06:19:00 PM
QUOTE(BulletMag @ Jan 30 2010, 05:10 PM) 
Does this mean it'll list RockBand and Guitar Hero DLC and tell you whats missing ???
................ hope so
It will list it, but it won't tell you what's missing...that's the next release.
Post by: minus5252 on January 30, 2010, 06:38:00 PM
Minus
Nevermind, I found it, it's under dev/stfs
This post has been edited by minus5252: Jan 31 2010, 02:39 AM
Post by: snakers2 on January 30, 2010, 06:43:00 PM
Post by: node21 on January 30, 2010, 07:44:00 PM
QUOTE(snakers2 @ Jan 30 2010, 08:43 PM)
does this work with map packs?
If map packs are DLC, then the answer is yes.
Post by: dufc1983 on January 30, 2010, 07:55:00 PM
This post has been edited by dufc1983: Jan 31 2010, 03:57 AM
Post by: node21 on January 31, 2010, 09:52:00 AM
QUOTE(dufc1983 @ Jan 30 2010, 09:55 PM)
i've noticed the dlc that i haven't run through yaris swap ie stuff like forza and left 4 dead dlc we have to use dlc patcher but this app im guessing is using yaris as a base hense it will still report the dlc locked so unlocking it within the app might cause problems im to scared to even try it when i know the dlc is working :-) just thought i'd put that idea forward to you otherwise ace work as always
No, xm360 no longer uses the basic "yaris swap". It has knowledge of the entire block of licenses.
If your DLC is showing up as "locked" in xm360, it just means that if you choose to "unlock", xm360 *will* be changing something. That something might not actually have any effect, but it is very unlikely to break anything. ( as it turns out, there is a slight bug in how it determines if it is "unlocked" or not, but unlocking it if it was wrong won't do any harm...explanation follows, I've already fixed it for the next release)
Once and for all, the algorithm for determining if your content is "unlocked" is as follows:
All 16 license slots must have either all zeros or all FFs in the first 8 bytes.
All 16 license slots that have all FFs must not have 4 zeros after them.
That is the correct algorithm. The bug in 0.6b does this:
All 16 license slots must have either all zeros or all FFs in the first 8 bytes.
All 16 license slots that have all FFs must have the value 0x00000001 after them.
The reason this isn't harmful is that the *UNLOCK* code does the following:
All 16 license slots must have either all zeros or all FFs in the first 8 bytes.
All 16 license slots that have all FFs must NOT have 4 zeros after them. If they do, the value 0x00000001 is written. Otherwise, the existing value is left there.
So, if you have some DLC that has:
FF FF FF FF FF FF FF FF 00 00 01 01
xm360 0.6b will say that it is locked (which is the bug). If you unlock it, it won't do anything.
Anyway, the short story is that it is safe to "unlock" with xm360, as the algorithm is sound.
Post by: snakers2 on January 31, 2010, 10:03:00 AM
QUOTE(node21 @ Jan 31 2010, 03:44 AM)
If map packs are DLC, then the answer is yes.
I guess you consider map packs not to be DLC because I do.
I have not found anything to allow me to use my WaW Map Packs on my JTAG yet.
Next time smartass, dont say anything unless youve tried it.
Post by: danked on January 31, 2010, 10:23:00 AM
Post by: node21 on January 31, 2010, 10:44:00 AM
QUOTE(snakers2 @ Jan 31 2010, 12:03 PM) 
I guess you consider map packs not to be DLC because I do.
I have not found anything to allow me to use my WaW Map Packs on my JTAG yet.
Next time smartass, dont say anything unless youve tried it.
It's comments like this that make me wonder why I bother spending so much time away from my family to write software for free, for other people's use.
Look, xm360 doesn't know anything about map packs, it doesn't know anything about rockband songs, it doesn't know anything about arcade games, it doesn't know anything about anything. It searches the hard drive for files, and those files have a "content Type" embedded in them. If "map packs" look like *ALL OTHER* DLC then they will work. if they don't, I don't know what to tell you...except for this... please forget that xm360 exists, and find some other software to use. I'll sleep better at night knowing that all of my hard work isn't being enjoyed by *you*.
Post by: hfmls on January 31, 2010, 12:23:00 PM
pls read that last post:
http://forums.xbox-scene.com/index.php?sho...amp;mode=linear
that is for you too.
***king asshole.
let the guy work, it's free for ***k sake!!
node21 keep up the good work!
Post by: snakers2 on January 31, 2010, 01:55:00 PM
QUOTE(node21 @ Jan 31 2010, 06:44 PM)
It's comments like this that make me wonder why I bother spending so much time away from my family to write software for free, for other people's use.
Look, xm360 doesn't know anything about map packs, it doesn't know anything about rockband songs, it doesn't know anything about arcade games, it doesn't know anything about anything. It searches the hard drive for files, and those files have a "content Type" embedded in them. If "map packs" look like *ALL OTHER* DLC then they will work. if they don't, I don't know what to tell you...except for this... please forget that xm360 exists, and find some other software to use. I'll sleep better at night knowing that all of my hard work isn't being enjoyed by *you*.
QUOTE(hfmls @ Jan 31 2010, 08:23 PM)
snakers2 idiot
pls read that last post:
http://forums.xbox-s...amp;mode=linear
that is for you too.
***king asshole.
let the guy work, it's free for ***k sake!!
node21 keep up the good work!
You two obviously COMPLETELY miss the point of my post. I was not criticizing XM360 in any way shape or form. I actually think its one of the most useful apps I use.
I simply asked a simple "can it do this question" and got a smart ass response that was WRONG.
If map packs are DLC, then it can unlock them. Well, Map Packs ARE DLC, but XM360 can not unlock them so my post was made directly to, and only to, the post that was incorrect and rude.
Im not hating on the product or work, but I was hating on only ONE specific post:
"If map packs are DLC, then the answer is yes."
They are, but it doesnt. Simple.
Post by: s7voogy on January 31, 2010, 04:10:00 PM
Post by: node21 on January 31, 2010, 05:39:00 PM
QUOTE(snakers2 @ Jan 31 2010, 03:55 PM)
You two obviously COMPLETELY miss the point of my post. I was not criticizing XM360 in any way shape or form. I actually think its one of the most useful apps I use.
I simply asked a simple "can it do this question" and got a smart ass response that was WRONG.
If map packs are DLC, then it can unlock them. Well, Map Packs ARE DLC, but XM360 can not unlock them so my post was made directly to, and only to, the post that was incorrect and rude.
Im not hating on the product or work, but I was hating on only ONE specific post:
"If map packs are DLC, then the answer is yes."
They are, but it doesnt. Simple.
Please go back and read my post. Then read it again. Because you obviously didn't understand it.
I'll spell it out a little differently for you. If your map packs can't be unlocked by xm360, then it isn't unlocking that they require.
Now, go back and read my post again. Especially the part about not using xm360. It makes me sad that you find my software "one of the most useful apps", yet you think I'm a smart-ass for giving you a very simple, truthful, correct answer.
Post by: snakers2 on January 31, 2010, 09:02:00 PM
QUOTE(node21 @ Jan 31 2010, 03:44 AM)
If map packs are DLC, then the answer is yes.
Please explain to me how the quote above could even be misconstrued to say " If your map packs can't be unlocked by xm360, then it isn't unlocking that they require."
Thanks!
Post by: Cybersnuff on February 01, 2010, 04:12:00 AM
. Thanks for it. I have a problem with the live Version of 0.6
When you click on collection managment the box freezes.
If I load the xex one with Xexmenu its all o.k.
Really looking forward to the next update
Thanks!Post by: Antman1 on February 01, 2010, 05:00:00 AM
QUOTE(snakers2 @ Jan 31 2010, 10:02 PM)
Please explain to me how the quote above could even be misconstrued to say " If your map packs can't be unlocked by xm360, then it isn't unlocking that they require."
Thanks!
WaW map packs (ALL of them) are working fine for me. I unlocked them ages ago using Yaris Swap 0.4, Sounds like something is wrong with your map packs. now you should leave it alone.
Thanks node21.
I do have a question for you though. XBLA Unlocker had issues for me about unlocking some content. it would not unlock the "Optional Media Update" and only Yaris swap worked for it. Then the Left 4 Dead Map packs would not work with XBLA Unlocker or Yaris Swap but I was able to make it work with DLC Patcher made by Fatum and it worked fine. Does this have the issues XBLA had? I know that if you patch the content with yaris swap first for Left 4 Dead then if it doesnt work try DLC Patcher and it will be broken. You have to use 1 or the other. so basically if this scans my content and tries to unlock anything and it doesnt work all of my content it tried to unlock will be broken. Here is the explaination I got from Fatum as to why it breaks it:
QUOTE(Fatum;1094614)
Content lock is simple.
Example:
We have DLC for "GAME". This dlc contains national flags. There are 3..5..6..100 flags inside. Everyone download this same dlc but you are from Germany and you have unlocked your flag. Your friend is form Canada and he has Canadian flag why?
Your license: xxxxxxxxxxxxxxxx Content: 00000001
Friend license: yyyyyyyyyyyyyyyy Content 00000002
Other license: zzzzzzzzzzzzzzzz Content 00000010
File is this same only Content bitmask is different
If license is changed to FFFFFFFFFFFFFFFF (hex) bitmask is set to any console/profile (i think that this is set by last parameter: flag)
What do yaris swap?
Overwrite License to FFFFFFFFFFFFFFFF (very good;) and License to 00000001 (good for arcde and 80% of dlc)
What do dlc patcher?
If Content is different than 00000000 (ex 01000000) it's not touched but license is changed for FFFFFFFFFFFFFFFF.
If Content is 00000000 license is changed to FF.... and Contnet to 00000001.
That's all
If something is patched by yaris you can't patch it again because you don't know right content. Only forza dlcs have files connected with content mask. DLC Patcher was fast dirty app for Forza
dufc1983
You can manually fix files using hex editor
File 62138F85356E99BD8C62911766E4B7A13471133345 change 4 bytes at offset 0x234 (00000001) to 00020001
File 31DFB2848A16CDE4B0FB475BE7123B0FFFF0842145 change 4 bytes at offset 0x234 (00000001) to 00010001
Example:
We have DLC for "GAME". This dlc contains national flags. There are 3..5..6..100 flags inside. Everyone download this same dlc but you are from Germany and you have unlocked your flag. Your friend is form Canada and he has Canadian flag why?
Your license: xxxxxxxxxxxxxxxx Content: 00000001
Friend license: yyyyyyyyyyyyyyyy Content 00000002
Other license: zzzzzzzzzzzzzzzz Content 00000010
File is this same only Content bitmask is different
If license is changed to FFFFFFFFFFFFFFFF (hex) bitmask is set to any console/profile (i think that this is set by last parameter: flag)
What do yaris swap?
Overwrite License to FFFFFFFFFFFFFFFF (very good;) and License to 00000001 (good for arcde and 80% of dlc)
What do dlc patcher?
If Content is different than 00000000 (ex 01000000) it's not touched but license is changed for FFFFFFFFFFFFFFFF.
If Content is 00000000 license is changed to FF.... and Contnet to 00000001.
That's all
If something is patched by yaris you can't patch it again because you don't know right content. Only forza dlcs have files connected with content mask. DLC Patcher was fast dirty app for Forza
dufc1983
You can manually fix files using hex editor
File 62138F85356E99BD8C62911766E4B7A13471133345 change 4 bytes at offset 0x234 (00000001) to 00020001
File 31DFB2848A16CDE4B0FB475BE7123B0FFFF0842145 change 4 bytes at offset 0x234 (00000001) to 00010001
Fatum worked with zouzzz and they rewrote Yaris swap to have better compatibility with this.
Post by: node21 on February 01, 2010, 06:45:00 AM
QUOTE(Cybersnuff @ Feb 1 2010, 06:12 AM)
I have a problem with the live Version of 0.6
I wasn't even aware that there *was* a live version of 0.6. Where did you get it? I didn't produce it, so I'm not sure what the problem could be.
QUOTE(Antman1 @ Feb 1 2010, 07:00 AM)
WaW map packs (ALL of them) are working fine for me.
Thanks for that report.
QUOTE(Antman1 @ Feb 1 2010, 07:00 AM)
Here is the explaination I got from Fatum as to why it breaks it:
Fatum worked with zouzzz and they rewrote Yaris swap to have better compatibility with this.
That explanation is exactly what I used to implement unlocking in version 0.6b. So, to turn that conversation into mine, broken english and all (IMG:style_emoticons/default/huh.gif)
QUOTE
What do xm360 version 0.6b?
If Content is different than 00000000 (ex 01000000) it's not touched but license is changed for FFFFFFFFFFFFFFFF.
If Content is 00000000 license is changed to FF.... and Contnet to 00000001.
The only difference (that might not be a difference, since it isn't spelled out anywhere) is that xm360 will not blindly write FFs over a license slot that is all zeros. My interpretation of a license slot with all zeros is that it isn't a real (used) license slot.
This post has been edited by node21: Feb 1 2010, 02:45 PM
Post by: Midnight Tboy on February 01, 2010, 08:54:00 AM
I used the Rock Band Downloadable Content Sorter to sort out my RB set before copying it over mind - as the folders on the pc were an absolute mess.
Are there any plans/found a way to have it show up missing DLC yet?
the RB DLC sorter is handy as a quick starting point for the RB files - but it obv relies on updates to have a new database of whats out held, and once I have them on the 360 there's no point keeping them on the pc too to resort each time. And of course, haven't started trying to organise my GH and Lips collections yet
Post by: node21 on February 01, 2010, 10:32:00 AM
It isn't looking good.
The scraper took about 20 minutes to run. It produces a huge file (huge is relative, it isn't gigs or anything). I think there were about 6500 items found.
I was worried that sucking that file into xm360 would take too long, but I wrote the code to do it and it sucks it in and stores it in an internal map (by the title the DLC is for) in well under 1 second, so that won't be an issue...
However, this is where I'm stuck (I think there is probably a solution for it, I just don't know how to proceed). As I've mentioned before, DLC doesn't have a unique identifier that I've been able to find. It has the title it is for, and the title of the DLC. That should be enough...but string (title) comparison isn't something that is terribly reliable...and here's why:
The web site that I'm scraping from uses some non-ascii characters (There's a more technical description for this, but I'm not knowledgeable on the subject to know what it is. :-) UTF-8? ) So, there are some foreign characters there (example, the tilda over the n in Viva Pinata, the copyright symbol after some titles). The perl program that I use to scrape the site doesn't know what to do with these, so I strip them out so I can produce a real ascii file. What I think probably needs to happen is for the scraping program to spit out a binary file that includes the wide, or unicode representation of those strings...because...
Ultimately, what I read out of the DLC once it is on the 360 is a wide or unicode representation of the same string...If we have *any* hope of clearly identifying titles as matches, then we need some way to have the identical strings in the first place.
If anyone has any clue how to proceed with this, I'm all ears.
I'm going to continue writing the code in xm360 to support this (because it will work fine for the majority of titles), but until someone can help me with this issue it won't be complete...
This post has been edited by node21: Feb 1 2010, 06:33 PM
Post by: StrictPuppet on February 01, 2010, 11:24:00 AM
I have a feature request..... when highlighting an individual title or dlc, would it be possible to show the path @ the bottom of the screen?
Awesome job node21 and Dstruktiv.
Post by: node21 on February 01, 2010, 11:29:00 AM
QUOTE(StrictPuppet @ Feb 1 2010, 01:24 PM)
I have a feature request..... when highlighting an individual title or dlc, would it be possible to show the path @ the bottom of the screen?
Yes, pretty simple, actually. I'll put it in for next version.
Post by: StrictPuppet on February 01, 2010, 11:32:00 AM
QUOTE(node21 @ Feb 1 2010, 10:29 AM)
Yes, pretty simple, actually. I'll put it in for next version.
Post by: nevernow on February 01, 2010, 02:28:00 PM
QUOTE(node21 @ Feb 1 2010, 06:32 PM)
[...]
The web site that I'm scraping from uses some non-ascii characters (There's a more technical description for this, but I'm not knowledgeable on the subject to know what it is. :-) UTF-8? ) So, there are some foreign characters there (example, the tilda over the n in Viva Pinata, the copyright symbol after some titles). The perl program that I use to scrape the site doesn't know what to do with these, so I strip them out so I can produce a real ascii file. What I think probably needs to happen is for the scraping program to spit out a binary file that includes the wide, or unicode representation of those strings...because...
[...]
Do you absolutely need the file produced from the scrape to be pure ASCII? Couldn't you use an UTF text file? Also, I'm not too familiar with perl, but I've read you can tell it to work in UTF with:
CODE
use utf8;
or like this:
CODE
$line = Encode::decode_utf8($line); # set the flag
Otherwise, what about using a language that's more UTF-friendly (and that I'm more familiar with (IMG:style_emoticons/default/tongue.gif)) like PHP? Would you send me your perl script to see if I can rewrite it?
All of this is obviously pointless if you do need the resulting file to be ASCII-only.
Post by: Cybersnuff on February 01, 2010, 04:13:00 PM
.
Post by: node21 on February 01, 2010, 05:29:00 PM
QUOTE(nevernow @ Feb 1 2010, 04:28 PM)
Do you absolutely need the file produced from the scrape to be pure ASCII? Couldn't you use an UTF text file? Also, I'm not too familiar with perl, but I've read you can tell it to work in UTF with:
CODE
use utf8;
or like this:
CODE
$line = Encode::decode_utf8($line); # set the flag
Otherwise, what about using a language that's more UTF-friendly (and that I'm more familiar with
) like PHP? Would you send me your perl script to see if I can rewrite it?All of this is obviously pointless if you do need the resulting file to be ASCII-only.
I don't need it to be ASCII...I just need a way to match the web to what is inside the DLC itself.
You basically already have the script...The one for XBLA content is already included with version 0.6b, and you can see that it is stripping the strings to be ASCII. The works fine for XBLA since the names aren't used for matching...but it won't work for DLC.
Thanks for the pointers to using utf from perl...but I'm not even sure that's what I'm dealing with...I suspect I'm going to have to learn a bit more about all of this. :-)
Post by: node21 on February 01, 2010, 06:05:00 PM
I take it all back.
I was doing the exact right thing in perl...and when I look in the scraped file, it appears perfectly.
The problem was when I wrote the code to then suck it in and put it in a map I tested it on the PC...in a console window...which doesn't know WTF to do with utf-8 encoded strings! So, I'm back on target...Now I have to figure out how to read in utf-8 strings from a file from C++ so that I can compare them to Unicode...but I'm sure I can figure that out.
Post by: nevernow on February 01, 2010, 06:34:00 PM
Post by: node21 on February 02, 2010, 07:25:00 AM
QUOTE(nevernow @ Feb 1 2010, 08:34 PM)
Sure you can! And I'm glad things are moving on. Give a shout if you think you need some kind of support.
Well, I might need samples of DLC that have these issues in both their own "title", and in the "title for". We'll see when I get closer.
Post by: dufc1983 on February 02, 2010, 07:39:00 AM
Post by: nevernow on February 02, 2010, 09:36:00 AM
QUOTE(node21 @ Feb 2 2010, 03:25 PM)
Well, I might need samples of DLC that have these issues in both their own "title", and in the "title for". We'll see when I get closer.
All right. Just let me know. Speaking of DLC anomalies, I just noticed that the Ninja Gaiden 2 Mission Mode DLC shows its title in both the "title" and the "title for" places.
QUOTE(dufc1983 @ Feb 2 2010, 03:39 PM)
anyway of supporting file names by game for title updates especially if u have alot in cache folder and odd occasion you want to delete one u need to remember its id but if it goes by name of game would be much better
I think you should request this feature to the authors of Xexmenu. I'd like it too, but it has nothing to do with XM360 (which already calls everything by name rather than by ID, by the way).
Post by: node21 on February 02, 2010, 11:15:00 AM
QUOTE(nevernow @ Feb 2 2010, 11:36 AM)
All right. Just let me know. Speaking of DLC anomalies, I just noticed that the Ninja Gaiden 2 Mission Mode DLC shows its title in both the "title" and the "title for" places.
I think you should request this feature to the authors of Xexmenu. I'd like it too, but it has nothing to do with XM360 (which already calls everything by name rather than by ID, by the way).
It's quite possible that Ninja Gaiden 2 DLC actually has it wrong inside the DLC (much like super contra XBLA). In that case, it will just be broken. I hope to eventually get this to a point where the "known" broken ones can be a special case in the code.
I haven't looked at title-updates at all yet. It's possible that there is some interesting information inside them...if that is the case, I wouldn't mind adding an ability to list what TUs you have installed in your cache folder...but after DLC collection management is done...
Post by: nevernow on February 02, 2010, 11:57:00 AM
QUOTE(node21 @ Feb 2 2010, 07:15 PM)
It's quite possible that Ninja Gaiden 2 DLC actually has it wrong inside the DLC (much like super contra XBLA). In that case, it will just be broken. I hope to eventually get this to a point where the "known" broken ones can be a special case in the code.
I have just checked and it does have a wrong name. They just wrote "Mission Mode" in every text field.
QUOTE(node21 @ Feb 2 2010, 07:15 PM)
I haven't looked at title-updates at all yet. It's possible that there is some interesting information inside them...if that is the case, I wouldn't mind adding an ability to list what TUs you have installed in your cache folder...but after DLC collection management is done...
Title updates to have some information so it would be possible to at least list the TU names alphabetically (hoping that they're not mostly named "TU 1"
). I replied somehow harshly to dufc1983 because I consider XM360 a read-only app (with the exception of unlocking, of course), not a file manager, and you can't delete stuff from there anyway. About Super Contra, I still do not understand the problem. Both files I have checked have the right ID at offset 0x360, by right I mean the same as xbla_titles.csv and xbox.com. Still, as of XMv0.6b, I see the game title as two rectangles, it shows up as locked and is not unlockable (but it's actually unlocked). Maybe it's got something to do with the conflict management/compatibility with other unlock apps you implemented. Time to go hex, I'll let you know what I find out.
Post by: nevernow on February 02, 2010, 03:25:00 PM
In XM360 0.5, Super Contra shows up as unlocked and with the correct title. Could you tell why it's different in 0.6b?
Post by: node21 on February 03, 2010, 07:01:00 AM
QUOTE(nevernow @ Feb 2 2010, 05:25 PM)
Ok, I promise I'll stop annoying you after this.
In XM360 0.5, Super Contra shows up as unlocked and with the correct title. Could you tell why it's different in 0.6b?
The scrapeMS.pl script changed slightly to *stop* including the 2nd version of super contra. The reason I had to stop including the second one was that it had the *exact same* titleID as another title. And, when launching Super Contra, it could erroneously launch the other title.
Have you tried launching it?
I'm ignoring super contra for now, like I've mentioned. There's something *wrong* with that title. (Or, at least some versions of it). I do hope to return to it and recognize it for what it is.
=-=-=-=
Status update on DLC Management.
I worked a little on this last night. I've managed to take the perl scraped UTF-8 encoded strings and display them beautifully inside XM360. No more wacky backslash characters. Japanese titles are listed in Japanese. What remains to be seen is if the actual DLC files contain the *identical* strings. Also, I bumped into at least one Rock Band title when the embedded title of the DLC had some garbled characters...so it wasn't able to match. This will likely be a bigger problem down the road.
I won't have much time to work on this until this weekend, but I hope to have something ready to release around that timeframe.
Post by: evans05 on February 03, 2010, 07:04:00 AM
Post by: nevernow on February 03, 2010, 10:13:00 AM
QUOTE(node21 @ Feb 3 2010, 03:01 PM)
The scrapeMS.pl script changed slightly to *stop* including the 2nd version of super contra. The reason I had to stop including the second one was that it had the *exact same* titleID as another title. And, when launching Super Contra, it could erroneously launch the other title.
Have you tried launching it?
I'm ignoring super contra for now, like I've mentioned. There's something *wrong* with that title. (Or, at least some versions of it). I do hope to return to it and recognize it for what it is.
It can be launched. You could say the issue is mainly cosmetic.
I know the scrape file has changed, I meant to ask if something (SC-specific) had changed in the app code, as well. Otherwise, running different versions with the same xbla_titles.csv file should produce the same behaviour, and I'm not sure this is the case.
Anyway, you're right, enough about Super Contra and its quirks, at least for now. DLC hell awaits!
Post by: node21 on February 03, 2010, 11:16:00 AM
QUOTE(nevernow @ Feb 3 2010, 12:13 PM)
It can be launched. You could say the issue is mainly cosmetic.
I know the scrape file has changed, I meant to ask if something (SC-specific) had changed in the app code, as well. Otherwise, running different versions with the same xbla_titles.csv file should produce the same behaviour, and I'm not sure this is the case.
Anyway, you're right, enough about Super Contra and its quirks, at least for now. DLC hell awaits!
Interesting that yours launches, but is marked as not found. I think this means that you don't happen to have the other title that has the same titleId? In my case, I have them both...so when I try to launch it, it goes searching for it in the internal datastructure, and happens to find the *other* one first...so, it launches the wrong title. Maybe you have them both and they just end up in the opposite order in the internal datastructure...that would explain it. But it would mean trying to launch the other title would launch super-contra :-)
I don't recall exactly what changed, but my recollection is that it was just the contents of xbla_titles.csv (because I re-ran the scraper after commenting out that one line...).
QUOTE(evans05 @ Feb 3 2010, 09:04 AM)
sorry to be an idiot ere, do i put this on my hard drive? or a sub drive? and how do i run it from xbr
I run it from a usb stick...but you could just as easily copy it to your internal HD, or elsewhere.
Launch it from any launcher (make sure the launcher isn't set to only show default.xex, since this is still named xm360.xex [or rename it yourself to default.xex]). I make a quicklaunch icon for mine, but I probably run it more than everyone else combined. :-)
Post by: nevernow on February 03, 2010, 02:44:00 PM
QUOTE(node21 @ Feb 3 2010, 07:16 PM)
Interesting that yours launches, but is marked as not found. I think this means that you don't happen to have the other title that has the same titleId? In my case, I have them both...so when I try to launch it, it goes searching for it in the internal datastructure, and happens to find the *other* one first...so, it launches the wrong title. Maybe you have them both and they just end up in the opposite order in the internal datastructure...that would explain it. But it would mean trying to launch the other title would launch super-contra :-)
I don't recall exactly what changed, but my recollection is that it was just the contents of xbla_titles.csv (because I re-ran the scraper after commenting out that one line...).
I run it from a usb stick...but you could just as easily copy it to your internal HD, or elsewhere.
Since you mentioned it...
I tried running v0.6b with 0.5 xbla_titles.csv and the result was "0.6b-like", so something is different in the code (of course I don't know if it's game-specific or not). In collection management, though, I had two entries for SC, one Have and one Missing. Removing the CC entry from the CSV file removed the Have line from collection management. Rocket Riot was there and unaffected, appearing unlocked and launchable.
Honestly I have never had any evidence of the ID collision between these two games you are talking about, and my impression is that in the app code you somehow considered the version with an ID ending with CC the "good" one. Could this be true? Maybe if all special handling of SC was removed, the problem would be fixed.
Post by: g.m.skel on February 03, 2010, 08:25:00 PM
anybody know where it's at?
edit:
nvm, found it.
This post has been edited by g.m.skel: Feb 4 2010, 04:27 AM
Post by: node21 on February 04, 2010, 07:13:00 AM
QUOTE(nevernow @ Feb 3 2010, 04:44 PM)
Maybe if all special handling of SC was removed, the problem would be fixed.
I can assure you that there is absolutely no special handling of *any* titles inside the xm360 source. It simply compares what is on your devices (hdd (internal/external), usb sticks, etc), to what is found in the xbla_titles.csv. Nothing more, nothing less. I hope that it always remains that way, and that special cases can be handled externally in the scraper, but I have my doubts.
Post by: nevernow on February 04, 2010, 10:51:00 AM
Could you tell me what you read in an XBLA game, other than the eight-digit ID at offset 360?
For example, does the title displayed in the list (not the management view) come from the CSV file or from the game? The unlock status is also wrong... I'm suspecting that some critical data are not in a standard position in the container (but then the game title in the list appears correctly in v0.5).
Post by: node21 on February 04, 2010, 11:28:00 AM
QUOTE(nevernow @ Feb 4 2010, 12:51 PM)
I see. That's a sensible approach, for sure. But this makes me understand the problem even less. :|
Could you tell me what you read in an XBLA game, other than the eight-digit ID at offset 360?
For example, does the title displayed in the list (not the management view) come from the CSV file or from the game? The unlock status is also wrong... I'm suspecting that some critical data are not in a standard position in the container (but then the game title in the list appears correctly in v0.5).
Sure, but this is from memory, since I don 't have the code in front of me. :-) Also, this is subject to change in version 0.7 as I'm re-organizing a bunch of stuff.
The first scene that comes up where you "Scan" hasn't even read the xbla_titles.csv file yet. So, everything you see there is coming from the file itself. While sucking that data in, it also pulls the titleID from offset 0x360. The determination of it's "locked" status is grabbed at the same time. I'd have to check the code, but there could *easily* be an issue there... There are now 2 functions in the codebase that check if a title is "unlocked" (XBLA, and DLC), and 2 functions in the codebase that "unlock" content (the old way, and the new way). I'm certain that I never call the old "unlock" code...but it's possible that I'm still using the old "XBLA" check for the lock status, and maybe that is somehow getting confused? My intention was to not use that code either (and only use the new check) but I might have forgotten to change it? Anyway, there's no harm in it aside from the visual indicator being wrong (which is wrong enough to warrant a fix in the next version, so I'll check this when I see the code again).
Once you are in the collection management screen, everything that you see comes from the xbla_titles.csv file. It determines if you "have" a title by searching for it (by titleID) in the datastructure that was filled out when you did the initial scan back on the first scene.
Post by: nevernow on February 04, 2010, 01:19:00 PM
Here's some more observations:
In v0.5, with the original CSV file with two SC entries, in the "unlock view", SC appears as unlocked, correct title, but can't be played (gray box suggesting to download the game again). The game is playable from NXE.
In the collection management view, it appears twice (as expected). The CC line of the CSV file results in a "Have" entry, the 1A line is "Missing".
This means that when you check the CSV against the datastructure, the datastructure does not have a 5841081A entry. I have verified that the CC line status comes from Rocket Riot, not Super Contra (actually obvious since you compare titleids).
But assuming that the entries from the datastructure come from the initial scan, this does not make much sense (to me, at least). Do you only ever read the titleid from offset 0x360?
In v0.6b, in the "unlock view", SC's title is garbage and status is locked, which leads me to think that you have changed the way the scan works (I remember at least something about the license bytes has changed).
My next question is: what exactly do you read in the initial scan? If you only read the titleid at offset 0x360, which is correct in SC, I guess the id would go into your datastructure and the management view would show the game as a "Have".
Post by: node21 on February 05, 2010, 07:07:00 AM
What's most troubling is that you are reporting the title as coming up as garbage in .06. That shouldn't happen, but is probably related to the oddness that I've noticed with seekg on the 360. Sometimes it doesn't go where you would expect it to go before doing a read. However, I would expect all titles to be screwed up then... *sigh*
During the initial scan, it does this:
CODE
getContentType(F); // is this XBLA, or DLC?
getTitleID(F); // read the titleID at offset 0x360
getWTitleString(F); // get the embedded Title at offset 0x411
if ContentType == ARCADE
check if it is unlocked (the old way, confirming my earlier suspicion that I got this part wrong)
if ContentType == DLC
getWTitleStringFor(F); // get the embedded Title that this DLC is "for" at offset 0x1691
check if it is unlocked (the right way)
There is no other place to read the titleid from...it is only in one place.
=-=-=-=-=-
And now, a minor update from a short coding session last night.
1) I'm having major issues with XUI controls (specifically text controls) not doing what I expect them to do, but that's another post...
2) I'm starting to believe that "Collection Management" for DLC will never really work. There are *TONS* of titles that are on my hard drive (and I don't have much DLC), that just do not match to what is scraped from the MS site. Whatever database drives the MarketPlace site seems to have no real correlation to what is actually written inside the DLC at offset 0x1691 and offset 0x411. In many cases, it seems to be related to the fact that the marketplace tags "cover" songs (not the original artist) with an asterisk (*). In other cases, I think something must be wrong with the comparison code since a lot of the missed titles have an apostrophe (') in them. But, there are some cases where they just don't match... I'm sticking with it, for now, to see if it will ultimately settle down to a small number of inconsistencies, but it isn't looking good for now... If I could just get past issue #1 I'd be able to really concentrate on this!
3) My 360 VGA cable arrived in the mail, so now I don't have to continually kick the entire family off of the main TV every 2 minutes to test a build. That was getting old for all of us. :-)
This post has been edited by node21: Feb 5 2010, 03:08 PM
Post by: nevernow on February 05, 2010, 03:14:00 PM
QUOTE(node21 @ Feb 5 2010, 03:07 PM)
Unfortunately, I can't remember exactly what changed between 05 and 06. But I remember a massive re-write...so anything could have happened.
What's most troubling is that you are reporting the title as coming up as garbage in .06. That shouldn't happen, but is probably related to the oddness that I've noticed with seekg on the 360. Sometimes it doesn't go where you would expect it to go before doing a read. However, I would expect all titles to be screwed up then... *sigh*
During the initial scan, it does this:
CODE
getContentType(F); // is this XBLA, or DLC?
getTitleID(F); // read the titleID at offset 0x360
getWTitleString(F); // get the embedded Title at offset 0x411
if ContentType == ARCADE
check if it is unlocked (the old way, confirming my earlier suspicion that I got this part wrong)
if ContentType == DLC
getWTitleStringFor(F); // get the embedded Title that this DLC is "for" at offset 0x1691
check if it is unlocked (the right way)
There is no other place to read the titleid from...it is only in one place.
- if you're using seekg with offsets, and something is indeed wrong (or at least non-standard) in SC, this might explain both the garbage title and the wrong unlock status detection. Or not?
- isn't the title string at offset 0x412? I mean, 411 is blank and 412 is where the fist character is.
- I have found that in SC, the hex sequence "584181A" appears two times; sequence "584108" four times in total. In other games, the full titleid sequence appears several times.
That's why I asked if you only ever read 0x360. Still can't figure why it won't match the CSV file. I am 100% that at 0x360, SC reads "5841081A".
QUOTE
2) I'm starting to believe that "Collection Management" for DLC will never really work. [...]
About this issue, what do you think of a complete change of approach? I mean, instead of relying on a scrape of xbox.com, using that as a basis and building a cooperative database where internal labels from DLC items and scrape results are correctly matched? Something like this:
DLC item parse:
- titleid 12345678
- title label "Rock Band - Guns And Roses - Sweet Child O' Mine"
xbox.com scrape:
- title name "Rock Band: Guns & Roses - Sweet Child Of Mine"
Not an exact match -> need for a manual association. Which - in theory - could happen either locally and individually, through a fuzzy search by XM360 showing similar matches, or cooperatively on a database/wiki website. What do you think?
Post by: node21 on February 05, 2010, 04:03:00 PM
Post by: nevernow on February 06, 2010, 06:05:00 AM
Post by: node21 on February 06, 2010, 11:26:00 AM
Version 0.7 -- Feb 6th, 2010
* Further massive rewrites :-)
* Automatically scan on launch, showing progress
* That ugly fixed-width font is gone, except where needed (the XBLA Collection Manager list)
* Support for DLC "Collection Management" - it's integrated into the "Show DLC" scene. Use LB and RB to change views. Note there are *lot's* of missed matches, mostly because what is *inside* the DLC files doesn't match what is on the marketplace web site. Because of this, there is also the ablity to show content which you have, but wasn't scraped from the web site.
* There is no support for exporting a DLC "report" yet. It will come, if there is interest.
* Like scraping for XBLA, there is an included scrapeMS_DLC.pl perl script. It takes a very long time to complete. You shouldn't need it often. XM360 will search for a file called DLC_titles.csv before using the one included in the package.
* There's still no button to generate the XBLA_report.txt. It does it any time you leave the XBLA Collection Management screen, so expect it to be a little slow.
If the beta goes well, it should be released this weekend...
Post by: Midnight Tboy on February 06, 2010, 12:25:00 PM
DLC Report would be great.
wonder by way of scraping the MS site for both DLC and XBLA....presumably it'll be better some point to perhaps set to download a scraped file weekly from a hosted site rather than wait to scrape it itself - XBLA takes quite a while to scrape when I've tried it - so can imaging the DLC one will take ages beyond that.
Post by: node21 on February 07, 2010, 06:06:00 AM
QUOTE(Midnight Tboy @ Feb 6 2010, 02:25 PM)
nice one thanks...I'll have a play about with it a bit later.
DLC Report would be great.
wonder by way of scraping the MS site for both DLC and XBLA....presumably it'll be better some point to perhaps set to download a scraped file weekly from a hosted site rather than wait to scrape it itself - XBLA takes quite a while to scrape when I've tried it - so can imaging the DLC one will take ages beyond that.
Actually, I don't think scraping the marketplace is going to be a feasible solution in the long run...as you can see in version 0.7beta, there are so many mismatches that it probably isn't worth the effort. What we need is our own database of DLC with the *actual* internal string. But, I have no place, and no inclination to host this data. If someone does, then XM360 count connect to it, and always have "live" data.
Post by: node21 on February 10, 2010, 03:03:00 PM
Version 0.7 -- Feb 10th, 2010
* Further massive rewrites :-)
* Automatically scan on launch, showing progress
* That ugly fixed-width font is gone, except where needed (the XBLA Collection Manager list)
* Support for DLC "Collection Management" - it's integrated into the "Show DLC" scene. Be sure to use LB and RB to change views. Note there are *lot's* of missed matches, mostly because what is *inside* the DLC files doesn't match what is on the marketplace web site. Because of this, there is also the ablity to show content which you have, but wasn't scraped from the web site.
* There is a button to write the DLC report. It takes a while, and only includes information on DLC for which you have at least one title.
* Like scraping for XBLA, there is an included scrapeMS_DLC.pl perl script. It takes a very long time to complete. You shouldn't need it often. XM360 will search for a file called DLC_titles.csv before using the one included in the package.
* There's a button to generate the XBLA_report.txt instead of doing it all the time.
* Entirely new support for Title Updates. Including the ability to Delete them.
* Support for deleteing XBLA titles.
* Support for deleteing DLC titles.
Post by: Midnight Tboy on February 10, 2010, 04:23:00 PM
The obv trouble with the DLC lists being so large, will be all the c**p that MS sell like sport logos, and individual clothes items......some games on the xbox.com marketplace have dozens and dozens of useless junk( NHL games for example)....spanning over a dozen web pages.
Hopefully in the future there'll be some way to filter out all the unwanted junk like that to only show things like addon packs, and things that actually add elemends to a game.
Post by: node21 on February 10, 2010, 05:27:00 PM
QUOTE(Midnight Tboy @ Feb 10 2010, 06:23 PM)
wicked stuff - got a bunch more DLC to copy over. Will have to take a look at the generated reports to see how it displays...to see if any use for working out the missing DLC and such like.
The obv trouble with the DLC lists being so large, will be all the c**p that MS sell like sport logos, and individual clothes items......some games on the xbox.com marketplace have dozens and dozens of useless junk( NHL games for example)....spanning over a dozen web pages.
Hopefully in the future there'll be some way to filter out all the unwanted junk like that to only show things like addon packs, and things that actually add elemends to a game.
The way it works now is it only spits out information on DLC for titles that you actually already have some DLC...In other words, if you don't have any of the DLC for an NHL game, none of it's DLC will show in your report.
I have an idea on how to improve this even though we aren't getting good title matches. Just like the ability to mark XBLA content as "Ignore", I think I'm going to add the ability to mark a DLC title as "Have". That way, even if the title doesn't match, you can tell it that you actually have the content. We'll see how that works out....
Post by: aubrey_76 on February 10, 2010, 05:51:00 PM
QUOTE(node21 @ Feb 10 2010, 05:03 PM)
version 0.7
Version 0.7 -- Feb 10th, 2010
* Further massive rewrites :-)
* Automatically scan on launch, showing progress
* That ugly fixed-width font is gone, except where needed (the XBLA Collection Manager list)
* Support for DLC "Collection Management" - it's integrated into the "Show DLC" scene. Be sure to use LB and RB to change views. Note there are *lot's* of missed matches, mostly because what is *inside* the DLC files doesn't match what is on the marketplace web site. Because of this, there is also the ablity to show content which you have, but wasn't scraped from the web site.
* There is a button to write the DLC report. It takes a while, and only includes information on DLC for which you have at least one title.
* Like scraping for XBLA, there is an included scrapeMS_DLC.pl perl script. It takes a very long time to complete. You shouldn't need it often. XM360 will search for a file called DLC_titles.csv before using the one included in the package.
* There's a button to generate the XBLA_report.txt instead of doing it all the time.
* Entirely new support for Title Updates. Including the ability to Delete them.
* Support for deleteing XBLA titles.
* Support for deleteing DLC titles.
I am not seeing v.07 in the "usual places" Has this been uploaded somewhere else or is it coming out later tonight. Thanks and cant wait to try this out.
Post by: node21 on February 10, 2010, 06:21:00 PM
QUOTE(aubrey_76 @ Feb 10 2010, 07:51 PM)
I am not seeing v.07 in the "usual places" Has this been uploaded somewhere else or is it coming out later tonight. Thanks and cant wait to try this out.
Not there yet. PM on the way.
Post by: aubrey_76 on February 10, 2010, 08:01:00 PM
QUOTE(node21 @ Feb 10 2010, 08:21 PM)
Not there yet. PM on the way.
Thank you very much. I like it....this app just gets better and better.....again thanks for all the hard work
Post by: coldcut on February 11, 2010, 03:09:00 AM
Post by: Spaceone on February 11, 2010, 06:20:00 AM
QUOTE(coldcut @ Feb 11 2010, 11:09 AM)
looks good would like to give it a go look in the usual places but cant seem to find this anywhere even the older release
http://xedev.xbins.o...ic.php?f=5&t=84
Post by: coldcut on February 11, 2010, 08:20:00 AM
QUOTE(Spaceone @ Feb 11 2010, 01:20 PM)
Thanks
Post by: node21 on February 11, 2010, 10:00:00 AM
Version 0.8 -- Feb 11th, 2010
* Added support for a "backup" Cache folder. (hdd:\Cache2) Ability to see where your Title Updates are, and to restore from Cache2.
* Sorted initial screen by title.
* Added some special handling for Super Contra.
Post by: juggahax0r on March 29, 2010, 01:45:00 AM
This post has been edited by juggahax0r: Mar 29 2010, 09:19 AM