UDL 1.0 Updates, Bugs, & Feedback

Happy Friday Folx!  I’m here to give a rundown of the current status and where everything is in our efforts to keep you in the know on UDL. We’ll update the “What Needs Worked On” section in the first post with this list too. COMPLETED   First off in the things we have completed, Dim Light falloff was fixed and in the same update added the ability to customize the intensity of the dim light effect and the break line that was seen at the edge of the borders between Dim and Bright light. DIMMING: COMPLETED LIGHTING BREAK LINE: FIXED IN QA  Moving onto things that are actively in QA, people have mentioned that the UDL settings had some inconsistencies with saving value states (for example if I turn on Night Vision but then turn on Vision, I wanted the Night Vision value to be remembered for when Vision was turned on again). While we were in there we scooped up the bug where the total light value calculation in relation to Dim Light was incorrect. SETTINGS: IN QA TOTAL LIGHT VALUE ERROR: IN QA NIGHT VISION/DIM LIGHT: IN QA   IN PROGRESS  The next couple targets we have our sights set on are the multifaceted approach to addressing lag as it relates to UDL. We’re also working on the root cause that leads up to causing a Ring/Bullseye effect on a token. Once we get movement on some of these we will be pulling in things up from the Queue. LAG: IN PROGRESS -- currently analyzing various problems and solutions RING/BULLSEYE EFFECT: IN PROGRESS   CONFIRMED AND QUEUED  On deck the list below many of the statuses have moved and shifted as it became unblocked with groundwork from previous updates. Here is the list of things we have the information on and have what we need to get the solution moving forward.  GRID: CONFIRMED AND QUEUED   VISIBILITY: CONFIRMED AND QUEUED PAGE FREEZING: CONFIRMED AND QUEUED NIGHT VISION: CONFIRMED AND QUEUED JAGGED LINES: QUEUED -- went from in progress to queued: groundwork was made on an antialiasing approach that needs more adjustments  to give us the quality we’re looking for TOKEN SNAP LIGHTING: CONFIRMED AND QUEUED CTRL+L TOKEN SWAPPING: CONFIRMED AND QUEUED TURNING OFF UDL AFFECTS OTHER PAGES: CONFIRMED SAME AS PAGE FREEZING -- CONFIRMED AND QUEUED NIGHT VISION TINT: CONFIRMED AND QUEUED CTRL+L REVERSING ON PAGE SWAP: CONFIRMED AND QUEUED DYNAMIC LIGHTING LAYER HIGHLIGHT: CONFIRMED AND QUEUED LIGHT MULTIPLIER: CONFIRMED AND QUEUED   INVESTIGATING   Here are the handful of items we are still investigating the root cause of and are working to find solutions to.  CTRL+L CRASH ON PAGE SWITCH: INVESTIGATING LDL TROUBLES: Some people have reported an increase of problems using LDL. If you’re experiencing this issue, please contact the help center or make a new post in the bug forum! This thread is going to stay focused on UDL. DARKNESS OPTIONS MISSING IN DAYLIGHT MODE: INVESTIGATING REVEAL TOOL LEAVES PATCH OF DARKNESS: INVESTIGATING API INTEGRATIONS FOR UDL:  INVESTIGATING PAGE REVEAL: INVESTIGATING -- We put out a series of fixes that we believe cleared up the scenarios and the root cause of this but we want to be certain so if you’re still having issues we want to hear from you!     New stuff! And finally here are some extra items that are available to try out now and which will be hitting live soon CIRCLES are right around the corner. Currently on Dev so we can poke at it a bit more to test it and still give you Pro users a chance to play with them if you’d like. A reminder for folks who are using them as barriers that restrict movement but not light this feature update will alter that interaction and we want to provide a better long term solution to this that you will adore.  Freehand drawing support is on its way and likely to hit Dev servers next week for those times when you need a wall to just be a series of doodles. 

Hey Edward, We're bundling that into the Bullseye/Target fix that we're working on now, as there is a common thread there. If ultimately they aren't connected we'll get it prioritized to be addressed.&nbsp; Warm Regards, Corey J Edward R. said: Corey J. said: IN QA&nbsp; Moving onto things that are actively in QA, people have mentioned that the UDL settings had some inconsistencies with saving value states (for example if I turn on Night Vision but then turn on Vision, I wanted the Night Vision value to be remembered for when Vision was turned on again). While we were in there we scooped up the bug where the total light value calculation in relation to Dim Light was incorrect. SETTINGS: IN QA TOTAL LIGHT VALUE ERROR: IN QA NIGHT VISION/DIM LIGHT: IN QA Happy Friday. Does this include the bug Doug E. described at&nbsp; <a href="https://app.roll20.net/forum/permalink/9900485/" rel="nofollow">https://app.roll20.net/forum/permalink/9900485/</a> &nbsp;and I reproduced at&nbsp; <a href="https://app.roll20.net/forum/permalink/9910666/" rel="nofollow">https://app.roll20.net/forum/permalink/9910666/</a> ?