ASCII to Binary FBX conversion not working

[TennisGazelle]

Issues with the following cmd.

$ ./fbx-conv -v -o fbx ../yellow_oktober_ascii.fbx yellow_oktober_bin.fbx

the resulting yellow_oktober_bin.fbx file has zero bytes

$ > ls -fal yellow_oktober_bin.fbx
-rw-r--r--  1 daniellopez  staff  0 Aug 15 14:26 yellow_oktober_bin.fbx

the original is plenty large, you can download it by using

burning_man_camp $ curl http://singleclick.com/~jelwell/daniel/YellowOktober2018.01A.fbx -o yellow_oktober_ascii.fbx
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 15.7M  100 15.7M    0     0  8996k      0  0:00:01  0:00:01 --:--:-- 8994k
burning_man_camp $ ls -fal | grep yellow_oktober
-rw-r--r--   1 daniellopez  staff         0 Aug 15 14:25 yellow_oktober.fbx
-rw-r--r--   1 daniellopez  staff  16551030 Aug 15 14:31 yellow_oktober_ascii.fbx
-rw-r--r--   1 daniellopez  staff   5723002 Aug 15 14:24 yellow_oktober.g3db

i understand if you don't want to download the link because it seems sketch, but i needed this to be able to read an ascii fbx file (or convert it rather) into a format that Blender can read while preserving texture and other information. Objs alone won't cut it.

[Fentonator]

Ran into a similar issue, and I think I see the problem: while the help text for the -o option lists FBX as an available option, the implementation of FbxConv::save (in FbxConv.h, for some reason that doesn't particularly make sense to me) only has switch cases for FILETYPE_G3DB and FILETYPE_G3DJ (despite FILETYPE_FBX being defined in the relevant headers), and so it simply triggers the "unknown file type" error message and leaves the output file without anything in it.

This appears to date back to the very earliest versions and doesn't seem to have been changed (according to the annotation/blame view), and both the variable names used there and a quick look around make me believe that there has never even been an intention to support output as FBX of any format, whether ASCII or binary. Specifically, it appears that the only concept of a "writer" is a JSON-based writer (in other words, one of the G3Dx writers). So unfortunately I think the bug here is that the -o help text should not indicate that FBX is a supported output file type…