Ogre Forums

spookyboo wrote: Maybe it has been proposed before (I don't know), but isn't it possible to start some kind of kickstarter project to create a 2.1 demo with professional artwork/content?

syedhs wrote:

spookyboo wrote: Maybe it has been proposed before (I don't know), but isn't it possible to start some kind of kickstarter project to create a 2.1 demo with professional artwork/content?

That is a very good idea. I definitely will chime in and contribute! I don't speak for all, but I think old but non-active members will also be interested.

In Ogre 2.1; TagPoints are much better: they are exactly like regular SceneNodes, except they occupy a little more RAM (a few more bytes per node), and can be attached to Bones. Other than RAM consumption, there is no performance penalty for replacing SceneNodes with TagPoints (*).

You can make a TagPoint child of a SceneNode, a SceneNode child of a TagPoint, and a TagPoint child of another TagPoint. The only thing you can’t do is make a SceneNode child of a Bone. You must use a TagPoint for that.

MattStevens wrote:Do you know how hard it would be to retro fit the changes to 1.9 or how to have the equivalent in 1.9 ?

Entity *character;
Entity *weapon;

Ogre::SkeletonInstance *skeleton = character->getSkeleton();
Ogre::TagPoint *tagPoint = skeleton->createTagPointOnBone( skeleton->getBone(
                                            "Bone Name" ) );

SceneNode *childNode = rootSceneNode->createChildSceneNode();
childNode->attachObject( weapon );
tagPoint->setListener( new TagPointListener( childNode ) )
//Tell the child node that we have a tagPoint associated
childNode->getUserObjectBindings().setUserAny( Ogre::Any( tagPoint ) );

class TagPointListener : public Ogre::Node::Listener
{
    Ogre::Node	*m_realNode; //Node where we redirect our updates
public:
    TagPointListener( Ogre::Node *realNode ) : m_realNode( realNode ) {}

    void nodeUpdated( const Ogre::Node *updatedNode )
    {
        m_realNode->setPosition( updatedNode->_getDerivedPosition() );
        m_realNode->setOrientation( updatedNode->_getDerivedOrientation() );
        m_realNode->setScale( updatedNode->_getDerivedScale() );
    }

    void nodeDestroyed( const Ogre::Node* )
    {
        delete this;
    }
};

const Ogre::Any &any = childNode->getUserObjectBindings().getUserAny();

if( !any.isEmpty() )
{
    //Remove associated tag point, we don't need it anymore
    Ogre::SkeletonInstance *skeleton = character->getSkeleton();
    Ogre::TagPoint *tagPoint = Ogre::any_cast<Ogre::TagPoint*>( any );

    Ogre::Node::Listener *listener = tagPoint->getListener();
    tagPoint->setListener( 0 );
    delete listener;

    skeleton->freeTagPoint( tagPoint );
}

MattStevens wrote: Until we upgrade to Ogre 2.1 I'll use your system. I'm just wondering if it works with hardware skinning ? We use that feature for pretty much all of our animated skeletal meshes.

EDIT: Your system uses _getDerivedPosition of the TagPoint and sets it to the weapon's scene node. This function stops at the skeletal root bone, right ? That means you do not have the entity's transform accounted for. How do you fix that issues ? Will linking the weapon's scene node to the entity's parent scene node do the trick ?

hydexon wrote:How about the Apple Metal Rendering Subsystem? i saw your Metal programming rants in Twitter time ago?, i'm not asking a ETA yet, probably when the v2-1-pso is merged in v2-1 branches?, i really don't care about DX12 yet, since i have MacBook (2014) with the El Capitan installed, and i can't use it a lot since my projects relies heavily with OGRE..., and Xcode is somewhat nice to work.