Mark Ingram
-
Posts
5,358 -
Joined
-
Last visited
Posts posted by Mark Ingram
-
-
4 hours ago, dbeach said:
Me too. I can't go 5 minutes doing simple tasks such as using the paint brush without a crash.
HP Spectre x360 Convertible 150ch0xx
Processor Intel(R) Core(TM) i7-8705G CPU @ 3.10GHz 3.10 GHz
Installed RAM 16.0 GB (15.8 GB usable)
System type 64-bit operating system, x64-based processor
Pen and touch Pen and touch support with 10 touch pointsTry disabling hardware acceleration and see if that's better.
-
1 hour ago, Coirt said:
Direct feature and DirectX are the same thing. It is called DirectX because it sounds cooler. I'm on the may 2020 update.
No, that's not true.
-
10 minutes ago, walt.farrell said:
I'm not sure. If I use Shitf+F1 (for example) as a keyboard shortcut, Affinity sees it as Shift+F1 not F13. So perhaps that approach is not applicable with the Affinity applications.
Yes, I think you'll need a "physical" F15 | F16 key (or for Wacom to send it via hardware).
-
38 minutes ago, Yuli said:
Can we get an update for the brushes panel? The selection is gone after changing size of the brush or tool! I don't think this is too complicated to implement, please consider it
Please post feedback in the feedback forum - https://forum.affinity.serif.com/index.php?/forum/53-feedback-for-affinity-designer-on-desktop/
This thread / forum is for issues specifically affecting the latest customer betas.
-
Really those shortcuts are designed for Wacom tablets or similar. We already have shortcuts for zoom configured by default.
-
@RichardMH | @iHarri | @TEcHNOpls, I'm going to delete this thread, because 1005 build has some significant changes to hardware performance.
-
-
-
25 minutes ago, Coirt said:
Is there a list of compatible GPU's?
Any Direct3D Feature Level 12.0 card, except AMD Radeon 5000 series or above cards are supported. There is info in the help file about the requirements.
-
@kfriis, try disabling hardware acceleration and see if that makes a difference. If it does, can you let me know what GPU and driver version you are using?
-
On 3/7/2021 at 5:27 PM, Basse said:
Hi,
There are 22 *.dmp files (the last one 25 min ago) in the specified subfolder %APPDATA%\Affinity\Photo\1.0\CrashReports\reports. I've attached the oldest and the last two. Thanks so much.
ffbf7808-8505-47e4-a4e5-6cf53af0b87c.dmp c5826552-2235-48e3-b217-2d6c09913ad7.dmp 1e644d7b-26ef-432c-b349-689e8ea5e961.dmp 10e5f652-63d6-4d73-a3ac-f0b0cea8175e.dmp
Thanks for the crash dumps. I can see that it's crashing due to a bad Intel OpenCL driver that's installed (Intel are aware of this problem). You can either try updating your graphics card drivers, or, you can grab the latest beta to try, as we can work around these driver crashes at startup now.
-
Hi @Miri, I've looked at the crash dumps, and unfortunately I can only see that it's crashing inside .NET somewhere. The log file you provided shows a clean startup and shutdown (the "Exit" on the last line indicates shutdown was OK, and not a crash). Do you have a log file from the crash itself?
-
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
- Fixed crash with Vector Brush Tool when the Appearance panel is open and undoing a brush stroke and selection changes to an object that had no linestyle
- Fixed failure to create an object style if the only delta was line weight
- Fixed loading of certain assets consuming huge amounts of memory
- Fixed specific Print Profile crash
- Fixed crash when dragging Unsplash images from panel when Unsplash is returning errors
- Added F15 / F16 zoom shortcuts for tablets
- Fixed print orientation being wrong when printing Label with Auto Rotate selected
- Fixed stroke width being printed incorrectly on rotated objects
- Fixed "Print job was cancelled from print manager" using Canon iPF 5100 drivers
- Fixed ending the print spooler from Services causing the app to hang
-
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.Benchmark thread - https://forum.affinity.serif.com/index.php?/topic/137515-benchmark-1920-results/Changes
- Improved hardware acceleration performance
- Improved Lens Correction identification
- Added ability to organise LUT adjustment presets, including support for multiple categories and import / export as ".afluts" files
- Fixed LUT Adjustment being slow to respond after importing LUT
- Fixed loading of certain assets consuming huge amounts of memory
- Fixed specific Print Profile crash
- Fixed crash when dragging Unsplash images from panel when Unsplash is returning errors
- Added F15 / F16 zoom shortcuts for tablets
- Fixed print orientation being wrong when printing Label with Auto Rotate selected
- Fixed stroke width being printed incorrectly on rotated objects
- Fixed "Print job was cancelled from print manager" using Canon iPF 5100 drivers
- Fixed ending the print spooler from Services causing the app to hang
-
10 minutes ago, Ian Brockbank said:
Yay! This is the first 1.9.x which will start on my computer.
Thank you.
Sounds like you may have a bad Intel OpenCL driver on your machine, we've had a few customers who've reported similar issues (Intel are aware of the issue and are investigating).
-
3 hours ago, ArthurFfox said:
Can't find the file named "1.0" or Log.txt but I will be sure to turn off OpenGL. Thanks!
If you paste the bold text from my post, it will take you to somewhere like:
C:\Users\your_username\AppData\Roaming\Affinity\Photo\1.0
-
Probably bad OpenCL driver @JohnWest. I would encourage you to try the current beta version as that will work around the bad drivers.
-
@ArthurFfox, could you upload a copy of your log file? %APPDATA%\Affinity\Photo\1.0\Log.txt
After that, try disabling hardware acceleration in preferences.
-
29 minutes ago, enecece said:
Hello,
Same here. I was working fine with my version of AP a few minutes ago. I have just updated to 1.9.1 and I can't even open a file:
- I create a new document, and try to create a new pixel Layer. AP goes "Not responding"
- I create a new document and select the Pen tool. AP goes "Not responding"
- I create a new document and drag&drop an image. AP goes "Not responding"
It is not that crashes occasionally, but I have passed from being able to work to not working at all because I can do nothing without getting the "Not responding" status.
Here is my dump file (-zip):
https://www.dropbox.com/s/m14u24do6udttln/affinity-photo-dump.zip?dl=0
I hope somebody can help me.
Thanks for the dump file. I can see that we're trying to enumerate the graphics devices that you have on your system. We try to initialise one of these graphics devices in order to render to it, but then the driver hangs. I can see it's hung in igdrcl64.dll which I think is part of the Intel graphics driver. You've got 23.20.100.8142, so you may want to check for an update.
-
4 hours ago, Captain Haddock said:
Same here. 1.9.1 very slow on Windows. Simple image and the merge down function took 20 seconds and no better with HA disabled. Just downgraded to 1.8.5 and solved the problem.
With hardware acceleration disabled, there should be no (negative) performance differences between 1.9 and 1.8.5. If that is the case, we should investigate. Please can you attach a file that demonstrates Merge Down being slower in 1.9 (software) vs 1.8.5?
-
2 hours ago, Michael Tunnell said:
The problem is that most people do not adhere to this at all... <snip>
That's a great post Michael, thanks for your level-headed thoughts on this matter.
-
4 minutes ago, Redsandro said:
Fair enough. That's why we hope to get the WINE support. I would recommend a WINE check in your software though, so you can gather telemetry on how many users run your Windows version on Linux. You'll get an insight for free. You may notice that there aren't enough Linux users and your suspicions were right. You may even want to share the percentages after a year or two, to stop this discussion with some statistics as opposed to suspicions from both sides.
Yeah I'd definitely be interested in seeing how many users we had via WINE!
-
26 minutes ago, m.vlad said:
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
If the company fails, then the product wasn't very good. That's something that the market has decided. I understand the argument more with DRM related things, like, what happens if I buy some music, then my the company disappears, and I've lost my music forever, however, this isn't the same. If the company goes away, then the software still remains. But as I say, if the company has gone, then it means a better product has arrived.
27 minutes ago, m.vlad said: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.
Yes, because there's a massive market there (Windows and macOS), and we believe we can compete with those alternatives. On Linux however, we don't know if there are going to be enough people willing to pay for the software, to fund the development. i.e. what's the _potential_ market size of photo editing on Linux? (It has to be potential, because the current market size is zero).
Basically all that post did was highlight the concerns that we have, that people outright reject the concept of paid software on Linux.
-
15 minutes ago, Snapseed said:
I get the impression that a subsection of Linux users want software to be both open source and no cost so that they do not have to pay anything or donate anything. That is all very well but developers still have bills to pay and so I am fine with paying for softwar
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...
Apps won't launch on Win10 after Upgrade to 1.9
in V1 Bugs found on Windows
Posted
RE: resolution. You can change the Display Scale in Windows, so you can have high resolution and larger fonts etc.
RE: Multi-GPU, what issue is it causing?