I have a rather unusual problem, or at least I couldn’t find it on the forum. Well, when using rhino pdf when exporting above a resolution of 120 point / inch, it does not print textures in the project, as if it was able to export them to a certain point. I have no idea how to deal with it.
thanks for the answer, that’s how it is for the second question, but for the first one. It’s the textures that are not exported from rhino in their entirety. As if when increasing the resolution it was not able to 100% export textures to pdf
1 st question
a little more texture. 120 did the job, at 130 was te same problem
abaout big picture of my works,
Drawings are mainly used for communication with subcontractors, so I don’t need everything to be 100% the same as in rhino, I mean that if I actually insert something there, e.g. stone 1:1, so that I can send it to the subcontractor with dimensions and signature. I do not want to use add-ons in the form of adobe illustrator. I try to make the project 100% rhino-processed to save time on preparing project guidelines
i have no idea, this are my two main problems with layout, can find any solution, triend on geforce and redeon, maybe textures are too big like, rhino can’t handle 23 textures that are 2032 x 720 pixels each
It’s something to do with the size ratio versus the dpi plus maybe the source texture data…
Obviously it would be nice if Rhino made the easier to fix.
You might get better results using ’ -viewcapturetofile ’ and just creating a nice image to print to pdf afterwards with a different software dialogue maybe windows version idk.
Yes, that’s true, but for a long time I’ve been trying to embrace my work flow in rhino, so that one model is suitable for visualization for the client, and then for preparing drawings for the subcontractor, possibly sending the model to him, and everything is best for it to work in the worksession and blocks: D
I will definitely try, but this project was created for rhino 7 and I didn’t want to transfer everything to rhino 8, I decided that I would somehow figure out what it would look like and try to handle later projects on rhino 8. I was hoping that after all there is a solution in rhino 7 that I don’t know about because I have a few more projects started on rhino 7 and I don’t want to redo them
Yeah understandable. Maybe you can upload samples for others of us to mess with and recreate or isolate the issue?
So, far I can only have theories similar to what I’ve experienced, but would be interesting if this issue can be isolated to any specific combinations of settings, etc.