38
Sample programs and tutorials
The
\examples
directory of the FBX SDK distribution contains a library of
sample programs. For more information, including a brief description of each
sample program, see Sample programs on page 45.
For three of these sample programs, this documentation contains a tutorial
based on the program:
Tutorial
Sample program
Tutorial 1: Importing, Converting, Export-
ing a File on page 55. Shows how to im-
ImportExport
port a file and how to export a file. Builds
and runs on Windows only.
Tutorial 2: Traversing the scene graph on
page 67. Shows how to traverse all the
SceneTreeView
nodes in an FBX scene, and how to determ-
ine the content of each node, i.e., whether
a node contains a camera, a light, a mesh,
etc. Builds and runs on Windows only.
Tutorial 3: Adding Textures, Materials, and
Animation on page 79. Shows how to add
CubeCreator
textures, materials, and animation to
meshes representing a model. Builds and
runs on Windows only.
Platform Requirements
FBX SDK runs on the following platforms:
Requirements
Platform
Windows XP and Vista.FBX SDK also runs
on Windows NT 4.0 and Windows 2000,
Microsoft Windows
but has not been tested for those two
platforms.
Platform Requirements | 15
40
Requirements
Platform
Any Linux implementation that provides
GCC version 3.4.x/4.0.x, and libc version
2.3.4 or later.
Linux
Versions 10.4 and 10.5.
Mac OS
FDX SDK runs on the 32-bit and 64-bit versions of all these platforms, with
one exception:
■
Macintosh OS 10.4: 32-bit only.
For more information, see Recommended development environments on page
21.
Sources of information
Notes
Source
This document you are reading. You may
be reading it as a PDF file, or as part of FBX
SDK Help.
Autodesk FBX SDK Programmer’s Guide
Help system distributed with FBX SDK. In-
cludes content of Autodesk FBX SDK Pro-
FBX SDK Help
grammer’s Guide, as well a Reference sec-
tion containing documentation for each
class, member function, etc.
Distributed with FBX SDK. Contains last-
minute documentation, as well as what’s
readme.txt
new and what’s changed since the previ-
ous version of FBX SDK.
These FBX tools and their documentation
are a good introduction to what you can
Documentation for: FBX Plug-in for 3ds
Max; FBX Plug-in for Maya; FBX Converter;
FBX for QuickTime
do with FBX and therefore with FBX SDK.
If you are not familiar with 3D modeling
16 | Chapter 2 Introduction
VB Imaging - VB ISSN Barcode Generating help VB.NET developers draw and add standard ISSN barcode on photos, images and BMP image formats, our users can even create ISSN barcode on PDF, TIFF, Excel
extract images from pdf file; extract images from pdf files
36
Notes
Source
and animation concepts, consider learning
how to use 3ds Max or Maya.
Free, user-to-user discussion forums. See
Discussion Forums on page 19.
Discussion forums
Home page for FBX. Look here for white
papers, product sheets, new releases, and
other information.
www.autodesk.com/fbx
Describes how FBX technology is used.
Contains guidelines on interoperability
Interoperability and FBX Technology White
Paper
between 3ds Max, Maya, and MotionBuild-
er software, as well as other applications.
Available at ww.autodesk.com/fbx.
Visit area.autodesk.com for Autodesk news,
tutorials, discussion forums, downloads,
etc.
Area
Naming conventions
Header files and sample programs generally follow the following naming
conventions:
Notes
Prefix
Most FBX SDK class names begin with this.
Examples: KFbxNode, KFbxScene, KFbx-
Camera
KFbx
Many utility classes begin with upper case
“K”. Examples: KString, KFCurve,
KTime
K
Naming conventions | 17
29
Notes
Prefix
Parameters passed to a member function
begin with lower case “P”. Examples:
p
pWriteFileFormat, pScene, pFile-
name
Local variables begin with lower-case “L”.
Examples: lWriteFileFormat, lScene,
lFilename
l
Global variables begin with lower-case “G”.
Examples: gStart, gStop, gCurrent-
Time
g
Member data (properties) begin with
lower-case “M”. Examples: mDescrip-
tion, mImportname, mSelect
m
Getting Technical Support
Autodesk provides technical support, discussion forums and an email address
for feedback to the development team.
Autodesk Developer Network (Sparks)
Technical support for the FBX SDK is provided through the Autodesk Developer
Network (ADN) Sparks 3rd party developer program. The ADN Sparks program
is based on an annual membership fee. The program details, benefits, and
pricing are found on the Autodesk Developer Center web page
(www.autodesk.com/adn).
18 | Chapter 2 Introduction
16
Discussion Forums
Autodesk offers free, user-to-user discussion forums for developers and others:
URL
Forum
area.autodesk.com/index.php/forums/view-
forum/64/
FBX SDK
area.autodesk.com/index.php/forums/view-
forum/65/
FBX Plug-ins Import-Export Discussions
area.autodesk.com/index.php/forums
All discussion forums
Email the FBX development team
The FBX technology development team welcomes your feedback at
fbxsdk@autodesk.com.
Getting Technical Support | 19
C# Imaging - Scan RM4SCC Barcode in C#.NET PDF, Word, Excel and PPT) and extract barcode value Load an image or a document(PDF, TIFF, Word, Excel barcode from (scanned) images, pictures & photos that are
extract image from pdf c#; how to extract images from pdf in acrobat
20
Installing and Configuring
Recommended development environments
The following table lists the platforms and compilers recommended for
developing with FBX SDK:
Supported development environ-
ment or compiler
Supported platform
Any implementation that provides gcc
version 3.4.4/4.0.2 or later, and libc ver-
sion 2.3.4 or later.
Linux
GCC 3.2 on PowerPCGCC 4.0 on PowerPC
and Intel x86
Mac OS X
Visual Studio 2003, 2005, and 2008.
Windows XP SP2, Windows Vista
If your platform or compiler is not listed above, then you may not be able to
compile and run programs that use FBX SDK.
3
21
39
Vertex cache compilation support
Class
KFbxCache
supports vertex caches, i.e., accessing point animation in a
cache file. But this feature is not supported by some compilers on some
platforms:
Compilers not compatible with ver-
tex caches
Platform/Environment
Not supported by all GCC 3 compilers.
Linux
Not supported by all GCC 3 compilers.
Mac OS
Not supported by .NET 2003 compiler.
Windows XP
For these compilers and platforms, you may be able to compile calls to
KFbxCache
methods, but the compiled code will not execute properly:
■
Methods will return
False
(i.e., failed).
■
A call to
GetLastErrorID()
will return
eUNSUPPORTED_ARCHITECTURE
.
For more information about vertex cache, see Storing animation in a vertex
cache on page 111.
Downloading and installing
There are separate distributions of FBX SDK for Linux, Mac OS, and Windows.
The structure of the FBX SDK distribution directory is, however, identical on
all these platforms. See Directory structure on page 23.
For each platform, there is more than one version of library file for FBX SDK.
See Runtime libraries available in different flavors on page 23.
To download and install FBX SDK, follow the instructions for your
development platform, either Linux, Mac OS, or Windows on page 27.
22 | Chapter 3 Installing and Configuring
42
Directory structure
The structure of the FBX SDK distribution directory is identical on all platforms:
Description
Directory
The root of the FBX distribution directory
contains readme file, the license text, and
the uninstaller.
yourpath\
Contains FBX_SDK_Program-
mers_Guide_2009_1.pdf, a directory
yourpath\doc
containing FBX SDK Help, and
FBX_SDK_Help.html. To start FBX SDK
Help, open FBX_SDK_Help.html.
Sample programs, each in its own sub-
folder. Contains platform-specific project
files, makefiles, etc.
yourpath\examples
Header files for FBX SDK.
yourpath\include\fbxfilessdk
Library files for FBX SDK.
yourpath\lib
Runtime libraries available in different flavors
The library runtime files (located in the
\lib
subdirectory of your FBX SDK
distribution) are different for each platform (Linux, Mac OS, and Windows).
For each platform, the
\lib
subdirectory contains different “flavors” of FBX
SDK. For example, you can link your application to a runtime library for
Windows which is:
■
For Visual Studio 2008, 2005, or 2003.
■
For projects that build statically linked libraries or dynamically linked
libraries.
■
For libraries in debug mode or release mode.
■
For 32-bit processors or 64-bit processors.
Downloading and installing | 23
38
■
For single-threaded (Visual Studio 2003 only) runtimes or multi-threaded
runtimes.
Library runtimes for Windows
Here are the names of the library runtimes for Windows:
Description
Library file name
Static, 32-bit, release, multithreaded, VS
2008
fbxsdk_mt2008.lib
Static, 32-bit, debug, multithreaded, VS
2008
fbxsdk_mt2008d.lib
Dynamic, 32-bit, release, multithreaded,
VS 2008
fbxsdk_md2008.lib
Dynamic, 32-bit, debug, multithreaded,
VS 2008
fbxsdk_md2008d.lib
Static, 64-bit, release, multithreaded, VS
2008
fbxsdk_mt2008_amd64.lib
Static, 64-bit, debug, multithreaded, VS
2008
fbxsdk_mt2008_amd64d.lib
Dynamic, 64-bit, release, multithreaded,
VS 2008
fbxsdk_md2008_amd64.lib
Dynamic, 64-bit, debug, multithreaded,
VS 2008
fbxsdk_md2008_amd64d.lib
Dynamic, 64-bit, release, multithreaded,
VS 2005
fbxsdk_md2005_amd64.lib
Dynamic, 32-bit, release, multithreaded,
VS 2005
fbxsdk_md2005.lib
24 | Chapter 3 Installing and Configuring
Documents you may be interested
Documents you may be interested
