Re: FxPlug Fx3DAPI
Re: FxPlug Fx3DAPI
- Subject: Re: FxPlug Fx3DAPI
- From: Darrin Cardani <email@hidden>
- Date: Sun, 23 Mar 2008 13:30:35 -0700
On Mar 23, 2008, at 1:18 PM, Matt Rhodes wrote: I'm trying to retrieve the Fx3DAPI during param setup and during frame rendering. I'm using: id threeDApi = [_apiManager apiForProtocol:@protocol(Fx3DAPI)];
This doesn't seem to be working. It's returning NULL.
The 3D API will not be available during a call to your plugin's -addParameters method. It should be available during rendering (but only in Motion, not in FCP which doesn't support 3D). I have the following in my info.plist: <dict> <key>protocolName</key> <string>Fx3DAPI</string> <key>versions</key> <array> <integer>1</integer> </array> </dict>
Is this the proper way to gain access to the 3D API?
That looks correct to me. (And for the record, I believe we've relaxed the requirement that you have to declare which protocols you use. You shouldn't have to do that anymore, if I recall correctly.)
I can retrieve the other protocols just fine. parmsApi = [_apiManager apiForProtocol:@protocol(FxParameterRetrievalAPI)]; setParmsApi = [_apiManager apiForProtocol:@protocol(FxParameterSettingAPI)]; timingApi = [_apiManager apiForProtocol:@protocol(FxTimingAPI)] ;
I'm using v1.2.2 of the FxPlug API.
That all looks correct to me, and I'd expect the 3D API to behave the same.
Darrin
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden