-
Posts
522 -
Joined
-
Last visited
Posts posted by Max N
-
-
1 hour ago, Mark Ingram said:
For ref, we only use .NET for the UI, so the memory usage is unrelated to garbage collection.
Now, for the interesting part, yes, the memory usage will appear much higher in this build, and you will not be able to open a file, then close a file, and compare the amount of memory in use. We need to make sure the amount of memory doesn't keep increasing through the lifetime of the application, hopefully it should steady out at a certain level (which will depend on what you've got set in performance preferences).
If the AP is running during the working day, and I open 100-200 images per day - will this affect the performance of the AP or not? Do I need to restart the program each time or will the used memory size be used as efficiently as if I had just opened the program?
-
When you run the program takes 195 MB of RAM.
Opened in the program 10 cr2 files. Closed all tabs.
The program takes 3.6 gigabytes of memory.
This is normal? -
47 minutes ago, Juergie said:
The same problem as in the beta version before!
I did not know about this problem.
-
-
44 minutes ago, Chris B said:
Hi Max N,
This is my fault. I missed the bit below your link:
I thought you were reporting the Paint Mixer crash again—I'm very sorry.
As Rick said, I have had this happen to me and I've seen other reports but haven't found a recipe yet Are you getting any crash reports?
We've got a new feature for the beta (Preferences > Misc > Include registered name xxxxx for diagnostic purposes) which allows us to find crash reports using your email (which I can find from the Admin panel) so I can ask dev to take a peek and see if we can find what is going on. This can still be a minefield if you're having other crashes, so when it happens again, please let us know roughly what time and day so we can narrow down our search
The program is closed but the message about sending the report does not appear. The program just instantly disappears from the screen, as in the video to the last error.
As for the new function, I'll try to turn it on. I did not find a recipe for how to get a crash. -
1 hour ago, Chris B said:
We have a log of this for Windows and macOS. There is no need to raise a new thread if something hasn't been fixed in a beta update. Simply bumping the original post is enough to bring it to our attention again. We can then do our best to notify the developers that this is still an issue.
Thanks!
Thank. Always happy to help with any information.
Created a new topic because I haven’t met this error yet. For the errors that I described on the forum and which are not in the log, I do not write. I am writing only about new ones. I can duplicate the topics that are on the forum, but the reason is very poor knowledge of the language. -
14 hours ago, Rick G said:
I have experienced this although I cannot pin it down to a specific cause
I definitely can not say what exactly was the cause. But program crashes occurred while working with layers. -
In the last betta version I described the problems of arbitrary closing the program when working with a mix brush.
In (1.7.0.231), the program closes when transforming and dragging layers (there were masks and groups, not sure if this is somehow connected). The program closes without sending an error report.
-
1 hour ago, Gnobelix said:
Hello Max N,
The transformation macro work correctly for me,
in the attached is an example macro, please try it out and report what happens to you. Thanks
Your macro works correctly.
But you do not have a transformation layer. I think the error happens in this step. -
52 minutes ago, Chris B said:
Does this happen if you set your document to use pixels? If so, this is already logged and needs a bump.
Moreover, if the stabilizer is turned on, the size of the point changes minimally depending on the pressing force. A point with a maximum force of clicking on the pen can turn out as the minimum size, and any other. Problems arise only with drawing points (without moving the stylus over the surface of a graphic tablet).
-
42 minutes ago, Chris B said:
Does this happen if you set your document to use pixels? If so, this is already logged and needs a bump.
Here? No, this does not solve the problem.
-
If you draw a point with a stylus (pressing force = brush size), the diameter does not change in real time. The diameter of the circle can only be seen after the stylus has been raised above the surface of the graphic tablet. It is necessary to guess what diameter the point has turned out. There is no such problem with the lines.
-
The problem remained in version 1.7.0.209.
-
-
For the latest version did not check. But judging by the list of changes, there should be no difference.
-
Brush preview is not size. The dynamics of sour from 0% to 100%, the preview is not displayed as 0%, which prevents the brush from being correctly positioned.
Wacom pth-451, windows 7 64-bit. -
In 1.6 I did not encounter such a problem. In 1.7, this is a permanent error.
I often work with a brush mix. And I have a question, will someday be saved settings brush (all). In PS, I set up a brush mix two years ago and I work for her. In AP, when I open each document, I should make about 5-7 clicks of the mouse before starting to work. For the year, this is thousands of extra gestures. -
1 hour ago, Sean P said:
Hi Max,
Could you attach a copy of the document in the video please?
It looks like the stroke on the top object (possibly a group?) is actually applied to the objects inside, so when the clipping is applied, its applied to the top (possibly group) object causing the line to be clipped. -
1 hour ago, Sean P said:
Hi Max,
Could you attach a copy of the document in the video please?
It looks like the stroke on the top object (possibly a group?) is actually applied to the objects inside, so when the clipping is applied, its applied to the top (possibly group) object causing the line to be clipped.
Group in order to draw a vector illustration that needs to be cropped, and around which you need to make a stroke.
With a single vector figure, the result is the same. -
36 minutes ago, Sean P said:
Hi Max,
This is a known issue (that isn't new to this beta) that is already with development to be fixed! Thanks for letting us know -
The trim tool works differently with stroke on vector and raster objects. Is this an idea or a mistake?
-
A shape outline appears below the stroke.
-
The program closes when working with a mix brush.
-
The transformation macro is applied incorrectly.
There is an error in both the stable and beta versions.
Focus does not go to the active tab. 1.7.0.243
in [ARCHIVE] Photo beta on Windows threads
Posted
When working with a large number of documents, the focus does not shift to active document management. There is no possibility to close the document by clicking on the cross.