Can the devs PLEASE work on moving nodes far enough apart that clicking the wrong one because the hit boxes almost overlap becomes a thing of the past?
Mmmm. We know Strange Sights in particular has had a “colourful” history with bugs where the nodes are stacked on top of each other.
We’ll take a look at the current spacing. Unfortunately adjustments have to be made by changing hard-coded values with no preview () so it can be a little bit trial-and-error with moving them.
The 4E, the hard wave node, and the CN are the 3 that seem to cause me the most trouble. With the obvious exception of the 5E completely disappearing, of course
The Deadpool Daily Quest is another one that could use some help. There is a ton of wasted space there, but the wave node in the middle and the 4* node are pretty close to each other.
A lot of these events existed before the introduction of both the CN and 5E so the design space available was quite a bit different. When those extra nodes were added they were probably crammed into what space there was rather than the visual display being re-jigged for proper spacing, thus where we are now.
No, a common problem that affects development industry-wide! A problem already solved. One approach is to describe a layout in relative, as opposed to absolute coordinates, that each device then renders on it own hardware accordingly.
But if the OG devs didn’t bother, can’t expect the follow-on devs that had incomplete undrstanding of the codebase to do it, or for any editor to survive the hacked up Unity reimplementation.
With the 90+% empty maps from Strange Sights in mind … DAZ0273’s projection is an unearned level of grace. Acres and acres of screen those nodes could have gone … anywhere!
Oh yes, sorry, you are right, they did it on purpose, the naughty munchkins! But I am hoping “Unearned level of grace” is a forum reward, I love those badges!
As someone who writes S/W for a living I can tell you that’s easier said than done. Relative co-ordinates only works if EVERYTHING on the screen is relative. By that I mean you can’t use fixed images (pics of characters or nodes or anything) because those won’t scale relatively so they won’t look right as spacing increases relatively.
Otherwise it makes no sense they don’t have a preview screen. That has existed in Visual Studio and Eclipse for nearly 20 years now.
My post was triggered in this case by sub 1 of the current TaT event. The other subs are not bad at all but the first one has a lot of crowding happening.
Seems like this is a hard issue to address via node shifting, but maybe at some point an optional set of arrow keys to move from one node to the next could be added to the UI, as an easier thing to implement.
Absolutely (harhar) they all must be relative. Relative coordinates and dimensions. Of course rastered assets can be used … if the available tools and skills anticipate and support their use.
End user devices are rendering everything to fit their displays anyway. Playing as I do in a windowed environment, can resize and re-render on the fly. All relative … on the user end.
If what we are told here is accurate, that the devs are working blind / in the dark, no excuse for that. They should be able to preview what they’re doing, relatively quickly and on demand if not in real time.
That the comms person is asking for examples could be confirming specifics of the complaint … or revealing a lack of familiarity with the product they’re supporting. Bleh.