Skip to content

Latest commit

 

History

History
25 lines (20 loc) · 2.12 KB

limitations.md

File metadata and controls

25 lines (20 loc) · 2.12 KB

Inherent Limitations

there are following limitations in x3ogre. Some of them are due to underlying limitations on Ogre itself and some are necessary to make the rendering efficient.

  • No Events. All logic is supposed to be on an higher level. (scripting language) Limited support for onchanged type events would be possible though.
  • As a consequence: No general ROUTEs: you can only create Routes between a small set of predefined Nodes. This is needed for a decent performance. Yet animations are still resolved.
  • No shearing support in Transform: i.e. the scaleOrientation field is only valid for multiples of 90°. However this field is hardly used anyway.
  • No two sided lighting support (TwoSidedMaterial). DirectX lacks this and therefore Ogres Material lacks it too. Rarely used anyway, but could be emulated using the RTSS.
  • There are some unresolved X3D compatibility issues. These are solvable but have a low priority right now.

Programming Interface

SceneAccessInterface is the main Interface for interacting with X3D Scenes. Subset of the standard http://www.web3d.org/documents/specifications/19775-2/V3.3/Part02/servRef.html.

Method Description
setNodeAttribute(node, field, value) equivalent of getNode(node).getField(field).setValue(value)
getNodeAttribute(node, field) equivalent of getNode(node).getField(field).getValue(value)
nodeExists(node) equivalent of getNode(node) != NULL
loadURL load a X3D file (with x3ogre extensions)
getCurrentFrameRate