RobWu

Hi Walt,

After some more ideas popped up in my head, I did some extra testing before sending out a file.
It looks like the copy/pasting text from OneNote had some weird side effects in Publisher. Or it seems like that?

First I fiddled with the existing content and styles on the brochure, even deleting/rebuilding text frames and TOC. But still gave me weird results in the PDF TOC, like double chapter headers etc. There was some more fiddling, but I won't bore you with that....

But after this testing with the styles, text frames and text, I reverted back to the beginning and tried just completely redo the current text in the existing text frames for one chapter.
And just to remove all traces of formatting, I used Notepad to strip it all down within the route from Publisher and Notepad v.v.
After pasting the original flattened text back, and re-applying all the styles, the PDF TOC finally shows me just the chapter list.

In the brochure, the text blocks in the other chapters that are not replaced/fixed this way, the PDF TOC result is still the same with chapter and text in one 'block'.
So it is really has something to do with the previous pasting of text out of a OneNote Notebook.

Now I know what -more or less- is going on, I will rebuild the rest of the pages doing the same thing.
Although it's a bit of pages already, re-doing the text as stated above will still be fixed fairly quickly.

Or if this sound familiar, any tips are welcome to avoid this in the future. 

rob

<pedantry>
I know, I was just explaining both 'regular' locations for .exe Windows applications within Windows. Otherwise somebody could start looking in the wrong folders again...  
</pedantry>

As the links from @Pšenda will tell, is that the MSIX apps are a different 'beast' from the old .exe installers most of us are used to.

So simply said, every MSIX app (from the MS store) runs in the C:\ Program Files \ WindowsApps environment, and is heavily locked down by the OS after installation.
Good for preventing shenanigans from stuff like viruses or trojans, maybe not very practical if you want to acces the folder as a user.

If you don't like this behavior, switch back to the .exe installers Affinity is still providing for the v2 software. That will 'move' the application back to the regular Program Files or Program Files(x86) environment.

rob

Hi Walt,
That might be the best route to go here. I'll prepare a file later today for peeps to have a look at.
Like I said, I probably am doing something wrong style wise, or overlooking some other setting.

I'll be back....

rob

However, if you move back to the EXE/MSI installer, be very careful when the programs notify you that an update is available. When you click Download, and are directed to the website to manually download/install the new installer, it is very easy to choose the wrong one and get the MSIX version instead.

Because you probably installed a "sandboxed" MSIX version. If you don't like this type, try the MSI/EXE version.
This has been mentioned many times here on the forum, so try searching for detailed information.
For example:
 
 
 

Yes, but you'll need to install the hyphenation dictionary. If you're on macOS, the spelling dictionary is included with macOS but you have to install the hyphenation dictionary. If you're on Windows, you'll need to install both the spelling and hyphenation dictionaries. You can download the files from this page, read the instructions carefully because you must place the hyphenation dictionary into a folder you will create named nl_NL. Cheers.
 

I don't understand your issue here. The PS video does -exactly- the same thing as in AP.
You would already have figured it out in AP, instead of posting  comment after comment.. The examples given should give you enough to start yourself..

AP isn't PS.
Differences can cause confusion and changes in workflow.

This....
A lot of times these videos will show you a basic way of copying a certain look, but the original artist may have come to that look a completely different way.
There could be several plugins involved for all kinds of tiny details for all we know, in combination with additional manual tweaking like smearing, blurring etc.

Isn't it the journey to take a video as a basis and see if you can make it even more interesting?
The fun of using PS or AP is that it isn't cookie cutter filters from e.g. Instagram.

This....
A lot of times these videos will show you a basic way of copying a certain look, but the original artist may have come to that look a completely different way.
There could be several plugins involved for all kinds of tiny details for all we know, in combination with additional manual tweaking like smearing, blurring etc.

Isn't it the journey to take a video as a basis and see if you can make it even more interesting?
The fun of using PS or AP is that it isn't cookie cutter filters from e.g. Instagram.

I don't understand your issue here. The PS video does -exactly- the same thing as in AP.
You would already have figured it out in AP, instead of posting  comment after comment.. The examples given should give you enough to start yourself..

AP isn't PS.
Differences can cause confusion and changes in workflow.

I don't understand your issue here. The PS video does -exactly- the same thing as in AP.
You would already have figured it out in AP, instead of posting  comment after comment.. The examples given should give you enough to start yourself..

AP isn't PS.
Differences can cause confusion and changes in workflow.

A bit late, and maybe not what you want to hear, but...

Always save a file in multiple versions, especially when it becomes one in which you put in a lot of time and effort.
Also, be sure to have backups, LOTS of backups so you can (hopefully...) revert back to a previous version before the data corruption occurred.

But good luck on retrieving (most of) the data. This stuff always sucks when it happens. 

Fun fact: The current generation of generative AI models is what the older of us remember being the first handys: 3kg with battery, sound worse than a walkie talkie and expensive like a car.
You all argue like this AI generation is the end result, but its not even a full start, b3cause they are ONLY ONE YEAR OLD. 
Computer WILL beat experts and artists in terms of creativity, inventions and - always - price. 
 

If this is really the case, this a major issue. E V E R Y  application can work just fine with files from a external location.
I never had any issues working from my Windows Server with Affinity, but if this is really the case I might just stop using Affinity software until this madness is fixed.

What is this? the 90's????

If this is really the case, this a major issue. E V E R Y  application can work just fine with files from a external location.
I never had any issues working from my Windows Server with Affinity, but if this is really the case I might just stop using Affinity software until this madness is fixed.

What is this? the 90's????

@Chris B

Had a little bit of time to play around with settings and try to consistently see what AP is doing.
Again, let me start by saying we work with large 35K, 32 bit pano's. File size is appr. 7,5Gb per pano.  Also still using AP 1.9.2 due to 'reasons'.
I tweaked the performance settings a bit by upping the RAM usage for AP to 24Gb, and limiting the undo's to 24 before some tests.

- Opening a 35K pano isn't much of an issue, it just takes a while for AP to load it. You can see the progress slowly getting to 100% in the 'percentage ticker'.
- RAM or VRAM at this point isn't taxed at all.
VRAM is roughly holding on 2 Gb, and RAM used for loading the pano is slightly over 4 Gb. Now totaling appr. 8,6 Gb of RAM for the system.

- Now I add the live projection to the pano layer, and the RAM usage shoots up with appr. 20 Gb to almost 29 Gb. Rotating the pano around will add another couple of hundreds Mb's of RAM.
- So I end up with appr. 30 Gb of RAM in total used by the system.
Some paint actions might add add another few hundred Mb's of RAM to the mix. (RAM in the system is 64 Gb btw.)

- When done with editing, I release the Live projection, which also takes a while. Sometimes AP crashes on this.
Strange thing is the RAM usage after the projection release is way higher than before the projection. Often hovering around 20 Gb compared to 8,6 Gb.

- And after closing the pano, not all of this RAM is released.
AP often 'sticks to' the RAM usage, slowly going up and down a couple of hundred Mb's.
Or AP releases some, but 'sticks' to something around 16 Gb of RAM while not closed. So 'hoarding' over 11 Gb of RAM before we loaded the pano.
At this point AP will often crash when you close it. RAM will be released after a successful closing of AP. Or crash

I did this several times, and RAM usage and AP behavior is similar every time. Hope it helps.

rob

@Chris B

Had a little bit of time to play around with settings and try to consistently see what AP is doing.
Again, let me start by saying we work with large 35K, 32 bit pano's. File size is appr. 7,5Gb per pano.  Also still using AP 1.9.2 due to 'reasons'.
I tweaked the performance settings a bit by upping the RAM usage for AP to 24Gb, and limiting the undo's to 24 before some tests.

- Opening a 35K pano isn't much of an issue, it just takes a while for AP to load it. You can see the progress slowly getting to 100% in the 'percentage ticker'.
- RAM or VRAM at this point isn't taxed at all.
VRAM is roughly holding on 2 Gb, and RAM used for loading the pano is slightly over 4 Gb. Now totaling appr. 8,6 Gb of RAM for the system.

- Now I add the live projection to the pano layer, and the RAM usage shoots up with appr. 20 Gb to almost 29 Gb. Rotating the pano around will add another couple of hundreds Mb's of RAM.
- So I end up with appr. 30 Gb of RAM in total used by the system.
Some paint actions might add add another few hundred Mb's of RAM to the mix. (RAM in the system is 64 Gb btw.)

- When done with editing, I release the Live projection, which also takes a while. Sometimes AP crashes on this.
Strange thing is the RAM usage after the projection release is way higher than before the projection. Often hovering around 20 Gb compared to 8,6 Gb.

- And after closing the pano, not all of this RAM is released.
AP often 'sticks to' the RAM usage, slowly going up and down a couple of hundred Mb's.
Or AP releases some, but 'sticks' to something around 16 Gb of RAM while not closed. So 'hoarding' over 11 Gb of RAM before we loaded the pano.
At this point AP will often crash when you close it. RAM will be released after a successful closing of AP. Or crash

I did this several times, and RAM usage and AP behavior is similar every time. Hope it helps.

rob

Graphic cards..
One of the PC's still has an oldie GTX970, but that performs well for other software
The other one(s) I have to ask around, we're not all on the same location and I'm the tech head of the bunch...
Ah... Have to add we're doing 32 bit, full float 35K HDR panos. Not sure how that changes the equation...

We see this on various PC's, ranging from somewhat 'older' CPU's to the one year old setup. RAM is always 32-64GB, and VRAM is always 4GB+
We use dedicated disks for temp data where ever possible with lots of space to fill.
Looking at the Task Manager, we never tax the RAM of VRAM.

Unfortunately this project cannot be shared due to NDA's. I have to see if we can share a similar image for testing.
 

Tom,

https://affinity.serif.com/tutorials/publisher/desktop/
But if you start the application there's a image link too in the popup window.

And a question to the devs:
I understand this is beta, but will the file format change before the final?
I would like to start fiddling with this, but not have to redo all the work later on

cheers!

rob
 
p.s. Watched the videos, love the app already

Congrats to all of you! Well deserved, for the Store app and desktop applications.

Next year, another Ninja Cat for Affinity Publisher

Missed this one for some reason...

I'll just wait a bit longer to see if, and when Publisher is emerging from the alpha depths. ;-)
 
 
rob