LabVIEW
3D representation problems with some new graphical cards
The 3D graph is based on OpenGL and LabVIEW uses an OpenGL driver probably derived from an Open Source project. It’s perfectly imaginable that they regularly synchronize their version with the Open Source project so there is a very big chance that the 3D control in 2012 is quite a bit different than the one in 2018. But it is also very likely that it is not as simple as replacing the according dll in 2012 with the one from 2018 due to binary incompatible changes in the dll abi.
Unfortunately we are moving more and more into a software as a service model where compatibility between components only gets guaranteed for a limited time, sometimes as little as one or two years. The 2012 OpenGL driver couldn’t know about 2019 3D graphic accelerated video drivers and the modern drivers don’t care as much about backwards compatibility if it complicates the development substantially.
@JohnHug wrote:
Many thanks Bob and Rolf. In synthesis I suppose we need to buy the new LV release ...
You could evaluate the new LV release first (7 days). Upgrading is usually a good think, but if you know it fixes the problem it's probably easier to sell to management.
Just for fun, I'd try to make the text\grid\etc. not black on a black BG. Make it very dark... 0x000000 might be something special on some cards...
It seems to relate to alpha blending, handled differently. Can't reproduce it (maybe my card, maybe my LV version)...
Search LabVIEW like a graph!
@JohnHug wrote:
Regarding the 3D concern it's not only a problem of money to buy the new release. We are in the medical field and our products are 93/42/ECC certified while our company is ISO13485:2016 certified: for these reasons every change must be verified, validated and documented. Now, one thing is a small change in a very limited portion of the software, another is a total rebuild of the executable and installer for our customers with a different development tool (even a new release): it means to re-verify in laboratory and re-validate on the field all the functions and parameters calculation of our medical software (with all the related amount of papers...). In any case if there is no other way...we will do.
I figured that might be the case.
@JohnHug wrote:
Dear Wiebe, many thanks. By the way I bought your pdf toolkit for LabView some time ago.
Thanks for that.
I use it a lot myself. Our customer actually has 3D objects (rotatable) in the PDFs. Too bad Acrobat made a mess out of the renderer (u3d format) and than decided not to finished it because it wasn't used that much. *sigh*.
See attachment. (Trust once, press the question mark. Acrobat Reader only, AFAIK).
Of course, I have to keep explaining you can't rotate anymore once it's printed 😂.
