Jump to content

Belmont

Members
  • Content count

    26
  • Joined

  • Last visited

About Belmont

  • Rank
    Newbie

Recent Profile Visitors

313 profile views
  1. 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!
  2. 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.
  3. 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...
  4. 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
  5. 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?
  6. Belmont

    Slow performance still

    Just realized something...the performance problem only happens when dragging the size handle in the bottom right. If I drag any of the other corners it works fine. Strange.
  7. Belmont

    Slow performance still

    Excellent, thanks.
  8. It seems the performance in the newest beta is still messed up. See the movie I attached. All I did was create a new document, float the window, then drag t he window size handle around. This doesn't happen in the production version. My computer is a windows 10 machine running an i5 processor and 2 GB NVidia card. Nothing to brag about but totally sufficient for Affinity. Matt 0001-0213.mp4
  9. Has anything be found out about the problems described above?
  10. Same problem here. It is even worse if you try and resize a floating window.
  11. The procedural textures are a neat idea but they seem very unusable unless you have a math degree. The same was true with the equations filter. Perhaps making some sort of user friendly interface would increase their usage and make them more useful? Or at least substantial documentation with lots of examples.
  12. I second all of these suggestions. I was just trying to replicate my process for gathering up pictures for scapbooking and these deficiencies make the whole process take 10 times as long as it does in photoshop. It's simple things like this that make the program so much more useful. I realize I could come up with a different process that might fit AP better but these suggestions seem so 'simple' and logical. Another example: I convert all images to 320 dpi for printing (that is how the printer wants them). So when making a layout I create a 12x12 320 dpi image to create the scrapbook layout. Now I open each picture that will go on that layout. They open with 72 dpi so I have to convert them. In PS all I do is grab the crop tool, set it to 320 dpi (once per session) and then crop the image to whatever size I need. It automatically converts it to 320 dpi thus killing the proverbial two birds with one stone. In AP I have to create a new 12x12 document. Then open up the image. Go to resize document, click type in 320 dpi, uncheck resample image, then click ok. Then I have to grab the crop tool and crop. This obviously take much longer. There are MANY other example. Still love the program but it does take more work to do many things.
  13. Sorry, when I said beta I meant the pre-release version. This isn't like affinity where they have a beta version that is actually a later version being tested. This was the release BEFORE the final release was put out so it is actually older. If I didn't push the highlights all the way down then it wasn't quite so scary. They introduced a Raw Develop 'filter' in the release version that helps the highlight recovery a lot (among other things).
×