Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Unable to select vectors in Dynamic Lighting layer

I have built some maps that use another line segment to represent a doorway in the Dynamic Lighting layer instead of FoW. When I built the maps, I tested with a player and was able to select/remove the line segments to represent a door opening. Today I am unable to select anything on the DL layer, and with a lack of an erase tool this means I cannot delete or reposition DL vectors without erasing everything on the layer. This applies to maps created before Rugged Reroll and new maps. Side effect: I cannot manipulate or erase any DLL vectors while drawing a new map, so if I mess up, start over. Example of a map segment with thick line segments representing doors: Using Chrome 31.0.1650.63 m, Win 7 x64.
Update: Closing/reloading the browser twice fixed it. Can a dev tell me what causes this, i.e. memory load, so I can avoid having this happen during play? I'm using an i5 4670K, 16GB RAM, Nvidia 650ti Boost 2GB, and all stock options in chrome://flags/.
Not totally sure...if it happens again tell us the name of the Campaign. Also be sure to check your console log for errors -- sometimes if you trigger an error the app becomes "unresponsive" (e.g. you can't select things).
I'll check the log if it happens again. When this happened I could still select anything on the other layers, just not DLL vectors.
1387595440

Edited 1387596521
Just happened. The console doesn't display anything besides warnings on non HTTPS content. I have confirmed that I can grab things on other layers. <a href="http://pastebin.com/phpFh1aW" rel="nofollow">http://pastebin.com/phpFh1aW</a> Campaign named "Cago." I suspect it might just be events going crazy because of the number of DLL vectors present. Edit: Refreshing the tab cleared the error. Console probably not relevant but added. <a href="http://pastebin.com/NUkA7mVb" rel="nofollow">http://pastebin.com/NUkA7mVb</a> Re-Edit: Stopped being selectable again. No new entries in the console.
1387596868

Edited 1387597588
I have reproducible steps. The error is caused by alt-scrollwheel scaling. 1) Load campaign. 2) Move to map with DLL. 3) Select DLL from the left hand toolbar and the selector (pointer) tool. 4) Confirm that DLL vectors are selectable. 5) Click somewhere else to clear selection. 6) Use Alt+Mousewheel to scale. 7) Try to select a vector again. This does not occur using the Ctrl+Mousewheel whole window resize (browser tool). Edit: Did a fresh install of Firefox 26.0 and the bug is present there as well. Also found this bug when drawing a vector on any layer, so it's a problem with vectors and alt-mousewheel, not specifically the DLL.
1387605367

Edited 1387605508
Gauss
Forum Champion
Just a note: This is something I have seen more of recently (possibly since rugged reroll has come out), I do not think this is just Alt+Mousewheel. It is any zoom level other than 100% makes it difficult to select the lines. Moving obects is also a problem because you cannot select and drag the object. Workarounds: Use only single segmented lines in your DL polygon/lines instead of multiple segment polygon/lines or shapes. Then you can use the 'drag' technique to select your line. After selecting the object you can move it by using the arrow keys (major movement) or Alt+arrow keys (fine movement). Note: I always advocate single segmented lines for a number of reasons, this is just one of them.
Confirmed; I can zoom out one click, then zoom back one click and the line segments are selectable again. They're unselectable at greater or less than 100%.
I had this problem last night actually and yes I was at 80% zoom. The lines I was trying to move (straight lines representing closed doors being opened) were unselectable.
1387668477
Gauss
Forum Champion
Update: I have filed a bug report on this.
This should be fixed!
Tested, works. Nice speed on the fix. Kudos to the team!