Jon P

We've found a recipe for a crash when clicking/dragging onto the layers panel, which can show itself in other ways too, so hopefully that should cover a good few of the crashes that we've seen in this thread. We should have this fixed in the next beta, so let us know if you still some of these crashes when we have that beta out, as I suspect there's more recipes to uncover from the behavior you've described. I'll keep poking

I've actually been able to reproduce a couple of crashes here, but am struggling to find a consistent recipe. I'll keep investigating. @Intuos5 If you do similar behavior on 2.4.1 did you ever get a crash? @Affinity-Inspiration To double check, have you been testing on Windows?

Unfortunately I'm struggling to get much from the crash report, as suggested above are you able to attach the file? Or upload it here if you'd prefer it to be private. If you let me know the areas you got the crash I'll have a look and see if I can reproduce anything

Are you able to upload any of the crash reports?

Thanks, I've not been able to reproduce any freeze with what was sent. Would it be possible to package the file up and send that to the same link?

@Pyanepsion You can use this link and it will confidential and only used for testing purposes.

This is correct, as a workaround for now, if you press enter after using the text field and then tick the regular expressions box it should avoid the crash

It looks like the apps are crashing when closing down. There was a recent issue where entering the export dialog and closing the app was causing this but that's fixed, so looks like this is something different. I'll get this logged, thanks for the report

Hi @soap, We export text out as splines, which AutoCAD will struggle to render correctly until you do a View > Regen All or perform the regenall command. The text not being exported out as text is currently by design.

Do you have any videos/files demonstrating this so we can look into it? Assuming this was exporting to DWG/DXF and then directly importing into CAD

I don't suppose you can remember if you had any of our other beta apps open when updating? The crash report seems to indicate that may have been the case, I'll see if I can reproduce it

Thanks for the report, I've passed this on. Seems to have been broken for a while and is specifically related to the outer shadow effect

I think it would be useful to display the export format if exporting from the Designer persona, so have logged that.

@GRAFKOM You aren't doing anything wrong, the feature is only available in Designer (Google Translate: Nie robisz nic złego, ta funkcja jest dostępna tylko w Designerze)

We've reproduced what we think you are seeing by exporting a shape with no stroke out to DWG and importing the result into SketchUp. The same however happens when you do a similar thing from AutoCAD (Creating a file with a single hatch object and no polyline, saving as DWG and importing into SketchUp). SketchUp doesn't seem to support hatches/shapes with no strokes so we currently believe this is by design

Thanks @debraspicher. I'll log the fact the origin changes when setting the selection box on a rotated object

Hi @elfis, I've just tested adding a simple rectangle to a page and exporting to DWG/DXF and it's importing into SketchUp fine. If there's no stroke on the object then it's discarding it as a "zombie object" on import, but again i'm not getting the error you are seeing. Can you attach the file you are exporting with the settings you are using?

Hi @Guadalupe, Are you able to upload the file that was created in 2.1 for us to look into? Thanks

Hi @EPriuli, Are you able to upload the document for us to investigate? Does this error only happen in the current beta and not retail version? Thanks

I logged an issue this morning that also shows an error, so there's definitely some more to flush out. If you can send me the afpub I'll check if it's a similar cause. Thanks

Thanks for the report, this is logged with us and should be fixed in the next customer beta

Thanks for the report, this is logged with us and should be fixed in the next customer beta

Option + [ and ] seem to be shortcuts that come from the OS for single/double quotes so override any custom shortcuts they are assigned to. An improvement would be for us to warn these are protected shortcuts when they are being assigned, which I can get logged

Ah yeah, I do indeed suspect this will have a similar root cause to the other issue, but will get it logged just to be sure. Thanks for the clarification

Thanks for the report @anto. It's now been logged that externally modified images aren't being detected.