You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this counts as a true bug, but I find that the movie3d function operates about 100x slower if I have the webshot2 package installed vs if I have it uninstalled. I don't know whether this is a problem with snapshot3d, webshot2, or something about my system. Maybe this is even to be expected from webshot2. However, it would be nice if a "use_webshot" argument could be added to the movie3d function to control whether or not the call to snapshot3d sets "webshot = TRUE".
For the moment, I'll either just leave webshot2 uninstalled or I'll save a slightly modified version of movie3d which defaults webshot to FALSE in the snapshot3d call.
Regardless, thanks for the great package!
Code to reproduce below, though I suspect this behavior is system specific.
I'm not sure if this counts as a true bug, but I find that the movie3d function operates about 100x slower if I have the webshot2 package installed vs if I have it uninstalled. I don't know whether this is a problem with snapshot3d, webshot2, or something about my system. Maybe this is even to be expected from webshot2. However, it would be nice if a "use_webshot" argument could be added to the movie3d function to control whether or not the call to snapshot3d sets "webshot = TRUE".
For the moment, I'll either just leave webshot2 uninstalled or I'll save a slightly modified version of movie3d which defaults webshot to FALSE in the snapshot3d call.
Regardless, thanks for the great package!
Code to reproduce below, though I suspect this behavior is system specific.
The text was updated successfully, but these errors were encountered: