Smaxx Posted June 21, 2019 Share Posted June 21, 2019 (edited) Hi, I'm still testing the waters with Publisher after using both Photo and Designer on and off since they became available for Windows (mostly for simple edits, fixing images, etc. for composition stuff). So after some initial issues with getting the layer sorting right (I'm still having massive issues trying to move a rectangle for clipping into a Live Filter layer for example), I stumbled over some weird issue and I'm not really sure what the issue is. Is this a bug in Publisher? So far it happened multiple times on new/fresh documents; there's no difference whether I'm editing a master or regular page. First I've tried an approach like I've seen in the recent live stream – since I found it very intuitive: Yeah, that looks… strange… The gaps between the "tiles" depend on the current Box Blur Radius and change with it. In my example, it's set to 50px. Also note the white blurring/vignette on the border. So at first I thought this could be some odd graphical artifact, but it's also in exported images. The mask I've included has no influence on this though. Also it seems that sometimes I'm able to "fix" it, just by dragging the Live Filter outside (as a root element) and then back in. Oddly enough, if I change order (so the image is above the Live Filter), the image is no longer blurred as expected, but these gaps are still there: The only guaranteed way to fix this issue for me seems to be moving the Live Filter all the way up as a root element: And this is where the interesting part starts! Sometimes, then dragging the Live Filter back inside the Picture Frame makes it appear (somewhat) correct, again with the odd vignette outside: Changing the order once more, just for being a completionist (now working fine as far as I can tell): Also noteworthy this doesn't apply to the Box Blur filter only, but some others as well. I'm not 100% sure if some filters are just immune to this (like Voronoi) or if it's really just coincidence. Either way, I've also attached the document in the broken (artifacts.afpub) and fixed state (artifacts-fixed.afpub) – and sorry for the size, didn't notice it at first and didn't want to redo everything. Edit: Just noticed this also happens with top level images and live filters, so doesn't need any Picture Frame to trigger it. Would really love to know if this is really a bug or I'm just doing something really wrong. Thanks P.S.: In case it matters, I'm running Publisher 1.7.1.404 with an Nvidia GeForce GTX 1080 on Windows 10 x64 (1809) with driver version 430.86, but this doesn't seem to be a driver/display issue only. Edited June 21, 2019 by Smaxx Quote Link to comment Share on other sites More sharing options...
Smaxx Posted June 21, 2019 Author Share Posted June 21, 2019 Ah, just seen another post where it's recognized as a known issue, so guess this can be ignored. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.