Gabe

We don't force anyone using the beta process if it's not something they have time for. If you choose to use it, you have to follow the rules.

This is a different issue. Your original video was about applying different table formats to a table already present on canvas. This is drawing new tables and not using the text format. I see why it does it. It's on the same lines as the original issue, as you still have some local formatting from the previous table. But I think it should create the new table "overwriting defaults" in that case as it's a new table. I will get this issue logged. We cannot do this as you're using both forums to report a mix of issues and cannot really be moved around. What rules are you struggling with? As we can help you out understand where bugs should go, and this will reduce all this back/forth dance of figuring out what type of bug it is. In the beta forums we ask people to report only issues that are new to the beta. It is the reporter's responsibility to check the retail version and see if the issue is new to the beta or not. If it's new, it goes in the beta forum. If not, it goes in the regular bugs forum. In the regular bugs forum we ask people to report only issues that affect the retail version.

I'm not sending you from left to right. I'm asking you to follow the same rules as everyone else. The text format works fine if you don't have any local formatting on that text ("no style" applied to it).

This is expected. Applying a table format will not overwrite any local formatting. Also this is not new to the beta. Please use the regular bugs forum when reporting issues that affect the retail version.

Thanks. We think it might know what this issue is in this case.

Interesting. Can you try and sort the LUT category by "date added" rather than by "name"? Then try to add a new preset in the gradient map.

I think I may know what's going on. When you start the app, don't move the cursor away from that monitor until the app start up. See if that make it render correctly.

Thanks. Issue logged.

Hi! One image is in 32bit, one is in 8bit. Have you tried to use the same bit depth?

Hey. It all seems to be fine here. Can you attach a screen recording of your workflow?

Are you using 2 monitors?

Thanks. Issue logged.

You could have a look in %homepath%\.affinity\Publisher\2.0 (Beta)\autosave and see if you have any files. You can rename them to .afpub and see if you have anything that you can use. If not, I'm afraid there's not much we can do. As for the crash, can you attach the file you used?

Please don't report/bump issues that affect the retail version of the app in this thread. This section of the forum is for new issues that affect the beta apps only. Thanks.

Thanks. Issue logged.

I'm not entirely sure what you mean. Can you attach a screen recording please?

Hi @Baniola Is this something reproducible or just a one-off?

Let us know if you notice a pattern or if it's something reproducible.

I wonder whether it's worth trying to do a screen recording to see exactly what's happened before it gets to that state.

It's part of the same bug. It still calls the same backend to "replace" that resource with the linked equivalent.

Thanks. We are aware of this issue.

That's expected. Control + Click on a node will convert it to a smooth one.

It looks like this was an intentional change. I'll raise an improvement.

Whoops. Ta. Sorted

Thanks. I have passed this on. In the meantime, you can save it by creating a new doc in Pub, and the Document > Add pages from file > … . You can then delete the blank initial page, open it in Photo and re-save it.