Friksel

It's not fixing this issue tho.

Hi @Leigh, Thanks for looking into this. I'm not using AdBlockers other than perhaps something which is build in. If an AdBlocker would cause the forum to stop working tho than there's something wrong in the forum as adBlockers have no reason to block traffic to the same domain. If they did that 99% of the website wouldn't function anymore so that would make no sense and adblockers useless. The issue is also there when not using a VPN. Perhaps you could re-read my opening post; I did put a screenshot of the error message of the console.log in there. There you can also see that a catch isn't handled of a Promise. That's not causing this error, but not an indication of great programming per se as the catch should be there. In the near future leaving catches behind would probably even make the forum to completely stop working as using Promises without a catch is deprecated for quite a while in browsers now so won't be tolerated in the near future. Having that won't solve this issue tho. For the record: ms Edge is just Chromium, so pretty much exactly the same as Chrome. I never had any issues with other sites and neither did I with the Affinity forum before. The following time I'll try if using Firefox has the same issues and/or look if I can see something in the developer tools. It looks like the frontend is requesting something from the backend, but the backend sends something empty or in the wrong format. Hope to be able to use Ms Edge again soon! Thanks again [edit] Sending this now from firefox worked directly. But that's also the case with ms edge sometimes, while other times it's taking me a thousand tries to make it actually send. [edit2] At the moment I'm behind a VPN, so that isn't an issue either. Also Firefox is automatically blocking things like Google Analytics, so that's way more strict than ms edge, which doesn't do that.

@carl123 I'm using Ms Edge latest, which is basically Chrome. No weird settings, no plugins. After trying yet another thousand times to react to your post with and without cookies enabled: The forum just won't let me react to others on my own thread or others. Also tried to open another thread, but it didn't work either. Now trying it from Firefox. But if this doesn't work I just cannot react to you. This should obviously not be browser dependent, espectially because I'm using a Chromium based browser which is #1 in world usage and so the first browser to test on.

After trying it a thousand times again with and without cookies: The forum won't let me react to others on the issue, so I try it now with opening another issue here just to answer to my own post. 😪 https://forum.affinity.serif.com/index.php?/topic/158919-bug-on-forum-cant-submit-topic-because-of-error-on-forum/&tab=comments#comment-900059 @carl123 I'm using Ms Edge latest, which is basically Chrome.

Bump. I can't be the only one having this issue. Nobody knows how to solve this?

There seem to be no forum here to post bugs of this forum, so by lack of another forum I had to post it here. Last months it happens about 90% of the time the forum doesn't allow to Submit a topic / react to a post because of this error on the forum: Most of the time this error means that a data object, for example received from the backend, isn't in the right format or a json stream is not valid JSON. Also Promises should always have a `catch()` to catch errors, which obviously are missing here. I'm surprised this still isn't fixed. It's pretty annoying to not being able to post on the forum after taking the time to write a post, most of the time with video too. It would be helpful if somebody of Serif or it's external forum supplier could finally dive into this issue and fix this. A forum doesn't make much sense if posting is impossible 90% of the time. Thanks in advance!

For some strange reason the isometric grid in a project I'm working on is unusable; when switching between front, top and side the anchors of the grids don't match. When starting a new project with isometric grid enabled this problem is not there. At least it seems like when 'Uniform' is unchecked. It's also a problem when 'Uniform' is checked. However, when unchecking the same switch in the project I'm working in it doesn't fix the issue. Anybody here that perhaps could tell me how it is possible that the isometric grid gets 'out of sync' between its planes? Please see video below: These are the grid settings: iso-issue.mp4

No, I was using the ' Edit in plane'. I never knew that 'Fit in plane' actually did just what I needed (thought before it was only using some fitting or whatever, didn't think this would also rotate and shear). This is exactly what I needed. Thanks for the quick response! 😀

I'd like to transform an existing bunch of layers, grouped together, to be isometric. I was hoping I could copy the group and paste it on an isometric plane when 'Edit in plane' was selected, but it doesn't work. I believe making it isometric is more than just slanting it. Anybody has any idea how to convert 'flat graphics' to an isometric top plane?

Bump!

@Dan C Thanks for the update. Glad to see it was still helpful. Hope it helps you find it. Keep it up!

Hello @Dan C, I am pretty sure I didn't duplicate an artboard. Also these slices didn't correspond with actual parts in the layout because when switching back to the normal Designer view I only had one of it there, no duplicates nor copies. That's what I think points to the reason of the crash. I should have saved the file at that state for testing, but I didn't so can't see what exactly what's going on right now. What I can tell you: In your video I see a rectangular box around 'artboard' in the slices panel, but I've never seen that UI piece here, only exclamation mark icons. There is a dmp-file in the location you mentioned, but it's from long time ago, so nothing of last days nor weeks.

Hi, So far since the launch of Affinity I've never had real crashes in the software. But in this version there's an issue that causes the application to crash. It looks like this is being caused by having two slices with the same name. It shows an exclamation mark next to the duplicate name, but when scrolling through the list the application crashes. This is consistent. I've tried re-opening the application and do it again several times in a row and everytime Designer crashed. I managed to check out the boxes for the duplicate slices and re-save the file and that seems to have 'solved' the crashing issue. But it's obviously not right that Designer crashes at that point. I also wonder how these duplicate entries ended up there in the first place. I'm not sure I've created these myself, but as well might have. I'm just not 100% sure. Unfortunately I don't have the errornous file anymore as it's restored, but hope this explanation is enough to test and fix it.

Muchas gracias 😉

Fine if you'd like to post translations here, but I don't like people changing my words in quotes as if it was me writing them

This issue is confirmed here. Linking the new issue thread here for future reference:

Hi @Dan C, Thanks for being honest and the workaround. Indeed the taskbar was turned off here too on other than the second screen (= first external screen, which is set as main screen). So I just tried with taskbar turned on instead on each screen, and that solves the black-out issue, just like the reporter of that other issue-thread. So that might help you figuring out where to look. I see in my previous posts I've talked about winkey-arrowleft/-right, but I forgot to mention the shift-key I'm holding with it to activate the action. So it's the exact same method I'm using as the other reporter.

Some things to consider: The laptop I'm using itself has a resolution of 3240 x 2160, so is not 16:9. So it's not 4k as I wrote, but is HiDPI though. The scaling on the build in laptop screen is therefor set to 225%. Scaling on the external monitors is just set to 100% as these are plain HD-screens (each 1920x1080px). There are no compatibility options nor hidpi options set for the Affinity applications here. So they run just as is and as meant to be run. The videocard is by Nvidea (GTX1060) and has up to date drivers, so nothing to update there. It doesn't make much sense of making a screen recording of what happens, other than you not believing me and needing proof. As it's exactly what I tell you: hovers don't work, clicks don't work, in other words: UI freezes on the app, while the rest of windows and other software just keeps working just fine, and the app works fine on other screens too. Guess you just gotta believe me on that and recording that doesn't give you any new information on the matter. --- I now switched to a different setup. Now I'm using both external monitors with display ports daisy chained. So I only use one displayport output on the laptop to feed the screens. One of the monitors is swapped now too, as the other one got a new purpose outside of this computer setup. With this new setup it is not freezing the application on the third screen anymore with winkey-arrowleft/-right, but that keystroke still has weird artifacts: This is the situation now, which is also weird ** and only with affinity apps!! **: - open application affinity, it opens on screen 1 (the build in laptop screen) - move the application to screen 2 by using winkey-arrowright --> everything fine on the second screen (which is the first external display) - move the application to screen 3 by using winkey-arrowright --> everything fine on the third screen (which is the second external display) - move the application back to screen 2 by using winkey-arrowleft --> affinity does move to the second screen, but its UI is completely black!! Not even showing windows minimize/close and that other button on the top right corner, nothing. Only black. The windows taskbar is still visible though, but that's the only thing. - move the application back to screen 1 by using winkey-arrowleft --> everything fine on the first screen - move the application back to screen 2 by using winkey-arrowright --> everything fine on the second screen (!!) - move the application back to screen 3 by using winkey-arrowright --> everything fine on the third screen - move the application back to screen 2 by using winkey-arrowleft --> affinity does move to the second screen, but its UI is completely black again, same like before. Important: This is consistant for days now and goes the same since I switched to this setup, so every time the application moves from screen 3 to screen 2 this black-out issue happens, but all the other directions don't cause this blacked-out issue. Even when stresstesting it by quickly using the keystroke after another. This only happens to the affinity software!! All other apps I test this with, also software using the Nvidea card fully (like Blender), work just fine no matter what I do and how much I stress test it!! So there's definitely something in Affinity that can't handle the change of screens. Weird thing though is that it only happens now when switching from screen 3 to screen 2, not even when switching from screen 2 to screen 3... while both screens have the exact same resolution. I would understand this issue a lot better when it would be from screen 1 to screen 2 or visaversa, as these resolutions are different and screen one has hidpi... but that's not the case with screen 2 and 3. This is the configuration in Designer: So as you can see I don't have Nvidea set as renderer in this test. But it doesn't matter when switching the renderer to the 1060GTX card and restart the software; the issue persists. I'm not even loading a file to work with, all above with the blacked-out issue already happens with just a blank Designer interface without any tab loaded/open. Good luck figuring this out as I don't see any logic in this.

Having a laptop with 4k screen and 2 external screens, both 1920x1080, when using Winkey-shift-arrow(left/right) to move the application to the third screen, the interface doesn't respond to hovers and clicks anymore, so is completely unresponsive and unusable (freezing UI). The software itself doesn't freeze though, as it's still possible to move it back to either screen 2 or screen 1 with winkey-shift-arrow and there it still works. Other software is not having this issue, so this seems to be Affinity-only. When, instead of using winkey-shift-arrow to move the application to the third screen, I just move the Affinity-window from the first to the third screen by mouse, this issue doesn't occur and the application still works on the third screen. Also, weirdly enough, on the second screen, which is also 1920x1080, just like the third screen, it also just works, so also when using winkey-shift-arrow to move the window there. So to me this means this isn't a resolution thing, or at least it shouldn't be, as mon 2 and mon 3 both have the same resolution and refreshrate. Using windows 10, build 19042.1288

Thanks for the reaction guys. As you can see in my last post above I already found that out myself quickly after posting the initial question, but it's always great to have some confirmation about it. Thanks! That's indeed very welcome! I'm no beginning user and it was still confusing to me. I still have the impression it can be improved as something feels off. Also when lines are too close next to each other I could imagine a better default would be to even than show these sub-lines on all zoom levels. The sub-lines are per default more grayed out so they shouldn't mess up with the main grid and at least then we know as users there is a sub grid actually working! If we than decide to turn on the auto-to-zoom-behaviour switch that could be there than after that we know we did that on purpose and know the subgrid is working! Being able to tune the threshold, as you say, would be a nice improvement I'd say! have a nice day

Alright, so after some more testing this seems to have something to do with the zoom ratio. Propbably Designer is being clever in when to show and when to hide the sub-units depending on the current zoom level, see video below. Not sure how I feel about this behaviour, have to find out by using it. But I see the sub lines of the sub units now when on the right zoom level! 😀 (see video below) iso-grid-zoom.mp4

On normal grids we can set the divisions of each grid unit to have sub-units in the main units with lighter grid-lines. However, how can we do the same for isometric grids? The division fields in the grid settings don't seem to chang anything, so not sure what that is for, but I would expect that to be for the subdivision of each grid unit. [ see video ] How to divide the isometric grid into more detailed sub-units (without changing the main unit-size)? Subdivision-Iso.mp4

alright, thanks

Thanks for the confirmation @Old Bruce I saw that Inkscape is able to directly import DXF, so not sure if everything imports 100%, but guess it will and should as it's an open format, so we could than import DXF in Inkscape, save it to SVG and open the SVG with Affinity without (much) issues I guess. Is 'plain graphics' a wellknown term used for what I would describe as 'graphical design', normally done with tools like from Adobe, Affinity etc., like graphical design, webdesign, UI design, illustrations etc. as being somewhat the opposite of 'technical design' like CAD, or via another route 3D graphics like made with Blender, Maya, Max and such? Or is that just a term only you use? For me it would be nice to know a term others understand immediately to address the type of user instead of fiddling around with descriptions like 'creative' and 'graphical' (which they all are in some way).

Thanks. I'm not on a Mac, but on Windows though. After a quick search I've found a site that has a 'DWG Tools' for windows, which looks like the 'official' website, but both shopsites it's pointing to for downloads actually don't have that software in their lists. BTW As a graphical designer for many years I've never got a customer ever before coming with this file format. I've found by searching that it's the main format for Autocad and it's obviously a well known format in the area of cad-systems. And obviously it's a propriatory fileformat by Autodesk. But are there, next to the cad world, also professional graphical designers working with this file format when using only graphical (creative) design software? Or is this pure a main thing in the CAD world?