Just loaded a gltf demo document (will attach) and got this helpful message: warn:vcl.opengl:3356:348:vcl/source/opengl/OpenGLContext.cxx:458: OpenGL debug message: source: API, type: error, id: 2261, severity: high with message: glDeleteShader has failed because parameter <shader> specifies the name '28' which is a program object instead of the expected shader object (GL_INVALID_OPERATION) I wonder if that is a more general issue outside gltf ? warn:vcl.opengl:3356:348:vcl/source/opengl/OpenGLHelper.cxx:431: GL Error #1282(invalid operation) in File C:/sources/master/vcl/opengl/gdiimpl.cxx at line: 1887
Created attachment 118502 [details] a duck -> but should it truly be blue ? =)
Presumably in the MCW / libgltf work; not urgent - now an experimental feature - but would be good to chase.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
I guess we now just read the fallback PNG from this document on current master (where GLTF is gone), so it's hard to reproduce the problem. Should we close this?
Yep - makes sense - thanks =)