Hi @Prehabitat,
The time to port a plug-in from Rhino 5 to Rhino 6 depends mainly on the SDK used (C++, RhinoCommon, Rhino.NET, RhinoScript, etc).
A RhinoCommon plug-in should work out of the box or require very few changes, but a C++ plug-in (like VisualARQ or Lands) will take longer, as the SDK has changed and a new compiler is used. Moreover, as the C++ SDK was stabilized about 2-3 months ago, we started porting it then, as we preferred to wait until no more changes were introduced in the SDK. The most breaking changes in the Rhino 6 SDK are related to annotations (text, dimension, etc) and to display, and VisualARQ is using most of these features.
Don’t get me wrong, I’m not complaining about the changes in the SDK, at the contrary, these changes are done to get new features, or to fix problems in the SDK, even being many of them asked by us!
But as @fsalla said, VisualARQ 2 for Rhino 6 is nearly finished, and we’re currently testing it, but it is not stable enough to be released. As VisualARQ and Lands share a common core plug-in (named Tibidabo), porting Lands to Rhino 6 is partially done (I guess nearly 80%).
Regards,
Enric