I tried the code drwr gave me and it printed:
2 implicit pages:
/c/Panda3D-1.3.2/etc/Config.prc
/c/Panda3D-1.3.2/etc/Configauto.prc
Here is what the configauto.prc has in it:
###########################################################
Panda3D Configuration File - Auto-Generated Portion
Editing this file is not recommended. Most of these
directives can be overriden in Config.prc
###########################################################
Define the display types that have been compiled in. Panda will
pick one of these by going through the list in this order until one
is found that works, unless the user specifically requests a
particular display type with the load-display directive.
aux-display pandagl
aux-display pandadx9
aux-display pandadx8
aux-display pandadx7
The egg loader is handy to have available by default. This allows
clients to load egg files. (The bam loader is built-in so bam files
are always loadable).
By qualifying with the extension “egg”, we indicate the egg loader
should be made available only if you explicitly name a file with an
.egg extension.
load-file-type egg pandaegg
The following lines define some handy object types to use within the
egg syntax. This remaps { name } into whatever egg
syntax is given by egg-object-type-name, which makes a handy
abbreviation for modeling packages (like Maya) to insert
sophisticated egg syntax into the generated egg file, using a single
object type string.
egg-object-type-portal portal { 1 }
egg-object-type-polylight polylight { 1 }
egg-object-type-seq24 { 1 } fps { 24 }
egg-object-type-seq12 { 1 } fps { 12 }
egg-object-type-indexed indexed { 1 }
These are just shortcuts to define the Model and DCS flags, which
indicate nodes that should not be flattened out of the hierarchy
during the conversion process. DCS goes one step further and
indicates that the node’s transform is important and should be
preserved (DCS stands for Dynamic Coordinate System).
egg-object-type-model { 1 }
egg-object-type-dcs { 1 }
The following define various kinds of collision geometry. These
mark the geometry at this level and below as invisible collision
polygons, which can be used by Panda’s collision system to detect
collisions more optimally than regular visible polygons.
egg-object-type-barrier { Polyset descend }
egg-object-type-sphere { Sphere descend }
egg-object-type-invsphere { InvSphere descend }
egg-object-type-tube { Tube descend }
As above, but these are flagged to be “intangible”, so that they
will trigger an event but not stop an object from passing through.
egg-object-type-trigger { Polyset descend intangible }
egg-object-type-trigger-sphere { Sphere descend intangible }
“bubble” puts an invisible bubble around an object, but does not
otherwise remove the geometry.
egg-object-type-bubble { Sphere keep descend }
“ghost” turns off the normal collide bit that is set on visible
geometry by default, so that if you are using visible geometry for
collisions, this particular geometry will not be part of those
collisions–it is ghostlike.
egg-object-type-ghost collide-mask { 0 }
This module allows direct loading of formats like .flt, .mb, or .dxf
load-file-type p3ptloader
Define a new egg object type. See the comments in _panda.prc about this.
egg-object-type-direct-widget collide-mask { 0x80000000 } { Polyset descend }
Define a new cull bin that will render on top of everything else.
cull-bin gui-popup 60 unsorted
The following two lines are a fix for flaky hardware clocks.
lock-to-one-cpu #t
paranoid-clock 1
The config.prc was the other one I already posted.
It looks to me like the config.prc either modifies or overrides this one.