Rick,
I figured out how to reproduce this error. If you actually disable URO+, your async script calls enter a RACE condition sometimes, especially if you are in an area with high UR density (500+) and/or if you have a lot of scrolls or movements in close succession.
Somehow, the URO+ backfill setting seems to keep this from happening at some point. Probably due to the fact that some event is fired after the URs are backfilled.
I figured out how to reproduce this error. If you actually disable URO+, your async script calls enter a RACE condition sometimes, especially if you are in an area with high UR density (500+) and/or if you have a lot of scrolls or movements in close succession.
Somehow, the URO+ backfill setting seems to keep this from happening at some point. Probably due to the fact that some event is fired after the URs are backfilled.
rickzabel wrote:What i am seeing happening is that sometimes time on page load WME is not loading all the information used by a few scripts. when this happens i noticed that WME does not have any UR data loaded and for hardhats the user rank is not loaded. causing script errors or unexpected behavior.Cardyin wrote:I'm getting the same behavior as well. It almost seems like it's stuck in a loop. My guess in this situation is that the UR pill data are trying to load, but is waiting for the filtering which is waiting for the UR pill data.
i disabled all waze scripts and extensions and every few reloads i still have the issue where UR pins are not showing up until i either reload the page, use the reload button, or move the map.
I could not recreate this at all, i tried both filters and pills. i even went so far as to leave my computer sit for an hour to see if the data was loading slowly.Cardyin wrote:Turning of the setting: "Enable URComments UR filtering", instantly allows the screen to load all URs and pill boxes, re-checking this box after the screen refreshes seems to enable the filter correctly and instantaneously
for people who are not seeing UR pins on the map on page load i wrote a script to try to detect this situation and that will move the map an unnoticable amount. on my computer this forces all the WME data to load. this also might help with some of the other script problems other people are having. i don't have any details as to which other scripts other then there is script issues...
when the script detects this situation you will get a toolbox type message that says "WME-Force-Data: Waze's data is missing attempting a map move to force data into loading.'"
This has not had any testing so let me know if it helps or causes other issues.
the script can be found at,
https://greasyfork.org/en/scripts/14746-wme-force-data
hopefully waze will fix the issue and we wont need the script.
Maybe you can just pick three sizes: small, medium, and large. That would be more awesome than what it is now... Would something like that be doable? 
Re: [Script] UrComments