nitro912gr

No, OP did not:
V2 should be able to import (which it already does) and export V1 files. Not vice versa. And I absolutely agree with that.
Similarly to OP, I could use V2 on iPad if I could export V1 files to use on Mac (running an OS unsupported by V2). Besides, it would make the instability of V2 less of a burden, because one could always go back to V1 if needed.
Right now, having purchased the whole V2 suite, I can only make use of V2 Designer on iPad, and only for knife and shape builder and port the vectors to V1. Quite limited. Not to mention user base fragmentation, but I guess I've sent enough feedback.

I’m hoping we have fixed this in the next beta. Thanks all for the feedback and help. Much appreciated.

Hello I just wanted to make a clean thread asking for backward compatible files between v2 and v1 of programs.
I didn't had any reason to need it till now but now I do notice what a big problem it is.
First of all now that the summer time that I have most of my workload I did noticed problems with designer v2 performance and I wished to move back on v1 till it is fixed, but nope. I can't open v2 files, I need to do workarounds with sketchy imports.
Second, I wanted to work on my macbook from home so I tried to get the designer v2 trial there to see what's up, but nope OS not supported so it can only use v1. But I use v2 on workstation and this is another roadblock.
So yeah dear Serif, please we need backward compatibility.
It is understandable that there is tools that are simple not available on v1 but this can be bypassed by automatically converting to curves whatever is not gonna work and display a warning of losing the editability of some objects if the file is saved with the older program version.
Thanks

Hello I just wanted to make a clean thread asking for backward compatible files between v2 and v1 of programs.
I didn't had any reason to need it till now but now I do notice what a big problem it is.
First of all now that the summer time that I have most of my workload I did noticed problems with designer v2 performance and I wished to move back on v1 till it is fixed, but nope. I can't open v2 files, I need to do workarounds with sketchy imports.
Second, I wanted to work on my macbook from home so I tried to get the designer v2 trial there to see what's up, but nope OS not supported so it can only use v1. But I use v2 on workstation and this is another roadblock.
So yeah dear Serif, please we need backward compatibility.
It is understandable that there is tools that are simple not available on v1 but this can be bypassed by automatically converting to curves whatever is not gonna work and display a warning of losing the editability of some objects if the file is saved with the older program version.
Thanks

Just wanted to add my 2 cents here.
I wish there was a way to use v2 files on v1 so I can move there till is fixed.

Yes - The more I've been using Designer the more I've been experiencing this too. And it turns out we are not alone - there is already an ongoing thread all about it as well, with lots of people reporting the same thing:
 

To all our forum members,
Unfortunately we have become aware that personal data relating to users of these forums may have been accessed from outside the company following a cyber attack on 6 April 2023. It appears that an administrator’s account was compromised, allowing access to our forum members list.
What data was accessed?
The data which may have been accessed is what is on your public forum profile (e.g. username, post count, reputation, joining date, etc.), but additionally includes your Email Address and Last Used IP Address which would ordinarily be private. Thankfully we can be sure it would not have been possible to access your forum account password so that has definitely not been compromised in this breach.
What information is available on your public profile depends on what you have previously given. You can view your profile by logging in to your account and clicking on your avatar in the top right-hand side.
Please be reassured that any information accessed does not include any financial data, purchase history, physical addresses, phone numbers or anything else held within your main Affinity account / AffinityID. The forum is a standalone system which is completely separate from your Affinity account.
We cannot tell what proportion of our forum members’ email addresses were accessed so we are making all members aware as a precaution.
We have reported this incident to the UK Information Commissioner’s Office (ICO) as well as taken immediate steps to make the forum system more secure to avoid this type of attack in future. 
What should you do?
We do not think you need to do anything, other than be mindful that this happened and to follow general advice around email and online account security.
One thing to be particularly diligent with is possible email “phishing” attempts. This will be when someone contacts you pretending to be us, requesting you change your password or give other account information to them. If you are concerned about any email being legitimate, don’t click any links in the email. If you wish to update any of your forum account details type forum.affinity.serif.com into your browser and log into your account from there to be sure.
Generally, if you do receive any suspicious email which you think could have originated via this breach (for example if an email you receive addresses you by your forum username) please let us know.
If you wish to make any such reports or have any further questions, then please contact us at dataprotection@serif.com. Full details of Serif’s Privacy Policy are available on our website https://affinity.serif.com/privacy/.
As well as this forum announcement we are notifying all forum members about this via email.
Customer data security is something we take extremely seriously and, while cyber attacks are an unfortunate reality of doing business today, we are incredibly sorry that your data may have been accessed in this way.
Sincerely,
Ashley Hewson (Managing Director) & Patrick Connor (Data Protection Officer)

Why? I don't know.
Specific G is crazy.

It's broken in AD 2.04 but working in the beta 2.1.0.1736 (macOS), so hopefully will be fixed in the next release.

Your shopping cart needs to have some nodes added where the G intersects or overlaps it.

It's an issue with the 6800 gpu and affinity. It happened when hardware acceleration was on, and using another app with acceleration crashed the driver more often. Using Affinity and Spotify at the same time crashed the driver constantly (and affinity would crash half the time too, losing some work depending on the restore point). There is a forum post with others having the same issue, all with the same card. And yes, drivers are updated all the time. So I'm hoping this update fixes that conflict. Like I said, we'll see.

Dear Thread Followers.
In the Windows betas builds of the Affinity range, we have recently reworked the memory handling in hardware acceleration which may benefit AMD cards. Users of AMD (Navi) Graphics cards who now have Version 2 of our software, we would be grateful if you can sign up to the beta and let us know in the Beta Memebers Area if you find it has had any positive or negative effect, as is already being reported elsewhere.

Sorry for bringing back that older topic but implementing Ai assistant tools could be a life changing thing. I mean it could make things like background removal or specific selection a painless activity in our workflow and let us focus on creating than doing little repeatable and soulless tasks like background removal.
It can also help by upscaling stupid little graphics that are sent from our clients and even making great image trace vectors. Or making object selection a reality, or improving the healing brush. or automatic levels between 2 layers or anyway just imagine all the tools that can do a little bit more than what they actually do now or that their auto part actually is working or going beyond what it can do now.
There are so many ways that can make use of AI without touching the copyright mess of image creation right now. I just imagine that I could give a command to Designer AI to populate the space withing a object with the letters from the text I provide. Telling it to use different fonts and sizes and rotations for each letter or something. That could be great!

had this popping to me today while working on an older file. revert did the trick, but shouldn't there be some short of fool prof setting in place to avoid that? I spent half an hour trying to fix this.

Having the panel available in Designer was a bug. The button to invoke it shouldn't be there, either. 
Try selecting the text frame or text object, then Edit > Defaults > Revert. If that doesn't work, try Edit > Defaults > Factory Reset.

@walt.farrell Revert worked. Thanks a ton for the quick reply!
The panel remains a bug on top of a property that shouldn't exist, though I think it would be great to be able to fill/stroke a Text Frame (pia to do it manually).

VRAM is increasingly important for 2D. I don't recommend to skimp on it as that may just introduce another bottleneck. I'm using 12GB and I've almost filled it at times with editing one simple RAW, having multiple Affinity apps up and running. I'm sure other things as well, but Affinity takes a mighty big chunk out of GPU memory. 1-2 it would gobble up no problem. Basically, I know never to have these apps open anymore if I do decide to run a game.

The benefit of adding another card as a secondary and setting it to primary renderer in Affinity though is theoretically it will have sole discretion of its VRAM, so there is that. We don't know what the OS does with memory management with two dedicated cards (probably not hard to google). Laptops might be a different story entirely.

I used to have avast, then it started to become bloated with some nonsense and I moved to free Bitdefender. But my son is using Windows Defender and both out machines are fine.

The manual way of editing SVG code, in order to remove a SVG transform matrix, is very well described here ...
Removing transform translate from an svg code

This is largely anecdotal, but installation process seems sensitive to age of hardware/Windows installs from what I can tell and behaves as if it's idling when it's running. Not sure that means the process is "bugged", but maybe has to do with the unpacking process /shrug I don't overthink it. It's Windows.

We are pleased to announce an update for the Windows release of Affinity Designer 2, version 2.0.3
The changes in Affinity Designer 2 for Windows 2.0.3 (those made since the last release Affinity Designer 2 for Windows 2.0.0) are as follows:
We plan to also release this build as a MSI/EXE installer. Please follow this FAQ thread for notification of it's release.
Fixes & Improvements:  (since the last release 2.0.0)
New Document: Custom Document Preset order is not retained between app sessions Current DPI of selected layer does not show in V2 Shape Builder Tool now has an additional option to delete open curves that were inside a newly created area, plus you can now hold Alt to delete areas while still in Add mode - more to come... Warp Group editing now supports the Shift modifier to lock node edits to an 8-axis grid. Also can be used with off-curve nodes to maintain their angle while dragging them Modifying Global Colour swatch fails to update document until you click out of the Colour Selector Sliders for Warp Group are broken Using the Select object/ transparency object selects all objects Symbols - Delinked nodes get forgotten when swapping out nodes from synchronised instances Shape Builder Tool: Alt to delete on rotated shapes fails Shape Builder Tool: sometimes drags out a selection marquee Shape Builder Tool: functional improvements on some shapes Placed documents with bleed fail to render the top and left side correctly Quotes can be incorrectly put on newlines and cause text to render differently compared to V1 Straightening in the Develop Persona offsets the image from the canvas entirely, until developed or crashes Transform Panel- Differences in panel size when switching between Curve strokes and expanded objects Cmd+Z / Ctrl+Z isn't working in V2 apps for adjustments Outline Layer Effect is making the anti-aliased edges transparent, rather than blending with the shapes colour Quick Access to Node Tool no longer allows you to insert node Fixed spurious "future version" error under certain circumstances Improvements with PDF Import and Layers Fixes for RTF import - font name discrepancies, fields in footnotes Update for HEIF importer DWG Import scaling improvements DWG file takes a long time to open then shows incorrectly (file specific). Colour Panel now remembers user preference for CMYK documents Export Panel UI fixes Fixed some tool drawing issues relating to selections across spreads etc Pen tool tweaks and fixes Fixed hang that could occur composing vertical centre aligned text OpenType handling does not respect lookup flags such as IgnoreMarks Hit box of scaled text could be incorrect Gradients on text strokes don't render unless the fill also has a gradient Fixes for line breaking in some odd cases with punctuation Resource Manager updates Light UI Improvements Many and various Layers Panel updates and fixes Clipboard: 32 bit DIB support added Auto Flow Place: Added an option to auto-flow place to replace the content of already populated picture frames More attributes are retained when replacing images in frames Ensure global colour edits update live Select Same Name should only select objects with user supplied names New clearer icons for stroke properties (cap, join, align) Help & localisation improvements. Licensing and Registration improvements and new help links  
UPDATING TO THIS VERSION (Free for existing customers)
The software version can be seen on the splash screen and the About dialog (in Help > About Affinity Designer ).
If you’ve purchased from the Affinity Store — each time you start the Affinity Store software it will check for updates and offer any available update. The latest update will install over the top of any earlier version, with no need to uninstall. You can download the latest installer by logging into the affinity store here and find the order in your account and use the "Download" button in there. Alternatively, this new release (and previous versions of Affinity Publisher for Windows) can be downloaded from this link. (those installers are NOT for Windows Store purchases).
If you’ve purchased from the Microsoft Store — Microsoft Store updates are done automatically by the operating system (each time you start the application). If this does not happen for you, open the Windows Store app and click the three dots in the top right corner of the app and then go to Downloads and Updates. Click Get Updates. This should hopefully force the update to show.

It's all in the help file...
 
Edit All Layers and Select Same/Select Object
The behaviour of the Select Same and Select Object commands depends on the Edit All Layers setting on the Layers panel:
When the setting is enabled, the Select Same/Select Object commands will match objects across all artboards. When the setting is disabled, the Select Same/Select Object commands will match only objects on the current artboard.

Probably, many people do Soon it will end, but it is still a thing.

That is not completely fair. AMD drivers were terrible and buggy. They were 50 times slower than other manufacturers so we blocked you being able to turn it on for AMD in Windows V1 because it had already led to lots of support contacts complaining about the performance. Since about May '22 the AMD drivers have been improved and are now only about 3 times slower than other makers. Consequently during the internal V2 early beta we re-allowed AMD chips to have hardware acceleration on and made further changes to the code accordingly. So although it appears as though we could technically now "allow" AMD to turn on hardware acceleration in a Version 1 patch, it is not that straightforward. Other changes made during the the V2 development cycle have also facilitated AMD drivers, and it is not a simple matter to port any of those back into the V1 codebase. The recent patch for critical OS issues is the only change we can make given our resources here. As it happens there are lots of "fixes" in 2.0 that were a problem in 1.10 but we are trying hard not to sell the software based on those so much as the many improvements and new features that you get. I think it is better that some things got fixed as well as the improvements and new features, than that 2.0 would have all the same restrictions as 1.10.x
So yes if this was the ONLY change in 2.0 over 1.10 I would agree we had put this "behind a paywall" but it is not how I would describe the development cycle where things change over time and occasionally we will ask for more money.
tldr; New AMD drivers mean that enabling AMD in 1.10 might now work better, but would likely lead to unforseen problems making it still unusable.

UPDATE for anyone still using V1 Affinity applications - 
Versions 1.10.6 of the Affinity suite have been released, which resolve these .NET Windows crashes.
Please see the below link for information on how to download and install these updates:
With the Affinity updates installed, you can now un-hide any previous Windows updates you have paused and install these without concern.