-
Posts
3,328 -
Joined
-
Last visited
Posts posted by Pauls
-
-
that's a similar spec to me - Publisher is very resource hungry and 9GB is not unusual especially for an image heavy document like yours.
If you do ever get a crash report from the release version please add a note to this thread. -
@Sporkmanstudios- I've not been ble to recreate the lagging you are experiencing. Howwever I would be interested in seeing any crash reports you may have - you can upload then to the same location as the tiff files. You will find the crash reports in the %AppData%\Affinity\Publisher\1.0\CrashReports\reports.
Finally what cpu does your system have ?
-
Do you create affinity assets from these?
The beta can be considered a seperate product - you would have to import those seperately. It can be found here :- -
Curious I tried your sample file and that was working fine for me. If it happens again please get in touch
-
@Sporkmanstudios - we would need the linked files to investigate could you upload them here. This is a private URL.
As mentioned the very latest beta has some improvements in this area and it would be interesting to know if performance is better in that version for you
-
@DougMcould we get a copy of the Feast of Flesh font you are using for testing
-
This is due to the text frame being on master page - We've logged an issue for that
-
Can you upload the file here.
Have you tried deleting and recreating the table ?
-
the example file works perfectly for me did you generate the PDF from that?
-
thanks - that's been logged
-
-
is it placeholder text?
-
Firstly choose the correct Bugs forum, according to the application you are using (Designer/Photo/Publisher), and the Operating System you are using. In that forum state the following
-
Are you using the latest release version?
(here's how to check) -
Can you reproduce it?
(if you cannot then we may struggle to also, making it even harder to fix) - Does it happen for a new document? If not do you have a document you can share that shows the problem?
- If you cannot provide a sample document then please give an accurate description of the problem for example it should include most of the following:
- What is your operating system and version (Windows 10, OSX Mojave, etc)?
- What happened for you (and what you expected to happen)
- Provide a recipe for creating the problem (step-by-step what you did).
- Screenshots (very handy) or a screen capture/video.
- Any unusual hardware (like tablets or external monitors or drives that may affect things) or relevant other applications like font managers or display managers.
- Did this same thing used to work and if so have you changed anything recently? (software or hardware)
-
Are you using the latest release version?
-
-
Thanks for the report I have logged that
-
You could try udating the driver for the intel graphics or even disabling it in device manager and seeingif that cures the problem.
-
Would it be possible to get a copy of the log.txt file found here :- "%AppData%\Affinity\Publisher\1.0\Log.txt"
if you could grab it just after doing the mask operations shown above please -
It is a problem with the Gaussian Blur - i think the only work around at the moment is to rasterise that live filter layer
-
Could you upload a sample file hereand I'll see if I can recreate it
-
I think the frame needs a crop or scaling applied before you start replacing images
-
-
Either is fine - but linked with all the associated images will be better for me.
-
Its a display preferences option - make sure its disabled

-
I think this is related to your other error and probably the same cause.


Dashed border not exporting properly to pdf
in V1 Bugs found on macOS
Posted
Aligning to centre does solve it - I've also logged an issue to see if we can fix the PDF export