Gabe

Hi @Mark Downey, Sorry for the delayed reply. What if you create a new doc in Publisher, and choose File > Edit in > Photo or Designer. I wonder if that works.

Hi both, Do you get any crash reports?

Do you use any add ons to auto-save the image after it's been rendered? The only possible thing I can think off is that blender does not lock the file when it saves over it. We did have similar problems with Lightroom where we would get a "File type not supported". I believe we fixed this by notifying the user the files has changed, but due to the nature of the file update, we can't auto-update it in our app. Try to manually save the rendered jpeg rather than rely on the auto-save in blender. That will most likely work.

Most of the crashes we get recently are caused by Hardware acceleration ON. Let us know how it goes. Maybe you will get a crash report this time and we can see what's going on.

The one is crashing in a Windows dll (ntddll.dll). Try to run System File Checker (SFC): In the search box on the taskbar, type command prompt, press and hold (or right-click) Command Prompt, then select Run as administrator > Yes. At the command prompt, type sfc /scannow (note the space between sfc and the /). Scanning will take a few minutes. If SFC finds corrupted files and replaces them, restart your PC and check if the issue persists.

Hi @Joachim_L, This sounds more like a feature request than a bug.

Hi @Joachim_L, This is indeed a very unusual scenario (staring from having all the constrains active at the same time…). The compound parent doesn't really have a fixed size, but it's created by its child objects. So constraining to something doesn't really exist it's not gonna work. Anything can happen so what we see here is expected. It doesn't break the app, so it's just handling it in a (expected/unexpected) way.

Hi @Radd, Can you package this project up and upload it on this link? https://www.dropbox.com/request/Z4QJHHfOktsdnllvOolD

Hi @BillHans, Welcome to the forums. Can you attach a sample afpub file and/or a video of this in action?

Hi @Joachim_L, Thanks for spotting this. Issue logged. It only seems to affect Windows though.

Hi @StainX, Thanks for spotting this. Issue logged. I'm afraid there is no workaround for this - other than using Replace.

Hi @artokmt, Is this a document specific issue? Can you replicate it in a new document?

Hi @Ron Broach, Can you try to disable Hardware Acceleration in Preferences > Performance?

Hi @Thomahawk, Can you attach the afpub file?

Hi @Rcoopr, Can you attach a crash report? What GPU have you got?

Did you contact Capture One? Or was was the context of this "small zip"?

Just double checking. The "Automatically update resource…" in Preferences only takes effect for newly created/opened documents. If that was OFF and you turn it ON with a document already opened, it won't take effect until you re-open the doc.

I'm afraid no. Sorry.

Hi @Joachim_L, Sorry for the delayed reply. Issue logged.

Or you can choose a preset that doesn't force a new colour profile and ICC. PDF Digital will convert everything to RGB/sRGB while PDF for print will keep the current document working space/icc. Digital will take a very long time with your file, and it is expected.

Hi all, Sorry for the delayed reply. I can't replicate this issue either. Can you try to edit that image in Paint (or any other app) and see if that auto-updates it?

Hi @skmwrp, Sorry for the delayed reply. Did you manage to create a simple test case where this happens so we can have a look? I can't replicate this issue here with a basic doc.

Hi @muelli75, Sorry for the delayed reply. We are aware of both issues and they have been logged with our developers.

Your PDF is exceeding the maximum page size. (200inch at 72dpi) - your page size is 236inch wide . We have already logged an improvement to want users about maximum size.

PDF (digital - small size) takes a few seconds to export. What do you exactly mean by "can't export"? Do you get an error message? What's going on?