Jump to content

nitro912gr

Members
  • Posts

    288
  • Joined

  • Last visited

Reputation Activity

  1. Sad
    nitro912gr reacted to ℓurié in Massive lag with the whole Suite   
    Hello all,
    unfortunately I have bad news. In recent days I tested the latest release and the lag reappeared (even worse than before), but now it doesn't hit Curves, Shapes and Stroke (a very light latency is still there, but it doesn't impede the work). Now the massive lag affects the paragraph alignment (only Align Left, Centre and Right. With Justify is ok). I don't know if the previous release (1790) was affected, because I tested it less and after I deleted the files for reinstallation. Maybe yes, but it doesn't matter. What matters is realizing that the problem isn't fully resolved, because this delay makes the programs unusable. Now I don't know if it affects other elements, in the next days I will try again the whole Suite and I will update the topic if there will be news.

    Alignment.mp4
    Switching.mp4
  2. Haha
    nitro912gr got a reaction from Old Bruce in AMD Radeon RX Hardware Acceleration   
    Wtf really? Man this is why I never win the lottery, I never had problems with AMD GPUs in my life, probably spent all my luck there
  3. Like
    nitro912gr got a reaction from JPBERUTTI910 in Affinity Designer V2 getting really slow and laggy after some time   
    there are more answer below that that clarify that affinity team is on it.
  4. Thanks
    nitro912gr got a reaction from shushustorm in we need backward compatibility   
    yeah, graphic design in general can be demanding, but most of the work doesn't require a ton of horsepower. I still use that c2d mac for light work for example, maxed out at High Sierra on OS side.
    I consider getting some older i5 now that they sell out because how much value they lost with the release of M1 and M2 macs.
  5. Thanks
    nitro912gr got a reaction from shushustorm in we need backward compatibility   
    this is not working as you need constant access to the system with the v2 version and it is a great burden to go back and forth.
    Those days I work everything in V1 till the lag issue of v2 is fixed, plus at home where I need to work too, my wife is also working on the main system that have v2 so I'm left with my old macbook that can only run v1. So if I need a file made in v2 (like everything I have worked since v2 release) I simple can't work on it.
    Even if I had access to v2 on my macbook I need to spent time that I don't have, to do workarounds to get the file to v1 because at the workstation (windows) v2 lags so much that I can't work on it without restarting the app every few minutes so I need everything those days worked on v1.
     
    So yeah backward compatibility is something that I and others need, and I will ask for it because I do expect at least some level of it on my tools of the trade. I see no reason being locked in the latest version of the app, the other day a friend sent me a v1 file to fix something and I only had v2 on my system so I couldn't help him. What supposed to do, to tell him to go pay for a newer version that he doesn't need?
  6. Sad
    nitro912gr got a reaction from Westerwälder in we need backward compatibility   
    thats some valid points too, I was considering to jump back to mac recently only to realize that just to add 256GB extra storage and 8GB of extra RAM on a mac mini, they actually asked me to pay another 2/3 of the price of the basic machine... and if I didn't I would be locked on that ram and storage till I replace the machine, which in the end made me reconsider.
  7. Thanks
    nitro912gr got a reaction from dcr in we need backward compatibility   
    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
  8. Like
    nitro912gr reacted to Bobby Henderson in we need backward compatibility   
    I think one of the reasons why Mac sales numbers are dropping is a bunch of the product line is severely limited and has features that turn off a lot of people. For example, look at the current iMac lineup. There's just one 24" model. It kind of looks like a child's toy rather than something that would look proper on an adult's desk. The units have no expandability or user service-ability inside; all the parts are soldered-in. They max out at only 16GB of "unified" memory (translation: a graphic chip is sharing system RAM). Older iMac models could be ordered with more than 16GB of RAM and I think some past models had removable memory modules. All of Apple's notebooks have baked-in RAM. The Mac Mini also has a max of 16GB of RAM (baked-in). Only the expensive Mac Book Pro can be ordered with more than 16GB of RAM. The Mac Studio (a Mac Mini on steroids) can be ordered with more than 16GB of RAM, but its starting price is $3999. And all its parts are baked in.

    The only computer Apple sells that is truly expandable after purchase is the Mac Pro tower. That thing is hella expensive.
  9. Like
    nitro912gr got a reaction from Rudolphus in we need backward compatibility   
    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
  10. Like
    nitro912gr got a reaction from Aeromachinator in Massive lag with the whole Suite   
    if minutes can turn to hours, I will be happy
  11. Like
    nitro912gr reacted to Aeromachinator in Massive lag with the whole Suite   
    Okay, so I'm running an instance of the 1790 build with OpenCL disabled on my Windows computer right now, and I have to say that so far it's a remarkable improvement over the lagging I got in 1781—probably at least as fast as version 1 or close to it. Granted, it's only been running for a few hours, but I'll let this instance run overnight and see if I find anything different the next day.
  12. Like
    nitro912gr got a reaction from Aeromachinator in Massive lag with the whole Suite   
    Let's don't exaggerate here. And well, compared to how long we wait for illustrator to update and fix anything at all, I think people at serif are lighting fast.
     
  13. Like
    nitro912gr got a reaction from PaoloT in we need backward compatibility   
    yeah, graphic design in general can be demanding, but most of the work doesn't require a ton of horsepower. I still use that c2d mac for light work for example, maxed out at High Sierra on OS side.
    I consider getting some older i5 now that they sell out because how much value they lost with the release of M1 and M2 macs.
  14. Like
    nitro912gr got a reaction from Aeromachinator in Massive lag with the whole Suite   
    yeah so far seems like something in windows versions, how I wish I have gone for the universal license now
  15. Like
    nitro912gr reacted to deeds in we need backward compatibility   
    Both very good points.... and one more:
    High Sierra is far and away the most stable for animations and audio work. As a result of significant later changes, many professionals are stuck on it (10.13.6) for those reasons, on at least one of their machines,  and will be for the foreseeable future as subsequent changes aren't ever going to be good. Like font rendering and T2 "security" interrupting audio.
    Ableton Live, by way of example, is still supporting 10.13.6 in latest releases, for these very reasons.
  16. Like
    nitro912gr reacted to Aeromachinator in Massive lag with the whole Suite   
    It seems to be largely specific to the Windows version of the suite, so given your specs, it's no surprise.
  17. Like
    nitro912gr got a reaction from deeds in we need backward compatibility   
    yeah, graphic design in general can be demanding, but most of the work doesn't require a ton of horsepower. I still use that c2d mac for light work for example, maxed out at High Sierra on OS side.
    I consider getting some older i5 now that they sell out because how much value they lost with the release of M1 and M2 macs.
  18. Like
    nitro912gr reacted to PaoloT in we need backward compatibility   
    Something to be considered is that sales of Macs have been dropping by some 30-40%. It is very likely that many people purchasing Macs not as a luxury toy, but as a work/hobby machine, are remaining with an older OS for long.
    Paolo
     
  19. Like
    nitro912gr got a reaction from PaoloT in we need backward compatibility   
    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
  20. Like
    nitro912gr got a reaction from deeds in we need backward compatibility   
    this is not working as you need constant access to the system with the v2 version and it is a great burden to go back and forth.
    Those days I work everything in V1 till the lag issue of v2 is fixed, plus at home where I need to work too, my wife is also working on the main system that have v2 so I'm left with my old macbook that can only run v1. So if I need a file made in v2 (like everything I have worked since v2 release) I simple can't work on it.
    Even if I had access to v2 on my macbook I need to spent time that I don't have, to do workarounds to get the file to v1 because at the workstation (windows) v2 lags so much that I can't work on it without restarting the app every few minutes so I need everything those days worked on v1.
     
    So yeah backward compatibility is something that I and others need, and I will ask for it because I do expect at least some level of it on my tools of the trade. I see no reason being locked in the latest version of the app, the other day a friend sent me a v1 file to fix something and I only had v2 on my system so I couldn't help him. What supposed to do, to tell him to go pay for a newer version that he doesn't need?
  21. Like
    nitro912gr reacted to Chris B in Massive lag with the whole Suite   
    Thank you Sam LaGargouille, this is exactly it. It can be extremely difficult to fix an issue that we cannot reproduce. There are a few threads regarding performance with maybe a dozen customers reporting the issue within them. The sheer amount of Windows configurations, as you say, can really hinder us diagnosing an issue.
    Saying that, we have a release candidate that has hopefully made some improvements:
    Please see Bugs affecting Windows > General performance improvements in the thread Ash linked to.
  22. Like
    nitro912gr got a reaction from Sam LaGargouille in Massive lag with the whole Suite   
    Let's don't exaggerate here. And well, compared to how long we wait for illustrator to update and fix anything at all, I think people at serif are lighting fast.
     
  23. Like
    nitro912gr got a reaction from v_kyr in we need backward compatibility   
    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
  24. Like
    nitro912gr reacted to Bobby Henderson in we need backward compatibility   
    It's pretty common for other vector graphics applications to be able to save layouts down to earlier versions of the software. Obviously newer effects and features would "break" when saving down, but if all one needed to do was get elements with a basic appearance exported to another application such a thing should be do-able.

    For example, the current version of Adobe Illustrator can open an AI file made in any prior version, going all the way back to the late 1980's. In Illustrator it's possible to save AI or EPS files down to any prior Creative Suite version, as well as versions 10, 9, 8 and 3. This capability is there because a lot of other applications, such as industry-specific software, cannot import an AI, EPS or PDF file saved using the latest version of Illustrator. CorelDRAW has some backward saving capability, but not nearly as good as Illustrator. The past few versions of CorelDRAW will not open or import CDR files made prior to version 6 and will save down no farther back than version X5.

    I wish there was such a thing as a truly generic, open source vector graphics format that supported all the advanced features in applications such as Illustrator but wasn't dependent on such an application. I think EPS is about the closest thing we have to that (PDF is not really an edit-friendly format; it's really for viewing & print only). But the EPS format is primitive. It doesn't support features like true transparency. SVG is not a print-friendly format.
  25. Like
    nitro912gr reacted to shushustorm in we need backward compatibility   
    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.
×
×
  • 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.