Hello,
I have been using Archvision's RPC API to read and process RPCs since Revit 2014. In the Archvision's RPC API there is a method `setRpcId` where you set the unique id of the RPC, so you can then read all data about this RPC. This unique id is read during export in Revit from the RPC's asset, i.e. for example the M_RPC Tree - Deciduous American Beech - 6.0 meters it is "RPC-16-G1GQ-43Q0-7NP3-0000-ST1L-LVER-AU". Up until 2019 this worked perfectly and I was able to read all data for the RPC. With 2019 however the behavior is different. Here is a small part of my code:
m_instance->setRpcId(id);
if (m_instance->contentType() == -1) {
ret = false;
System::String^ fmt = "RPC with ID:{0} does not exist. RPCInstance object is invalid.";
throw gcnew System::InvalidOperationException(System::String::Format(fmt, rpcId));
}
else {
ret = true;
mIsValid = true;
}So unlike previous versions of Revit, with 2019 the content type is now -1 and I throw an exception. Even if I ignore the fact that the content type is -1 and go on to read the RPC info, the RPC now renders with ArchVision's watermark on top of it.
Has the licensing of the built-in Revit 2019 RPCs changed, i.e. do you have to have a license for ArchVision Dashboard or no?
