So I give it time and then go to Updates and Statistics in Rhino 7. But it tells me it has just checked and seven hours after the announcement my older SRC is still the latest
So I click on Check Now… and Rhino admits it was telling porkies and there really is a new release
If you’ve announced a new release and I’ve allowed 7 hours to pass and check now shows the release is available, why does Updates and statistics do such a bad job of spotting what the rest of the world has seen? Does Rhino need glasses?
Footnote: In the general scheme of things this doesn’t really matter. But it is bloody irritating.
I think it only checks once a day… not sure why. Also has been requested that when one punches the “Check now…” link, that if there is a new build, it will download automatically.
yes exactly, when there is an update, it will automatically tell you without the need to click check now.
at least this is what happened to me yesterday. someone from Mcneel can confirm that.
The automatic system always works, even on V7. However it doesn’t check constantly. I’m not sure if they changed that for the WIP. It downloads in the background, so when Rhino tells you there is a new build available, it has already been downloaded and is ready to install. But that may happen up to 24 hours or more after release, as it doesn’t check all the time, I think only like once a day.
Hi Mitch,
I agree that it only seems to check automatically once a day. But in the second screen capture the timing of the check is seven hours after the announcement and it doesn’t see the new version. My question is why. If the check is once a day I’m going to have to wait another 24 hours.
In this particular instance, I shut Rhino down ten minutes after posting and it told me the new release had been downloaded! So it had found it and it appears that the issue is actually that the wrong message was being displayed.
Hi -
I don’t know how this works and this thread was assigned to Brian so perhaps he chimes in at some point…
I subscribe to internal builds and those are released every few hours. In my experience, checking the updates page will trigger a new search for new versions. Often I have to close all instances of a particular Rhino version to make sure that a newer build is searched for.
If you launch Rhino, and a new version becomes available, you won’t be notified until you either manually check for the update or exit all instances of Rhino, then launch again. Then, Rhino will find and download the update but you won’t be notified until you check or exit Rhino.
-wim
For commercial service releases, Rhino checks daily for updates. For WIPs and Service Release candidates, it checks more frequently. We do this to save on bandwidth hitting our servers. The vast majority of the time, there’s nothing available if you’re on the stable stream. So having zillions of computers checking every few minutes or hours for an update would just swamp us for no appreciable gain.
I’m afraid you’re missing my point. I’m asking why, when Rhino makes its once a day check and seven hours have elapsed since you announced a newer SRC, it says it is up to date. Especially as if I click “Check Now” it tells me there is a new release.
I have no desire for Rhino to check more frequently. I’d just like it to check more effectively!
Because it probably checked automatically within the last 12 hours already! It is showing you reliably the results of the last check. Just because you open the dialog doesn’t mean that it’s going to check again (when you click the link, it takes you to our website which has the current information). I hear that you’d like it to check when you open the dialog instead of waiting for the 12-24 hour time limit to pass - this is logged here: RH-42820.
And it is showing me the last checked time, which in the screenshot posted was moments ago and hours after the SRC announcement, not 12 hours beforehand… Hence my doubts over its efficacy.
But thank you for RH-42820. That seems like a sensible little tweak.
