Jump to content

NathanC

Staff
  • Posts

    4,415
  • Joined

Everything posted by NathanC

  1. Hi @Ivan V. welcome to the forums, Could you possibly share a screen recording demonstrating the issue on a new document? I've followed your steps, but after switching the shape from 'Tight' to 'Outline' wrap mode and manipulating the wrap nodes of the shape, the text remains visible. Thanks!
  2. Hi @scott2023, This is a limitation of the Export Persona path components, if one of the values is left undefined in the scaling field, the variable will not be listed in the file name even if it's been added to the path components. This is also similarly observed when swapping the scaling from defined W/H values to a scaling multiplier (2x), as the W/H values are no longer specified. For both the W/H to be present in the name, this will need to be added in the scaling field, for example 1000w,1000h in the scaling field will export as 'test 1000x1000px.png' as the file name.
  3. Hi @davidgall, Looks like this may be related to an issue with 'Snap to object geometry' logged internally. It should be possible to snap to the smooth node on the rounded curve via the node tool workaround below: Convert the Rectangle to curves In the Layers panel, highlight both the rectangle curve and the rounded shape Highlight all four nodes of the rectangle Move the position of the top-right node to overlap, it should snap to smooth nodes along the rounded curve Switch to the move tool, highlight the rectangle curve and re-scale as required.
  4. From my understanding the 'Select Same' command failing to select objects with the same colour values but different colour opacities when this works as expected on different layer opacities is unexpected behaviour, so I'll be logging this with the developers for further review and confirmation.
  5. Hi @Ash Eldritch, I can confirm this toggling the wireframe view mode shortcut is returning me to the standard vector view instead of leaving it in Hairline. This appeared to work previously as toggling the wireframe shortcut correctly returns me to just the Hairline view mode when I've tested this in 2.4.2, so it's a regression. I'll get this logged with the developers. πŸ™‚
  6. Hi @davidgall, I can confirm this is a known bug currently logged with the developers. The issue will typically trigger after increasing the curve width, deselecting and reselecting the curve, causing the transform origin to incorrectly offset and prevent selection. I've bumped this issue with your report.
  7. Hi @Jason F welcome to the forums, We're aware of issues relating to the expand stroke function unexpectedly breaking the curve on certain segments, I've updated the existing issue and bumped it with your report.
  8. Hi @influxx, As well as providing the crash reports it would be beneficial if you could also upload an .afdesign file where you've encountered this issue so we can confirm if the issue can be replicated and therefore logged. πŸ™‚
  9. Hi @Brookr, Looks like this is caused by a known registration loop issue when attempting to sign up for an Affinity ID in-app on MacOS devices running 10.15 Catalina. Instead of registering in-app, I'd advise signing up for the free trial using the link provided below. This will create you an Affinity ID which you can then sign in with in Photo 2, avoiding the looping issue. https://affinity.serif.com/trial/
  10. Hi @mattspace I've updated the issue internally and bumped it with your report. πŸ™‚
  11. Hi @Dennison, We don't provide tech support directly via zoom calls, but if you have a sample file where you're encountering issues with text style updates along with any further info on the issue based on the context of the file we're happy to look into this further and explore possible cause and solutions. I can also provide a private upload link if required. πŸ™‚
  12. No problem! Happy to hear that's worked. To clarify, do you want to save this sequence of pages in the native .afpub format to continue editing? It may be easier to delete the pages you don't want and then File -> Save as to create a duplicate of the file that only contains that set of pages. Alternatively, you could create a new single page document and use the Document -> Add pages from file function to merge the document (and specify the desired pages or page range) into the new file and save it separately.
  13. Hey @mattspace, I can't say I've observed similar issues historically or can see anything logged internally relating to your system's Kernel panic while working in the apps and the random nature of the freezes would make it difficult to replicate, it's likely the issue is related to your local system enviroment. In terms of mitigating the issue, I'd recommend making some amendments to the app's performance settings. To clarify, OpenGL and Metal under the 'Display' dropdown are different rendering APIs that the affinity apps can use to render the viewport (canvas area), switching from Metal to OpenGL may have some affect on performance but this can vary from system to system. These API's aren't specific to Affinity, I've provided some links below which provide more info. https://en.wikipedia.org/wiki/OpenGL https://developer.apple.com/metal/ Here's some changes I'd recommend in the app performance settings, I'd recommend changing one setting and then monitor the stability before changing anything else: 1. Disable 'Metal Compute Acceleration' checkbox (AKA Hardware Acceleration). This setting can improve performance in certain raster based tasks but may also be contributing to the system instability. After disabling the setting close the menu and restart the app when prompted to. 2. Change the 'Display' renderer dropdown from Metal to OpenGL and restart the app to apply the setting. Let us know how it goes.
  14. Hi @Charter, On the basis that you're working in Publisher, you can change the page dimensions and orientation via the File -> Document Setup menu under the 'Dimensions' Tab. At the top of the dialog you can also change the page/spread you'd like to be affected by the change.
  15. Hi @Minus44, I've replicated and logged this issue with the developers, thanks for providing a detailed report and screen recording. While testing I didn't encounter any crashes when altering the cell fill or stroke properties, but if you're able to replicate this issue please provide a screen recording, sample file as well as any relevant steps and we can then look into this further.
  16. Hi @MmmMaarten, Thanks for raising this, looks like a regression as this is working as expected when I've checked in a previous build (v2.4.2), I'll get this logged.
  17. Hi @COUYA, If you're referring to the Bold shortcut on the selected font, check that the font has a bold variation available from the styling dropdown which is located to the right of the font dropdown. We're aware that this isn't working as expected with certain fonts even with a bold style present, such as 'Milo OT', so let us know which font you're using. You may be encountering this issue if you're exporting with the area set to 'All Pages', if not please provide more details on the issue, as well as a sample file.
  18. At 0:07 in the second recording Kai selects the High Pass Filter, but at no point was the filter applied to the selected layer. It's not as obvious as on Desktop since it appears as a dedicated menu, but on iPad this indicated by the filter radius slider and Apply/Cancel options on the Context toolbar.
  19. Hi @Rajib Ghosh, Switching to the MSIX(x64) version of the apps should resolve this renderer detection issue, you can download this version via the direct download pages below. Photo - https://store.serif.com/update/windows/photo/2/ Designer - https://store.serif.com/update/windows/designer/2/ Publisher - https://store.serif.com/update/windows/publisher/2/ Before doing so, could you send a copy of the Log.txt file so we can check what's happening on startup? This log file can be found by pressing WIN + R and entering in the following path: %APPDATA%/Affinity/Publisher/2.0/ Many Thanks
  20. Hi @Pavel Koko, I'm not sure if we've had anything through on email, if you could PM me your ticket number and email address you sent from I can check this on our side, or alternatively feel free to submit a new request through the support form. https://support.serif.com/hc/requests/new
  21. This is an issue that we resolved via email, but for the visibility of others, this is caused by keeping the High Pass filter active without applying the filter to the selected layer, so the effect moves when switching between active layers. πŸ™‚
  22. Thanks, can confirm I'm also encountering the immediate app crash when sorting the Palette by colour, this has been logged with the developers.
  23. Welcome to the forums @Cesc Garcia, I've just confirmed this worked as expected for me after creating basic set of curves and shapes in Designer, exporting to SVG and then placing this SVG in Powerpoint. I was able to right click the SVG -> Convert to shape to split all the elements. If you can share a copy of the .afdesign file and SVG pre-export this should help confirm what the issue may be, as it's likely getting flattened to pixels on export.
  24. Hi @SteveRoberts, After updating the bullet text field within the Paragraph panel, instead of clicking immediately clicking out try hitting the Enter/Return key to commit, and then click out of it and you should find that the field and text keeps the new bullet formatting.
  25. Hi @Iztok, It looks like the crash may be related to linked resources, but there isn't anything conclusive in the backtrace from the crash report attached. As Outfit mentioned, the crash report alone really isn't enough without additional explanation and context. If you're able to reproduce the crash, please provide any relevant steps required as well as the necessary files so we're able to investigate further. The second .txt file isn't an Affinity Publisher crash, it's a MacOS Mail app crash.
×
×
  • 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.