Discussion in 'FIFA 18 Editing' started by pe pe, Feb 19, 2018.
how can i make teams like addidas 11 appear in career mod help please
Hello! I happy CGFE for launch but May I ask one question where camera gamcam height and zoom settings I mean the forsty editor have Broadcasting/attribsys/gameplay_camera_settings but in the CGFE I can't find them anyone can help me !
thank you !
how to change tattoo design in CGFE 18?
You want people to answer? Then respond to their helpful replies in the other threads you're asking questions in, damn. Something like, "Thanks for the help!"
how i can import kits in cg fileexpèlorer ? because for others files there is export and import but not for kits , someone can help me ?
Hi, my dear friend thank for replay. I'm not in another threads. I know this with the Frosty editor, but I do not know about CGFE program.
Where are the kit files, I will test.
I found the kit dds files, they import/export no problem. Located data/ui/imgassets.
not , friend bangus the kits are in bundles/win32/content/character/kit
here you can find all the kits, that you have told are the minikits
and like in frosty i thought that i could replace the dds files
i open but i don't find import or export
click on select section/DA/select database language
thank you very much friend
may be you can help me also in other problem , i have modified the db of the infinity patch (customized db) i have only modified balance and trait 2
but to import it should i use the tree in the first column? legacy/data/db? or i must use dbmaster in select section? because appears an error when i try to import it
The DA (Creation Master) is very buggy. I stopped trying to use it. I use DBM and Excel to edit the db. After editing, import back in Legacy Files/data/db.
I didn't recommend DA (Creation Master) for kits because I assumed it wouldn't work, can't import minifaces for example. Are you saying it works for kits? Because I want to switch some generic GK kits, EA did things like assign white GK kits to some teams with white home/away kits!?!
will get an update to cg file explorer
hi bangus , i have made like you have told (yesterday) .
i have extracted the db (from the patch infinity) from legacy files (from the tree on the left) , used db master to open and excel to modify. then i have reimported the db but always it gives me an error when i try to import it.
i'm trying to understand why it gives me an error importing the db
Yes, same to me. I Import some kits and in game they looked like Stone washed Jeans and game Crash if I want to start a game. If I Import more than 1 Team´s kit´s that happend. What are you recommend to Import kits without frosty.
Do the original infinity patch files you are using, import back in? Test that. Don't edit them, just export them, then see if you can import them. Maybe the original infinity patch files are the problem.
Import errors are often caused by data errors, a common one happens at the bottom of the worksheet. You edit the 18,500 players, but you've left data for 18,600 players in one of the rows. Check all the rows at the bottom.
If you used DA Creation Master to edit kits, that's probably why. I don't use that tool, it's too buggy. I've been able to export dds files, but not import them.
But you got it to work for at least one team? How, what did you do, did you use the DA tool?
Creation Master had a bug for years. It wouldn't save unless you switched tabs to change the view screen. Example: the edit player screen has 3 edit tabs: info, stats and face. If I edited stats, I had to switch back to the info tab/screen before saving, otherwise it often wouldn't save.
I don't have any issues importing kits or minikits usings the DA or the Tree View methods.
Using the DA all you have to do import like you were using CM.
Using the Tree View method you highlight the file you want to import and the select section portion at the bottom select export/import and select import and
choose your texture.
It is always best to save and import the texture in the format the game is using.
This information is in the documentation.
Separate names with a comma.