Does Rhino.Inside scan Revit's memory to overcome Revit API limitations?

Does anyone know if Rhino Inside tries to retrieve values out of Revit process memory directly? Revit API proves to be limiting and maybe it could be solved by scanning its memory directly.

Would anyone know if Revit’s EULA allows for this use case?

We exclusively use the Revit API and are compliant EULA. I’m not aware of any memory scanning methodologies that would circumvent the Revit API.

We exclusively use the Revit API and are compliant EULA

Thanks, that’s good to know. I’ve had to perform a rather brittle workaround and follow what’s in Revit API.

I’m not aware of any memory scanning methodologies

Well, there are plenty of methodologies to do that, none of which would protect you from Autodesk taking your license away when detected if that’s against EULA (which I haven’t checked) :sweat_smile:

If anyone knows for sure that memory scanning goes against Revit’s EULA I’d be interested to know that.