Jump to content

Tim Clarke

Members
  • Content count

    18
  • Joined

  • Last visited

Everything posted by Tim Clarke

  1. I've had Nexus Font installed in the past, but I don't think it's been installed for the past year or so. I have a fresh download on my desktop, so I'm assuming I had uninstalled it before. The Wacom driver is uploading now. When I rebooted my PC yesterday, Wacom complained about mismatching hardware (even though the driver I'm using now was downloaded from their website for this particular tablet). So I may need to uninstall the new one and reinstall the one I'm uploading for you. Of course, if I do, I will do some testing before and after. In case you want to check for common shared libraries, these are the font managers I installed. The first two are still installed, the rest have been uninstalled again. I still have the downloads if they'd be useful. High-Logic MainType FontExpert 2019 NexusFont 2.6.2 Typograph FontBase 2.9.4 Font Runner 3 Font Manager Printers Apprentice Font Viewer I also have a zip of all the fonts that I removed from my system. But that's a 226 MB. If it's helpful though, I can try uploading it over night (I'll split it up with 7-zip if necessary). In addition, I have an image of my drive (a week or so old) in case there is anything you want me to check if it was removed/changed/whatever. I don't know how long I can keep this image though, as my backup drive is only a couple of TB.
  2. Edit a text style. In "Color & Decorations" tab, click on any of the fills to bring up the colour chooser. Hit "Escape" on the keyboard and AD crashes. Changing tab (including changing, then changing back) in the colour chooser, then hitting escape, does not cause a crash.
  3. You'll maybe hate this, Sean, but I've been doing some things to my system, and out of curiosity checked to see if the bug was still there. And it isn't. In either Designer or Publisher. If it's any use to pinpoint the error (and of course, if it happens again I'll update you), the only things I can think are some way connected: messing about with gradients and the transparency tool in Designer (more likely) installing and uninstalling various font managers, uninstalling some previously installed fonts, doing some tempoary font installs (testing the font managers) (hmmm ... maybe ...) I uninstalled my Wacom tablet yesterday, and so went to the Wacom website to download the driver. It's a different driver to the one I had before. I still have the OLD driver, if you want me to uninstall the new one and install the old one again. Or send you the old driver. Or whatever.
  4. Both keyboard drivers are the generic Windows drivers (Microsoft 6.1.7601.17514, dated 21/06/2006), likewise for the mouse drivers (Microsoft 6.1.7600.16385 21/06/2006). Nonetheless I uninstalled what I could, and it made no difference. I removed the Kensington trackball and tried it woith a mouse, and still the same problem. I removed TrackWorks. Unfortunately I don't have a wired keyboard. I notice though that both Alain and myself have wireless keyboards, and we have the full Affinity suite (but ... I'm guessing you also have the full suite installed). Edit: I also renamed the full Affinity directory in AppData, and it made no difference.
  5. If I install Designer on a Windows 10 virtual machine, will that mess up my licence or anything for my normal AD installation? I'm pretty sure it doesn't, but it would be great if you could confirm that.
  6. It's a Wacom Bamboo tablet, not currently attached. I haven't used it for a long time (months, if not years --- except, coincidentally, I breiefly attached it yesterday as I was experimenting with something). The first crash I reported happened before yesterday, and I think they all happened without the tablet attached. Would you like me to uninstall the driver? It is version 1.2.2.0, date 29/06/2009 (!). The 1 and A icons are TrayStatus 4.0 --- on-screen indicators for caps lock and numlock. Other than the Wacom, I also have a cheap (£6) generic wireless mouse installed --- not switched on unless I accidentally knock a button. I have a Kensington wireless trackball --- my main pointing device. I also have a Logitech keyboard and mouse set (wireless, NON unified USB) --- Logitech MK270. The keyboard is the one I use all the time, the mouse is used when I'm sitting on the couch watching a film or whatever, so it's not used when running Designer. I also have a Logitech wireless K350 keyboard (unified USB) which is not switched on, and the dongle is not attached (they're waiting to be put on eBay), but I haven't yet uninstalled the driver. (Yes, four pointing devices and two keyboards!) Other software I use which might be considered not typical: Directory Opus BitDefender AV trial Macrium Reflect backup Vmware Virtualbox My career used to be software development (from C embedded systems through to Java mid-tier) so I'm quite happy to try different things and uninstall/reinstall stuff, if it's any help. But I'm trying not to change the envioronment too much in case the bug can't be replicated. Just let know if you want something uninstalled, updated, whatever.
  7. Ok, that should be it uploaded. If it still doesn't work, let me know and I'll work something else out.
  8. That's a partial upload too. It's only 20 MB, while the original is 38.9 MB. If you send me a dropbox request, I'll send whichever you prefer to there.
  9. I'll attach a 7z. If it doesn't work again, feel free to send me a dropbox request and I can upload the zip or 7z there. 1.0.7z
  10. Morning Sean, After posting the video, I wondered too if it was something to do with the custom palette. Though I made that only recently, since the last Designer update. Would you like me to try removing the palette? I didn't want to change anything -- I'd rather leave stuff as much as it is to help you replicate this, unless you want otherwise. I hadn't tried it in Publisher. I have now though, and it also crashes. So I'm not sure if that means the attachment is no use. I assume you dont want me to report the crash in the Publisher forum too? designer-1.0.zip
  11. Not as far as I can tell. I'm using a UK keyboard. I've attached a video. Interestingly, the crash does not happen when I use the on-screen keyboard. If there's anything I can do or send, let me know.
  12. If a symbol line/fill/effect colour is from a document palette, and that colour is edited, and then the edit undone: the colour of the symbol remains the new colour and is no longer linked to the palette. While hapening most of the time, it does not appear to be consistent, so more than one attempt to replicate the bug may be necessary. Edit: further testing suggests the symbol colour is still linked to the document palette. After replicating the bug, and leaving the symbol with the wrong colour, editing the fill a second time is reflected in the symbol.
  13. Hi @GabrielM This recording shows the problem. Note that before starting the recording, I had confirmed that the symbol's outer glow colour was from the document palette. If you can give me an email address, I will send you the document, if it is of any use to you. Tim
  14. On checking the behaviour of non-global palette colours, before submitting the bug "[AD 1.6.2.97] Palette Colour Opacity", I noticed that for those colours a noise value can be set. This value cannot be set for global colours. However, the noise value is picked up (along with the opacity), but cannot later be edited. This bug is identical to "[AD 1.6.2.97] Palette Colour Opacity", except instead of opacity, it relates to colour noise. And it affects global colours only (non-global colours have a control to edit the noise). It's possible both these bugs should be combined. But in my experience there should be no assumption about the underlying code, and seperate issues should be reported separately. My apologies if I'm wrong.
  15. When creating a new palette (ordinary or global), the opacity (alpha channel) is copied from the selected object (if there is one). There is no way to change the opacity after palette colour creation. Even using "Edit Fill..." and using the colour picker does not work. So if (for example) a global palette colour is created, accidentally with a opacity value of less than 100%, it cannot be later fixed. It would require a new palette colour to be created, and each object referencing the incorrect colour to be modified to use the corrected colour. Thus in part defeating the purpose of global palette colours.
  16. Hi all. I just bought Affinity Designer on Sunday to take advantage of the sale. Except for minor edits to a couple of SVG files, I've not worked with vector art before (or really any art except my camera since I was at school about 24 years ago), and am enjoying it very much. I used to code software and considered it an artistic form of logic, and vector art seems to be a logical form of art. Well ... perhaps it's just the way my head works. But I did a couple of tutorials (one and a half anyway!) and am now working on a picture of two of my nieces. Intro over! Most of the work is just the foundation shapes and colours. Zoe's (the girl on the left) cheek line, laughter line, mouth (ouch, those squint teeth!) and nostril are just place holders. Her skin tones are what I was working on today, and I'm pretty much happy with. I realise I haven't yet done the shadows around her neckline, but at the moment I'm struggling with the nose. I just can't seem to get it right. I'm just wondering if some fresh sets of eyes might be able to see where I've gone wrong. Perhaps I've just been working on the picture for too long today. I'm attaching the picture so far, as well as the reference photo. And a close-up of the nose in case that helps. Any other criticism is welcome. They're both a few years older now (Zoe just left for university, and Emily is now ten), so I don't know if they'll like this. But I hope they'll like the gesture, and so I'd like to put the effort in. Tim PS Just noticed that maybe I need to add some more darker shades under the nose -- I've been concentrating on the ridge and sides. Unfortuantely I now need to get some work done and get to bed, but any input is more than welcome.
  17. Tim Clarke

    [AD] Noses! -- Advice Needed

    Thanks retrograde. I was out for most of today, and I think stepping away from it has helped. Yes, I think building up the shadows beneath the nose will work, and I realised too that I had accidently removed shadow work beneath the left eye (left to us, Zoe's right eye) so that side of her face is looking a little flat. I haven't had time to work much on it today, but fixing that helped a little, as did shortening the nose just a wee bit. Thanks for the tip of using multiply. I just looked it up, and it's probably something I should be using instead of the skin tones document palette I set up. I already did a little work on Emily's skin, but it's not too late to try the multiply blend on her skin instead. Thanks. I showed them both today. Zoe hates it and refuses to look at it! But she's eighteen, and tells me she hates that photo (in fairness she's got quite a strange pose --- one she probably thought was "grown up" at the time). Emily hugged me and said "I love your picture, Uncle Tim." Not sure how to take that. She might be only ten years old, but she learned the arts of sarcasm and being patronising years ago! Well for a first effort, I don't think it's too bad so far (I'll probably look back in a year and cringe!).
×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.