Awesome plugin, it would be really great from a urban designer/Landscape architect perspective if there was a “highlight area” and change feature built in for already created photos. For example, If I want to change some planting in a certain area of this image. It would also be great if edits were at a reduced cost since they were already created.
I think you’re absolutely right. What I have in mind is to introduce an edit option for images that already exist in the “Images” tab. This would make it possible to mark or draw an area and prompt a change for that specific region. I think this feature is probably two releases away. I haven’t started working on it yet, but you’re spot on in identifying the need for it.
I’m not yet sure what the cost will be. It may be possible to use other APIs or cheaper models for this, but that’s something I’ll need to investigate further. I very much agree that the plugin is a bit expensive at the moment. The main reason is the underlying API cost of NanoBanana Pro, which is a quite expensive model. My hope is that other providers will catch up with cheaper alternatives. This is a space that evolves very rapidly, and in the past we’ve seen costs for similar performance drop over time. I hope the same will happen for image generation as well.
New: Upscale generated images (2k/4k/8k) directly from the Images gallery.
Improved prompt context: “Layer colors + names”, plus a new Layer Hints editor (geometric/region-based hints) and better preview tooltips.
Smoother UI: Images view loads faster with infinite scroll/paging, resolution badges, and more consistent thumbnail cropping; UI no longer reloads on resize.
Easier updates: Update banner can open Rhino Package Manager from inside the UI.
Rhino 7/8 polish: Improved Rhino 7 menu/icon handling, and clearer messaging for Rhino 8 users running the .NET Framework build.
Fixes: Password reset/register edge cases and general stability/bug fixes.
It looks like the plugin is not being properly uninstalled, which results in both the old and the new versions being present. I’m afraid the best way to resolve this for now is to go to:
I get error messages about the .NET version sometimes when starting up RhinoBanana, even though it’s set to NETCore v.7. I can solve it by downgrading to version 0.1.7 and restarting, which makes it work.
But if I later check the PackageManager, version 0.1.8 has been installed anyway. So, if I close Rhino again and restarts it, I get the same error message.
You shouldn’t see this error if you’re running .NET Core 7, so I’ll need to look into why this is happening. If you wouldn’t mind sharing your SystemInfo (Rhino command) with me in a private message, I think that could help me track down the issue.
Thanks — this is a tricky one. Would you mind sending your SystemInfo right after you see the error, if it happens again?
For now, I think I’ll remove the message about .NET Framework. That should prevent this issue going forward, but it also means users running .NET Framework won’t get feedback about what needs to be fixed.