When I Drag the Slade.fbx into the FaceFX Studio 2015(No Save), The Sudio Ouput Error:
File "C:\Program Files (x86)\FaceFX\FaceFX 2015 No-save\Scripts\FBXImporter\messagehandler.py", line 88, in on_drop
FBXImporter.full_import_fbx(fbx_file, betf_file, True)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xce in position 0: unexpected end of data
Note:
while I use my classmate's computer (System:Win10, My Computer is Win 7) it's OK.
It's probably that your "Batch export text file", the text file that describes what frames each pose is on, is saved with an invalid encoding. Try using the text file that comes with the Studio install, and if you are using a custom one (or have re-saved the one from Studio), make sure you are saving the file as UTF-8.
jamieThank you for my reply！ I check the format of the Betch-Export-Slade.Text using Notepad++ ，it show that is UTF-8 No ROM Decode and i also use my classmate's but it did not slove the problem.
Add: The Output Error yesterday show the error track＇ last two line is：
……\Python\python26.zip\subprocess.py ,line 569,in list2cmdline
UnicodeDecodeError utf8 codec cant Decode byte 0xce in position 0:unexpected end of data
Try saving with a BOM (byte order marker).
What language is your Windows 7 install?
What language is your classmate's Windows 10 install?
Try to uninstall and then reinstall FaceFX Studio 2015 (No Save).
If none of that works, please send us the .fbx file and .txt file that does not work to support [at] facefx.com
Thank you for sending the files. The Batch Export text file you sent is not the same one that ships with the No-save. The encoding is different. You can fix the issue by opening in Notepad++ and going to Encoding->Encode in UTF-8 Without BOM, then saving the file.
Reinstalling the FaceFX 2015.1 No-Save Installer should fix this problem. If the problem persists after a re-install, I would definitely run a virus scanner on your system because some process is modifying installed files without your permission.
hey buddy ,have you had this problem sloved? i get stucked on this problem ,thank you.
This issue is resolved. The Batch Export text file had an unsupported encoding.