I’ve been waiting for an update. Just checked via Help -check update and it said I had the latest. which is 8.0.23297.13303, 2023-10-24
But you say there is an 8.1?
On the update dialogbox. Change the release level from service release to service release candidate.
Then check for the update.
There is no release level on the dialog box on the beta release of V8 I am running.
oh, I see, you are still in BETA although beta period is over since rhino is released now,
you can start you 90-day evaluation (unless you are keeping that for something big)
Well, that’s funny. I started on Rhino 5. In the past, I’ve always gotten a message when a new version was available for purchase.
It is a soft release, Mcneel won’t publicly announce it until the issues in this thread will be resolved.
That’s not quite accurate, there is a planned date for the release public announcement, but it is not dependent on certain bugs being fixed.
okay, I have V8 now, still feeling the suspense of when it will be released!
Actually I’ve had a full V8 license since the start of all this (never beta’d 8 at all like I had for 6 & 7).
It’s still not showing the update even with the dropdown in general set to include candidates. I had to find a download link in another thread and manually download the update and replace the 8.0 purchase build manually.
8.1.23318.13002 Installed.
PrintDisplay Still Broken, still takes a bunch of fussing with when multiple files are open to get stuff them in sync.
PDF export still very slow regardless of “raster” or “vector” settings compared to a V7 print (using print and the OS supplied “use PDF” dropdown in the print dialog).
Multipage PDF export goes from really slow to horrifically slow, like give up 10-15 minutes or more to print 5-8 pages to PDF, and the same file under V7 does that in maybe 30 seconds.
Still not sure where the standard MACOS print dialog vanished to, as I’d gotten quite in the habit of using it’s little PDF dropdown to “open in preview” which was very handy when outputting multple rhino docs to PDF to bolt them into a singe “package” and reorder if necessary, then save the combined one at that point,
Yeah I think they are resolving these issues on V8.2 builds that’s why there wasn’t any big fixes to report on this week’s release candidate.
There is a lot of work to do and Thanksgiving holiday is this upcoming week so I’d expect more solutions early - mid December. I hope so.
Hi @LewnWorx,
On Rhino for Mac 8, under Rhino → Settings → General on the Mac, pick the Update Frequency as Release Candidate.
This week Sr1 is expected to ship.
Sr2 will because the Release Candidate, and these issue should be fixed there soon.
It seemed so odd when Rhino for Mac came out 10 years ago, and now I miss it too…
But there will be a way to print and have the PDF view open immediately after printing.
That issue has already been logged.
We can duplicate the slow printer here. A developer is looking at it now.
Like @tay.othman has pointed out, the Thanksgiving holiday will make the fixes take a little longer than usual.
Thanks again for reporting.
Sincerely,
Mary Ann Fugier
Sorry if this has already been logged but another print bug I’m finding is that when printing a single sheet with Rhino PDF (it takes forever, as mentioned) but it will export portions of the drawing as vector and other portions as raster
You can see here it looks good from afar:
But is raster upclose:
Yet, other portions of the same print are vector:
It may be worth noting that the vector portions are “on top of” the layout as an exploded title block and the raster portions are within a detail view on the layout.
I was getting away with saving my files down to R7 and printing from there until I remembered that R7 only supports vector prints in wireframe display mode (or am I missing a setting?)
So, the elevations I set up and section cuts won’t work in R7 since all the wires come through.
Perhaps I’m missing something in R7, please do let me know if that’s the case.
Otherwise I’ll just eagerly anticipate the printing fixes.
Thank you all!
EDIT: I believe the Raster/Vector hybrid is a result of the viewports being derived from a Shaded viewmode (I thought they were Technical based, my bad)
Yes, Rhino tries to figure out what details it can output as vector and uses vector for those. Other details that Rhino can’t determine as being ok for pure vector get output as raster.
A post was merged into an existing topic: Multipage Rhino PDF always raster
Uploading: 20231121224423.jpg…
RHINO 8 PDF
@WATER85
Thanks for image.
Can you post a small, sample 3DM for us that we can repeat this issue with?
And what are the steps that you are using to see this issue?
Rhino 8 for Windows or Mac?
We appreciate the report.
Sincerely,
Mary Ann Fugier
Hello @mary
I have attached a test file to illustrate the linetype-related issues. In my view, these issues are not necessarily bugs; rather, they appear to stem from a suboptimal design decision during the implementation of the new Linetypes. Specifically, the scaling behavior between model space and layout space renders them impractical for generating printable drawings.
a) Linetype segments are always defined in either Model units or just mm, for the millimeters option, none of these options actually scale properly when viewed in a layout page.
vs
b) Linetype Thickness: I was initially very excited about this addition, finally Rhino has a comparable (even better way) to AutoCAD’s Polyline Widths, the problem again, unless it is set to pixels, It will never scale to match the detail’s scale on a layout
I think it is an urgent task for the team to figure out the real specific usability for the new added linetypes because I believe they still need work.
See Attached
Scaling Linetypes.3dm (87.1 KB)
Thank you