Jump to content
You must now use your email address to sign in [click for more info] ×

Mystical

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by Mystical

  1. 6 hours ago, Ana-Irina said:

    They could make the icons on the top as a carousel, so that you can scroll through the icons. They could even make the list customisable, so you could choose your most used formats and arrange them according to your needs.

    Would be cool if you could favorite export types and those would appear at the top in icon form like classic Photo v1 and the rest are in a list. Best of both worlds.

  2. On 11/11/2022 at 6:38 AM, 00maxx00 said:

    Hi Ludger.

    If you type "*" and press enter when you are in the folder with the .bat file, you remove the filter that shows only .exe files. Then you can select the .bat file.

    It's the same with FastStone Image Viewer and DXO Photolab - and every other sw that works the same way.

    Unfortunately this method does not work with all software. If I try and choose a non-exe in 3D Coat as my external editor program it denies the file (Bat and shortcuts to photo 2). Likewise if I choose the windows app Photo 2 exe located in: WindowsApps\SerifEuropeLtd.AffinityPhoto2_2.0.0.1640_x64__3cqzy0nppv2rt\App the program never launches.

    So for now I am stuck using Photo 1.0 still as my external layer exporter from 3D Coat until the Photo 2 exe can somehow be recognized as a normal program exe.

  3. I honestly do not see the issue being treated as a new user or having to pay the same price as anyone else for v2. Its a literal steal compared to other subscription models like Adobe where after just 2+ months you'd already be paying more than Affinity Suite. On top of that you still will never have the enjoyment of perpetually owning the Adobe products no matter how many years go by on top of the constant payments. Its not like you need v2 right now anyways and can wait for bug fixes and additional features which I am sure the 40% discount would come around in the future.

     

    With all that said the moment the website refreshed for v2 launch I bought the whole suite no questions asked. Been an Affinity user for a good 3+ years.

  4. Unfortunately the bat file workaround does not work for me. The program I use (3D Coat) requires an exe and it does not recognize the secondary 0kb exe's from Photo 2 in the Local Appdata section. I can only use the exe from WidnowsApps version when choosing the exe. However, doing so Photo 2 never launches when I choose to export layers from 3D Coat for Photo 2 (like I was doing with Photo 1.0 where it works)

  5. 1 hour ago, ChrisON said:

    Same problem with DXO Photolab - can no longer export a developed raw file directly to Affinity. Big step backward for me. If there is no workaround for this I'll probably get the refund within the 14 day window and find something else to use.

     

    Chris

     

     

    Similar issue for me with a program called 3D Coat where I regularly export all the layers to an external paint program which was Photo 1.0

     

    While I added the Photo 2 exe as my new external export editor for layers it literally does nothing now when I choose to export. Its like Photo 2 being a Windows App in that directory blocks everything and not sure how I can fix it so I have to keep using Photo 1.0 for now, save the file in Photo 1.0, close Photo 1.0, then open it in Photo 2.

  6. 46 minutes ago, jochoalions said:

    I am VERY HAPPY to pay $99 for the Version 2 Universal License.  I will also pay for future versions. I am a happy customer and use these applications extensibly every single day. Kudos to Affinity and their entire teams; keep up the excellent work, and keep chipping away at the bug lists and feature requests.

    I agree. No online always subscription fees and only having to pay for big version number updates is ok by me.

  7. This is the most unstable version of Affinity Photo and I've been a user for a good while.

    If I have one 4096x2048 image open with maybe 30+ pixel layers my PC's RAM goes straight to 100% freezing the program. I need to point out I have 64 GB of RAM lol. Even in super large affinity files in the past versions I wouldn't even have 50% of my RAM used. Something is definitely off with this version. I hope they can fix it soon.

     

    I also have Windows 10, Nvidia SUPER RTX 2070 too but its my RAM that seems to be skyrocketing for me.

  8. That is good to know its optional and also Affinity will continue to support offline mode of the tools. It is  one of the huge reasons I left Adobe and bought all the Affinity products in their place. As long as the online sign in stays as merely an extra option and has no impact on offline tool use I am ok with it.

    I have more faith in Affinity than adobe, though I will admit I've seen similar things happen with like substance painter where they said they wouldn't remove perpetual licenses and do just that a year later backtracking their promises. So I will stay vigilant when it comes to any required log-in features for a program I bought that previously didn't use it before.

  9. Hello,

    Yes after I raster the grouped folder I zoom in 100% at least and I can see the raster issue. I've also noticed that if I zoom in closely the issue does not appear to happen on the one I am looking at but some of the other layers out of view do have it always occur. However with larger canvas sizes (like the one I uploaded) its not possible to stay zoomed in on all the layers so the issue happens no matter what unless I re-raster again, then they all magically seem to look ok.

  10. I searched all over and could not find any issues reported similar to this so not sure if Affinity team is aware of it. Essentially when I rasterize a group of layers that are in a folder group (usually these layers were scaled down and there are multiple grouped together) some odd raster effects appear.

    What is even more odd if I undo the raster operation then right click and raster again it completely fixes the issue. If I undo the operation but use the history panel instead and apply the first raster I did the same issue will appear. I am not sure how redoing the same raster operation fixes the issue but here is what is looks like:

     

    Incorrect first raster where it is all pixelated: (sometimes it makes it half pixelated)

    image.png.6c4329701b60c9e0d2a2eb2c7c594323.png

     

    Undoing the raster and re-applying it fixes the issue where everything appears smooth:

    image.png.c9fc16f755c2db837727b4d6d1e24fad.png

     

    I have plenty of memory and with the affinity project file open its only using 16% of my ram and 0% cpu usage so I don't think its a processing power issue where it cannot raster correctly. I am using Affinity Photo windows version 1.8.3.641

     

    I have to constantly re-check everything I raster becasue this seems to happen almost 70% of the time especially for images in groups that were scaled down. I don't think its a particular file format either as I've seen it occur with SVG and PNG files in the same grouped folder and it randomly will affect different ones in a raster.

     

  11. On 3/3/2020 at 7:29 AM, Chris B said:

    Since I last commented on this, I have had a few instances where I've had a pause that lasts a few seconds when brushing/resizing etc. but I can't get a recipe. 

    I've also seen the behaviour where objects cannot be moved/resized as seen in the video from studio97 but I haven't been able to reproduce this. I would encourage you to install the beta alongside the retail version and monitor the improvements Mark and his team are making.

    I am actively trying to get a recipe for both issues—though they are unrelated.

    Thank you for continuing to investigate the issue. The brush resizing issue has definitely been plaguing my work on 1.8. I have lost count how any times Affinity has froze on me where I had to restart the program to regain control. At least I now know my freezing issue is not an isolated incident and others are able to see it at least. I'll have to try the beta version when I get time and see if there are any improvements.

  12. 18 minutes ago, Frozen Death Knight said:

    The freeze we're talking about isn't really about the brushes being slow. The program can freeze at any random brush size, so it happens even at the lowest brush sizes possible. The program just simply stops responding altogether in the middle of using the shortcut and you have to go into the Task Manager to close the program there since you can't close it down any other way. I can try to record the freeze in action some day, but because of how random it is it is hard to make Affinity freeze on command.

    I've noticed if I just open a document and resize it usually freezes but then a few seconds later I will regains control. If I have had a document open for quite awhile working on it then try to resize the program just hardlocks completely and I have to close it with task manager too.

    Again, this issue never occurred for me in 1.7.3 and I have always had my performance set to GPU using my Nvidia 2070 Super so pretty sure the issue is from something in 1.8 changed. I've just been fighting through it by saving my documents very often so I don't have to do any work again if the erase brush resize crashes the program.

  13. I am experiencing this issue since the 1.8 update where the erase brush tool freezes my application every time I increase or decrease the brush radius. It sometimes will take several seconds before I regain control of the application again and in some instance I think the program has just hardlocked on me. I have always had my performance setting to GPU and I have a Nvidia RTX 2070 Super so I don't think its my hardware, I did not experience any freezing like this in 1.7 either. I've been working on a 4096x2048 document as well in-case that extra info is helpful.

×
×
  • 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.