Extensibility Model

22 Apr 2012 11:56
Last Modified
20 Jan 2013 10:23

I wanted to provide an easy way to extend the application with additional bodies, textures etc. I had previously used a single configuration file for visual elements, so while it was possible to configure existing or add additional elements it required a configuration change.

I wanted to support a "drag-and-drop" approach, so that additional items could be added, or existing items updated, just by copying files to a directory. This has the additional benefit of allowing the app to "ship" with minimal data (hence size) and be easily updated.

I'm using an XML-based configuration to define star systems. New files added to an "extras" folder can add or amend as many nodes of the XML configuraiton as they wish. In this way, one or more new/existing objects can be added/amended per file, with additional (e.g. texture) data, being referenced by a relative path. The application will recursively search for multiple .xml files, only following a particular branch of subdirectories until an .xml file is found.

I'm currently defining a set of sample extras to serve as examples.


19 Jan 2013 21:36
Hi there,
I'm looking for a solution to input self-designed 3D-Models into NUIverse (designet with Blender, 3dsMax, etc.). For example a detailled model of the ISS. I dont just want to put a texture onto a spherical surface, but need a possibility to add any non-sperical object to NUIverse.
Is this possible? And if so, plz give me a hint, how to make it.
Thank for your help.

Best regards.
20 Jan 2013 21:23
Hi Philipp. Yes, this is possible. Please see my post at http://drdave.co.uk/blog/2013/1/20/Extensibility-Model-Part-2 for further details. Provided you can compile the model to an XNB file, everything else is specified in configuration.

Add Comment