When I output a layout as pdf, the output looks like the view on the screen, but if I output to a .jpg, the lighting is completely different. This does not happen when the resolution is set to 100, but it does happen at resolutions 200 and higher. It appears to affect layouts with rendered details - it did not happen when I tried it with a 3-light setup, just the default lights.
This continues to be a large problem for me, 3 years later. I can’t provide decent resolution detail pages to my clients. I’ll attach some files, and I notice this only seems to happen with rendered views (not shaded.)
I’ve also tried this in the new WIP with default settings and seen the same results.
Hi Peter,
Sorry for the frustration of this issue.
My test are attached below.
Like Pascal, I am unable to duplicate it here with your model, your setting and my Rhino. I remember something similar, a few service release back, but I believe it has been fixed.
So we we have a few more questions for you.
Go to Help and About Rhino. What is the date and SR release you are using?
If you could send us a screen capture of the About Rhino, the Rhino screen & title bar, and the Options → View → OpenGl page, that would maybe give us more to go on.
What is the Windows OS? I have Windows 8. You are using the Windows Image file out driver. I also used it.
Do you see any different results if you use a PDF driver like Adobe or PDF995?
(You can print to a Adobe PDF in with Acobat convert the PDF to a JPG. Not a great workabout, but possible.)
Do you see any different result if you use the hard copy printer?
Let me know if I have missed anything here. It has been going on for a while.
Thanks for any additional information you can provide for us.
Sincerely,
Mary Ann Fugier
Hi Mary,
Version 5 SR12 64-bit
Windows 7 Ultimate
I use CutePDF and I’ve tried it on several resolutions & have not seen this problem happen at any resolution.
Printing a hard copy seems to work fine at ‘highest’ quality (though I’m not clear what that resolution is.)
The magic number seems to be 136dpi - everything is fine up to that, but at 137dpi, the weirdness starts happening (I just did a test with single-dpi increments from 130 to 140)