[Liz Larsen]

It was something they sent you if you signed up for it at the kiosk in the Interactive Zone at XCON2022. Otherwise, if you have Bluebeam 20 or below, you have to pay for access.

Bluebeam University is included with Bluebeam 21, though (I’m pretty sure).

[David Cutler]

That’s what I thought @lizlarsen – that it was automatically included in Revu 21 – which I believe @Vince is using…🤔

[Vince]

It is rather baffling @David Cutler

[Vince]

Thanks @lizlarsen

I’ve got Revu 21 and University has been working fine for the last month or so. I think the first time I used it it was a case of simply clicking on the link under the Help menu.

But for some reason I am now being asked for an Access Code.

Thanks for sending the code from XCON but I think I’ll get on to Bluebeam directly to get this sorted out.

[David Cutler]

While you have them on the line @Vince perhaps you can get an update on the status of the fix for the “disappearing layers” issue… 😎

[Vince]

I did chase a while ago @David Cutler but was just told that it would be fixed in the next update – not very helpful!

[David Cutler]

I don’t mean to be negative @Vince but we need a “dislike” option…

☹

[Vince]

It’s getting a bit boring now @David Cutler – having to correct the disappearing layers costs time that I don’t have and it’s been going on too long with no end in sight.

Plus, it’s hardly a glowing recommendation for Revu when every time I tell someone how good it is, I have to also add the proviso that certain bits don’t work properly!

[David Cutler]

What is even more frustrating is that the feature worked just fine in a previous update…

[Vince]

All working now – turns out that they gave me a temporary code initially which expired at the end of 2022.

[David Cutler]

Glad to hear that @Vince !

Now you will need to start a couple of new posts sharing what you are learning… 🙂

[Vince]

Not learning anything about Revu today unfortunately @David Cutler – instead I’m wasting my time with Microsoft trying to fix the problems that their latest Excel updates have caused. 😫

[David Cutler]

Saw your post on LinkedIn @Vince

We have become so dependent upon these software packages that it is crippling when these types of things happen. No fun for sure!

[Isaac Harned]

You would think the enterprise track of updates would be properly tested and vetted. Oh well, back to disabling!

[David Cutler]

I don’t disagree @isaac-harned – at the same time with some of the workflows that folks like @Vince , @lizlarsen , @Doug McLean and yourself (among others) come up with you run the risk of the developers (Bluebeam/Microsoft/Revit/Etc.) saying “Huh, never thought someone would try that.” 😎

[Vince]

@David Cutler the worrying thing is that they are not new workflows! Instead, they are things that have worked for a while (and in the case of my spreadsheet – years) and are really only using the basic core functions so I really don’t understand how an update can make them go that badly wrong.

[Doug McLean]

Yeah, sometimes you do something and you get an unexpected result.
One simple line of code can change something that’s worked for years. You don’t even realize what you’ve done.

[Vince]

The thing here is that we haven’t changed anything – it is purely the Microsoft update that is causing all of the issues.