xml

Long time no see but polymorph engine development…

Long time no see, but polymorph engine development is back on track! The XML describing a polymorph’s project is now able to configure the Ogre’s compositor, understand the post-processing module. The first screenshot is using a custom compositor with this configuration: <workspace name=”TuningScoreWS”>   <script group=”General” workspace=”CustomCompositor” />   <colors>     <color name=”background_center” value=”0,1,0″ node=”0″ pass=”1″ index=”4″/>     <color

Today a lot of bug fixes on the…

Today, a lot of bug fixes on the basic classes of the polymorph packages. New: it is now possible to declare the resources folders in the XML! The common resources.cfg of Ogre can be replaced by a configuration.xml, placed in the same folder as the exec. The resources.cfg was looking like this: [Essential] Zip=../media/packs/PolymorphTrays.zip [General]

Dynamic scenes loading Based on an #XML description…

Dynamic scenes loading. Based on an #XML description of the project, that looks like this: <polymorph version=”0.1″ date=”20161124″> <scenes> <scene id=”3″> <pobjects> <plight name=”main_sun” visible=”1″ debug=”1″> <pnode name=”floor” visible=”1″ debug=”0″> and so on, it is easy to load a new scene. The deletion and creation job is managed by a cool object call “PObjectManager” see: