31 lines
1.6 KiB
Groff
31 lines
1.6 KiB
Groff
.\" Automatically generated by bam2egg -write-bam
|
|
.TH BAM2EGG 1 "27 December 2014" "1.9.0" Panda3D
|
|
.SH NAME
|
|
bam2egg \- convert a native Panda .bam file to an .egg file
|
|
.SH SYNOPSIS
|
|
\fBbam2egg\fR [opts] input.bam output.egg
|
|
.br
|
|
\fBbam2egg\fR [opts] -o output.egg input.bam
|
|
.br
|
|
\fBbam2egg\fR [opts] input.bam >output.egg
|
|
.SH DESCRIPTION
|
|
This program converts native Panda bam files to egg. The conversion is somewhat incomplete; running egg2bam followed by bam2egg should not be expected to yield the same egg file you started with.
|
|
.SH OPTIONS
|
|
.TP
|
|
.B \-noabs
|
|
Don't allow the input bam file to have absolute pathnames. If it does, abort with an error. This option is designed to help detect errors when populating or building a standalone model tree, which should be self-contained and include only relative pathnames.
|
|
.TP
|
|
.B \-noexist
|
|
Don't treat it as an error if the input file references pathnames (e.g. textures) that don't exist. Normally, this will be flagged as an error and the command aborted; with this option, an egg file will be generated anyway, referencing pathnames that do not exist.
|
|
.TP
|
|
.B \-ignore
|
|
Ignore non-fatal errors and generate an egg file anyway.
|
|
.TP
|
|
.BI "\-o " "filename"
|
|
Specify the filename to which the resulting egg file will be written. If this option is omitted, the last parameter name is taken to be the name of the output file, or standard output is used if there are no other parameters.
|
|
.TP
|
|
.BI "\-cs " "coordinate-system"
|
|
Specify the coordinate system of the input bam file. By default, this is taken from the Config.prc file, which is currently zup_right.
|
|
.TP
|
|
.B \-h
|
|
Display this help page.
|