since the announcements as far as I understand just relate to changes / fixes / additions related to the previous version, I wonder if there is a place where all new features are listed, even if they did not change since the last version…
@brian or @will if we could get an auto-generated merged view of the posts that are created every week for announcing new builds, that would seem to fit the bill. For the Rhino 8 WIP, we could have a single page that is just all of the bullet points that are made for Rhino 8 WIP Available Now!, but merged into a set of sections.
Can I ask… Rhino 7 was just released, and Rhino releases are often years and years apart… why are there already seemingly bugfixes being moved to Rhino 8 instead of 7 (I see at least 1 bugfix that was reported for 7)?
I ask because I ended up awkwardly jumping between 7 WIP and 6 for a project, due to some fixes being in one but not the other, and that wasn’t a very good situation. I know I’m not alone in this, as I’ve seen people complain in several places on this forum that fixes are only done in WIP when they need them in production.
(I totally get it when a fix relies on a new feature, though.)
Generally ‘bugfixes’ that require some major rework of core code - possibly breaking other existing functionality and plug-in compatibility - are moved to the WIP so as to insure stability of the release version.
This is also based on the fact that since V6, the WIPs have been available in parallel to the release version - so there is no waiting really - you can have fixes and new features as soon as they are implemented instead of having to wait for the next release.
Yes, the official word is always no until the WIP hits the Beta stage. However, nothing should prevent you from using the WIP for the things you need that are fixed and the release version for the rest - keeping your files in the release version format.
Remember when FlowAlongSrf and Squish and all the other tools using that tech first came out? And people were using the WIP in production even though it wasn’t simply likely to crash but might actually damage your files when it did? Good times.
the shadow is not crisp (though you can fiddle with settings to improve this slightly you shouldn’t have to), and the light source is not fixed relative to the model. it makes it hard to judge what you’re doing. the dark area is pitch black for some reason… like it’s painted with vantablack. rhino could get sued by anish kapoor for this.
i don’t want this in a raytraced viewport. that’s going to kill my gpu. this should be level of shadows in the “shaded” view… the GPU in wireframe view already idles at +10 to 15 degrees F with Rhino open in a blank model.
I think you misunderstood: said settings are less taxing for your gpu.
I concur with your “vantablack” comment though.
I think this can be solved by custom lighting too, but it should look better on default.