Jump to content

ladlon

Members
  • Content count

    72
  • Joined

  • Last visited

About ladlon

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi. I have a vector line (with multiple points/elbows), and I want to run a multi-colour linear gradient along the length of it. So, I made my line, then created a linear stroke gradient (with 4 colours) for it. However, it applies the gradient for each section of the line (from point to point... or elbow to elbow), rather than applying the gradient ONCE across the entire length of the line. How do I apply a multi-colour gradient across the entire length of a multi-point line ONCE, without having it do the entire gradient range across EACH segment of the line? NOTE: I do not want it to apply a SINGLE colour on each segment (ex. First segement is blue, second segment is green, etc)... but, instead, just apply the entire gradient range over the entire length of the line based on DISTANCE, not segments. In the attached pic, you see the line I want to apply the gradient to... but, currently, the gradient is applied, in full, to each segment, rather than across the entire length (once) of the line. Also, why is it that the gradient isn't really oriented to the angle of the line, but rather always aligned to an either pure vertical or horizontal axis? (90 degrees) Any help? UPDATE: Okay, so I think I just discovered/realized one thing... The gradient doesn't follow the line/curve itself, but instead is a single line gradient that simply 'shows through' the overall shape of the entire shape... In the case of the attached sample image, that gradient is going left to right... which explains both why the transitions are not aligned to the lines, as well as why the gradient seems to go through random phases in the colours, rather than a predictable one (...until you realize the gradient is a single line going left to right, and that the colour is entirely dependent on the horizontal position of the current area of the line, not the distance through it). So, that explains that... but, I'm wondering if there IS a way to do what I'm trying to do... aside form making the curve using multiple, separate straight line segments, each with their own gradient.
  2. ladlon

    Affinity Publisher (1.7) Launch Announcement

    The Vimeo link to the presentation works great. Thanks for that! Still can't get the vid to play on the Affinity site, but I can watch it fine on Vimeo. Congrats on the great releases!
  3. I still can't view/download the keynote. I refreshed the screen, restarted the browser, and even rebooted the computer. Just isn't working...
  4. Hi, Michael. I don't have any controls on the screen. The full Keynote page is there, but the video area is just a dark grey square (as it was when I was 'watching' it live). I've been having trouble with some embedded videos lately. I think sometimes it's a Flash thing.... sometimes, perhaps a script being blocked (although I don't appear to be blocking anything on Affinity)... Not sure what is up with this. I wish they'd just slap it on YouTube.
  5. I too can't seem to download/watch the stream video. I just get the blank grey box on that Keynote page. I don't seem to have any security stuff blocking it. When the stream WAS actually live, earlier today, I could hear it, but not see anything. Now, I can't even hear anything... if it's even playing. Is it going to be available elsewhere to view?
  6. Hi, S. Agreed... While I can understand a brush being able to have an 'open' stance on blending mode, having some 'open' and some 'controlling' really does present a problem... especially in that a lot of people probably wouldn't notice that the settings are not as they expect, and they continue working through the piece, not realizing the 'mistake'.... and maybe even fighting/compensating for that discrepency in expected performance. I can see the arguement for some people finding changing brushes results in their custom settings (blend mode, wet edges, etc) being 'reset' each time they get a different brush... So, it's going to upset people, either way, I guess. But, I'd say the best route would be to have it manditory for brushes to have a 'default state' stored in them (ex. watercolour brushes have wet edges, dry media doesn't..), and then maybe have a option/toggle set for whether the USER wants to use those, or 'lock' their current preferences. Kind of like locking layers. Okay, well thanks for clearing that up. I had actually previously reported a very odd behavior in Designer, where the brush selection aspect of the program (clicking a brush in the brush list) would often HIGHLIGHT the brush (indicating that the click was registered), but sometimes the brush itself would not change. That seemed to go on for a long time without any solution or official response. I have to check if 1.7 has fixed that. Anyway, I thought maybe this Blend Mode/Wet Edges thing was more of the same! Cheers!
  7. I just updated to 1.7 on both Photo and Designer, and in Photo I noticed something that I wanted to verify here... If I have a regular brush (ex. Dry), then select a Daub Watercolour brush, the Wet Edges checkbox gets checked, as it seemingly should. But, if I then select a regular brush again (say, the Dry one I previously had), the Wet Edges checkbox does not uncheck... so, from that point on (after having selected a 'Wet Edges' brush), all brushes after that have the Wet Edges checked. Can someone confirm this is happening to them as well, and if this is a bug? UPDATE: Actually, I also just noticed that the Blend Mode doesn't seem to update with each brush type selection. It will be on Normal by default, and remain so until I select a Daub Gouache brush, which changes it to Average... but then when I select 'regular' brushes again, the Blend Mode doesn't switch back to Normal. Win7 Pro
  8. I suppose technically I could create some sort of desktop shortcut to wherever you turn Aero on/off, and switch it on whenever I need to use Affinity on that machine.... Kind of a drag, but certainly a valid solution. Actually, if it's a GPU strain, rather than a CPU one, it's not as bit an issue. My GPU is a 1060 3G. It's my CPU that is the issue (old i7)... and it's only a concern, as this is my gaming rig (so I want to free up the CPU as best as possible).
  9. Hi, Dan C. No worries. Certainly a faster/better response than I often get in other forums! Well, that all makes sense. Unfortunate, for sure (the whole Aero thing... which previously seemed stupid, but later I came to understand the actual technical reasoning behind it). So, I guess the video card is the difference here that is determining if the refresh works properly or not? Unless it's a Pro vs Premium thing (Win7). Certainly not a game-breaker (just have to always tap or scroll every time you return to the screen). I'm glad, though, that at least it's a known thing, with an explanation. I guess (besides aesthetic preference) the reason I insist on Aero being disabled on the systems is the (possibly incorrect) assumption that it (to whatever degree) robs some performance from the system. Actually, I recently read that if you switch Aero on, but have all the 'effects' turned off, there is no real drain. Not sure if that's true or not. If true, it certainly would motivate me to switch it back on. (Come to think of it, I need to check my Pro machine, where Affinity IS refreshing properly... as I'm starting to think that maybe I DID do just that... Switch Aero on, but with every effect off... which would explain why it is working there!)
  10. Hello, Dan C... The drivers are up to date, but it's still doing it. Specific to Affinity. The canvas isn't refreshed when something goes on top of the canvas. I can take (say) a window from some other program (or from Affinity), drag it across AP, and it acts like an eraser on the canvas (and ONLY the canvas... the interface refreshs fine, and is not erased by the drag). The mouse pointer does not 'erase', though. The canvas gets refreshed when I zoom or pan. It's only happening on the Win7Premium (GTX 1060 3G) 12gig RAM machine. The other machine is a Win7Pro with a 500 series NVidia card and 32gigs RAM, and it doesn't have the issue. Not sure what other things may be different between the two.
  11. Hi. I have Affinity Photo running on two machines. On one, everything works fine. On the other, I find that the image (canvas) is invisible until I zoom, and then everything is fine. I will often have to zoom just to get the canvas back. Obviously some sort of display/screen update issue. I seem to have to do it every time I put some other software in focus. Tabbing back to AP results in the invisible canvas, every time, and is fixed by just zooming in or out. I also find that sections of the canvas that get covered by various palettes/windows do not get redrawn, so again, a sort of screen refresh issue. On both machines, I DO have Aero disabled, but am using the -NoWarning command workaround. The one machine is Win7Pro (where AP works fine), and the other is running Win7Premium (where I have that disappearing issue). I'm wondering if this is a known issue, and if there is some fix or workaround (other than temporarily zooming to get the image back). Win7Premium 12gigs RAM NVidia 1060 3G Affinity Photo/Designer
  12. I'll see what I can do... it happens rarerly... although if my theory about moving palettes is correct, I may be able to trigger it. I imagine I'd have to use an external (iTouch) device to record it, since the issue completely buggers up Windows, and I would not be able to stop/save the recording, as a system reboot is needed each time.
  13. I have (along with the default brushes) the Frankentoon(?), Daub Blackbox, and from the recent Black Friday sale, theDaub Watercolour/Washes, Markers, and Etching sets. I guess you'll have to compare that to what Kyo has. I can't say that I have seen it happening specific to any sets, nor any particular sequence of events or setup. For me, it just seems to happen quite often, like the buttons are randomly unresponsive (yet the button HIGHLIGHT seems to trigger and hold properly every time). I'll try and do some more tests, and see if I can isolate any particular factor. I am also using a tablet (which I believe Kyo is as well)... I have an Intuos4, and I believe Kyo has one of the other Wacom tablets.... Not that I can see that being the factor, since, again, the button hilight seems to always trigger, so the pen doesn't seem to be at fault I believe I found it happened with my mouse, too. Both Designer and Photo, too, I think. I can't really imagine (from a programming standpoint) what would cause the button to hilight, yet the brush to sometimes not switch over. Keep in mind, too, that it appears that (in Kyo's video) one of the brushes switched over WITHOUT CLICKING A BUTTON... He clicks the button, the hilight appears and locks to the new brush button... he paints a stroke, and it's the old stroke... he paints again, and it's the old stroke... AND THEN he paints again, and it's the NEW stroke... So, it's almost like there was a delay... as if (randomly) it sometimes takes a while for the brush (not the button) to switch over, and it's TIME and not necessarily always repeated button presses, that finally cause the proper brush trigger. That may be a big clue. I'll have to test that on my side, as up to now, I always clicked the button in between painting brushstrokes in the test. I'll try and do a new screen recording, as well. ALSO: Please note the posts (above) from Chris_K and Chris J.
  14. Wow, Kyo. You got it bad! Quite consistant. Thanks for posting that, to help reinforce this issue. That really shows it clearly. Odd that with that one stroke, it actually eventually switched over without you re-clicking.. almost like your initial click was delayed. I'm running into this issue pretty much every session I have in Affinity. Quite regular. I'm having to click twice (or more) in the brushes palette, just out of habit now, to assure the brush properly switches.
  15. Ran into this issue again. Originally, I thought it had something to do with the Brushes palette being visible (as if the display of the stroke previews was straining the CPU)... but, now I'm more inclined to think it has something to do with moving palettes overall. That seems to be what triggered it this time (not specifically the Brushes palette). I move a palette, and suddenly ALL of Windows becomes very unstable until I reboot the system. The mouse cursor doesn't seem to be able to reach all areas of the desktop/screen, the pointer tends to disappear, system frame rate tanks randomly.
×