Print

[node21]

Sorry for not keeping this thread updated.

I've have a few setbacks in my normal routine.  Had a minor waterbed catastrophe that cost 2 days, and I've also been busy building a portrait photography studio in my basement.  Both of those things have distracted me from XM360 development.  But, it's coming along well.  I've been transferring save games between my 360s and it is doing the right thing with respect to the timestamp on the files (preserving them).  A few things are still left to do such as automatically updating the U/I when a transfer succeeds...figuring out what to do if a transfer fails...etc.  

One thing that I haven't figured out yet is what to do about content that is *pushed* to the remote 360.  It would be really nice if the next time you ran XM360 on *that* box that you didn't have to do a "rescan all"...but it gets there via a normal FTP push, so it doesn't really know that new content was added...  Maybe I'll add a custom ftp command to tell the remote session to "rescan all" and send that command after a successful push.  If I do that, I could probably also expose some U/I so that you can also remotely "rescan all" to update what is on the remote 360.  Oh well, just thinking out loud here.  A "rescan all" could take a while on a box with lots of storage, so a better custom command would have the ability to tell it specifically about the content that was just added.  *Sigh* that's more work...

-node

[jimmy2x2x]

Sorry to hear about the waterbed incident! Hope all is well now.

I have a couple of suggestions for your already great manager.

1) Delete orphaned content.

Imagine you delete a game from your drive, and are left with the content.  Would it be possible to list all orphaned content (title updates, dlc etc...) and allow the user to delete this content from within xm360?

2) Profile cleaner.

Cross reference gamelists against entries in players profile, generate a list then allow users to delete content. I think this could be useful to users who use a profile across legit and jtagged 360s.

Just a couple of ideas, good luck with the photography!

[node21]

QUOTE(jimmy2x2x @ Apr 19 2010, 06:54 AM)

Sorry to hear about the waterbed incident! Hope all is well now.

I have a couple of suggestions for your already great manager.

1) Delete orphaned content.

Imagine you delete a game from your drive, and are left with the content.  Would it be possible to list all orphaned content (title updates, dlc etc...) and allow the user to delete this content from within xm360?

2) Profile cleaner.

Cross reference gamelists against entries in players profile, generate a list then allow users to delete content. I think this could be useful to users who use a profile across legit and jtagged 360s.

Just a couple of ideas, good luck with the photography!

Waterbed incident is sorted...Although it cost over $7000.

Photography studio took up all of my time this weekend, so no progress on XM360.

Both of your suggestions probably aren't possible, but I appreciate them!

1) I can't delete orphaned content since I have no way of knowing if there is a game that you play all the time but haven't installed it to the hard drive...some people (like me!) still play some games off of DVD...

2) I can't read profiles.  Two issues there.  The first is that I don't know how.  The second is that if you are signed into a profile, I can't even read the file (it's locked?).  And another issue...there doesn't seem to be a way to "iterate" over a profile to list all of the games played by that profile.  This must be possible, since the NXE dash does it...but I haven't a clue how to do it.

-node

[jimmy2x2x]

QUOTE(node21 @ Apr 19 2010, 01:23 PM)

1) I can't delete orphaned content since I have no way of knowing if there is a game that you play all the time but haven't installed it to the hard drive...some people (like me!) still play some games off of DVD...

$7k wow....  Maybe you should have moved your bedroom to the basement and had the studio upstairs!

How about maybe generating a list of possible orphans, then allow the user to delete these on a singular basis?

[node21]

QUOTE(jimmy2x2x @ Apr 19 2010, 12:37 PM)

$7k wow....  Maybe you should have moved your bedroom to the basement and had the studio upstairs!

How about maybe generating a list of possible orphans, then allow the user to delete these on a singular basis?

Nah, it wasn't a $7k problem...it just turned into one.  First we needed a new mattress.  That led us to the furniture store.  We saw a bedroom set that we liked.  One thing led to another... Of course, it isn't finished yet... Now the "lamps don't match", and the window treatments are "just wrong."  *sigh*  All this because the kids jumped on the bed.  Anyway, this thread isn't about why you should never get married or have kids (although it's worth it...).

A list of possible orphans is do-able, I guess.  But since everything is already categorized (for the most part) by "title it's for", you could probably delete the content that you no longer care about pretty easily already.

-node

[modslave]

Node you sure got a lot goin on! I feel lazy in comparison

Prob a dumb question and apologies if its already covered but after choosing which titles to ignore if I reboot xm360 it doesn't remember my choices.

Normal?

Thanks for constant updates BTW

[node21]

QUOTE(modslave @ Apr 20 2010, 06:10 PM)

Prob a dumb question and apologies if its already covered but after choosing which titles to ignore if I reboot xm360 it doesn't remember my choices.

Not normal.  The location where the file gets written is configurable.  I think it defaults to the first usb device.  If you don't have one of those, it doesn't know where to put the file.  Configure it to put it somewhere on the hdd: and you should be fine.

[modslave]

QUOTE(node21 @ Apr 21 2010, 06:34 PM)

Not normal.  The location where the file gets written is configurable.  I think it defaults to the first usb device.  If you don't have one of those, it doesn't know where to put the file.  Configure it to put it somewhere on the hdd: and you should be fine.

Excellent node I've now custom paths for everything and what an easy fix!  Great not having to grab a usb to write the reports anymore.  Thanks again

On a side note that's barely worth a mention a number of times after opening XM360 I have selected collection management straight away and the program has crashed forcing a reboot.  As I said not every time - weird

[schoenof]

Back to the possible feature of XM360 automatically downloading the latest title updates...

If you look at what iso2god does, it extracts a titleId and also a mediaId....The mediaId can be used to query http://xbuc.tk/ website directly...and it appears that the mediaId already takes into account the region differences...

Is this possible to automate in XM360 or am I missing something?

Is this mediaId lost once it is a GoD or after ISO is extracted to files?

Thanks node...loving XM360

[node21]

QUOTE(modslave @ Apr 21 2010, 05:29 PM)

On a side note that's barely worth a mention a number of times after opening XM360 I have selected collection management straight away and the program has crashed forcing a reboot.  As I said not every time - weird

No, it's absolutely worth a mention.  It's happened to me to during development, and I always wondered why no one else noticed it...So, there's certainly something lurking in there that I'll have to spend some time looking for.  Might be impossible to find though, since it's so sporadic, and I don't have a devkit.

QUOTE(schoenof @ Apr 23 2010, 01:00 AM)

Back to the possible feature of XM360 automatically downloading the latest title updates...

If you look at what iso2god does, it extracts a titleId and also a mediaId....The mediaId can be used to query http://xbuc.tk/ website directly...and it appears that the mediaId already takes into account the region differences...

Is this possible to automate in XM360 or am I missing something?

Is this mediaId lost once it is a GoD or after ISO is extracted to files?

Thanks node...loving XM360

I really don't have a clue, as I haven't looked into this at all.  I really have to get back to XM360, as I've been concentrating on the photography stuff too much.  I'm beginning to realize that I've been holding back the release primarily due to unfinished code with respect to transferring game saves between consoles...but as I've learned in the past, most people don't care about the transfers...so I should probably just finish up what is there and get a version released.

-node

[krizalid]

How about a gamesave/con resigner?


You know, if you take your HDD or gamesaves to another HDD or console, some games don't like that (SF4, Dante's Inferno as example)


A way to sing Console ID and Device ID and Profile ID (folder it is in I guess) properly so we may use the game saves with ease.

Currently zouzz Hb Resigner v3 is good at doing this job, but it's in PC, you must do 1 file at the time, etc, etc.


I mean, run in console and manage all baby.


Just my two cents.

[madusmacus]

node...

Is this some sort of microsoft timeout - seems to happen at random palces in the scraping

C:\Develop\Perl>perl scrapeMS_DLC.pl  1>DLC_titles.csv
Could not find scrapeMS_DLC.xml in .\:. at scrapeMS_DLC.pl line 26

or is it because i used this strawberry thing :¬)

[madusmacus]

EDIT: 3rd go went through all the way :¬):¬)
must be a site timeout thing :¬)

[node21]

QUOTE(madusmacus @ Apr 24 2010, 10:56 AM)

node...

Is this some sort of microsoft timeout - seems to happen at random palces in the scraping

C:\Develop\Perl>perl scrapeMS_DLC.pl  1>DLC_titles.csv
Could not find scrapeMS_DLC.xml in .\:. at scrapeMS_DLC.pl line 26

or is it because i used this strawberry thing :¬)

Could be strawberry... why are you doing 1> DLC_titles.csv instead of just > DLC_titles.csv?

It does take a long time, but I've never seen an error like that... Can't imagine how it's coming up with "scrapeMS_DLC.xml" either....

[madusmacus]

strangely enough my batch file does not have 1>
when it runs it gets put in by cmd.exe

prolly something in the perlstartup.bat shell
vaugly remember 1> being unix standard out and 2> being standard error

in the old days :¬)