Jump to content
You must now use your email address to sign in [click for more info] ×

Komatös

Members
  • Posts

    3,117
  • Joined

  • Last visited

Posts posted by Komatös

  1. 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

  2. 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.

  3. 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.

     

     

  4. 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, 

  5. @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.

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.