AdamStanislav
-
Posts
537 -
Joined
-
Last visited
Posts posted by AdamStanislav
-
-
-
OK, I tried to install .net 4.7.2 manually. That failed, too. It opened the following in my web browser:
OS Version = 10.0.14393, SP = 0.0, Platform 2 OS Description = Future OS - x64 MSI = 5.0.14393.576 Windows servicing = 10.0.14393.0 CommandLine = D:\72cf8c361efa54f2901a69\\Setup.exe /x86 /x64 /redist TimeZone = Central Daylight Time Initial LCID = 1033 Using Simultaneous Download and Install mechanism Operation: Installing Package Name = Microsoft .NET Framework 4.7.2 Setup Package Version = 4.7.03081 User Experience Data Collection Policy: Disabled Number of applicable items: 6 Exe (D:\72cf8c361efa54f2901a69\SetupUtility.exe) succeeded. Exe Log File: dd_SetupUtility.txt Exe (D:\72cf8c361efa54f2901a69\SetupUtility.exe) succeeded. Exe Log File: dd_SetupUtility.txt Exe (D:\72cf8c361efa54f2901a69\x64-Windows10.0-KB4054590-x64.cab) failed with 0x57 - The parameter is incorrect. . RmRestart failed with error: 352 Final Result: Installation failed with error code: (0x00000057), "The parameter is incorrect. " (Elapsed time: 0 00:03:37).
And the dd_SetupUtility.txt says,
[06/06/2019-16:04:07:607] INFO: Log file path: D:\tmp\dd_SetupUtility.txt [06/06/2019-16:04:07:607] INFO: #################################################################################### [06/06/2019-16:04:07:607] INFO: **************** SetupUtility Started **************** [06/06/2019-16:04:07:607] INFO: Command Line: SetupUtility.exe /aupause [06/06/2019-16:04:07:611] INFO: Pausing Automatic Updates ... [06/06/2019-16:04:07:611] INFO: ... succeeded. [06/06/2019-16:04:07:611] INFO: **************** SetupUtility Ended **************** [06/06/2019-16:04:07:853] INFO: Log file path: D:\tmp\dd_SetupUtility.txt [06/06/2019-16:04:07:853] INFO: #################################################################################### [06/06/2019-16:04:07:853] INFO: **************** SetupUtility Started **************** [06/06/2019-16:04:07:854] INFO: Command Line: SetupUtility.exe /screboot [06/06/2019-16:04:07:854] INFO: **************** SetupUtility Ended **************** [06/06/2019-23:15:26:424] INFO: Log file path: D:\tmp\dd_SetupUtility.txt [06/06/2019-23:15:26:425] INFO: #################################################################################### [06/06/2019-23:15:26:425] INFO: **************** SetupUtility Started **************** [06/06/2019-23:15:26:425] INFO: Command Line: SetupUtility.exe /aupause [06/06/2019-23:15:26:427] INFO: Pausing Automatic Updates ... [06/06/2019-23:15:26:427] INFO: ... succeeded. [06/06/2019-23:15:26:428] INFO: **************** SetupUtility Ended **************** [06/06/2019-23:15:26:604] INFO: Log file path: D:\tmp\dd_SetupUtility.txt [06/06/2019-23:15:26:604] INFO: #################################################################################### [06/06/2019-23:15:26:604] INFO: **************** SetupUtility Started **************** [06/06/2019-23:15:26:604] INFO: Command Line: SetupUtility.exe /screboot [06/06/2019-23:15:26:605] INFO: **************** SetupUtility Ended ****************
-
1 hour ago, walt.farrell said:
It would help if you can provide more details about your version of Windows 10. If you use Windows Start > Settings, then under System click on About, what version number and build number are shown?
Windows 10 Home, version 1607, build 14393.953.
-
Tried to upgrade Affinity Designer from 1.6.5.135 under Windows 10 to 1.7.0. It tried to install .net, which failed saying a parameter was wrong (did not say which parameter). It wouldn’t even bother me that much if the old Designer stopped popping up the message asking me if I want to download the upgrade.
So, what now?
-
My SVG viewer? I always view my SVG files in several viewers, including two different web browsers as well as opening the SVG in Affinity Designer. All I am asking is how do I turn your color management off. Just put the same colors into the SVG file that I have chosen for the .afdesign file.
-
This is so frustrating. When I create a new document, AD insists on managing my colors. Why? Why, why, why?! My monitor is properly calibrated and the system (Windows 10) driver manages the colors. But AD thinks I want it to manage the colors, too. So, after carefully choosing the right look, and exporting the image to SVG or other format, the result looks disastrous.
Why is AD doing this? And how do I turn it off? There seems to be no way to turn it off. There is a myriad of options for a profile, but there is no do nothing option.
-
On 8/14/2017 at 5:50 AM, Matti Lintula said:
The pressure sensitivity started to work. I just chose a different brush (Solid brush with pressure size 128) and adjusted the brush width (to 30) and it works. I have no idea why that helped, but it did.
Thanks for that information!
-
There will only be ONE 1.5.0 release build and only ONE 1.5.1 release build of Affinity Designer for Windows, and at some point there will be only ONE 1.5.2 release build to the public. The Public Released app will only prompt to patch 1.5.1, 1.5.2, 1.5.3, 1.6.0, 1.6.1 etc.
OK, thanks.
-
The only way I know of is to check the News section of the forum - https://forum.affinity.serif.com/index.php?/forum/4-news-and-information/ there's a post from Patrick Connor announcing the new build - 1.5.1 and there is a link to the initial announcement - https://forum.affinity.serif.com/index.php?/topic/30631-affinity-designer-151/
It's best to check back with the News section often.
Thank you, though I’d be surprised if most Affinity users were even members of the forum. It would make more sense for the software itself to check it automatically every so often and/or have an option to check for the latest version from the Help menu.
Anyway, I have version 1.5.1.43. Is it the latest? Because the announcement only mentions 1.5.1, but not the fourth number.
-
The beta has expired because the latest customer beta is the same as the latest patch.
There’s a patch? How do we find out about it, and where do we get the patch from?
-
I believe they can only be turned off in the Pro version.
Maybe for the average person. But if you know how to get to the services (e.g., press Win+x, then g, then select Services and Applications, then Services), you can scroll down to Windows Update, stop the service (if running) and disable it. And then, when/if you want to check for updates, enable it, turn it on, check for updates, stop the service and disable it again.
-
This entire use of pixel units makes no sense to me. AD is a vector graphic design software program. There is no concept of a pixel in a vector graphic. Strictly speaking there are no points, either. There is not even a size in a vector graphic. There are just some abstract relative units; relative to the overall graphic, not to anything in the physical world.
Only when a vector graphic is being rendered, whether to a bitmap image, or a vinyl cut, or whatever else, do physical units enter the equation. But they are different for different renders.
-
Mark, just because it isn’t an Affinity error message does not mean it is not caused by something inside Affinity. TLS is a protocol used by encrypted communications over the Internet. Since AD always checks if there is a new Beta available, it is perfectly conceivable this message is related to Affinity, albeit indirectly. If anything, it should not be causing a fatal error in Affinity.
-
Let’s not forget that the entire idea of what is white is relative. There are many objects we call white, but if we placed them next to each other, we’d see they often are quite different. No matter how white something is, we can always think of a whiter object. Our brains know it and adjust for it automatically, even for those who are completely oblivious to the relativity of colors (on the other hand, digital cameras either need to have their white point set, or contain some software that sets it automatically, though not quite as successfully as our brains).
In graphic design it is very important to keep that in mind. I have always been puzzled why various flags depicted on wikipedia in the SVG format use #fff as white. Why puzzled? Because that is also the color of the background of wikipedia pages. As a result, the white portion of such flags simply become “invisible” because they are indistinguishable from the background.
Please, don’t just take my word for it. Take a look at the Flag of Russia on wikipedia. What it actually looks like is as if it had two colors, blue and red, though placed lower than the top of the page. Compare that to the Flag of Russia I made back in early August. It has all three colors, white, blue and red, all clearly visible despite its white background because I used #F7F7F7 for the white stripe.
That AD programmers have chosen a default other than #FFFFFF shows they understand the problem. Good for them!
-
-
Back when I started Beta testing AD for Windows (which seems like a long time ago, even though it was not :)), naturally, I went through all the official AD tutorials on Serif’s web site (and some unofficial ones on YouTube) to see what it can do, so I know what to test.
Having watched them all, some more than once, I concentrated on the testing.
Well, just today, I went back to the Serif tutorial pages and was pleasantly surprised to find a number of new tutorials specific to v.1.5. They have added many nice new features I didn’t know about.
If you have not visited the tutorial pages lately, I suggest you do so. Not just so you can get impressed (which you will), but so you know what new things you may want/need to test, since of course if we don’t know about some of the features, we won’t Beta test them.
Adam
P.S. No doubt some of the people reading this work for Serif’s competition. That’s fine, of course. I do, however, want to suggest you make sure to be seated when you go visit the newest tutorials, as you may get quite dizzy seeing all the new ideas and things. :P
- Patrick Connor, Alfred, Mark Ingram and 1 other
-
4
-
Agree. As Leonardo da Vinci once said to an impatient pope, "It's finished, when it's finished!" Let them do there work. You'll be the first to know! ;)
I thought it was Michelangelo Buonarotti telling that to Pope Julius II. :P Or should I say Charlton Heston to Rex Harrison (The Agony and the Ecstasy, 1965)?
-
Not too many programmers take this kind of time and patience any more.
Hey! It’s not the programmers’ fault when the companies they work for rush things to production before being ready. Serif is clearly one of the few companies that let their programmers do their job right.
- Heath9409 and Mark Ingram
-
2
-
-
Please implement an auto updates features into the software.
Oh, gosh, nooooooo!
-
It turns out my statement was wrong! The macOS version does indeed support Type 1 fonts, so we will add support to the Windows version as well. Keep an eye on the changelists in the coming weeks.
That’s the best news I’ve ever read on this forum. Thanks, Mark!
-
I should add that the reason why I posted this was to help you by showing you how I do the things I do because it seems to me most vector graphic software is not even aware of the possibilities.
-
You should have been prompted to open those files the next time you start Designer. On a clean close of the application, it should remove those old autosaves.
Well, I wasn’t prompted. And they were not removed until I found them there today.
-
I've just closed AD, declining to save the *.autosave file and another modified file that I had open, and only the most recent (0 KB) autosave has been removed: the other four (including one from four days ago and another from more than two weeks ago) are still there.
I was only opening them one at a time, always opening the most recent one left. So that’s consistent with your experience. :)
Upgrade to Designer 1.7.0 (Win) fails
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
No, 4.8 failed, too: