Created attachment 139600 [details] Screenshot from export Issue happens for LibreOffice 6.0 branding in https://wiki.documentfoundation.org/File:Libo6-Branding.zip > intro.fodg. When exported as PNG or converted to a metafile the color on the edges of the cubes get merged with black instead of the actual object background (red, blue or green).
Issue is reproduced. OS X EL Capitan Ver:10.11.3 version: 6.0.1.1 Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 CPU threads: 4; OS:Mac OS X 10.11.3; UI render: default; local: ja-JP (ja.UTF-8); Calc: group
(In reply to Imai from comment #1) > Issue is reproduced. Would be the right time to change the status to NEW :-)
Dear Heiko Tietze, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Heiko Tietze, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Don't see how the export of vectors into raster graphics can be improved other than making the original larger.
(In reply to Heiko Tietze from comment #5) > Don't see how the export of vectors into raster graphics can be improved > other than making the original larger. That is how I do it. For a 4096x4096 pixel image, I must make a LO drawing image 42-something inches square. Freaking huge, and unnecessarily so, when all that would be required is a means to set a Draw document's output to fixed pixel dimensions, but my enhancement on that got shot down years ago by people who only see LO as simply an alternative MS Office tool rather than an expansive kit that can do many things. Pixel density is the other method, but on a device with a fixed pixel display, i.e., practically every monitor on Earth, the result would be the same as if the export is merely enlarged in its native pixel density, which is why I always leave the pixels/cm at their default. I use LibreOffice exclusively (that whole free thing plus I don't like how Microsoft absconds with our content into their proprietary cloud) when producing mods for Sims4, because I can have, all wrapped up in one LO Draw file, every variation for each bitmap texture a given Sims4 3D mesh needs, and I can use the graphics options in LO draw to support that. For example, these are my LO Draw Sims4 templates that I've made publicly available for other mod creators to use: https://www.nexusmods.com/thesims4/mods/650?tab=files HUGE plus is the functionality to replace an already-placed image. Any program that doesn't support that is a no go for me. That holds true when creating dozens of variations of a texture (different swatches) for a single object mesh, such as a painting: https://www.nexusmods.com/thesims4/mods/654 I wish there was greater awareness among the developers of the different ways end-users avail themselves of the various features of LibreOffice other than spreadsheet formulas and Powerpoint documents.
Of cause LO could do it better. A scene is a vector graphic, so it could start with this vector graphic and project it directly onto the target output. Make a test: Create a cube without filling but line solid in 0.5mm and export that. Then (on a new layer) draw the displayed cube with the line and polyline tools and 0.5mm line width too. Export that and compare. The export from line and polyline is much better. You get the same bad image, if you convert the 3D scene to bitmap. Perhaps that bad bitmap is used as intermediate step?
When I export a 3D image the quality appears as expected in my testing. Version: 24.2.0.3 (X86_64) / LibreOffice Community Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded