Hadriscus

I have to know whether or not this is going to improve in future versions. Is there a roadmap I can look up ? I'm used to Blender's more open development style, and I understand not every developer does that, but at some point there needs to be clarity. What are the plans ? Is this area likely to improve ? Thank you, Hadrien

Hi, thanks for the suggestion! Choosing nearest neighbour does just that, but doesn't appear to change the definition of the images. At full zoom, the preview images that appear in place of the "real" ones are made up of blocks 8px wide, when they should be 1px (because the linked images match the document resolution and are not scaled). I understand this is not the support forum, but I can provide the file if you think there is something worth trying. Thanks ! Hadrien

Hi all, forgive the clickbait title. I use a GTX970 which admittedly is far from new, but canvas compositing is not just sluggish, it doesn't update at all my linked resources when I zoom on the image, even after I've let ten minutes pass. On the other hand any compositing software works smoothly with composites that are much more complex. It seems like it's trying to recalculate everything (including live effects such as blur) every time I change the zoom level, every time I move a layer, basically any action causes a full recalculation. Is there even any caching going on? any plans to move away from OpenCL? (which is a discontinued standard) The card has 4Gib of memory by the way, which is well enough to handle a single A0 150DPI image (as evidenced by most of my other pictures which lack live effects and work somewhat more smoothly). Even selecting layers in the layer stack stops working half the time on that specific image. I'm trying to get work done and it seems mad that even waiting for the canvas to update does nothing. I'm not sure what more I can do? I will upgrade my hardware at some point in the near future but right now it is a daily struggle. So I guess my question is, are there plans to improve canvas updates and general reactivity in Publisher? Thank you

There's hardly anything more I can do, so I'll just let this sit here. The wetransfer link expires tomorrow, to anybody willing to investigate this : hit me up if the link is down by the time you read this. Cheers, Hadrien

Well then, let this thread be my report

I believe this is the place to report bugs ? is there another ?

Fantastic @Wosven. Thank you so much for investigating this ! I was at a loss. So I rasterized the whole group for convenience and it worked. I won't be doing any more adjustments on this so I feel safe just baking it into the layer. What is it about the curves adjustment (or the way the layers were arranged) that makes the bleed blank, do you have any idea ? I don't really see a connection. Is it a bug, or something that's expected (given the initial layer arrangement) ? Hadrien

Guys here is the file. No clipping is going on as far as I know. https://we.tl/t-TUsFjhG57k

Thanks for the suggestions. All these would show in the viewport too though, wouldn't they ? I don't see how something would affect only PDF exports. Do you care in taking a look at the file by any chance ? On the attached picture, you can see page number four, left half of the problematic spread (misleadingly the layer group is named P3). It contains the main text on the page, as well as three groups for the sea turtles' endangerement level graphic below. The page is constructed the same as all others, and does not contain a master page at all. As you can see the bleed is full of interesting pixels. The PDF export however, looks like this : All other pages look like this :

Publisher 1.10.1.1142 on Windows 10 PDF export for print outputs a fully white bleed area on pages four and five instead of the colour that's supposed to be there, whereas all other spreads include proper bleed. The file is on wetransfer, please come forward for the link, thank you Is this something I've caused unintentionally ? is it an option somewhere I checked by accident ? Btw some linked documents (PDFs specifically) will still not render on export, I assume this is a different issue ? Thank you Hadrien

Hi, 1.9.1 crashed on saving, now 1.9.2 crashes on resizing inline tables. Resizing them while they're floating works fine, so that's what I do, and then only do I cut&paste them inline. Additionally, on reopening my document two out of my four tables (that each occupied a page) have disappeared. One was invisible (supposedly because it was slightly too big for the page it was on, even though I had not toggled it invisible), and I was able to recover it by cut&paste, resize and "make inline" again. The other one does not exist anymore and all the content that came after it is simply gone. I inspected all the subsequent pages, they're totally empty ! That's several pages of work, gone ! Before noon, when I saved and closed Apu, everything looked fine. How can a file look fine on saving and then look different on reopening, with loss of information ? These problems have been going on for several months now and what I thought was stable quality software is turning out to be completely unreliable, has been making me miss deadlines too many times. I can't spend my time reporting bugs, uploading log files, I just can't. This is unbelievable really. So right now my mindset is to go look for an alternative that's reliable. I don't need anything fancy, no bells and whistles, just that it works for what it's supposed to do. Obviously I don't have time to migrate now, so I'll have to put up with these issues, finds workarounds, walk this landmine until this particular job is done. Cheers, Hadrien Get yourselves some quality control ! something is wrong with your development practice.

@Jon P it appears to work ! Thanks ! Now, APu crashes when I try to move a table. Will report when I get the time.

Yay thank you !! I'll be trying out as soon as I ship my current work, so in a few days.

Hi @Jon P , I saw 1.9.2 was released some days ago. I couldn't tell from the release notes whether this particular bug had been fixed. Would you be able to tell me ? Thanks, Hadrien

Thanks @Old Bruce ! it's an improvement, now my 6 chapters go 1, 2, then start over at 1 until 4. Seems like I have to wrap my head around this numbering thing still, ... what could be the reason it restarts after a while ? should I upload my file instead of beating around the bush ? edit : there's something super fishy going on, and I wonder if that's not related to my file corruption issue (logged after 1.9.1 release) : one chapter appears twice in my TOC, on pages 10 and 14. It's actually on page 14 so I have no idea what's going on. I'll investigate some more...