Keyser

You could export the FR-EN databases (database + Skin specific: Looping & Sphinx) to excel through the Database Manager. In some cases the authors correct some typos or use shorter words etc. This way you can look up what has been previously used and copy paste the english translation. If you got that far then I'm pretty sure you did all correctly. I started translating METRO V3 for 735 and although I had a complete database of the previous versions there were like 50 records in english and some others with corrections like Bannieres -> Bannières etc. So there will always be some work to do. Have fun.

Thanks JPizzle. Cover.xml is processed correctly now.

There seems to be a problem with covers.xml from JQE360 site. F3 as GaDaBaMa use this file to get all the links for all the covers. An error pops up <semicolon expected>. Can't dig any deeper right now.

To translate a skin you have 2 options that I know of: 1) Opening each xur file with xuitool and change/translate all texts 2) Using XUITT RXE Style is from aurelien07. I've translated 2 skins (Looping/Sphinx) from french to english. The FR-EN databases should be included in XUITT 2.1.5. Maybe he used the same expressions so that most of it will already be translated. When I translate a skin to english I use the english expressions found in the official/default FSD skin. That makes it easier for other translators if they take an english translated skin as base. Keep that in mind.

Mega: Something is wrong. This is certainly not the way it is meant to be. I can't tell you what is wrong in your setup. Try downloading microsoft visual c++ 2010 redistributable. Install XUITOOL + Access 2010 + SP1 + XUITT again. You can translate each xur/xui file manually with Xuitool although I do not recommend it at all.@SPAM: rev483 FreeStylePlugin.xex was also translated with XUITT using the XEX hack option in Step1. It seems like rev735 FreeStylePlugin.xex is different. You can't open the HUD xur files with Xuitool. Search in this forum, I think there was already a topic about that.

Humidity was a typo in 483 -> HumidtyJust change the table for default.xex. i think its in Database tools. There you can also insert new strings.Gesendet von meinem GT-I9100 mit Tapatalk 2

Jeje, I think you did not understand what F3 ESP-EN database stands for. This file is probably the same file I created some weeks ago -> POST To 1) in settings you specify your default language To 2) your question cannot be answered right away: a.) yes, if a file has id's then you should use/enable them. b.) if your excel file does not have any id's you don't need to put them. Just select From Lng and To Lng. XUITT checks if a file has ids or not. If you select use xls ids then it doesnt matter which language you have chosen. If a file does not have Ids columns then you'll not see the option to use xls ids. Just click on the HELP button inside XUITT - it doesn't bite! It explains pretty much everything as easy as possible. Cross Translation This function has been explained in the POST link above. For example if the skin is in spanish: You select in STEP2: Original language (ESP), Translate to FREnch. You activate Fill missing with Cross-Translation ENGlish If you've imported the above database correctly you'll have this option. So XUITT does the following: ESP to ENG & ENG to FRE = ESP to FRE That's why I posted the F3 ESP-ENG database. I even put special attention to use the original ENG translation so that Cross-Translation gets the most hits. I haven't tested F3 rev735 so I don't know why it gets stuck. I read that members were able to translate 735's skins. So I'm guessing that this is not XUITT related. If it gets stuck while opening xui files just increase the slider value in the settings (also explained in the manual). Make sure your xuitool folder has also xuipkg.exe. As this file is used to extract the contents of a skinfile (xzp). I would appreciate if some members could confirm that it works with rev735 skins. Thanks EDIT: If XUITT can't extract your xzp file, then just extract the xzp file manually to a folder using xuipkg. then select that folder in step1 -> obviously use the folder icon... EDIT2: syntax for skin extraction 'Unpack XZP ChDir mySkinfolder runcmd = xuipkg & " /U " & Chr(34) & myXZPfile & Chr(34) or use other apps like xzptool of fsb

Thanks for the bug report.Interesting, looks like resetting the IDs is what was giving errors all the time.Thats of minor importance, what is of greater importance is that the xzp file has been created.errLine = 5'5 Reset ID!DoCmd.RunSQL "ALTER TABLE [Translation] ALTER COLUMN ID COUNTER(1,1)"As I stated in my site I'll not release a newer version for the time being as I'm too busy.Just ignore the error. Some users reported the same error in previous versions and then it was gone.El error no deberia de tener ningun efecto para el archivo xzp traducido.De momento estoy demasiado ocupado para sacar una nueva versión. Ignora el error.

Something must be wrong in your settings, or your xuitool folder is incomplete. If the function hangs there then it is obvious that xuipkg.exe is missing: Call ImportXZPContents(myChosenFile, False) The above function calls this routine:'XUIPKG neededSelect Case SetVariablesCase TrueCase FalseGoTo Exit_ErrorEnd Select That routine checks if all exe files needed exists 'xuitoolFolderXuiToolFolder = Nz(ELookup("xuitoolFolder", "tblSettings", "ID=1"), 0)Select Case XuiToolFolderCase 0SetVariables = FalseCase ElseSetVariables = TrueEnd Select'XUIPKGxuipkg = Nz(ELookup("xuipkg", "tblSettings", "ID=1"), 0)Select Case xuipkgCase 0SetVariables = FalseCase ElseSetVariables = TrueEnd Select Supongo que te faltan archivos (como por ejemplo el xuipkg.exe) en la carpeta xuitool. Asegúrate de tener xuitool completo y controla la configuración de XUITT. En cada inicio XUITT mira en la registry donde está instalado xuitool. Si no lo encuentra pero existe el programa bajo la carpeta guardada (por ejemplo al añadirla manualmente bajo configuración) deja la carpeta guardada, sino borra el contenido del campo (carpeta xuitool) en la configuración. No obstante busca tambien todos los archivos exe que hacen falta para hacer funcionar XUITT correctamente. Si no los encuentra puede ser que en algún paso se quede sin hacer nada dado que no encuentra el exe.

I just took a look. I get the same error. I can't open the database with a SQLite GUI either. So the problem is not GaDaBaMa related. I would suggest the following. Format a USB stick as Fat32 (search for guiformat in this forum). Connect the USB Stick to your Xbox360 console and copy F3 folder. I think you have to do it from another FSD2/3 install or Xexmenu as copying the databases while in use is not possible. Connect then your USB Stick to your PC and try GaDaBaMa. If your USB stick is large enough you can use it for sync purposes as well. Depending on your collection you'll need at least 4-16 GB. I even boot/start F3 with my USB stick.

You can send me a pm with the link.

Your folder structure is correct.I've seen this error but it was very long ago. Can't remember if it is a wrapper error (dhSqlite.dll) or file error.To make sure that your database file (content.db) has no errors I would need to check it. You can do an integrity check as well with a Sqlite Gui or sqlite.exe.Gesendet von meinem GT-I9100 mit Tapatalk 2

Check database files attributes. Are they read only? What do you mean by per pdf?I recommend preserving the folder structure when doing it manually.F3 Data Databases GameDataGesendet von meinem GT-I9100 mit Tapatalk 2

Tha'ts probably just because nxeart says Crysis 2. F3 takes it's info from that file. Once you download artwork it will download all images/descriptions according to its TitleId.

That explains it then. I disabled internet access while in safe mode. Ended up doing it as always over USB. To clarify: In my case having avast installed, AUTO-UPDATE in Safe mode with networking worked flawlessly. Thanks again blakcat! It's much user-friendlier than doing all steps manually.

I read that deinstalling avast! would solve the issue, but that is not an elegant solution. Therefore I thought of disabling it for a short period of time, but it looks like something still runs in the background. Gonna check the avast services. Do you communicate through a special port? I'm on Win 7 64bit with Admin rights. On a side note, I had once a similar problem with ESET security suite.If network drives scan where enabled it ran into problems. Video ESET security EDIT: Even disabling the avast services gave the same error. I ended doing it in Safe Mode with Networking. Somehow the dash got updated correctly but the Avatars are still missing. I started it manually (Auto-Update Avatars) and it gave the same error:

Thanks for the app! I'm having the same issue as the others. After reading the nand it saves it correctly, but the app says no nand. Here is the video: picasaweb

3.1.3 [*]Added CLEAR DATA sync -> see YouTube tutorial

Everything is possible as long as you understand the database behind F3 (sqlite). You might be interested in this post.

http-~~-//www.youtube.com/watch?v=vjZ_pYMnSVk This is a short tutorial showing the function: ClearData sync for GaDaBaMa 3.1.3 or higher CLEAR DATA The main problem by doing a clear data is that it can happen that GameIds will not match the old database. This means that all folders under ..DataGameData have the wrong folder name. (Folder name = hex(ContentItemId) from ContentItems table in content.db). So doing a backup of your GameData before clearing your data is almost useless. This means that you would have to re-download all artwork. Using this tutorial you'll save your artwork/descriptions etc. NEW INSTALL If you can't start F3 you might try importing your database to GaDaBaMa as well. In that case overwrite your old/faulty F3 install with a new installation after the first part of this tutorial. WHY using this method There is of course a more simple way to backup and recover your data. But as the problem might be an assets file I decided to go all the way. Extract all content from .assets files and recreate them for the new database. On USB 3.0 for over 3500 images it just took few minutes. BUGS Additional note: In my case it happened, that although I had disabled all Assets downloads it just started downloading them again. Therefore I recommend unplugging your Ethernet cable on your Xbox before scanning for content! You can delete all rows in HttpQueue table (content.db) to wipe out the download queue if it happens to you as well. I don't know if it was just in my case or if it is a F3 bug. SUBS Subtitles have been added. Use this file if you would like to translate it into your language. If you upload the same video with your translation give credit where due. Otherwise I'd be happy to upload your translation to my video. HOW_CLEARDATA_F3.zip

Looks like the .assets file for Gundam 3 is faulty.Delete or rename that file and try it again.You find the file location like this:Search the game in GaDaBaMaFind GameData folder (above Overview Tab in GaDaBaMa) for example 00000043 = GameIDGo to {F3 install dir}DataGameData{GameID folder}Delete or rename {GameId}.assets

FSD2.2 used several files, but different methods: Icons Were saved as blobs in Assets table All other images Were saved as files under GameData folder. Their location were saved as text in Assets table F3 uses a single file (gameid.assets) under GameDataGameId This file has a header and all images are packed into the same file as well. This post here explains a bit how the header looks like. Some team members gave also some answers about it - if you like to look it up. It is much faster and easier to manage than the method used in FSD2.2. Migration You have the option to migrate your FSD2.2 data to F3. Backup When the GameId changes then all your backup is almost useless. You would have to change the GameFolder/.assets file names manually to match the new database. New GameId might happen when doing a Clear Data. But there is another way to easily edit/manage/backup your artwork using GaDaBaMa for F3 FSD2.2 and F3 do not use jpg files - it uses dds instead GameId = ID in ContentItems table in hex.

GaDaBaMa 2.2.1 is only for FSD2 and migration purposes. The .assets files created through the migration are fully compatible with F3. This means, that you can use all options to insert fullcovers: automatically through F3 (custom cover downloading) manually adding covers (covers.jqe360.com) to your download queue (needs user profile) and syncing with F3 manually through http using the latest GaDaBaMa 3.x If you use GaDaBaMa take note of: .assets files content will be extracted and saved locally under %appdata%gadabamadds during Step4 (sync). If you use a plugged-in USB stick to sync no further actions needed. If you sync over LAN/Samba I'd recommend copying your migrated FSD2 GameData*.* folder to %appdata%gadabamadds. This way it will not extract any files as they will already exist - speeding up the process considerably. Unfortunately there are some game-covers in the jqe360.com database with broken links/no images. You'll have to use the TreeView to filter the missing covers and download them manually (use the view covers function - Tab JQE360, current game) The only crash I had was syncing to a USB stick over Samba. Therefore using Samba Enabled on the database you wish to sync is disabled by default. The F3 database should not get messed up when crashing as the use of .assets files makes it much safer. GaDaBaMa extracts the content of the .assets file and rebuilds the file with your modifications/additions = small/equal filesize. F3 seems to use another method - as far as I could test, if you modify a lot it'll blow up the .assets file. I guess it just appends the new file and changes the header to point to it. If an .assets file is faulty it can crash F3. There is no verification process - wasn't needed until now.

If that's the case then write down which game gives the error + titleid according to GaDaBaMa. This way I might be able to recreate the problem.

Migrating with GaDaBaMa - the simplest way to get FSD2.2 data/artwork to F3. Actually it’s pretty simple and safe as long as you follow this brief instruction: [*]Install F3 in a new folder [*]Execute F3. This will create the databases (content & settings) but do not configure anything [*]Copy your FSD2 and F3 folder to a fat32 formatted USB stick [*]Install GaDaBaMa 2.2.1. Access 2010 Runtime. Access 2010 SP1 Runtime. Make sure your regional settings in Windows are configured as follows: [*]Plug your USB stick and wait until it is recognized by Windows [*]Execute GaDaBaMa If you want to use fullcovers (for 3D view/coverflow): [*]Do Step1 – Select FSD Folder [*]Do Step2. [*]Click on JQE360 tab and download only Covers(!) for All Games If you don’t need fullcovers or the continuation of the above steps: [*]Tab DataBase Tools. Migrate FSD2 to F3 [*]If you’ve downloaded all covers select the option convert jpg to dds. [*]Enable all other features [*]Select the paths of your FSD2 and F3 folders (root folders!) [*]Press Start Once finished plug your USB stick back to your Xbox. Start F3. You’ll have all artwork, all scanpaths and content as with your FSD2 install. On USB it’ll take just a few minutes (may take longer if you opt for the fullcovers route). Copy your F3 folder to your Xbox HDD. Configure Dashlaunch. That’s it.