Jump to content

Tristan Biesecker

  • Content Count

  • Joined

  • Last visited

Posts posted by Tristan Biesecker

  1. Hiya,


    So i've tried to replicate a similar document setup to what you explain and haven't had any luck replicating any "craziness", especially something that an undo wouldn't fix.


    What type of constraints do you have set up on the children objects? As that could be the reason I can't reproduce it.


    If you can attach me a sample file that shows the issue it would help make sure that i'm not missing anything when trying to reproduce it.


    Thanks :)


    Well, I unfortunately deleted the file in question (I know I know, that's terrible of me as a tester). I've tried to recreate the problem and haven't been able to.


    I'll post back if it happens again. Thanks for the prompt response!

  2. If I select multiple constraint objects (i.e., there is a parent object with children) and check "Lock children", then drag those selected objects, lots of crazy things happen to said children (see attachment). Unfortunately, a simple undo doesn't revert back to a stable state; the changes to those children seem to be disconnected from the undo stack.


    In the attached photo, the frames (rounded grey lines) are the parent objects, and the rest of the objects are children. When all of those top level objects are selected, and "Lock Children" is selected, a tornado of weird changes hits the children very rapidly. I have also attached an image of those objects as they should be without errors.


    Example of object hierarchy:


      -> Child

      -> Child


    Has anyone else experienced this issue?


    P.S. I am very excited to see 1.5 becoming more stable (still some work though ;))! The functionality enhancements are shaping up to be wonderful!





  3. Great work you guys!


    A few bugs I think:

    1. The measuring tool doesn't work with groups, only individual objects.
    2. Holding Alt/Option while hovering over another object and nudging doesn't seem to work. For me, nothing seems to happen, or if I have a text object selected, the tracking is adjusted instead.
    3. Dragging to select doesn't seem to work anymore. Dragging to select without modifiers, as well as holding the Alt/Option key, doesn't work.

    Still sinking my teeth into it, but keep it up!



  4. Hi Tristan,


    Can I ask if you would try the latest betas? 1.4.1 (Beta 2) may actually be better on your system... There seems to be an issue regarding the highest spec GPUs on each system - something about the way we use OpenGL actually seems to be slower on these GPUs than on the lower end systems - which is really baffling, to be honest... I have the top end iMac 5K with the high end GPU and it's actually slower to pan/zoom than the one with the lower GPU and I was actually tweaking things to improve the performance for the last beta version. My iMac seems better now - not perfect, but better than it was...


    We will continue to look at this over time, so don't lose hope...





    Matt, thanks for the suggestion! I tried AD Beta 3, and the performance is markedly better! The scrolling is back to where I'd expect it to be. Zooming is still a bit jumpy, but both scrolling and zooming are very workable now. Of course, keep working on getting the remaining performance issues worked out as you mentioned, but performance overall is much better! You are certainly on the right track with whatever coding you are doing.


    I am about to get an iMac 5K (7i 395 2GB)  and i am a bit uncertain about it and AF. What size is it when you speak about large photos? Is it 32 MPixel or lager? Do I have to expect problems concerning a smooth workflow?


    pixfam, see my reply to Matt. The image I was playing with using AD Beta 3 was around the size you mentioned. The current versions of AP+AD don't perform well on the 5K iMacs. However, whatever they are tweaking in 1.4.1 seems to bring the 5K iMac line up to the performance of my Mac Pro (at least for scrolling and zooming).

  5. Hi Tristan,


    I'm not aware of any issues with our apps and 5K iMacs. Are you getting the same performance in other apps or just Affinity apps? Do you get the same choppy scrolling etc in the latest beta builds? 


    Hi Leigh,


    If what you mean by "other apps" is other apps I use on my system, then mostly yes. I completely understand that performance might drop a bit given the extra juice required to push all of those pixels. However, the significance of the drop I experienced with my 5K iMac was more than expected. Frame rates can drop to something below 15fps; jumping is very noticeable for scrolling in particular, but zooming as well sometimes.


    I have not tried the latest beta builds, only the latest on the Mac App store.

  6. Hi all,


    I have been a long-time user of AD and AP (since they were in betas!). I have always known AD+AP to be blazing fast. I have typically used AD+AP on my Mac Pro or my Macbook Pro. The Mac Pro was pretty much 60fps most of the time, and the Macbook Pro performed admirably, though not quite as well as the Mac Pro, understandably.


    I recently purchased the newest 5K iMac (the fastest processor and graphics specs available) for 2015. The performance is pretty mediocre on this device, relative to my other devices running AD+AP. In particular, scrolling is very choppy for large photos, though the marching ants have issues when there are a lot on the screen as well. I am a long-time developer so I'm fully aware of the GPU class in the iMacs, as well as the increase in pixel density, dimensions, etc., and how all of that requires better hardware to run efficiently.


    I was wondering if the Affinity team is preparing any updates to speed things up for the 5K iMacs? Or does the Affinity team feel they have achieved the best performance from a software standpoint, and performance gains will only be seen when the hardware improves for 5K iMacs?



  7. For precision work, I prefer to keep most layers locked after I am finished editing them so I don't accidentally nudge them, or I don't want them to be selectable all the time.


    I think it would really help workflows to be able to hover over a layer that's locked at have a lock icon show up, perhaps in the upper lefthand corner of that layer, and you could click it to unlock that layer. Normally, I have to navigate through all of the layers to find the one I want to unlock in the layers palette (since I can't select it), which can be a time sink in complex documents. It would be a dream for me to be able to just hover over a locked layer, click the unlock icon, edit, and lock again, all without having to dig through my layers palette.



  8. Ahah! Success! I did the following in this order:


    1) I did pretty much a full wipe of the apps except for the UI preferences and uninstalled.

    2) I ran the commands (see attached photo).

    3) Restarted.

    4) I installed the apps while being logged in as an admin (not logged in as a normal user and inputting admin credentials to install, not sure if that does anything).


    And after that, the icons are showing up correctly on my main machine. We'll see if this also works on my laptop. You might suggest going through that process if others are having this problem as it worked for me.


    Thanks all!


  9. Unfortunately, there's currently nothing you can do but we are still looking into it. It's a side effect we introduce because we share the same iCloud folders. Hopefully, we find a fix for the next release. Sorry for the inconvenience.


    Hi Andrew,


    Your suggestion for the icons (which I only saw in my email thread, it didn't post it here for some reason) didn't work. It still shows just the AD icon for both .afdesign and .afphoto files (given the conditions posted above). There was only one generator found using the command below

    qlmanage -m

    which was com.seriflabs.affinity -> /Applications/Affinity Photo.app/Contents/Library/QuickLook/QuickLook.qlgenerator (2.0 - loaded)

  10. Sorry about this :(  We'll get looking at this when AndyT comes in later this morning - he's our resident expert in this field so now the apps are both live on the store we should be able to see what's happening more clearly and sort it out. Sorry about this in the meantime...



    Thanks Matt. Any news?


    For now, the icons would be nice, but is there any way to fix the .afphoto and .afdesign default app issue? This is really annoying as I have to right-click on all .afphoto files and say open with .afphoto instead of just double clicking.

  11. So, after downloading Affinity Photo from the app store, there have been all kinds of bugs with the file thumbnails for AD and AP. In addition, the default applications for launching these files are mixed up.


    First, the thumbnails. I am experiencing various bugs here. On some of my accounts, the thumbnails for AD and AF files don't show up (they are still the white page). On other accounts, the new AD thumbnail shows up for both .afdesign and .afphoto files (see attached). I have also experienced them being swapped; i.e., the .afdesign files show the AP thumbnail and the .afdesign files show the AD thumbnails.


    Second, the default app for launching. Basically, the "default" application for either file type is one application. Put differently, the default application for both .afdesign and .afphoto files might be AD; or, it could reversed. For example, when I select a particular file type (say .afdesign) and choose the default app for that file type to be AD and apply that to all files of that type, that also changes the default application for .afphoto files to AD! See attached.


    I have tried everything I know to fix this from wiping everything (that I know of) related to AD and AF and starting from scratch (reinstalling), to rebuilding launch services, etc. Nothing seems to work.


    Any ideas?


    Update 1

    I have found that, although the icons are still mixed up between applications (at this point I actually don't have AP icons, AD icons show up for both AD and AP), I can reliably show them if I increase the font size in the Finder window to 13 from the default 12 (in column view). They show up as the default white page though if the font size is 12. In list view, however, the icon size has to be set to large (regardless of font size) for the icons to show up. Weird??


    Update 2

    So, it appears that changing the font size in column view only showed the icons for one of my machines. It didn't do anything for my laptop (still just white pages).



  12. Hi Tristan Biesecker,

    This is already possible. Please check that you have Snap to object bounding boxes (and optionally Include bounding box mid points) enabled in the menu View ▹ Snapping Manager...

    Also enable Show snapping candidates so you can see which objects are being currently considered as snapping candidates (those are the objects you can align your objects to. You can identify them by a purple outline). If the object you want to align to isn't considered a snapping candidate, mouse-over it for a few seconds while still dragging your object until a purple outline appears. From that moment you can align it with that object too.



    Hi MEB, I think there's a misunderstanding. I mean that I would like to be able to snap to a locked object (that isn't already a snapping candidate) without unlocking that object first, by holding down Alt+hovering over the object to force it to become a snapping candidate. Currently, when I have a non-snapping-candiate object that is locked, I have to unlock it first before the standard procedure of hovering over it with the mouse adds it to the snapping candidates list. Unless there is something that I am missing? FYI, I have everything checked in the snapping manager (I like snapping ok).

  13. Please enable the ability to force a locked layer to become a snapping candidate. Often times I lock layers so I don't accidentally edit them, but periodically I still want to snap other objects to them.


    A suggestion would be to hover over a locked layer while holding Alt (to ignore the fact that it's locked) to add that layer to the snapping candidates.

  14. This is an iCloud issue. Any documents you save in the top level will automatically be shown in the corresponding iCloud folder for the application. It will automatically append a note (in iCloud Drive) to the file to show you it is also in the top level root area. It doesn't take up any more space as the files aren't duplicate, the folder actually act as a filter in these cases.


    You should get the same result will TextEdit or any other application that supports iCloud drive.



    Ah! I did not see the "Alias" for the document kind in the file's info. Thanks for the quick response!

  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.