RadarScope

RadarScope for iOS, Mac, Android, and Windows. 24/7/365 For support: Settings - Support - Email or [email protected]

[RadarScope @RadarScope]

@OriginWx Please email support and they will help sort it out.

[RadarScope @RadarScope]

@TheRochelleEF4 Confirmed fixed in build 16450 going out to beta testers this evening.

[RadarScope @RadarScope]

@TheRochelleEF4 Checked in a second fix for that a few minutes ago for the next update. Similar issue, but original ticket had a different test case so we missed this one.

[RadarScope @RadarScope]

@FrannyWX As far as I can tell, you’re the first person to request it. We’ll look into it.

[RadarScope @RadarScope]

@CRyanMauk @therobdale @noah_emmert In the meantime, the timestamp only updates when the data do, so it’s a reliable indicator that things are current.

If you open a support ticket, please send me the ticket number. The dev team can work with you directly on it if you like.

[RadarScope @RadarScope]

@CRyanMauk @therobdale @noah_emmert Completely agree, and we’re spending a lot of time to identify any other possible causes. The next release should address the most likely case of false errors. It’s awaiting Apple’s review.

[RadarScope @RadarScope]

@therobdale @noah_emmert @CRyanMauk Would also help to know how often you see it. Based on the handful of reports we have and our own testing, it’s generally rare and difficult to reproduce, but somewhat frequent for customers who do see it. So we’re working to find a reproducible test case and fix it for them.

[RadarScope @RadarScope]

@therobdale @noah_emmert @CRyanMauk It would help if you’d email support from inside the app and include details such as what you were doing when it occurred (first launch, resume from sleep, in use for a while, etc.) and whether the data were actually up to date in spite of the error message.

[RadarScope @RadarScope]

@TheRochelleEF4 Sorry for extended delay on this. We pulled it back into 5.5.6 for iOS, which is awaiting Apple’s review. Hit a snag with our Windows portal and beta release. Awaiting Microsoft tech support to resolve that issue.

[RadarScope @RadarScope]

@connercarlow We reported it to Weather Pulse and they deployed a fix.

[RadarScope @RadarScope]

@KapriiSun_ @NWS @NWSSevereTstorm It was a bug in the Weather Pulse warnings feed. They deployed a fix.

[RadarScope @RadarScope]

@MikeDarden_AZ Our intent was to keep it simple because there are already so many different colors that mean different things. But we’ve had some requests for it and it’s something we revisit periodically. So will think about it for a future release.

[RadarScope @RadarScope]

@eas3964 @NickCMNWX19 Possibly. We can reach out to them.

[RadarScope @RadarScope]

@tstokes8040 @NWSOmaha Coming back online now. Sorry for the delay.

[RadarScope @RadarScope]

@tstokes8040 @NWSOmaha We opened a ticket on it for the data team. Haven’t seen a status update yet. Must be an unusual issue.

[RadarScope @RadarScope]

@skelly54 @NWSOmaha Yes, for the L2 data we use for super res products. We have an open ticket on it.

[RadarScope @RadarScope]

@omaha_wx Yes. We’re looking into it. Standard res products are working as are super res from alternate providers.

[RadarScope @RadarScope]

@theYankeeHajny @NWSOmaha @NWSHastings Not sure when you saw that, but radar was down for a while in late May.