Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.

Jay1991

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Jay1991 reacted to Athanasius Pernath in Variable fonts support   
    Version 1.8 of OpenType was released in 2016, it included Variable fonts. The feature is mature and widely used nowadays. 
    It would be great to have support for variable fonts. 
  2. Like
    Jay1991 reacted to ThatVeryHooniz in Still no .dds support?   
    I get that not every feature can be implemented. And there has to be concessions made in places, and that affinity isn't a huge company yet.
    But the fact that there STILL isn't any sort of .dds support at this point is crazy considering just how common that file type is in 3d applications. I bought Photo 2, but still find myself using photoshop more purely because I can work with the format I need to work with in photoshop through a plugin.
     
    There doesn't even need to be native support. If the intel or nvidia plugin for photoshop could be used on photo that would fix the issue perfectly. It's just the fact that there's NO support for .dds files that makes it very hard to actually switch.
     
    This isn't a new request either, I've seen people asking for this since 2018. I get that it isn't a very glamorous or advertiser friendly feature. But Photoshop got its userbase by unfortunately being the best option available, and being the best option means working for as many people as possible in as many situations as possible.
     
    Basically, in short. We need .dds support, it's necessary at this point, whether that be through supporting existing plugins or adding native support is irrelevant.
  3. Thanks
    Jay1991 reacted to Ash in Affinity V2, updates, pricing and no subscription (moved)   
    Hi All,
    Well, it’s been a pretty crazy week since the launch of V2!
    This has been a real labour of love for us over the last year or so, and I can’t even begin to describe how hard the development team have worked on it. Not only getting the V2 apps launched, but also of course finally bringing Publisher to iPad. 
    With this being our first paid-for upgrade there has understandably been a lot of feedback / questions around future updates and our pricing policies. I thought it was worth addressing / clarifying our position on some of these personally...
    Updates to V2 moving forward
    Buying V2 not only gets you all the new features you have seen, but we have various updates planned – including many more new features and improvements – which you will get for free. This will continue until such a time that V3 is released. We’re not sure exactly when V3 will be, but I can confirm we are not going to move to anything as regular as an annual upgrade cycle as has been speculated.
    It’s worth saying too that V2 does include many under-the-hood changes to our underlying technology, and we have also been investing in several new areas of research recently. Some of these haven’t manifested themselves into new features yet, but overall V2 does give us a better platform to develop on moving forward and I’m sure you will be pleased with the updates V2 will receive.
    Updates to V1 moving forward
    While we did say on the FAQ that V1 would no longer receive any updates, I want to clarify that was about new feature updates. We will be updating V1 to fix any critical problems caused by operating system updates in the future. So if the next version of macOS breaks V1 we will endeavour to fix it. There will be a point in time when continuing to maintain V1 in this way will not be tenable, but certainly for the foreseeable future we will continue to patch. In fact, we have an update to V1 queued up for release very shortly with some fixes for Ventura and issues caused by a recent Windows security / quality update. 
    We will update our FAQ shortly to make that clearer for everyone.
    Offer period
    In case you didn’t see, I’m pleased to confirm we have decided to run this initial launch offer until 14th December to give everyone the best chance possible to get it if they wish / have a decent amount of time to trial it. 
    Upgrade pricing
    It’s been really hard to see some of the comments about us not looking after our existing customers – we’re pretty devasted that anyone feels like that to be honest. But the fact is we felt our hands were tied somewhat with being able to offer upgrade pricing in a fair way. The main reason for this was App Store customers (which make up around 35% of our userbase). The problems with that are two-fold: firstly, we didn’t have a way from within V1 to validate an App Store purchase receipt to reliably ensure customers who were entitled to an upgrade could get one; and secondly, we could not find a good way for people to get that discount via the App Store. Us pushing upgrade customers to go exclusively via our own site (including customers who were previously acquired via the app stores) may also have put us in violation of App Store Ts & Cs which we were obviously concerned about.
    I’m not saying that these issues were completely insurmountable, but any solutions we came up with would be messy, and most importantly could have resulted in some bona fide V1 customers struggling to get validated and claim their discount. We certainly don’t have the support resource here if we ended up needing to manually validate tens of thousands of receipts for example.
    The only option we felt was safe to move forward with was a general launch offer, which would guarantee that every V1 customer could get the discount, whether they purchased directly through us or the App Stores. We knew a side effect of that would mean some new customers would end up receiving that same discount – but we felt that was a better option than V1 customers missing out. It’s also worth saying that while there has been some good press about V2, all our main marketing has been via email and through social media to our followers. In other words, we felt ok about it because we knew the vast majority of people who would find out about it or take advantage of the offer would be existing customers. I would be surprised if over the offer period customers upgrading from V1 didn’t make up more than 90% of our sales.
    Overall I do believe us giving a 40% discount, along with the addition of the new Universal Licence of course, is offering fantastic value for money for those who want to upgrade. 
    However, taking on board some of the feedback there is something extra we can do – we will offer a new free bundle of content exclusively for V1 customers upgrading to V2 as an extra thank you for your support. I’ve seen this suggested by a number of customers and it’s a great idea as it does remove the App Store conflict entirely. 
    We’ll need a little time to put something together, but all customers who previously registered or purchased V1 and have since upgraded to V2 will receive a voucher code for this via email as soon as we can.
    A comment on no subscription
    I do want to say that some of the points above are exactly the reason why software companies move to subscription. Whatever you do with upgrade pricing, you still have the issue of customers who bought the previous version 3 months ago vs. those who have had it 2+ years. Offering perpetual licences also gives the additional overhead of needing to maintain the previous version longer than you would if everyone was on subscription / generally always on the latest version.
    We are a small team so some of these complications are not ideal — all we really want to do is focus on developing our latest codebase, push out regular updates and continue with our mission to make great creative software accessible to everyone. 
    But it does need to be funded somehow. We know you love our no-subscription model, but there also needs to be a level of appreciation that the alternative is having paid-for upgrades from time to time. That unfortunately comes with its own problems.
    All of that said, I have to say we have been blown away with the response to V2 - around 3 times as many people have upgraded in the last week than we expected - and we really can't thank you enough for the support you have shown. More than anything the success of this upgrade puts us in a great place to continue investing heavily in development which is ultimately what it's all about, and we’re super excited to crack on with some great updates coming next year!
    All the best,
    Ash
  4. Like
    Jay1991 reacted to Patrick Connor in Affinity V2.0   
    No, version 2 of the Affinity suite will be a one off purchase (perpetual license) and will not be sold as a subscription service (monthly or otherwise)
  5. Like
    Jay1991 reacted to Mark Ingram in Affinity Designer Windows Customer Beta - 1.10.0.1127   
    Click here to download the latest beta
    Status: Customer Beta
    Purpose: Fixes
    Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

    As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

    If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
    Changes
    Added 'Select Parent', 'Select Top', and 'Select Bottom' to main menu Changed behaviour of Select All when Edit All Layers is disabled - if you’re inside a group, it will now Select All within the group Fixed PDF passthrough getting rasterised if vector cropped  Previous release notes
  6. Like
    Jay1991 reacted to justajeffy in Affinity for Linux   
    That statement does not seem true to me and certainly not fair to Serif.  It's perfectly reasonable for them to be extremely cautious in their decision-making with regard to possibly developing for another platform and then having to support it.  It would also be perfectly reasonable for them to say they won't make a Linux version because they simply don't want to.  That's their prerogative.   All we can do is continue to make it known that we want it and are willing to pay for it.
  7. Like
    Jay1991 reacted to Michael Tunnell in Affinity for Linux   
    Ideological zealots are problematic regardless of subject, my point is the Linux community is not filled with zealots. We are pro Open Source of course but pro open source does not equal anti-commercial.
    I don't see where there is a PR nightmare possibility. They get good PR from letting us prove ourselves and if it fails they get good PR for at least giving us the chance. It sounds like they are worried about having their software compared to the jank stuff that is on Kickstarter and other services that are just scammy nonsense. They don't want a guilty by association outcome is what I think creates the hesitation.
    However, there have been thousands of successful campaigns from reputable companies, otherwise those sites would have never worked and wouldnt still exist.
    Ultimately, the only people who are doing ANY RISK at all is me and the Linux community. I am risking my reputation to promote a crowdfunding campaign that I have hope that it would work but no evidence that it would or not. The Linux community would be risking future companies using a failed crowdfunding campaign as a metric for not considering a Linux port of their software.
    Serif is at risk of basically nothing if they handle it well and especially if they partner with me to promote the campaign.
    I am willing to risk my reputation for proving the Linux ecosystem is strong enough to justify it if the company is behind the effort to find out. . . I am not willing to risk my reputation on a "maybe if this then we might consider thinking about it".
  8. Like
    Jay1991 reacted to Mark Ingram in Affinity for Linux   
    Exactly that. And that's exactly why apps and games aren't flocking to the Linux desktop. Because we just don't know if we will make any money at all from it. Let alone cover the initial costs of development.
    People need to realise that yes, FOSS can be great, but often these projects need massive sponsorship to be successful. Relying on 1 or 2 developers using their spare time in the evenings to make a competing app isn't going to deliver the kind of quality that you would expect from a piece of proprietary software. And then you have to consider product support, documentation etc...
  9. Like
    Jay1991 reacted to m.vlad in Affinity for Linux   
    I disagree, if anything what I got from that comment is that some people want to pay for things, as long as they're FOSS because when the company fails, at least people will be able to learn from the available code of the FOSS app, instead of starting from scratch. That doesn't mean that they represent the entire userbase. I think this is something that should be discussed with someone like Black Magic Design, who offers a paid studio version of DaVinci Resolve, and see what their numbers are in terms of people who pay for the studio version on linux, people who use the free version and how those numbers compare with the Windows numbers. They're probably in the best place in the market to give Serif advice on this, since video editing and graphic design are similar industries with a lot of crossover.
    As far as gaming goes, it's an entirely different beast from a design app, there's way less stuff going on behind the scenes and to be fair, most game developers either use an in-house engine, which they spent years developing because it's such a huge beast to manage and they haven't planned for linux ahead of time, or they use one of the existing Unreal Engine & Unity engines and either don't know enough about the linux market or don't have the capacity to export to linux. Or I guess there could also be the case they just don't care about Linux, or are entirely reliant on steam's Proton development which makes most games playable on linux. Sadly, Affinity does not have that benefit, Proton doesn't work on Affinity and even this attempt to get Serif to work with CodeWeaver seems to be a "oh let them contact us first" as if it's CodeWeaver themselves who would benefit from this, not you who'd get access to an entirely new market at the price of... a few hours of e-mailing?
    Also, Mark, for the same reasons you mentioned you could say "oh people use free browsers, play free games and use free apps like inkscape, figma, gimp, photoshop online and others on windows, we don't know if we will make any money at all from it." and yet you did. I hope you can see how this sort of statement can appear biased to someone like me when there are a multitude of other better reasons to make the jump.
  10. Like
    Jay1991 reacted to XangelMusic in Provide General Updater and Update Automatically   
    Ever since I bought the three products, I noticed that I've been constantly updating Designer, Photo, and Publisher quite often when I open these programs, mainly because I seldom use these programs. This has become tedious for me to go to the download webpage and download the latest version, for each program. Hence, my recommendation.
    Is it possible for you to create an updater that downloads and installs the programs automatically without having me go to the website each time an update is released? I wouldn't mind how this is implement as long as I don't need to go the website.
    P.S. On that note, why is there a separate page for each program for these installers no less?
  11. Like
    Jay1991 reacted to MichaelMeeuwissen in My car made with designer   
  12. Like
    Jay1991 reacted to Mark Ingram in Affinity Designer Windows Customer Beta - 1.8.4.647   
    Click here to download the latest beta
    Status: Customer Beta
    Purpose: Features, Improvements, Fixes
    Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

    As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

    If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
    Fixes
    Fixed crash when dragging items in the Layers control Improved performance of PDF import (~40% faster) Improved performance of text when rendering text Fixed vector export of text occasionally filling characters Fixed crash when closing floating document  Fixed New Document dialog previous document selection highlight not being remembered Fixed Ctrl+M with nodes selected to not bring up the curves dialog  Fixed crash when docking a panel with the Brushes panel Fixed crash with Appearance panel after using Ctrl+Z on vector brush input  Fixed PNG export not displaying the size warning if the export dialog was previously closed with a different preset  [Installer] Added MSI error strings to installer results page to help diagnose problems 1.8.3.641 release notes
  13. Like
    Jay1991 reacted to Patrick Connor in Affinity Designer for Windows - 1.8.3   
    We are pleased to announce an update for the Windows release of Affinity Designer, version 1.8.3
    Changes in this Build
    The changes in Affinity Designer for Windows 1.8.3 (over the last release Affinity Designer for Windows 1.8.2) are as follows:
    Fixes & Improvements:
    Fixed layers getting clipped to embedded documents would not get clipped Further boolean operation improvements  Tweaks to Alignment Fixed line caps on strokes with pressure profiles that have sharp pressure changes at the start getting incorrectly expanded Fixed loss of selection scope when deleting objects Improved boolean operations on large shapes Fixed PDF export failing due to colour profile being rejected wrongly Fixed rendering artefacts with small radius filter effects Fixed PDF export to honour gradient map's colour space Fix for autosave/recover not working on anything but new documents. Fixed crash opening empty (0 Kb) files Fixed PDF export failing with embedded LAB document Fixed PDF export of images to preserve their colour space Fixed PDF export failing when a document contains an empty clip Fixed cropped result when creating a selection from a mask Fixed sporadic selection failure when invert selecting with Move tool Fixed sporadic PSD import crash Fixed floating panels being clipped when collapsed  Help and Localisation improvements. Earlier changes and fixes in 1.8 since 1.7 (including the new 1.8 features) are listed in some detail in this 1.8.0 update announcement and this 1.8.2 update announcement
     
    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 Designer for Windows) can be downloaded from this link (that installer is NOT for Windows Store purchases and needs a product key).
    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.
  14. Like
    Jay1991 reacted to silvio r. in New Document Dialog UI proposal   
    Hello,
    I recently noticed that version 1.8 presents a user interface that is difficult to understand about (new) document formats.
    Here I present a proposal about the user interface and would like your feedback.
    Thanks

    Thanks
  15. Like
    Jay1991 reacted to alexpi in Roadmap and an Update of these Feature Requests - Blending Shapes, Shape Tool, Offset Path   
    I have designer friends that are using Illustrator, and upon showing them AF Designer, almost every one dismiss it due to the lack of Offset paths, Patterns, Blends and Gradient meshes (in that order!) 
  16. Like
    Jay1991 reacted to Mark Ingram in Affinity Designer Windows Customer Beta - 1.8.3.628   
    Click here to download the latest beta
    Status: Customer Beta
    Purpose: Features, Improvements, Fixes
    Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

    As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

    If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
    Fixes
    Fixed loss of selection scope when deleting objects Improved boolean operations on large shapes Fixed PDF export failing due to colour profile being rejected wrongly Fixed rendering artefacts with small radius filter effects 1.8.3.623 release notes
  17. Like
    Jay1991 reacted to Aammppaa in [1.8.1.604] Expand Stroke Bugs still happening   
    I'm afraid that there are still bugs in the expand stroke function.

    Pentagon with stroke width 10pt expands correctly, but increase the stroke to 14pt and an extra node appears.
    Have noticed other shapes generating unwanted nodes on perfectly straight edges… Star, trapezoid, diamond etc.
     
  18. Like
    Jay1991 reacted to Mark Ingram in Affinity Designer Windows Customer Beta - 1.8.1.604   
    Click here to download the latest beta
    Status: Customer Beta
    Purpose: Features, Improvements, Fixes
    Requirements: A valid product key (for Affinity Store purchases), or an installation of the full retail version from the Microsoft Store

    As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing, including the total loss of any documents. We hope you enjoy the latest build, and as always, if you've got any problems, please don't hesitate to post a new thread in this forum and we'll get back to you as soon as we can. Thanks once again for your continued feedback. 

    If you have a general question about the software, please head over to the Questions Forum, or if you have any suggestions, please head over to the Feature Requests forum.
    Fixes
    Allow PSD smart object support  Fixed crash when switching between artboards with Appearance panel visible Fixed New Document dialog Presets bar incorrectly hidden when switching between Templates and Presets Fixed New Document dialog Template folders with a '.' cutting off subsequent characters  Fixed several boolean operations and expand stroke issues on simple geometry or compound objects Fixed unable to paste text into editors after receiving tab focus Fixed New Documents dialog allowing minus values in Document Size, Margins and Bleed  Improved performance of Layers Panel when updating previews of Artistic Text Fixed input lag (500ms) when drawing with a pen using Windows Ink Improved text responsiveness 1.8.1.595 release notes
  19. Haha
    Jay1991 reacted to MattP in Expand Stoke   
  20. Like
    Jay1991 reacted to dominik in [1.8.0.526] Expand Stroke with Multiple Strokes   
    I, too, did some testing of the 'new and improved' Expand Stroke feature and this seems to be a very big improvement. Congratulations! I am sure some of the glitches (see above @Aammppaa's post) can be ironed out.
    Here are some of my test results (please note: under each of the blue objects there is an original unexpanded object in bright orange colour. Nowhere you see any of it bleed throug).

     

     

     

     
    d.
  21. Like
    Jay1991 reacted to catlover in Annual Company Closure   
    Merry Christmas & a Very Happy New Year to all of you !
    Enjoy your well-deserved rest  
     
     
  22. Like
    Jay1991 reacted to JET_Affinity in Affinity Designer 1.8 New features list?   
    While I understand and mostly agree with the gist of your post, some caution is called for in perpetuating misconceptions—especially confusing to newcomers—by over-simplification and over-generalization.
    A PDF exported from some other program is not the same thing as a native Illustrator file.
    Illustrator can "open" a PDF because when it comes down to it, PDF started as a subset of PostScript and Illustrator is a full-blown PostScript interpreter. Illustrator can "open" a PDF in the same sense that Illustrator can "open" a PostScript file.
    Think of a PDF as a print stream "captured" on its way toward the printer. Native constructs of whatever program created it have been deconstructed to simpler, more basic objects that  the PostScript interpreter in an output device needs to understand in order to render it. PDF is not really meant for full "native" editing. (Some features, like form fields, are obvious exceptions.)
    A few years back, the much ballyhooed proclamation from Adobe was "Illustrator's native format is now PDF!" That is mostly marketing smoke-and-mirrors. What it really means is that the PDF format allows for inclusion of a "cordoned off" section (kind of like a commented-out line in a program) into which the program exporting the PDF can write a complete copy of its own fully native data, so that that content is recognized by the program that exported it, but is ignored by other programs.
    And that's what Illustrator does with PDF. When you Save a PDF from Illustrator, you have an option to also include in the PDF a fully native copy of the document with all its actually native Illustrator constructs. Predictably, that makes the PDF file size much larger. But if you don't turn on that option, Illustrator saves just the functionally "dumbed down" (deconstructed) PDF content.
    Inversely, when you Save a .AI file from Illustrator, you have an option to also include in it a PDF version of the content. So some programs that can't import actual Illustrator native constructs can import the PDF content. That's not the same thing as actually having an Illustrator import filter, like say Corel DRAW, that actually tries to interpret and convert native Illustrator constructs (blends and grads, for example) into its corresponding editable constructs.
    (Many Adobe users are blissfully unaware that even its own Adobe InDesign page-layout application (at least as of version CS6) cannot really import an Adobe Illustrator file; at least not in the assumed common-sense sense. InDesign can only import the PDF version of the content in an .ai file if it's there. If you don't believe that, try it: Save an Illustrator file from Illustrator, but turn off the default (what should be called) "Include PDF version" option in the Save dialog. Then launch InDesign and try to import it.)
    As I understand it, since PDF is now an "open" format, any software company that wants to can take advantage of that functionality. For example, there is nothing preventing Corel from burying its native DRAW document in a PDF that it exports, and any application other than DRAW would just ignore that content. It's much the same as when Macromedia Fireworks treated PNG as its "native" format. PNG format similarly supports a "commented out" area in which Fireworks copies its actually native content. A Fireworks document may contain vector-based artwork, live text, etc. If some other application opens a PNG file created by Fireworks, that application only sees a raster image. If Fireworks re-opens the same PNG, it sees and opens its native and fully editable content (if it's still there).
    So yeah, you may get away with just changing the ".pdf" extension of a PDF exported by some program other than Illustrator to ".ai" and the recipient will be able to open it with Illustrator. But that is not the same thing as exporting an .ai file from a program that has an Illustrator export filter. Illustrator can open it simply because it recognizes PDF content. Unless the file content is quite simple, it will very likely not be nearly as natively editable as the recipient expects.
    One should not rely on that practice to fool someone (especially a customer) into thinking they are actually receiving a native Illustrator file containing fully editable Illustrator-native constructs, just as if it had been created in Illustrator.
    I'm not saying any of this to insist that Affinity needs a dedicated Illustrator export filter. Illustrator's too-long stranglehold exists not because it's "best" but just because that's what most people have used for too long. That's the way the world works. But strangleholds never become broken until they are resisted, and that's the way the world works, too.
    I will use Affinity for its own merits, just as I do Draw or Canvas or anything else; not as "poor man's Illustrator." Unrealistic? Nope. That was exactly my stance throughout the whole history of FreeHand. If a printing house wanted to be awarded my client's projects, they had to support the application formats in which they were provided. It was always stipulated that any necessary edits would be performed by me.
    PDF is the "great liberator" of Captive Creatives, that finally provided us more freedom to use programs we prefer. No longer does one have to use Adobe products. And we should use PDF as such, not continue to cower in the face of the monolith, just because it's still conventional-wisdom to many.
    JET
     
  23. Like
    Jay1991 reacted to nezumi in Affinity Designer 1.8 New features list?   
    Some of what I read here remind me somehow that client I just had.
    Since I moved completely to Affinity I am mostly using PDFs now. Client called me and said
    - I need it in AI format
    - But you can import PDF perfectly well to illustrator..
    - No, I need it in AI format, I have a pipeline I use for years now! Please deliver AI!
    So I just renamed PDF extension to AI and resent the same file (yup, it does work).
    - You see what I mean? - client replied - now it works perfectly! You dont change proven, professional pipeline for no good reason!

    Yeah man, I can see that alright... Slightest change of what people used to and drama starts. Something isnt named the same, shortcut is different, format - whatever. People start to freak out, totally unable to change even trivial things. And if some option they used to is not there? Uffff Forget it - looking for workaround is completely out of question. Even if sometimes - many times - it is a non-issue and you can keep on working happily after showing tiny bit of flexibility.
    Most common thing:
    "In Adobe it is certain way and here it is different!"
    Yeah, so?
    There is more than one way skin a cat. Affinity is not a Photoshop. It can replace it but its not a Photoshop or Illustrator reskinned with different name and priced differently. It has its own strengths. I wouldn't bloody use it if it was simply cheaper but I could not work professionally on it. Thats what I do for living, I cant afford not being able to do the job.
    But I am and I am loving the Affinity way. Yeah you heard me - and I was using Photoshop professionally since version 4. Thats 23 years already. OK, minus last 3 because I have switched to Affinity immediately when it became available on Windows.
    "ow, so you are Affinity fanboy then!"
    I guess I am. I am loving it. Thats why I am here on Affinity forum. Meeting some Adobe fanboys.

    Listen sweetheart, your new girlfriend is not your ex, ok? It will never be the same. I know you miss Jenny. Maybe you should go back to her? Yeah, she was with you just for your money, but if you are happy with that... Maybe you should never try to have a new girlfriend? Because telling Lucy constantly about how good you had it with Jenny will not make things any better...
     
  24. Like
    Jay1991 reacted to MEB in problem with expand stroke....   
    Hi Friksel, nod74,
    This was indeed being worked/fixed at the time of the post (it's being tested as we speak). The fix will be included in v1.8 Beta for Mac (not available at time of writing) and in v1.8 Beta for Windows (at time of writing the current Windows 1.8 Beta doesn't include this fix). Some issues imply rewriting parts of the code or the whole feature - they are not just simple corrections or addons to existing code and take more time and testing than usual. With Publisher's recent release a lot of time and effort was spent on solving its issues and on its integration with the rest of the suite which ended up delaying Designer and Photo 1.8 Betas a bit. As explained several times we have limited dev resources and some fixes may end up taking more time than we hoped for but that doesn't mean we don't care about customer's issues/problems. We are simply doing our best with the resources we have. Thanks for understanding.
  25. Like
    Jay1991 reacted to MattP in Expand Stroke Needs Work   
    LOL! Thanks for explaining things to me, very educating, I'll try to do better in the future. So if everything else is so accurate, do you want to explain to me what I'm seeing here?
    (Blue background, white curve, semi-transparent pink result of expansion)

    and, just for those commenters who are about to say "But what about CorelDraw? You didn't include it and it would've been perfect!"... (white background, black original curve, pink expanded result)

    You'll notice that NOBODY has the right answer because - as I stated A LOT before - there IS NO RIGHT ANSWER because one curve does not perfectly become one other curve at an offset - MATHS DOESN'T WORK THAT WAY! It becomes potentially many curves, but in different ways. You need to use an algorithm to generate the offset and the results of the algorithm will vary.
    So... sorry to break the awful news, but.... we're actually not that bad. Shocker. Double-shocker is the fact that I've actually shown you that we really do actually have a new stroke expansion function and the 'fanboys' aren't actually fanboys at all - they're just not ridiculously pessimistic keyboard warriors.
    /micdrop
     
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.