Yikes. That's strange.bubblobill wrote: ↑Sat Aug 15, 2020 6:04 pmThe sweep ring is off playing hard-to-get with the fairies.
MT's facing method is strange, too (Wiki: getTokenFacing()). Is that the method being used here?
Moderators: dorpond, trevor, Azhrei
Yikes. That's strange.bubblobill wrote: ↑Sat Aug 15, 2020 6:04 pmThe sweep ring is off playing hard-to-get with the fairies.
You didn't say why the screen capture couldn't be uploaded (filename extension?).
I used CamStudio which produces *.mp4
A small change to the CSS moves the center of the animated detection wave from position 2 to position 1. That looks a lot better than where it's currently emanating, imo. But it doesn't scale with a larger width motion detector, so a modifier based on a custom size of the detector would need to be added. It seems that most of the CSS was written with an "ideal" width of 275 in mind...Full Bleed wrote: ↑Sat Aug 15, 2020 2:51 pmThere does seem to be 3 different "centers" at the moment that is a little disconcerting. There may be some technical reasons for it, but I was wondering if there would be a way to combine them (or at least a couple of them.)
MD_Centers.jpg
Current Centers:
1) X/Y coordinate of the targeting semi-circle.
2) Center of the animated detection wave.
3) Center of the token that is doing the detecting.
I think the X/Y coordinate of the targeting semi-circle would be the most accurate center (meaning the animation would have to be shifted down and the token blips shifted up.)
Code: Select all
bottom: var(--controls-height);
Code: Select all
top: calc(var(--container-height) - 2 * (var(--controls-height)));
Code: Select all
[posH = y*resolution+blipAreaRadius]
Code: Select all
[posH = y*resolution+blipAreaRadius-(controlsHeight-blipAreaBuffer)]
It is rather annoying... I felt like I was playing around with legos using 3 different metric systems.
Looks good. I see you've got a 360 degree field image done as well.I decided to animate the ping in SVG instead.
Az said he allowed SVG attachments now... let me test... nope... not working...The current latest work-in-progress version uses this tracker_back.svg.txt instead (remove .txt extension).
The scaling upside and flexibility after the fact is huge though. Glad you powered through. Will be looking forward to more SVG works-of-art from you in the future.I was wrong of course. Whilst this pic is much better for us, the learning curve caused me to crash into the mountainside many times.
Thanks for the update.
Apparently, it can't be defined as an "image", even though that's what the browser will consider it to be.Full Bleed wrote: ↑Wed Aug 19, 2020 5:32 amAz said he allowed SVG attachments now... let me test... nope... not working...
I can middle mouse click and open it into a browser window with my current Firefox settings so that's cool. Too bad we can't put svgs inline... seems like that might be a phpBB limitation.
I don't want to derail the overlay discussion, but... SVGs can contain script elements, so allowing users to upload SVGs and then inlining them so the user sees the image automatically is a security issue (per some web searching). It may be possible to filter such things from the SVG during the upload process, but I don't see a phpBB extension/plugin that does that — it may be more complicated than it appears.Full Bleed wrote: ↑Wed Aug 19, 2020 6:21 pmI can middle mouse click and open it into a browser window with my current Firefox settings so that's cool. Too bad we can't put svgs inline... seems like that might be a phpBB limitation.
It sure is. Moving the field up to clear the area around the origin blip was a good idea. I see what might be a 360 button now, too.
the issue with that is that we look at the centre of the token NOT the edge. so with large(r) tokens you can have an offset. We *could* try to do an edge to edge calculation but I'd much more prefer a centre to centre, this also omits the issue with assymmetrical tokens that are rotated. Next to that it would require yet another layer of calculations...-And the range finder seems inaccurate against large+ tokens when approaching from all quadrants except (-x,y). Example below.