norbinw
-
Posts
184 -
Joined
-
Last visited
Everything posted by norbinw
-
Affinity Designer freezes up when using export persona
norbinw replied to Bambao's topic in V2 Bugs found on macOS
Jeeeesus Christ!! Will this EVER get a fix?? I have to work on 4 different files, label groups.. after every one of them, it freezes on export!! At least in V1 you had to force close 2-3x max, and you were good to go. I've closed this shit app 6 times now!!!! and still persistent freeze. And I'm still not done with work.. Is there even a response from devs about a fix coming? It's fukken impossible to work and I'm losing money and time with this beta of an app that I purchased, 2x!!!!! 2 Times I have paid money, and BOTH versions crash. Seriously, whats up with that? -
wow, I didn't notice that as I didn't modify baseline 😬
-
Also, now that I want to use this as a starting point for my next design, something weird is going on.. Whenever I select text tool to make a new art text, the small "A" preview flies away from the mouse as it gets bigger. Selecting a new art text body after that, selects weirdly. Look at the screenshot, wtf is that?.. There are no spaces after the 15% Error.afdesign
-
WTF are you talking about @mink . I have the same problem, my eyes run circles when I see those lines in front of groups and curves. It has nothing to do with layer naming. I still won't find easily WHERE that specific object is nested. It will take time to get used to it, like I said, I understand what those are meant to be, but so far they are slowing down my workflow as V1 was cleaner in that area. Maybe different color hues would help a lot. It's about getting lost in layer structure, nothing to do with renaming files.
-
"The option selects objects which are located directly behind the currently selected object." It is a workaround, as there is NOTHING BEHIND the text 20%. All text is completely above and not touching the 20% bounding box (and layers too!). So cmd click should select it perfectly. I have NEVER used opt+cmd click in V1, and was able to select everything perfectly, objects behind, objects in groups. It this case, it's a workaround. Also opt+cmd still selects 20% first.. and after that the logo. But yeah, all this is caused by the bad bounding box zone for text.
-
Locking won't help as It's still in the moving, modifying process. it's a draft, testing phase. Anyway I converted to curves, but like I said, this app is always with the workarounds. And the bug fixes come sooooooooo slow. I had to go 6 months or so, in my first year of V1, with text not updating fonts, until I selected a specific font (hat no live font preview)
-
You have NO IDEA how mad and frustrated I am, because moving around stuff ALWAYS selects the damn 20%. Everything in range of that 20% is unselectable, unless I play the piano on my keyboard, pressing cmd + option, then maybe add shift, then I forget to press option, then the 20% won't deselect and so on.. If I convert to curves, it works fine. But I don't want to, maybe I have to change it later bc they don't like the font.. Even with cmd+option the 20% gets selected, and 2nd time click will select something above or below it. I'm MAD AF!!! Something so simple that worked, makes your workflow so slow and always looking for workarounds.. Whatever I do in this app, requires workarounds now! WTF? This isn't how it used to be. I could trust this app on some level.
-
But it still is bad!!!! How in the FK is it possible to select date instead of 20%?? they are not even overlapping!!! Again with the workarounds, again I have to adapt to this crap app because I am not even able to select non overlapping objects! Whenever I double click the date, it selects the 20%.. Edit: I can't even select the logo, which is even more up!!
-
What bout the blue accent in the stroke menu? Until now it was simple and elegant, you saw where the stroke starts (mid, outer, inner). Now with monochromatic icons, it's kind of harder to see what those are. I would understand if the tools were also mono, but they aren't.
-
Bleed not shown when added after document creation
norbinw replied to 000's topic in V2 Bugs found on macOS
Bleed should always work properly. Doesn't matter if AB or no AB. If you have bleed, it should simply work. But it doesn't. -
Bleed not shown when added after document creation
norbinw replied to 000's topic in V2 Bugs found on macOS
I still do not understand why Serif neglects bleed. In publisher, it's a disaster! Sometimes the bleed shows up till the edge of the bleed line, other times it's clipped to artboard, and sometimes it shows the whole image that you move, even outside the bleed area.. Then toggling bleed on off messes up everything, as there are now only 2 versions instead of the 3 I mentioned above. Also, don't get me started on exporting the bleed, in some cases the bleed is just white, even tho you have content in it. Don't understand why is it so hard to make an option for content clip to: 1. artboard only 2. ab+bleed area 3. no clip, see the whole mess wherever you put it. -
This is what made V2 difficult to work with for me. I understand what those lines are, but boy are they disruptive in my workflow. I get lost whenever I'm looking at those grey lines.. Also the dot is a "NO" for me, would prefer checkmark, and in front of the dot there is also a hidden(?) lock icon, which I discovered today. And the selection bug which makes it harder to select objects behind text or other objects..
-
Same here. Back to V1 till it gets sorted out. With a few layers it's manageable, but with complex graphics it's a true nightmare!
-
Nope. Still nothing. It's among the 3 things I hate and frustrates me about Affinity. I wouldn't even be here, hating the team and the app, if these crashes were sorted out. But it's already 12 months+ of this issue for me. So don't get your hopes up thinking it will be fixed soon.
-
Designer crashing whenever I Use export persona
norbinw replied to Willy Pimentel's topic in V1 Bugs found on macOS
I have never used same slice name, it's not even possible to export that way, as It overwrites? I always rename my artboards, so that's not the issue for my crashes. If that happens to you, that's another bug of this bug.. -
Designer crashing whenever I Use export persona
norbinw replied to Willy Pimentel's topic in V1 Bugs found on macOS
It's ongoing since Monterey.. You need to have some sort of cloud app installed. Try installing Google Drive. Then restart your mac, start designer, and save some files. Eventually you will have it, sometimes it takes 2 saves to beachball for me. Both V1 and V2, now on Ventura, intel MBP 16". -
Affinity Designer v2 Issues that slows down my workflow
norbinw replied to Tanya Mau's topic in V2 Bugs found on macOS
Slower, UI is worse (i use dark theme and the touch of blue on icons was nice, ex stroke menu..) - layer panel is hard to see (spacing is off?), the dots are annoying AF, +1 for checkmarks, whenever I open CMYK document color picker menu switches to CMYK instead of what I want.. I can change it, but it will revert back once I re open a CMYK file, V2 files won't open in V1 even if you have just 2 shapes, selecting objects and text is buggy, and so on and so on.. Back to V1 because I work slower in V2. Not to mention that If I get annoyed by the bugs, I can't continue to work in V1.. Copied some objects over and they were also off.. Man has this transformed into a shitty app.. I had hopes that it gets better with time, like Procreate, that app just keeps giving and giving, but nope!! This became less functional with time. And the most annoying part is, support is absolute garbage. I would still pay to get V2 knowing in January it will be fully ironed out, but after all the bugs going on for MONTHS in V1, lack of response and interest to fix those, I don't believe in this app anymore. -
Excuse me, but the market leader offers VASTLY superior app, and if you are in a company that produces money from the app, the market leader is a no brainer. I struggle to make a pattern with this app, using stupid symbols and duplicate artboards instead of just making a simple pattern maker.. Also I have never had a crash with AI, or issues with saving files (not saying it's flawless ofc!) . Also, warnings were there when backwards compatibility was selected, so you knew you had to save to an older version, and be fine. This one doesn't even notify you, and even if you use 3 shapes and nothing more, you still can't open in V1. This app is just cheap, and that's it. Good for experimenting with vector. I'm super mad, because in 2020 when I got it, it was rock solid!!! I had zero issues with crashes, bleed, speed, everything was working fine. And from there on, the bugs jost got worse and worse and never got fixed.. I'm not sure what happened since then, it's like they hired bakers and truck drivers to do the coding for them..
-
Designer crashing whenever I Use export persona
norbinw replied to Willy Pimentel's topic in V1 Bugs found on macOS
It only works after you force close the app, so after 1-2 force closes it doesn't matter, it won't happen again for some time. Man this app is plain poop!! Can't believe after 2 years of using it, it only gets worse and worse. I'm extremele frustrated as my workflow is slower and worse now. Both print and online work. Selection is buggy, strokes are buggy, saving is buggy, export is buggy, bleed is buggy, moving some shapes is buggy, changing color selection "menu" to HSL is buggy, reverting to CMYK after a print file re-opens, and so on and so on.. Worst part is it takes them AGES to fix 1 bug. The bleed bug is present since I started using the app, you can't export bleed from artboard to TIFF.. It's FKING WORK BREAKING STUFF, as some print companies ask for tiff file, and I can't give it to them.. Have to export to raster pdf, then convert to TIFF. 2 years of ongoing issue, and they don't care. If this app were a game, it would be Battlefield 2042! Riddled with bugs, and you purchase with the hope of being fixed with time. This is bad mentality! -
I have absolutely no idea how to make the color picker (menu?) stick to HSL instead of CMYK... If unlock and change to HSL and lock, still opens CMYK selector, if I leave it unlocked and change to HSL still changes back in CMYK file... WTF?? It keeps the setting until I close the file. Re opening anything, jumps back to CMYK..
-
Expand Stroke doesn't use brush Size Variance properly
norbinw replied to jdkn's topic in V2 Bugs found on macOS
It's good to see you've posted it in January, and by November it's still not fixed. I have so many stroke and brush issues, I'm not even going to bother to post them.. V2 with ALL the bugs ironed out would be a stellar app. Pity it will NEVER be fixed. Apps always have issues, no app is perfect, but boy o boy Affinity is king of bugs and has a good reputation of not fixing them. Otherwise tell me how are we posting the SAME bugs months in a row, some even from 2021.. Honestly I do not know what to do... purchase V2 and hope for a fix by next year, or simply study Illustrator and be in the industry standard with a solid app. The one time purchase doesn't warm my heart, if the bugs are never fixed and are keeping me back from my creative limits.. -
Mods should make a copy paste from the bugs from V1 and be done with it.. Whenever I create artboards with bleed, and export them as TIFF in export persona (+bleed option ofc!) the bleed disappears.. As usual, 2021 issue since V1.. You can see in the screenshot below.. top window is tiff, bottom is original. It was logged back then from my post, you will probably log it again now. Will probably be the same in V3 in 2023...
-
Hang, do you have google drive installed? or dropbox? Install 1 of those, even if you are not saving to that location. You will get beachball in export persona. Happened to me a few minutes ago. Export persona - export - when selecting locations, instant beachball. Now the times it worked I never tried to select different folders as my default is desktop. I'm pretty sure it's just like V1. Force close 2-3x and it should be fine until you reboot Mac. Other notes, the bleed bug is still here. Opening another thread in V2 also.. FFS!
-
No it won't. Sorry for lashing out, but I've been waiting for a fix since November of 2021. No fix came since then, not even in V2. And I was just about to press the purchase button LMAO, hoping they ditched V1 but V2 is finally out of beta stage. Well nope! V2 is still a buggy mess, and V1 bugs weren't ironed out at all, making V2 as anxios to use as V2. Mods can simply merge V1 and V2 forums, as they are one and the same. Yesterday I was working on some price tags, 84 of them to be exact. And at around 50 tags, I wanted to save and go home from work, hitting cmd+s just to have the app crash on me with the NEW (well, 1 month old already) bug - can't save file, app will now close.. And it close on me, rendering my work obsolete.. Because I forgot NOT TO SAVE ON EXTERNAL SSD.. I have to work around lazy dev's ass, and save to my own ssd, and move to external ssd afterwards, because their lazy ass was busy fapping or whatever they did instead of fixing critical and basic software functions. Export persona is compromised, save function is now also compromised. Great.
-
Dude.. it's the SAME issue we are having in V1 since 2021, so how about just logging it and be done with it. It won't be fixed anyways, and I am here because I just encountered this with V2 aswell. It's well known crash reports are not read, and no dev is interested in what we say. We are sending in reports, logs etc. IT'S ONGOING SINCE 2021! WHAT ELSE IS THERE TO DISCUSS ABOUT? I don't want to be rude, but with all those posts are you even reading the forums?? Because V1 page is FULL of threads regarding this issue. Just on the 1st page there are at least 3 threads complaining. It doesn't matter what OS, what chipset are you using, if you have some sort of cloud drive app, the app will crash. ALWAYS! until you force close the app 2-3x, after that, it will work until you restart your mac again. There is no workaround, no fix, nothing. And yes I am frustrated because we constantly report this, constantlyyyyy, and here it is, one and a half year later, same issue in V2.. I'm not asking for special features, I'm (we) asking to have a normal working save function. Nothing more. So that I may save without being insecure about the app crashing or not.
