Rise blank screen issue

Nicole, in short, Rise + Suspend Data = No go. 

My team and I learned this the hard way and it was a huge headache for some of the projects we where working on back then. We came up with different workarounds this issue:

A) We broke-up larger RISE modules into smaller chucks without any sidebar menu. We uploaded the smaller sections into the LMS and used the divider blocks with a shortcut to start the next Rise course.  From a user experience, the LMS and RISE would work like one system, however, for clients using Agile development, a small update in one module would only reset a learner to the beginning of that micro lesson, not the entire course. 

B) For meduim-sized courses where we wanted to keep the sidebar navigation AND the updates where minor or non-critical: We would hide the course from the LMS catalog and create a new course. This meant any current learners would still be able to complete the course without losing their progress and any new learner would be assigned the latest version. 

I know these are not optimal solutions, however, once we got the system and process down, we were able to keep the courses in RISE, and leverage some of the advantages this tool offers. Hope this helps. 

Mauricio

I am experiencing this issue too (in Totara) and just read this entire thread. Looks like the only solution proposed so far is from David Lockett --  "find an old Rise course (pre-Nov update) copy out the scorm driver and use this in any new packaged content." Is Articulate working on a fix?

Hi everyone,

Was there a solution to this problem? I have the exact same issue with my Rise file. I have updated content and republished for scorm 1.2. I have uploaded the zip to the course and all i get it a blank screen. 

I wanted to see whether the issue lay only within an existing course so i created a new mock course and uploaded the exact same file - it worked perfectly.

I cant erase learner records, etc so what would my solution to this problem be? 

Thank you

Hi Katie, this took a long time to solve and was found after much testing by our LMS provider (Kallidus). For us it turned out that the problem was caused after Articulate made a change to the Scorm driver file in the last Rise update (which I think was around November 2020). Our LMS couldn't handle the change (where a course was published as 1.2 but was being detected as 2004) and therefore anything that was packaged with the new driver would return a blank screen on second launch. The fix was to simply find an old Rise course (pre-Nov update) copy out the scorm driver and use this in any new packaged content. It iss a complete pain having to swap out the scorm driver every time we create or update some Rise content, but we don't have the issue any more. 

Incidentally there's a few mentions in this thread of testing in scormcloud. However our LMS provider stated that this doesn't fully test the granular detail and functionality of courses in the same way that a commercial LMS does, so it's a litmus test at best.

I hope this helps.

Hi Chris, if Kallidus v10.1.12 is also known as Classic, then it's the same issue as we had. We are currently using Kallidus Classic (sorry only know it as this rather than the version number). 

This took a long time to solve and was found after much testing by Kallidus. For us it turned out that the problem was caused after Articulate made a change to the Scorm driver file in a previous Rise update (which I think was around November 2020). Kallidus couldn't handle the change (where a course was published as 1.2 but was being detected as 2004) and therefore anything that was packaged with the new driver would return a blank screen on second launch. The fix was to simply find an old Rise course (pre-Nov update) copy out the scorm driver and use this in any new packaged content. It is a complete pain having to swap out the scorm driver every time we create or update some Rise content, but we don't have the issue any more.

It might be worth looking in to. My previous thread on this is https://community.articulate.com/discussions/rise-360/rise-blank-screen-issue?page=2#reply-725609

I don't understand how you fix this using a Chrome incognito window..  doesn't the LMS open the browser window for the course?   wouldn't you loose the Learner ID with incognito?

I see this issue when I update the content and replace the scorm files on the LMS. Anyone who has previously launched the content (pre-updated content) is presented with a blank screen when the re-launch the course. Have you made updates to the content in this way?

Also, I know Articulate point people to SCORM cloud for testing content but it is not really a particularly helpful tool as absolutely any scorm content will work on it as it should- regardless of how well put together the SCORM content is. No other LMS offers anything like the flexibility/forgiveness of scorm cloud.

Hi Stuart,

I also answered your other post here, and I wanted to share the info for Chris as well.

Have the learners tried to refresh the browser page? It sounds like it may be stuck on the relaunch as it's a new version of the course. 

When you update (overwrite) existing course files in your LMS or web server, learners who previously started the course won't be able to resume where they left off. They should start over at the first slide in the updated course. You'll want to keep this in mind when updating courses that have already been delivered to learners.

Thanks for the input, the course hasn’t had any content updates as it still in a prototype phase and hasn’t been rolled out to any learners yet. It's sort of doing what it was intended for – testing to see if the clients LMS will be able to run Rise courses before we go into full production. Unfortunately, it's not the result we were hoping for. 

That being said it’s something I will flag with them to see if they are doing any kind of update on their side of things. 

Ah, sounds a bit different than Stuart's issue than.

You mentioned IE11 - how does it behave in any other browsers? I've seen a number of issues with certain LMSs forcing IE11 into compatibility mode, and that will cause issues with Rise being strictly HTML5 output. I would think you'd see that on the first attempt, not just a relaunch but it's worth looking into with your team! There are some additional troubleshooting steps here that may help.