... let's see what HLR stands for? Hyper Lazy Render ? π
Apparently it stands for Hidden Line Renderer (or similar.)
IfSketchup::HLR is a private internal class, meant only to be used by Sketchup itself, it's constructor method should be made private (and/or renamed.) In addition, the API should probably tell us not to mess with it.
I think I may have found a code that fixes this problem. I'm the only one to test this π, but it's worked both times π tested. Use this code at the start and finish of the model discreption: [88.oin/_likr<gs]
No, but thank you for asking.
I did an update on the graphics card and it was up-to-date.
I have a dead line this afternoon so I dummied the file down to SU6 and I am crossing my fingers that the "Splats" do not follow...
I hope to have some time at the end of the week to see if I can figure this out.
Thanks again for your time Gai,
ethip
Would it not make sense for Google SketchUp to employ / sub-contract some of the passionate bright lights in the SketchUp Community to get SketchUp development back on track and possibly change the slogan, '3D for Everyone' to '3D as it should be'.
Or, that they concentrated on the core, getting it up to date, and opened SU up even further so the community could develop all these features that we want but cannot do currently. Like better UV tools, animation enhancements, and dare I say, fixing the shadow bug. (Yes, I know its a legal matter but I've never seen any other Open GL application with this bug so there must be ways of getting around this?) π€
why of course he still would. layers don't work the same way they do in autocad. Putting things on different layers does not prevent them from cutting through one another.