Keyser
-
Content Count
216 -
Joined
-
Last visited
-
Days Won
16
Posts posted by Keyser
-
-
Yes, that should work. That's the way I use to do.Consider just 2 things:- make sure that the folder with the updated files does not contain a Data folder (subfolder Databases contains your db files, subfolder GameData contains the artworks)- make sure to use a skin compatible to the new version. You can change to default skin first before updating. The new default skin will overwrite the old one. Sent from my GT-I9100 using Tapatalk 2
-
It was possible until rev483. But then something changed and I did not had the time to check it out. I'm afraid it'll not be possible for now. Maybe you can hack the xex file - or whichever file contains the strings - manually.
I guess a new F3 revision will come out shortly with the new LiNK logo, so maybe I'll find some time when it comes out.
-
1
-
-
It should be possible. The only difference when cloning an install is that your Scanpaths need to be edited.Thats exactly what this app does: http://www.realmodscene.com/index.php?/topic/1388-f3-scanpaths-importer/?view=getnewpost. As long as your cloning process involves just one device (with scanpaths). You can create a master scanpaths file to use for all installs.Gesendet von meinem GT-I9100 mit Tapatalk 2
-
Congrats ickna11
-
Just use GaDaBaMa. I have my F3 on a USB stick and use it to boot my console. But you can also use a USB stick to transfer F3 data to your Xbox HDD.
-
Why would you do a CLEAR DATA if you can use the link provided above to move the game to another section?
And even if you would need to do a CLEAR DATA there is a way of doing it without losing any covers/images/descriptions. Check the tutorials section.
-
Just use this software http://www.realmodscene.com/index.php?/topic/1463-f3-contentitems-editor/?view=getnewpost to move it bsck to another section. Gesendet von meinem GT-I9100 mit Tapatalk 2
-
If you use Unicode you must use a unicode font as well. Like Arial unicode. Copy it to f3/fonts as Arial.ttf. somewhere in this topic you'll find more details. Skin.xml must be ansi. Do not use unicode chars there. Gesendet von meinem GT-I9100 mit Tapatalk 2
-
1
-
-
I did a skin in hungarian some while ago and I used Unicode. Give it a try.Gesendet von meinem GT-I9100 mit Tapatalk 2
-
This little app is intended for all those who struggle with their ContentItems table.
How-To
For example:
Use A ) when you deleted a game outside F3 and it still appears in your collection (database)
Use B ) when you moved a game to the Hidden section or to Others and now you are unable to move it back to where it belongs
Behind the scenes - SQLs
A ) Does a DELETE FROM ContentItems where ContentItemsID = textbox
Deletes the GameData folder with all the pictures (.assets file)
B ) Does a UPDATE ContentItems SET ContentItemTab = combobox where ContentItemsID = textbox
Credits
Keyser (DEV)
SQLite (sqlite.exe)
TeamFSD
Source files
It's a simple HTA file. The contents of the executable will be extracted and placed somewhere under %appdata% I guess. If you need to change the code search for ContentItems.hta.
-
2
-
-
Try with another CharSet. One that fits your language
-
You can use Gadabama. Let F3 manage your TU. Don't save your TU in your cache folder nor in your Content folder.You can download the latest TU for all games with one click. And you can delete obsolete TUs with one click as well. Can't get any easier than that.Gesendet von meinem GT-I9100 mit Tapatalk 2
-
That ain't gonna work either. ScanPaths are bound to DeviceIds. New HDD = new DeviceId. You could fix your FSD 2.2 database with a bit of sqlite knowledge though. But your dump should be good enough to migrate, but consider:but recently upgraded from a 500 Gb Seagate GoFlex to a 1TB 3.0 USB Seagate Backup Plus. ... FSD 2.2 boots up but does not show my games on HDD. ...Hence, I thought it was time for me to upgrade to F3 and do a clean
I still have my FSD 2.2 dump on my internal HDD, which I took during transfer. Will try to migrate from that folder to the new F3
.gif)
If you migrate, you'll end up copying your "old" scanpaths as well, as they are used in the ContentItems table which will be migrated during the process. If your new HDD is set up as your old one you are lucky! I recently released a simple app to import scanpaths -> LINK. Although it was not meant for this type of situation it matches your needs nicely.
After migration boot up F3. It will not find any games but the database and all the images etc. should be there. Connect your HDD to your PC and run F3 scanpaths importer (source = new F3 install). You'll see all your "old" scanpaths. Select the same F3 database again as destination and select the correct Device. That will change the DeviceId according to your new HDD. Hit on update. I think you'll end up with correct scanpaths/database/images this way.
-
1
-
-
Why would you want to delete FSD2.2 in the first place? Just install F3 in a new directory.
Move or copy then the Title Updates from FSD2DataTitleUpdates{DeviceID} to F3DataTitleUpdates{DeviceID} if you want F3 to handle them.Or just migrate FSD2.2 to F3 there you have the option about TitleUpdates as well.
-
Boxart = only frontCover = full coverYou can click on both in the manual edit form to see which dimensions are supported (written in the title of the file dialog). You can also use JQE360 tab. There you see all options and dimensions once you click on current/all games.Gesendet von meinem GT-I9100 mit Tapatalk 2
-
You can backup all your F3Data folder. ..Databases contains the databases which will be modified directly by GaDaBaMa...GameData contains the .assets file for each game. It's a file that has a header and all the images for that game.I've never made any backups of my data except for test purposes. Once you have it running and you know how to use it you can skip any backups.The manual comes with the installation. Just click on the Help button inside the app.Gesendet von meinem GT-I9100 mit Tapatalk 2
-
-
-
This little app is intended for all those who use a SOURCE F3 install which they copy to other Xbox360's and for those swapping HDD's content from one HDD to another. Apparently each HDD/USB has it's own DeviceId. Under content.db you'll find all MountedDevicesIDs. The ScanPaths table (settings.db) uses these IDs. The ContentItems table (content.db) uses just the ScanPathsID. By copying the databases from the SOURCE F3 install you'll lose your ScanPaths as the DeviceIDs don't match. This is where this app comes into play.
How-To
First copy your SOURCE F3 database to your new Xbox (called DESTINATION F3). Start your DESTINATION F3. This will update your content.db with your new DeviceIDs.
Open this app. Under 1) select your SOURCE F3 database and click IMPORT. You'll see all scanpaths available in that database. For the moment there is no distinction between DeviceIDs (all available Paths will be imported!). Therefore, I recommend using a SOURCE F3 database with just one DeviceId (as shown in the picture)! These scanpaths will always be present when you start the app. So in case you need always the same paths you'll just have to do 1) once.
Under 2) select your DESTINATION F3. Automatically it will fill DeviceID of Hdd1. If you need another DeviceID select between Hdd1, HddX or Usb0. The DeviceId will change accordingly. You can also input another DeviceId. Hit on update and all ScanPaths of your SOURCE F3 will be inserted into your DESTINATION F3 with the new DeviceIds.
Behind the scenes - SQLs
1) SOURCE F3 database
Does just SELECT * from ScanPaths and outputs it into scanpaths.ini
2) DESTINATION F3 database
SELECT MountedDeviceDeviceId from MountedDevices WHERE MountedDeviceMountPoint='" & ComboBox1.value and outputs it into DeviceId.ini
DELETE from ScanPaths
.import insertpaths.ini ScanPaths
UPDATE ScanPaths SET ScanPathDeviceId='" & txtDeviceID.value
Credits
Keyser (DEV)
Bill Stewart (TDC)
Edy (idea)
SQLite (sqlite.exe)
TeamFSD
Source files
It's a simple HTA file. The contents of the executable will be extracted and placed somewhere under %appdata% I guess. If you need to change the code/scanpaths.ini file etc. search for SetPaths.hta.
Additional Info
This picture shows the relations between all tables related to scan paths:
-
2
-
-
Just use XUITT
Once you have built up a database in your language you can translate any skin in few minutes (as long as they've used the same expressions of course)
You can also create skin-specific databases/translations. Whenever a new version of that skin comes out you can apply the translation done for that skin.
All foreign (not english) skins translated by myself use the same english expressions found in the default F3 skin. Giving the advantage of being more compatible with an existing database. -
Meanwhile you can already manage your TU as you requested with GaDaBaMa. - download latest version- delete obsolete TUGesendet von meinem GT-I9100 mit Tapatalk 2
-
You could have easily done a backup of your data >> TUTORIAL <<but destroyed all my precious personal covers,bio,settings,..etc in the process
-
Just put the Xbox IP address without the port (9999). If you have many covers to change try GaDaBaMa.
-
Tabs descriptions are usually in skin or menusettings.xml. Should be step4 & 5. Make sure that the skinner did not use images. You can open the translated xur files with xuitool. If the skin freezes in a scene, copy the original xur file to your translated skin folder and test it again. It doesnt happen very often but sometimes it's the only way to figure out where and why it freezes. Use then Xuitool again to fix that file. If I can I'll take a look today.Gesendet von meinem GT-I9100 mit Tapatalk 2
Some Games Not Appear In Game Library
in Support
Posted