-
Posts
3,117 -
Joined
-
Last visited
Posts posted by Komatös
-
-
7 hours ago, Pyanepsion said:
... It would be interesting to know if the bug persists with the beta.
I've tried with the beta 1.9.4.1076 and the result looks like as in the retail version.
-
I use the 1.9.2.1035.
-
It gave me no peace. So I tested again with the Word document.
Since I had tested various things with the flow control and knew that the Word document was not automatically distributed to the pages, I clicked on the lower right flow symbol while holding down the Shift key. Nothing happened for a while and publisher closed.
And now a dump was also created.
And to test for yourself. An empty prepared publisher document and the Word file.
c6a2d658-d8f9-47b9-a97c-53810a1101c8.dmp Traffic Manager-President Edition.docx Master Frame Test.afpub
-
While looking for a solution to Pyanepsion's problem with incorrectly adding pages from files, I came across another bug.
I created a new document with overlapping pages for testing. Then I brought the master page into view and added a text frame to the left and right pages.
After that I had defined the text flow control. From the bottom of the right page to the top of the left page.Assuming that the text flow is automatically applied to all pages, I had placed a multi-page Word document. Unfortunately, the content was not divided smoothly between the pages.
So I had reset the process with Ctrl+z. Then I selected the master page again and tried to remove the flow control rule. The mouse pointer changed to the busy donut and about 3 seconds later the publisher terminated without an error message and without creating a crash report.
After that, I got carried away and started the whole procedure again, but without placing the word document.
That is, I had edited the master page, then back to the document page and back to the master page to change the flow control. Here too, the busy donut appeared and the publisher left without an error message.I repeated the game a second time. And ended with the donut.
-
Maybe! If I double click on first page to edit, publisher shut down with no error message.
In my case, however, the result of the document merge looks different.

-
Hello @ASR and welcome to the forums.
If the Designer does not open, renaming the profile folder might help.
Press Windows key + R. Copy or write %appdata%\affinity\designer in the input line and click OK.
There is a log.txt in the 1.0 folder. Please attach this file to your next post.
Rename the folder 1.0 to e.g. 1.0_old. This way, downloaded and self-created assets and other elements are preserved and can be copied back.
Restart the Designer. A new profile folder is created.If this does not help, a complete reset of the installation might help. To do this, hold down CTRL when starting Designer.
-
I had overlooked the zip file, sorry.
The bug is caused by a .NET component. Check with sfc /scannow if there are corrupted system files. Press Windows key + R and type sfc /scannow in the input line. Hold down Shift + CTRL and click OK.
-
You probably forgot to add a text frame to the left side of your master page A. And this was duplicated to the Document B.
-
I have followed the steps you describe, it works as expected for me.
Can you make a screen recording that shows your workflow?
-
OK, I see the dilemma. Since the workspace is larger than the document or page(s).
But this is not a bug but rather by design.That should be a feature request!
-
For me, Adobe Reader only shows the first and last pages as full pages. All pages in between are also displayed here with an offset.
Tested with a DIN A4 document at 71% with a screen resolution of 1920x1080.
-
0x00000050 or PAGE FAULT IN NONPAGED AREA
This Stop message occurs when requested data is not found in memory. The system generates a fault, which normally indicates that the system looks for data in the paging file. In this circumstance, however, the missing data is identified as being located within an area of memory that cannot be paged out to disk. The system faults, but cannot find the data and is unable to recover. Faulty hardware, a buggy system service, antivirus software, and a corrupted NTFS volume can all generate this type of error.
Possible solutions: Update Intel drivers, update GPU driver, test your memory, disable BitDefender for testing purposes,
-
Page navigation is recommended for scrolling page by page.

Since scrolling with the mouse wheel uses the Windows settings. Page-by-page scrolling via the vertical scroll bar is technically difficult to implement because the centre of the page is already changed when e. g. the view size is changed.
-
@MadMinstrel Can you please look into %appdata%\affinity\photo\1.0\crashreports\reports. To do so press Windows key+R and enter the bold text string.
If you have purchased the app in the Windows store, change the '1,0' to '1.0 (store).
There should be one or more .dmp file. The file with the latest timestamp will be fine. Attach them to the posting.
You also can try to install the latest beta. You'll find them here in the beta forums.
-
In the event of a BSOD, an error code and the process that triggered the blue screen are always displayed.
In addition to the error code and the process, it is useful to know a little more about the hardware used, especially CPU and GPU.
-
My CPU also goes up to 100% then drops to below 40% and then goes back to 100% in big steps. The blur level can only be deactivated in the time between 40% and 100%.
Photo can also only be ended then.
-
Is this a wireless tablet?
I use an Intuos Pen & Toch with BlueTooth and also switch between different programmes in the Affinity Suite and several other programmes. But can't provoke this bug.
If you are using a wireless tablet, it could be the power saving settings in the Wacom tablet properties.
-
When Windows shuts down with a BSOD. Faulty system files and/or drivers are usually responsible.
My quick tip. Press Windows key + R. Enter sfc /scannow in the input line. Hold down Shift + CTRL and click OK.
sfc scans the computer for faulty (system) files and repairs them if necessary.
-
Hello @Marcel Neumann welcome to the forums.
Can you tell us what other programmes you use; what version of Windows?
Are all drivers up to date?
-
I remember that another forum member had this problem a few weeks ago. But I can't find the thread about it anymore.
-
Hello @297Chrisc welcome to the forums.
I have carried out the steps as described. But with me the result is as expected.
-
-
Have you selected German or German ( Swiss ) in the language settings of Windows?
-
Hello @Stratosf8 welcome to the forums.
When the Text Styles tab is selected, click on the "hamburger" menu icon and deactivate the "Show Samples" menu item.



Publisher unexpectedly quits
in V1 Bugs found on Windows
Posted
It looks like it works with the beta, because the beta works stably after placing the Word document.