TU not working
Opened this issue · 40 comments
I used an older canary first to use TU but saves were not working, so i tried this version. However it doesnt even read my TU when launching the game, do you know why maybe? It's about diablo 3
Did you use stfs-writer?
Yeah I did, however when launching diablo 3 it's not the updated version, and it doesnt save either, if i quit game then i need to start all over. I'm not seeing any new folders and that's weird because it can save with the newer canary version but then I can't use TU
I mean new folders as in I deleted the xenia folder so it could remake itself but nothing's happening
I have had this issue with canary and it works fine with stfs-writer. stfs-writer does not work with canary saves. Make sure you are using stfs-writer by looking at your window bar. It should say "xenia (stfs-writer/"
Yeah thats what im using but after i enter the village it saves, but if i quit and restart it's all gone
Try making a new save to see if that fixes it.
Edit: Also take a screenshot of your content folder (Saves, Title Update).
these are the folders, i will delete them all and try again
Emoose said he was gonna upload 1.0.6 soon and that it should fix the title updates for Minecraft. It may work for Diablo 3. I don't own the game so I cannot check.
these are the folders, i will delete them all and try again
The saves are in 0000001 or something. They should NOT be extracted. Canary extracts them when being used. stfs-writer can't use canary saves.
What kind of files do they use? And are they just placed in 0000001?
Usually .bin and it is placed in 00000001.
Edit: Same as the 360.
I played some diablo 3 but there is not even a new folder created, not sure why
Don't delete the content folder, delete the save that is inside of /content/[GameID]/00000001/ . Also do you have a portable.txt in the same folder as the xenia.exe? If you do then your content folder is where your exe is.
I dont have a portable in my xenia folder, should I add it?
Show me your xenia folder (Where your exe is).
Im playing diablo right now and still no new files and this is how it looks
Add portable.txt then try it.
With portable it creates files. but no saves, and diablo said it saved already
Show me a video of your issue.
There is not much to record, but when i launch diablo 3 i can play normally, however once it says "checkpoint reached" and close the game after i need to start again like there are no saves, and as you see I dont have a content folder added
Re download Xenia (stfs-writer) and use that one. You may just need to update.
I already have the last version sadly
It updated last night. It is by the same 1.0.5
Yeah it's the on I have, i only downloaded it ~3 hours ago
Send me a video.
What would you like to see? Because the problem is that there is nothing happening in the background :p
I want to see the issue so I can find a fix.
Edit: I am using v1.0.6 (Which is the lastest one) and I have no issues.
I will send a video asap, but normally it creates a content folder but now it doesn't so if i launch the game again there are no saves. So im not sure of what i should make a video of, because there is not much to show you guys
Where did you download 1.0.6? Since the only version i see is a 1.0.5.zip
Nvm that was just the version of Minecraft.
stfs-writer-v1.07 fixes issues with TUs not applying to ISO/disc-originated games, and should hopefully fix the 35GB big-package bug too, maybe that'll help you out: https://github.com/emoose/xenia/releases/tag/mousehook-v1.13.4
Thanks man! Will definitely try it out once I'm back home!
It's indeed reading TU's now, but there are still no diablo 3 saves after reaching a checkpoint, do you know if it's an diablo related issue or something else? It's saving in normal canary tho
emoose, this is the xex and the TU you have requested
Title Update and XEX.zip
@GinjaNinja1998 hm ok, seems I was looking at wrong TU, the one you posted is for the 22AB4F7C media-ID, seems it patches version 10.0 to 10.1.
Looking at the XEX you posted, it's already been patched to 10.1 though, was that done by you? Xenia can't patch an XEX that's already been patched.
But if the x360 accepts that pre-patched XEX & also uses the TU, I guess it's skipping the actual XEXP patching since it's already patched, and just makes use of the files available in the TU ("TU__GearCamera.ini" "TU__GearPawn.ini" etc), maybe need to look into some way for Xenia to do the same.
@GinjaNinja1998 hm ok, seems I was looking at wrong TU, the one you posted is for the 22AB4F7C media-ID, seems it patches version 10.0 to 10.1.
Looking at the XEX you posted, it's already been patched to 10.1 though, was that done by you? Xenia can't patch an XEX that's already been patched.
But if the x360 accepts that pre-patched XEX & also uses the TU, I guess it's skipping the actual XEXP patching since it's already patched, and just makes use of the files available in the TU ("TU__GearCamera.ini" "TU__GearPawn.ini" etc), maybe need to look into some way for Xenia to do the same.
Yes I patched that particular XEX. I ran an unpatched xex with the TU in the documents folder, and ran a patched xex without the TU in the documents folder. Either way presented a crash when loading the game. For good measure, I even ran an unpatched god version with the TU in the documents folder too, and even that crashes.
Ah right, any chance you can upload the unpatched XEX somewhere too? I'll see if I can get it to trigger on my end, not sure if I'll be able to without the game files tho, but maybe I can just use files from a different gears 2 version.
If you can run xenia with log_level 3, then run the unpatched XEX with TU in documents, the xenia.log might have some more info about the crash inside as well, if you could post that too it might be useful.
Yes when I am off work I'll get that to you. that'll be in about 4ish hours or so
This should be the unpatched xex. Along with it is the log file
Well it looks like the TU is being applied at least, as you can see in that log "XEX patch applied successfully: base version: 10.0.0.0, new version: 10.0.1.0"
Game seems to run and try accessing a bunch of stuff from the TU, like "UPDATE:\TU__Xe-GearUI.ini", I'm guessing either the patched XEX, or something read from those TU UPDATE:\ files, is triggering some emu bug which makes it crash out.
If you try running the pre-patched XEX with the latest xenia-master (not stfs-writer/canary), does the game also crash or does it run fine? That might tell us if it's the XEX patch or the TU files that cause it, since master can't access UPDATE:\
Unfortunately cause of the crash doesn't seem to get logged, I'll have to try getting hold of Gears 2 and see if I can make that crash with a debugger, IIRC UE3 games can be pretty unstable in Xenia tho so not sure how likely a fix might be.
E: hmm, for me if I use 33FCE762 contents (from ISO), and drop in the 22AB4F7C XEX you uploaded + the 22AB4F7C TU, game seems to patch with the TU fine and lets me play, started campaign and all seemed to work fine, is there something you tried doing in-game that made it crash?
I don't have any saves or anything for it, just the TU, maybe try clearing Xenia/content/4D53082D folder and only copy the TU in there, and see if that helps?