Nice rainbow unwanted color

Rhino Rhino for Windows
21

I know, just replied what’s my assumption. Nice to see that the fix came in just several hours. :slight_smile:

1 Like
22

Hi Dan,

Thanks for rolling out the fix. FYI this latest RC is dated 5/5, not 10/5.

Regards
Jeremy

23

We noticed the same thing, it’s the correct one. Dan mentioned something about a dog running amuck at the time, fat pawed apparently.

1 Like
24

today download (automaticly vers 30 ) same issue
ok manualy latest buidl and all ok

25

Good eye!

It’s the date the build happened, not actually the release-date. So, in this case, it’s correct. It was built last Friday (May 5th). What happened here is that we had a build at 3:00 am PDT that contained this bug. Last Friday, we worked to fix it (I actually released another RhinoWIP for V8 to fix it), but we discovered later that the bug was in 7.x as well, so we fixed it there too. That build happened at around 3:00 pm (PDT) with the fix in it. However, on Tuesday afternoon I mistakenly released the 3:00 am version with the bug - even though there was a newer build. Correcting this mistake was relatively easy once we figured out what happened.

WARNING: Below the fold is some version-number-build-process-nerd-core-info. Feel free to ignore it…

Here’s a Rhino version number:

7.30.23125.15001

which can be broken down like this:

  • The first two decimal-separated numbers are easy: MajorVersion.ServiceRelease
  • The next five digits - 23125 - are the second two digits of the calendar year (2023 → 23) - then the ordinal day of the year: 125 is the 125th day of 2023 (so 23125 is May 5th, 2023).
  • The next 4 digits are the time the build started, so 1500 is 3 pm or 15h00.
  • The final digit is a rather “future-fragile” enumeration that we kinda tacked on at the last minute:
    • 1 = “stable” shipping version (Windows)
    • 2 = “stable” shipping version (Mac)
    • 3 = Beta (Windows)
    • 4 = Beta (Mac)
    • 5 = WIP (Windows)
    • 6 = WIP (Mac)

The nice part of this semantic versioning system is a newer version will always be a bigger number and, if you know the system, you can tell exactly when a version was built…something which I should clearly check more carefully before I hit the big red SHIP IT button.

Thanks again for your patience y’all.

1 Like
26

Continuing the discussion from Rhino 7 Service Release Candidate Available:

It looks kinda cool, but it’s super annoying.

How do I revert to the previous version I had, which was probably the last SRC?

image
image1230×603 89.2 KB

1 Like
27

don’t revert, update. the fix is in 7.30