Cool VL Viewer forum

I've been getting these crashes the last 2-3 versions of your mesh viewer - the non-mesh version has been fine so far - is this error message related to the problem in this thread?
https://lh3.googleusercontent.com/-Al-x ... 0crash.png

If not, let me know I'll start a new thread with a log.

This is a driver bug, I'm afraid... Try downgrading to the previous stable release of your driver (Nvidia v290.* drivers are full of bugs. I myself downgraded to v285).

Asking only because I'm driver-illiterate...

Why would a driver issue cause a problem with the mesh version, but not with the older non-mesh version?

Because the renderers are completely different (SG v1.5 renderer for the Cool VL Viewer v1.26.0, mesh viewer v2.6 renderer for the Cool VL Viewer v1.26.2) and are using different OpenGL calls and shaders. In any case, your issue got *nothing* to do with memory safety checks, so please stop posting about it in this thread !

(I had originally posted this in the wrong forum by mistake...deleted there and reposted here.)
Recapping from posts in another thread.

My error message:
https://lh3.googleusercontent.com/-Al-x ... 0crash.png

Henri's response


My reply (new, today):
Here's a screen of my driver version: http://i.imgur.com/cSO7g.png
These are the drivers that have BEEN on my system - I did not upgrade to 290.* versions.

Log will be forthcoming once I provoke another crash.

As already explained, this is a driver bug. I can do nothing for it. Please, complain to NVidia...

Okayyyyy, I guess I won't bother with the log then.

You said 285 was stable, and that I should backlevel from the 290 series.

Primariily, this was to point out that I was already ON the 285 "stable" series, and secondarily to serve as a pointer for -other- people who may come by with the same problem. This thread makes it easier for them to find it.

Yes, i can complain to nvidia. You know as well as I know what they'll tell me: Update my drivers. To ones you've already stated are buggy.

Frankly... How difficult is it for you to Google a bit ?...

You could find the confirmation this is a known Nvidia drivers/Windows bug, and even a suggestion for a work around...

Before posting a bug report, please folks, DO make a search on the web for your issue: you might find out it's not the viewer which is at fault !...

Keep this in mind: the more time I spend replying to such false positives, the less time I spend developing, improving and bug-fixing the viewer !...

Note: first, out of topic messages merged back into this new topic.