Belmont

Wow, so many assumptions, accusations and defections and the announcement isn't even 24 hours old! I know these things don't usually go well, some of my favorite programs got swallowed up never to be heard of again (even hardware, may Ensoniq rest in peace ) which was a real bummer, but take a deep breath and give it a chance to play out. V2 still works and does what it did yesterday before the announcement. It's still a good program. It could use some updates and meaningful bug fixes for sure, but nothing has changed since a week ago. We got exactly what we bought. I didn't buy V2 for what V3 might be, I bought it for the features in V2, and that is what I have and will always have. Maybe it will go subscription in the future, maybe it won't, we don't know. Enjoy what you have now, and move on to something else in the future if the situation changes. Complaining, insulting, insinuating, and condemning now isn't going to change anything, the deal is done. And if they made a bunch of money in the deal, good for them! I have a nice piece of non-Adobe software for a relatively inexpensive price, and they can take a nice vacation with their family and maybe pay down their mortgage a little. A win win. Making a profit is kinda the point of making and selling products after all. Now about fixing those bugs....how 'bout it guys....

Is it possible in Photo to draw a curve with the pen tool, then have that curve use one of the brushes to make the line? There is (still) an option in the pen stroke dialog for a texture line style but that (still) doesn't seem to do anything. It would be nice to be able to make a precise curve and have it 'drawn' with one of the brushes.

Has there been any progress on fixing this?

I want to just add another request for this. This really shouldn't be an issue the users have to deal with.

When I create a new document or open an existing one Photo sizes it to my screen. If the image is lower resolution than my screen it effectively zooms in. Is there was way to have Photo only scale the image down to fit in the window and not scale it up? I find myself always having to press CTRL+1 whenever creating or opening an document which is just annoying. Thanks for pointing me in the right direction.

Nevermind...stupid moment on my part! I was looking in the beta, not the released version.

I keep reading that the insky brushes were supposed to be available in AFPhoto on the welcome screen. I don't see that. Is there another place I can get them?

In the latest release, when creating a procedural, what you type in the equations field doesn't stay. For example: Open up an image Open up the procedural texture filter You should have no equation lines yet Click on the + to create a new equation line. It will just show a 0 in the field now. Change that 0 to x and hit enter or tab. Notice how the display goes back to 0 but the filter actually took effect? If you click back in the field it will show what the equation actually is (in this case just x). If you create another equation line by clicking the + button then the original line will now show the equation that was in there and the new line will show 0.

That is what I was doing wrong! I must have had a pixel layer selected 'by mistake' when it worked. Thank you very much for clearing that up!

Just a clarification for us PC users. Instead of hitting the delete key, hit the backspace key or you will delete the whole layer. That is what happens on my system anyway. They might want to fix this.

I'd like to make some suggestions for making the creation and use of the procedural texture filter a lot easier. Allow the formula to be created in a text area, not just a single line. Making this area collapsible would be great so you could hide it if desired Instead of having to use the RGBA buttons to target a channel, just make those global variables. Then from any equation, if you set R = some value, it would affect the red channel. Documentation There really needs to be more documentation. Not just a list of functions but what those functions do and possibly an example of what they might be used for. Not teaching mathematics but at least giving the idea of what a function does. There is mention that you can't use a variable name that clashes with established function names but there isn't a list of all the function names. Yes, there are the functions like smoothstep, vec3, abs, etc. But it also says you can't use w but we aren't told clearly what w stands for. I know it is width but there is also h which is height and that isn't mentioned anywhere. And then there is rx and ry which are very important but never clearly defined. Having all these clearly defined with an explanation of how they are used is a must. And when would you use x and when would you use rx? I know some of these answers by trial and error but more straightforward documentation would be very helpful. Range inputs It would be really nice to have input ranges instead of just 0-1 and -1 to 1. Without this you have to put scaling variables in the equation which just makes things messy and difficult to read and control. Letting the user define they want the slider to be a real number slider between 1 and 100 (or whatever other range or number types) would be wonderful. Errors It would be really helpful for the system to highlight where the error is instead of just not applying the filter. This would make it easy to find an error quickly especially if it is just a simple error (missing a ; or putting in " instead of ', etc) That's it for now. It's really fun to play with the procedural texture feature but frustrating at the same time. Through trial and error I've been able to make some interesting things but it is very slow going partly because of the above issues and partly because my math education stopped in high school...

Thank you!

Forgive me if this has already been answered. I looked but couldn't find the answer. Is it possible to do a tileable fill with Affinity Photo? I've seen references to doing it in designer but not photo. I did a bitmap fill using the gradient tool but it doesn't tile the bitmap, it just extends the edges which is not very useful (for me anyway). Thanks

Thank you. That's a good start.

In the docs for the procedural texture filter there are lines like this: mapcui(T v, T edge0, T edge1) perlin(S x, I octaves, S persistence) What do the S and T and V's mean. I'm guessing V is for vector. What are the others?