Mark Ingram
-
Posts
5,358 -
Joined
-
Last visited
Posts posted by Mark Ingram
-
-
2 hours ago, AdamRatai said:
Yupp, my problem vanished for good with when hardware acceleration is set to off, so I change topic and added "fixed'.
Thanks, but disabling the feature isn't really a fix 🙂
-
-
-
Hi @walddys, when exporting, on the "Rasterise" option, choose "Nothing".
-
Hi @Magicbean, thanks for the report. I've moved your post to the non-beta forum, as you mentioned this is a problem in the retail builds too.
-
-
Are you on Windows or macOS? Does some other software require ".tif" file extension?
-
-
3 hours ago, Roberto Sdul said:
In tools, when selecting the box, zooming in with the mouse wheel, the horizontal movement is lost, it should be done with the shift key plus the mouse wheel so that the image moves horizontally.
Best regardsIf you've enabled "Use mouse wheel to zoom" then you need to hold Ctrl in order to change to scroll mode (then press Ctrl+Shift while using mouse wheel to move horizontally).
-
-
-
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.Changes
- Added missing "My account" button
- Added new samples to the welcome screen
- Added anti-aliasing blend option
- Added "Find in Layers Panel" menu item
- Changed default for "Show Selection in Layers Panel" to be on (and renamed to "Auto-scroll to show selection in Layers Panel")
- Fixed incorrect attribute bits in exported 32-bit TGA
- Allow downloads to be cancelled, and changed auto-download to be off by default
- Fixed PDF export converting RGB bitmaps to CMYK if the original document had the bitmap's working profile
- Improved PDF import of tinted colour comparison for registration colours
- Improved Assets drag and drop from Explorer
- Added Ctrl+RightMouse to display tree of objects
- Improved ABR import
-
-
Click here to download the latest beta
Status: Customer Beta
Purpose: New features, performance, 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 Ctrl Reset not removing Assets
- Fixed crash when editing a macro with no document open
- Added Combined Raster & Vector benchmark
- Added placement policy
- Added missing baseline menu options
- Fixed blending issues with Live Filters
- Added support for 12bit mono TIFFs
- Added Pattern Layers
- Added Live Liquify
- Fixed pressing Backspace during Freehand Selection Tool (Polygonal mode) deleting the layer, rather than the last node
- Fixed Develop Persona Crop Tool rotation producing artifacts
- Fixed Focus Merge always creating 96DPI documents (now uses DPI and metadata from first source image)
- Fixed Live Projection artifacts in 32-bit documents
- Fixed cancelling Crop Tool not doing anything
- Added anti-aliasing blend option
- Added "Find in Layers Panel" menu item
- Changed default for "Show Selection in Layers Panel" to be on (and renamed to "Auto-scroll to show selection in Layers Panel")
- Fixed incorrect attribute bits in exported 32-bit TGA
- Allow downloads to be cancelled, and changed auto-download to be off by default
- Fixed PDF export converting RGB bitmaps to CMYK if the original document had the bitmap's working profile
- Improved PDF import of tinted colour comparison for registration colours
- Improved Assets drag and drop from Explorer
- Added Ctrl+RightMouse to display tree of objects
- Improved ABR import
-
1 hour ago, phoenixart said:
If you're incline to do so, my other advice is to use a tool called Display Driver Uninstaller.
I've used DDU a few weeks ago, as I had 2 NVIDIA GPUs that wouldn't work at the same time as each other. Following that I was able to re-install the latest driver and get them working together.
-
14 hours ago, AiDon said:
@Mark Ingram Hi Mark, I know this is an ongoing issue where suggested causes are both NVIDIA and Capture One, but how is it I can open and process a single RAW image but not multiple RAW images at the same time whilst using these settings? On a single image I can use Develop, Liquify and Tone Map Personas but working with more than one image still causes a Stack overflow in nvwgf2umx.dll :
Unfortunately I don't know - that crash location is the NVIDIA driver, as previously mentioned, so only they can say why it is crashing. I have reported the issue to them (and shared a crash dump, to which they have confirmed the stack overflow in their driver), but as we can't reproduce it here internally, they won't investigate further.
My only suggestions are:
1) Report the bug to Capture One
2) Report the bug to NVIDIA
As frustrating as this is, at this point, there is nothing else we can do.
-
2 hours ago, BartHovis said:
Well, things were going well this morning, but the crashing has returned. It appears that it will crash when I do File->Open (the file will open but AP crashes when doing any editing). However, if I open a file using File->Open Recent, I can edit and save files with no crashing. I'm attaching the most recent Crash Reports.
Yes that's what I suspected, it will only crash after showing the Open or Save dialogs. This does indeed sound like the bug caused by Capture One.
-
I'd be interested to know if it continues to work after a reboot?
-
Just now, Joachim_L said:
I might think your way of bug tracking is somewhat not too effective. In August 2019 you were aware of this bug and in the meantime the information about this got lost or was forgotten? And you have to be reminded again in the SAME post it was originally written? I admire all the busy forum users writing thousands of posts and remembering when they wrote something.
Not complaining here, you run your business and this bug is not top priority for me (I got used to it over the time).
The forum is not our bug tracking system, we have our own internal system. We haven't lost the information, I was just asking that discussion around a bug be kept in one place. We have links from our internal bug reports to forum posts, so if everyone makes a new post on the forum every few months, we get huge lists of forum links that we have to go through to read all the information.
-
Thanks @BartHovis - it looks like you might be using Capture One. We've seen customers complain of this same crash when using their thumbnail provider. Could you either disable their thumbnail provider, or, temporarily uninstall Capture One? Also, could you try doing File | New and seeing if that works? i.e. is it only crashing when picking an existing document to open?
-
10 hours ago, Fritz_H said:
Well, not referring to the main topic?
I will take this as an answer, Thanks.I'll be direct - please don't make duplicate posts, as it makes our job much harder 🙂
If something hasn't been fixed, and you have already reported it in another thread, please post in the original thread, then we can see all of it's history and discussion without having to search around for similar posts.
- Manofjesus and Alfred
-
2
-
7 hours ago, BartHovis said:
Hi Chris,
I've attached a .dmp file that was just generated. I am using Nvidia Studio driver 457.30, just installed yesterday.
Thanks,
Bart
I've just looked at the crash dump, and it's crashing inside the NVIDIA driver.
Could you try uninstalling and reinstalling the drivers to see if that works? We often find that an uninstall and reinstall works better than just updating the drivers.
-
Please don't complain about the stability of the beta builds. They are meant for testing, and you should expect bugs. I'll paste the top paragraph that I put into every new beta forum post:
QuoteAs 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.
I've commented on Scanner support previously in other threads. Your scanner manufacturer will provide software to import your scans, then you can just import those images / documents.
- Alfred, AiDon, Move Along People and 2 others
-
5
-
3 hours ago, BartHovis said:
I've tried a few different Beta builds, but in every case when I attempt to open a file AP crashes. My GPU is Nvidia GeForce RTX 2080 Super, perhaps it's not supported, but would this latest Beta fix the crashing problem?
I have that graphics card, and it works fine - so might need a few more details from you (or a crash report). Have you tried uninstalling and re-installing the latest Studio drivers?
Designer beta 1.9.0.864 on Windows 10 much slower than previous version
in [ARCHIVE] Designer beta on Windows threads
Posted
The user marked their own report as "fixed" after switching off the feature. That's not what we class as a fix, as we need to investigate why it wasn't working as intended.