This is on my list to add as an application level setting so you don’t need to remember the test command. I’m hoping to add this during the V6 service release cycle.
https://mcneel.myjetbrains.com/youtrack/issue/RH-43088
1 Like
One of the “side effects” I have noticed is that when the scale is set to less than 1 - say around 0.6 which I like for surface edges - the curve display color gets considerably duller. It is fairly dramatic with pure colors against a dark background, and I am discovering this just now as I am starting testing of V6 with our lasers.
I understand that when the lines get thinner, they emit less light, looking effectively duller… The bright colors in V5 enable me to easily see if the student has applied the correct color - i.e. 0,255,0 for ‘green’ and not 0,200,0 which the laser will see as a different setting. So I guess I’ll end up toggling that setting on/off according to what I’m doing, unless there will be a separate setting for curves and surface edges.
–Mitch
1 Like
I’ve noticed it switches back to default when trying to use viewcapturetofile. So the images get the thick lines again…
Yes Mitch this value is way better also for my eyes.
I’m not sure why but v6 have many issues / differences with ui/vieport look v5 maybe was bit jagged but way much crisper v6 is indeed smoother but imho it is somehow overscaled and maybe not blured but also not crispy enough
1 Like
Yeah, I keep trying to find a good setting, but I haven’t really. I do notice it’s also different between different cards, my 980 at work is a little better than my 780 at home. But neither of them have a nice an antialiasing as V5, I still see "jaggies and some fuzziness no matter what I do. It does get a bit better if I override the max Rhino 8X setting in V6 and force 16X via the driver but still the same as V5. I’m not sure if you’ll be able to see the difference in the following downsampled images, click to open full size.
V5:
V6:
The lighting is better in V6, V5 looks somewhat dull in comparison. But the edge/iso quality is nicer IMO.
1 Like
Hi @Pascal - since the WireThickness has been added to the advanced options in SR4, is there an non-test command-line access to it, or should we plan to use “testWireThicknessScale” ? ( there is no Enabled option in it anymore like before, so I guess it’s always on now? )
thanks,
–jarek
Hi @pascal, @stevebaer
It seems like the custom wire thickness set by this command ( _testWireThicknessScale ) somehow gets ingored for Curve-type objects when doing screencaptures that are bigger size than the screen (not sure what the actual treshold is, but generally “larger” captures). Please see samples below:
Could that be tweaked so it works with any resolution screencapture? This functionality is great to make hi-res captures that keep nice and thick edges/lines.
thank you,
–jarek
2 Likes
Hi @Pascal, wondering if you can see this problem on your end (and if so, if its reasonable request to fix).
thx
–jarek
Hi Jarek - checking now, thanks…
I do see it. Now… question is, what to do about it…If the command is genuinely useful then it should be made real and it would then make sense to get everything working but if it remains a test command, we’ll probably be at the mercy of Steve or Jeff to get things working with it as time and inclination allows. If you see what I mean.
-Pascal
Hi Pascal, good point.
I think it was first designed to deal with the discrepancies with AA-line thickness appearance in V6 and does the job well on most systems. The secondary use (which I understand may not work smoothly everywhere) is using it to get good line thickness on hi-res screencaptures, while this functionality is still buggy in V6 (by scaling the lines proportionally to captured view size).
If this is an one-line code fix/omission, why not; if complicated I understand that this may not be a top priority.
I personally find this very useful to have.
thanks for testing!
–jarek
This isn’t a one line fix.
1 Like
FWIW, I’d argue that this is not a test command since it is a setting in the advanced options.
I’ve put it on the heap (RH-49578) and set it to be fixed in the ‘future’.
Hi @Wim, yeah, it is advanced non-test setting in Rhino indeed. Only command is still a “test” one…
As a clarification to your YT item - it is only curves that are not properly scaled - edges/wires seem to be OK.
(on my screenshot edges look thinner because of much higher resolution…but they maintain 5px width)
Also, this happens not only when Scale is > 1; even with Scale=1 any pixel size that is bigger than screen causes the curves to ignore the wirethickness setting.
thanks for logging it.
–jarek
Thanks for the clarifications! I’ve added them to the YT item.
Wire thickness scale was really just intended to help figure out cases where users were complaining about the wire display in V6 being too thick. I think this issue is sorted out now and we could probably just get rid of the wire thickness scale hack… except now Jarek is using this to work around a bug in view capture.