Tristan Biesecker
-
Posts
32 -
Joined
-
Last visited
Posts posted by Tristan Biesecker
-
-
I noticed in 1.5.0-1 that at various points (seemingly indeterminate) the selection box of my object flashes when interacting, moving, scaling, etc. Additionally, sometimes the selection box of the object will disappear until the object is moved again, even though it's selected. Has anyone else experienced this?
Cheers,
-
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!
-
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:
Parent
-> 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!
Cheers,
-
Great work you guys!
A few bugs I think:
- The measuring tool doesn't work with groups, only individual objects.
- 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.
- 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!
Cheers!
-
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...
Thanks,
Matt
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).
-
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.
-
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?
Cheers!
-
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.
Cheers
-
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!
-
Was the AD 1.3.5 update supposed to fix the missing/mixed icons issue? They still aren't working for me.
Is there a way to "reset" the icons without reinstalling?
-
AD and AP are already quick, but I was wondering if utilizing Metal would give any speed improvements. If so, are you guys planning to do this?
-
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).
-
-
I agree with @evtonic3. This would be a handy shortcut.
-
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.
- Sonny Sonny, crow and robskinn
-
2
-
1
-
When exporting to a PDF, my embedded documents are rasterized, which is problematic for printing. Please rework this system so that, upon export, the objects from the embedded document are "extracted" so that the PDF can contain all vectored assets.
-
Thanks for the quick reply. It is a great feature to have and kind of a deal breaker for me for everyday use.
I use this to crop to certain dimensions for print. For example in photoshop I have presets for the different column widths in the newspaper I work for. Really speeds up workflow.
Other than this request though the application is very impressive.
I agree with @capephotos. Being able to specifically set the crop dimensions is very useful, and needed in quite a few situations.
-
Is there a reason you are using the Stroke LayerFx instead of a normal line. In the beta we have renamed Line -> Stroke and now offer alignment for your stroke in the Stoke panel. The original Stoke LayerFx is creating a raster based effect that can take some time to render, this effect is mainly used for alpha edged images and not vecotors. The new stroke (or old line) should render immediately.
To avoid confusion we have also rename the old LayerFx Stroke -> Outline.
For reference, we always render LayerFx at draw time so they don't use any memory. We have some designs with thousands of objects with LayerFx and this would be impossible if we cached the result as other Apps sometime do.
I wasn't actually using a stroke for my art. I just noticed that when any effects are applied the performance takes a real hit. I used a stroke as an example.
-
I have always noticed that dragging objects with applied effects (such as something simple like a stroke) lead to poor performance in Affinity Designer, particularly low frame rates and refresh rates. Since upgrading to Yosemite, however, these issues seem to have compounded.
Attached is a video of the performance issues of simply dragging an object with a stroke. Note that the recording accurately represents what I'm seeing on screen; the recording isn't just at a low frame rate.
Is anyone else noticing these performance issues?
Basic computer specs:
Mac Pro mid 2010
3.33 GHz 6-Core Intel Xeon
16GB RAM
ATI Radeon HD 5870 1024 MB
Affinity Designer Customer Beta (1.5.2 - Beta 2)
in [ARCHIVE] Designer beta on macOS threads
Posted
This issue occurred without minimizing. It might present itself more often when I'm switching back and forth between different snapping modes (e.g., All vs. Immediate Layers).