paulie.reklama
-
Posts
36 -
Joined
-
Last visited
Posts posted by paulie.reklama
-
-
16 minutes ago, frindley said:
But this is the problem!
When you open an existing document and then go to save as (e.g. to create an updated version of it), instead of automatically taking you to the folder in which that existing document lives – which is what users expect and would like because it's both logical and what other Mac apps do – the app offers you the latest used file path (i.e. the location in which you most recently saved a document, any document), which might be for some entirely different project.
Or to put it another way:I'm working on Project A and I save it to Folder A. All good.
Then I go to Folder B and open Project B. Work on it a bit; want to save it as Project B_v2. At which point Affinity automatically offers the location as Folder A because that's where I most recently saved something, anything. And if I'm not paying attention, which can happen, I end up saving Project B in Folder A and then wondering why I can't find it next time I need to work on it or share it.
The logical thing to do would be to offer the location as folder B because that's where the Project B file came from.
YES, I totally agree.
-
-
7 hours ago, Old Bruce said:
To create the ability to non-destructively edit in the Develop Persona the various raster file formats would require a container for the raster information from the PNG/JPEG/TIFF etc. Then the container would need to also hold the values of all the various adjustments and apply them to the raster layer. You would have a layer that is no longer pixels and this would mean some things wouldn't work/be available in the Photo persona as well as the other personas.
It could be possible to make such a thing but there would be bugs. Many many bugs. My two cents, I would rather Affinity fix the many many bugs they already have.
I don't know much of the internal structure of the application, but my idea is that the non-destructive Develop persona interface for JPGs (and other non-RAW) could simply behave like a live filter. I don't see many problems with this.
-
10 hours ago, R C-R said:
There really is no such thing as a jpeg object in an Affinity document. All raster objects are rendered either as pixel or image layers & only converted ('flattened') to raster formats during export to JPG, PNG or similar bitmap formats.
So if you use the Develop persona on a raster layer, it is destructive (other than through using the History panel to undo the edits, using snapshots, etc.). This is why it is a good idea to duplicate a raster layer before editing it in the Develop persona.
What AP V2 does have that V1 did not is non-destructive development of RAW files.
Thank for your response, I understand all this principles, but the reason for having the ability to non-destructively edit JPGs in Develop persona is absolutely the same as with RAW, i.e. it significantly speed up my work, also it does mean reducing the overall file size and reducing the total number of layers within the file.
-
Hi, I really understand JAClel's question. I am mostly working with jpg (architecture visualisation, etc.), Develop persona has better faster and more intuitive environment for quick editing, every basic tools what you need are opened, you're just pulling the sliders without working with layers. And what I am absolutely missing in the Photo persona is live filter with perspective correction tools based on sliders (horizontal, vertical, rotate, scale) like in Develop persona. It is absolutely essential for quick and serious work with architecture photography/visualisation in JPG.
I thought that might be the only reason I would switch to the new version of Afiinity 2. So non-destructive JPG develop persona is not possible in the new version?
-
-
-
On 9/30/2021 at 11:08 AM, Pauls said:
I would try the .Net Repair tool then
Hi Pauls, thank you very much for all your effore, but the problem have no solution for me. But I think solution could be also on your side, there is a big room for work on stability issues, need to analyze what changed from version 1.9 which was without these type of problems.
For any users in the future which will have similar problems and will have to stay with outdated versions... please add to Preferences "disable update notification at startup", it is very very annoying and flustering to have to confirm this every time at start.
-
On 10/17/2021 at 5:04 PM, madad07 said:
Can you pls give a bit of tutorial on how to "block dedicated graphic card in windows device manager" ?
cheers
AD
Ok, but I have no english version of Windows, so maybe some names could be different...
-Click in win on START icon
-Write Device manager, click on it
-In Device manager, find Graphic adapter, then use right click on your graphic card, and choose "Disable" or "Block" ..
That's is..
-
On 9/15/2021 at 4:47 PM, Pauls said:
@paulie.reklamawe've not been able to determine an obvious cause. A workround would be to run up the app(s) with the card disabled then untick 'Enable OpenCL Compute acceleration". You should then be able to renable the graphics card and use the apps.
Also could you confirm the exact path to where your application is installed pleaseHi Pauls, thank you for the tip, but when I disable GT525 in windows device manager, the openCL is untick everytime when I run app with the integrated graphic card. So it doesnt work unfortunately.
Exact path of Publisher is C:\Program Files\Affinity\Publisher\ It's on the main system drive.
-
-
On 9/8/2021 at 11:42 AM, Pauls said:
@paulie.reklama Are your graphices drivers up to date ?
Could the try disabling teh GT525M and seeing if affinity apps startup after that ?Hi Paul,
I've checked the driver, it seems to be updated. In 1.9.2 everything is OK with same drivers, so I don't think that drivers should be a problem.
All my Affinity apps run if I block GT525 in win Device manager.
By the way I think that bug is also the fact that Affinity crash if it finds something wrong with GPU. I think the standart reaction should be some notification about non-compatibile GPU and then run with integrated graphic card. Not the crash.
Thank you.
-
-
After new update the problem with crashing at start is still here. The splash screen dissapear after second and Publisher (and Photo also) won't lunch. I am attaching the crash report folder.
- I have i5-2430M, 12,0 GB RAM, GT525M, Windows 10 Pro (21H1) build 19043.1165
- delete temporary folder didnt help
- clear cache (start with CTRL) didnt help
Thank you.
-
Thank you for you response Matthias. Yes, I think, there is maybe more bugs that have different solutions. I've tried each hint in this forum I think. The switching GPU off in Device manager was my advice, 1.10 work with it, but without GPU the apps are very slow, and then I can't use the GPU with other applications also. With the testing of each hint I've deleted the cache(hold CTRL) and app data folder. Just for sure. There is probably nothing to do in my case, I'll be waiting for the fix.
Kind regards,
Paulie
-
6 hours ago, Bamboli said:
Hi everyone here,
the problems seem to be solved. All my desktop versions from the Affinity programs now are running in version 1.10. I deinstalled first the old version, then I installed the new version again. The programs started and I could work fine with it. Thanks to Callum from Affinity for his help!
By the way: On reason, why it's now running can be, that I updated Windows 10 to version 21H1.
Best Regards
Matthias
Hi Bamboli,
I tried it also, but clean instalation had not solve this problem in my case.
I am on the same Win version like you.
-
edit 2: Just out of interest, I've tried start previous good working version 1.9.2 of Photo with mode "start with integrated card" also, its running without problem, but in Photo Preferences is GT525m selected..so windows "integrated card mode" have no impact to the selection card by Affinity apps (Affinity sets dedicated card as a default during start in all cases if it finds the drivers). So I think problem is about noncompatibility of 1.10 Affinity apps with GPU in my opinion.
-
3 hours ago, Pauls said:
@paulie.reklama- What type of graphics card do you have ?
GT 525M.
Thanks.
edit: This shouldn't normally matter, because I tried running the application in mode with an integrated graphics card. But still, the dedicated graphics card probably has some impact on application crashes..(describtion in my previous posts). In 1.9.2 my GT 525M (with same drivers) works with all affinity apps.
-
Also deleting the 1.0 app data folder (temp, autosaves, etc..) didn't help.
-
I'am also attaching crash report. It's Publisher report, but the problem is identical as in Photo.. I've downgrade to previous 1.9.2 version of Photo.
-
edit3:
I found that if I block the dedicated graphic card in windows Device Manager, then launch of all Affinity 1.10 apps is without problem. Its strange, becouse I wasn´t successful with opening the apps in "Integrated card mode" (without hard block in device manager ) before. It looks like Affinity applications are bothered by the presence of a dedicated graphics card even if they don't use it directly. This is definitely the bug.
-
Me too, the splash screen disappears after 1 second and the program does not load. I have Photo and Publisher, it's the same in both cases.
I've tried turn off all my firewalls, run as administrator, run with integrated graphic, run with dedicated graphic, restart computer... all without success. Previous versions run without problem. Instalation of 1.10 od Affinity Photo took very long time, around 10 minutes! Instalation of Publisher was quick as usual.
I have i5-2430M, 12,0 GB RAM, GT525M, Windows 10 Pro (21H1) build 19043.1110
edit: I've downloaded instalation files again and then repair app without any impact... Also clearing cache (after start with CTRL) had not impact.
edit2: Both of the apps run in the Windows Safe mode.
-
Hi, I agree, please add this function.
- p10n, Wood Kit and Marcus_Dobler
-
3
-
Super, thank you :-)
And regarding the crop tool, at least please link setting of the grid and darken border with the presets.
Thank you,
Pavel
Default location for Save As (and Export)
in Feedback for the Affinity V2 Suite of Products
Posted
Can I ask the administrator to move this thread to the V2 section?