TEcHNOpls Posted April 20, 2020 Share Posted April 20, 2020 This may be connected to the other bug I added regarding masks. I have a file that when exporting unmerged, gives errors where layers overlap, when it's flattened no such errors happen. Multiple layers exported (400% zoom): Group pixel layers, disable other layers, merge visible, enable other layers, export (400% zoom): "I'm a lumberjack and I'm OK, I sleep all night, and I work all day..." Link to comment Share on other sites More sharing options...
Staff Chris B Posted April 21, 2020 Staff Share Posted April 21, 2020 Hey TEcHNOpls, Yes this is the merge selected issue we've been getting reports of. I've updated the developers. Sorry. TEcHNOpls 1 How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
TEcHNOpls Posted April 21, 2020 Author Share Posted April 21, 2020 I think this is existing for the last 1,5 years already, hopefully it'll be fixed before next release. "I'm a lumberjack and I'm OK, I sleep all night, and I work all day..." Link to comment Share on other sites More sharing options...
TEcHNOpls Posted April 21, 2020 Author Share Posted April 21, 2020 If you need more files for that, I can upload this one too. Chris B 1 "I'm a lumberjack and I'm OK, I sleep all night, and I work all day..." Link to comment Share on other sites More sharing options...
Staff Chris B Posted April 21, 2020 Staff Share Posted April 21, 2020 Thanks—I will let you know! How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
lepr Posted April 21, 2020 Share Posted April 21, 2020 (edited) 9 hours ago, TEcHNOpls said: I think this is existing for the last 1,5 years already, hopefully it'll be fixed before next release. I don't think your example is of the recently (1.8.x) introduced problem with Merge Selected command that Chris mentions, where the result is affected by the order of selection of the layers being merged. Unsightly artefacts can suddenly appear when exporting a layered document at reduced scale; that's a consequence of how each raster layer is first scaled by resampling and then the resulting layers are composited. The resampling of a given layer can introduce artefacts in that layer, and then blend modes, live filters and adjustments can intensify the visibility of these artefacts, and then the mess is composited and sent to a file. As you've discovered for yourself, best practice with raster artwork is to pre-flatten when exporting with scaling. Obviously, you can keep the layered document for future editing; just don't directly export it unless the export is at 100% scale. If you're not scaling when exporting, I'd be interested in examining a problem document that you are happy to make available. Edited April 21, 2020 by anon2 Link to comment Share on other sites More sharing options...
TEcHNOpls Posted April 21, 2020 Author Share Posted April 21, 2020 If this is the case, then it's a very bad way of exporting indeed. With so many layers getting rescaled first all sorts of artifacts can appear. I was under the impression it's merge then scale, which seems the only logical way to do it. "I'm a lumberjack and I'm OK, I sleep all night, and I work all day..." Link to comment Share on other sites More sharing options...
lepr Posted April 21, 2020 Share Posted April 21, 2020 37 minutes ago, TEcHNOpls said: If this is the case It's definitely the case. 37 minutes ago, TEcHNOpls said: then it's a very bad way of exporting indeed. With so many layers getting rescaled first all sorts of artifacts can appear. Yes. 37 minutes ago, TEcHNOpls said: I was under the impression it's merge then scale, which seems the only logical way to do it. It's easy to create tests which prove that the app scales then flattens. Anyway, now that you know what is happening, you can choose to flatten then scale. Link to comment Share on other sites More sharing options...
TEcHNOpls Posted April 21, 2020 Author Share Posted April 21, 2020 This needs to be fixed then. Simple as that, otherwise it defeats the purpose of the whole app (or a large portion of it). "I'm a lumberjack and I'm OK, I sleep all night, and I work all day..." Link to comment Share on other sites More sharing options...
Staff Chris B Posted April 22, 2020 Staff Share Posted April 22, 2020 Both issues have been logged and linked to your posts. I think anon2 is actually right and I remember seeing these halos with you last year TEcHNOpls 1 How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials Link to comment Share on other sites More sharing options...
TEcHNOpls Posted April 22, 2020 Author Share Posted April 22, 2020 Ye, I felt like my posts were ignored to make it in time for releases. "I'm a lumberjack and I'm OK, I sleep all night, and I work all day..." Link to comment Share on other sites More sharing options...
TEcHNOpls Posted September 2, 2020 Author Share Posted September 2, 2020 Still not fixed in 1.8.5.703 "I'm a lumberjack and I'm OK, I sleep all night, and I work all day..." Link to comment Share on other sites More sharing options...
Recommended Posts