for some advanced plugin usage scenarios we introduced two new interfaces in the upcoming 28 release of vvvv:
the device service can be used to enumerate all directx9 devices created by vvvv (for example through a renderer) or to get notified when a device was created or destroyed. this might come in handy if plugins do some kind of background work using a directx9 device (like texture preloading) and need to know when a device got lost in order to stop all processing scheduled for that device. another future use case would be for some sort of directx9 sink node, like a pipet for example, which needs a device in order to be able to evaluate its inputs.
the second interface can be used to get various notifications about all the different stages the main loop goes through when computing one frame. a possible use case could be a custom set of classes/nodes running in some kind of special "subgraph".
both can either be imported or retrieved via two new properties on the IHDEHost.
anonymous user login
~1d ago
~3d ago
~7d ago
~7d ago
~14d ago
~20d ago
~20d ago
~21d ago
~1mth ago
~2mth ago
Can you confirm whether the events are fired before or after or unknown?
i.e. OnRender occurs after all textures are rendered? or before?
To note (for others), the way to get these is to use:
but then you can't use FHDEHost in your constructor
so inherit
and start using them like:
i.e. OnRender occurs after all textures are rendered? or before?
Me too, I'm interested in when ecactly the events are fired. I hope that this could help me with shared texture read/write synchronisation.
Seehttps://github.com/vvvv/vvvv-sdk/blob/develop/vvvv45/src/core/PluginInterfaces/V2/IMainLoop.cs
Just to clarify: which event the Evaluate() of IPluginEvaluate is invoked on?
Well all nodes which need to be evaluated every frame (auto evaluate = true) are subscribed to the prepare graph event. The evaluation of their inputs leads to further evaluation calls on nodes upstream.