Hi there - I’m running into an issue where exporting a higher res PDF causes Parallel Line Shading to break at certain points horizontally and vertically; below is a screengrab of what I see after exporting a PDF, this line break is consistent through all of my geometry and is not visible in my Rhino viewport, so I suspect it’s not an issue with the model but the line styling itself, as if it started to repeat itself after a max distance - is there a workaround to this, possibly a setting I overlooked?
do you have a test file you can share with us?
LineShadingBlueprint.3dm (7.1 MB)
File attached - I am attempting to export this to a high DPI raster output for print; I kept the output to 11x17" and bumped the DPI up and preview in Illustrator; the line breaks seem to appear in the PDF.
Thanks for sending the file. You’ll have to include the viewport mode .ini file as well to make this work on my end.
Here it is…there is an image file for the background. Attached if you need it.
I’ve attempted a few other settings and the line splitting is still happening. 
Blueprint.ini (5.3 KB)
I see and can reproduce the issue you are having printing >300 dpi
If you are looking for a workaround, you could make a ViewCaptureToFile, which doesn’t seem to suffer from this issue.
Side question: 30000 dpi? Why would you want that? that will create a massive file size.
RH-86764 Print shows tiling issues in parallel lines texture
ViewCaptureToFile should produce the same results. High resolution captures are done by tiling a bunch of smaller captures together. Both ViewCaptureToFile and Print as raster use 90+% the same code.
Let me clarify…we are attempting to print a large scale version of this. The final will be approx 6m x 3m. I attempted to keep the Print setting to 11x17 and upscaled the DPI and not lose resolution.
I just tried the opposite - I changed my output to the final size, 6m x 3m, lowered DPI to 300 - and I still have banding splits at certain intersections as if it’s a repeating map. It’s not the DPI as the lines break eventually even at 300dpi.
Interesting; is the final image the expected resolution?
I misspoke.
Changing the dpi does result in the line breaks moving; if I attempt to ViewCapturetoFile at the full size of 6x4m @ 300dpi, no file is created; the program behaves as if nothing happened. I tried knocking it down to 3x2m @ 300dpi and worked, but the line breaks were back. They moved around on the page, so the horizontal breaks are gone, but the verticals are still there
I don’t think you need that much pixels though. Did you contact the company that is going to print this what their max resolution is for that size? it is often much lower, and you can probably get away AI upscaling it.
We’ve reached out to them for a test print while I troubleshoot the split lines. I will attempt to output the hatch lines separately and comp something together.
Here’s what I don’t understand though. Even if I set the dpi to 300, the program just ignores my ViewCapture set to the full size of 6x3m - what exactly is the restriction here, is this my machine unable to process the ask or Rhino?
I kept dpi to 300 and the highest the program would actually output was 1/3 scale, 2m x 1m; which to your point - and I apologize, it’s pretty obvious that I’m not the graphic production person in my team lol - I feel like this output SHOULD be fine once we upscale to full size, but the onus is on me to get the hatch lines fixed if possible.
Thanks again for your attention!