CenarioVR and ReviewLink

I uploaded the sample SCORM 1.2 file for Corals of the Caribbean that John directed me to into my ReviewLink account. It works fine in Windows Chrome. In the Oculus Browser, I get this error.

I can't find any settings in Oculus Browser for allowing Motion and Orientation, nor in the device settings. ReviewLink is definitely hosted on a secure (HTTPS) connection.

To confirm, I tested the same SCORM file in SCORM Cloud, and that gave the same error.

How should I proceed?



Discussion (8)

The Oculus headset is supported via the CenarioVR App, where you have access to the controllers and full function of the headset. SCORM publishes are for your LMS, and Desktop/Phone browsers. To use your LMS in full VR mode with a headset, the LMS itself would need to have native support for the headset.

CenarioVR has this support built in through its hosting and distribution of VR content via the CenarioVR site, and many CenarioVR apps on various platforms.


I was using the term "proxy" loosely. SCORM does support the idea of launching a SCORM-compliant course hosted outside the LMS/LMCS, and accepting SCORM messages back from that external server indicating completion and score (and other things, of course).

We do this with several vendors of training, for instance Smith System. They host the eLearning, our LMS manages the curriculum, records completion and launches Smith's player. I don't know how it's handled behind the scenes, I haven't dug deeply into the SCORM API.

Yup, xAPI/cmi5 would be great. If our LMS supported it. Our LMS vendor only fixed SCORM 1.2 support in 2019. In fact, their support for AICC is buggy. Great idea, won't apply to me any time soon.


May I say, I appreciate your quick, clear and courteous answers to this flood of questions from me? Because I do.

SCORM itself does not natively support proxies, and was only ever intended to be run in a browser. SCORM works with a Javascript wrapper around the content, and on the headset, no browser or JavaScript is used.

The ADL developed xAPI in order to solve the many deficiencies of SCORM, and you can certainly publish CenarioVR content as xAPI, run it on a headset, and pass the results to your LMS. The caveat is, of course, that your LMS will need to support xAPI.


Unfortunately this greatly reduces the utility of CenarioVR, because it makes native (to my company) tracking of the courses impossible.

I have not dug into your products' features in detail--can the CenarioVr server act as a SCORM proxy, so we could launch a course from our own LMS but open it in the app? That's yet a third variation of each course we would have to build: iDevices (can't use high resolution video), headsets, and everything else. It would also add a lot of complexity to the LMS setup at our end--we'd have to assign a course with three possible branches to each student, then have them pick the appropriate one depending on which device they are using. For Lectora courses, you also lose the "resume where you left off" capability because, of course, there would be two separate Lectora courses, and one "pure" CVR course that doesn't even relate to Lectora for headsets. You could not leave off in the Oculus Go and resume on your iPad or ThinkPad.

From what you said in the video you kindly directed me to, Lectora courses incorporate the HTML5 export of the scenario, which is not (from what you say in the message above) supported by headsets. Have you considered creating a new transport type (tvcvr://URI-of-secnario?) to launch the app, if available? You could also build the ability to detect that it is running on headsets directly into Lectora 19--courses already detect other platforms (e. g. iPhone vs. PC). This would be similar to the way some web conferencing companies create their own transport type to launch their apps, both on PCs and mobile devices.

Thank you.

For its course interface, SCORM is a JavaScript wrapper running in the browser that the course "talks" directly to via local JavaScript calls. If you code specifically to an LMS, you can create a wrapper outside of your LMS that talks to a stub course inside f your LMS, or something can be written specifically for your LMS to work externally using direct LMS APIs. This is generally how mobile Apps work with their respective LMS's.

If you have an external JavaScript wrapper/course stub, that could be applied to a CVR course in the same way it is applied to a normal SCORM course. Otherwise, this is one of the many reasons xAPI was developed seven years ago, to bridge imitations of SCORM.


Has Trivantis worked with connectors? We have created automated processes with other external companies to have their products create importable CSV files that are automatically ingested by our server, showing course completions and linking to their unique employee numbers in our HRIS. Large enterprises are very much going to need functionality like this. I know your salesman mentioned that you do support SSO.

Thats really the issue that xAPI addresses, and its been out for many years now. Have you discussed xAPI support with your LMS provider?

The LMS is part of our HRIS, which is both monolithic and lethargic. It won't change fast, if at all, and we have minimal leverage.

They fully support SCORM 1.2 now. That support was added in 2020.

No, that is not a joke.

Discussions have been disabled for this post