Slidemaster Layers not working in LMS

Folks,

To assist, I attached a picture which indicates my Slidemaster Triggers & layers and a base course slide with no other intelligence.

The idea here is that the Slidemaster has a 2 layers, one with a ding sound to indicate that the slide has been completed and the NEXT button is now active. And a second layer with an Error box and a buzzer. This is for when a user clicks the NEXT button when it is not active / slide is not complete. These layers are controlled by a single variable which is set to FALSE upon the start of the timeline of the Slidemaster.

In the course, I only indicate when the variable is set to true. I also restrict the NEXT button to when the variable is TRUE.

If a user clicks NEXT before the slide is done they only get an error indication and a buzzer sound. When a slide is done, a ding sounds and the NEXT button is not restricted.

In the SL2 Preview, this all works as it should. When I publish to CD as a test, it works. The file did get corrupted and the CD export had the error layer not working but I went back a few version to before the corruption and rebuilt the slides; However, the error layer doesn't work in Moodle. The side restricts movement, it just doesn't show the Error layer.

I've been having issues with these slidemaster layers since SL1. The triggers seem pretty simple so I don't know why I am having consistent layer errors.

Any help is appreciated, 

Hello Vaughan - You mention that this issue is happening in your LMS. Could you test via SCORM Cloud to see if you are able to replicate the issue? This will help us identify if the issue lies with the project file or within your LMS. If you are able to replicate, please feel free to share the .story file for us to take a look. If you cannot share here in the forums, you are welcome to share privately here. If you are not able to replicate, you may want to follow up with your LMS team.

Leslie,

I was unable to test via the cloud yet, but my issue has now changed. I decided to create a new template from scratch again. I didn't import anything as I didn't want to import a corruption as these issues have been dogging me for years on SL.

I have attached this template. In here I have more than my normal number of slidemaster layouts hope this isn't an issue. In any case, one of the slide layers works fine (the Ding layer indicating the slide timeline is complete), but the Error layer doesn't work at all, not even in SL2's preview. Worked yesterday (and for years past) in preview but after creating this new template, Error layer doesn't work anymore at all......????

Any help is appreciated. Great many hours spent on these issues.

Thanks for sharing Vaughan. I can see the issue you are reporting and I'm doing some additional testing. The layer seems to work when re-visiting the slide, but not initially.

Thanks for your patience Vaughan. I imported into a new file and it seems to be working just fine. Your file is attached, and the published output is here.

File corruption is unpredictable, and there's no straightforward way to determine what causes it. Common causes are environmental (disk errors, power outages, improper shutdowns), viruses, failed Windows updates, and even file size (i.e., very large files have a higher risk of corrupting). Consider using the preventative measures described in this article to protect your project files.

I finally found the problem to this issue. It has dogged me for many months, caused untold numbers of hours (in the 100's), frustrated the living hell out of me, set me way back on course creation & deadlines, and lost me at least 2 contracts. It was a result of a change from SL1 to SL2. The "NEW" restrictions on the Next button when the player is set to 'restricted' mode caused my triggers on the Next button to not work.

I am so disappointed and frustrated with Articulate for this change without making it clear to the purchasers of SL2 that this fundamental change had occurred. I had created my own "NEXT" button restrictions in SL1 and the change Articulate made on the NEXT restriction makes no sense. The NEXT button just doesn't work in restricted mode, no indication to the user why its disabled (there is a disabled state to the other buttons, if you'd have used that, then at least authors would be able to figure it out). There should be a pop up when you select RESTRICTED mode telling the author that the NEXT button will be deactivated until the Timeline ends. My restrictions to the NEXT button included a notification to the user why the NEXT button doesn't work; however, in SL2, my SL1 navigation caused my courses to break and broke the navigation, controllability and revisiting functionality. I contacted Articulate and informed them that I couldn't import courses from SL1 to SL2 because of the corruption it caused on my files, I got NO indication of this new programing change. I called my issues corruption in the files, because I had absolutely no idea what was causing this intermittent issue (I usually troubleshoot in FREE mode and finalise in RESTRICTED-never caused issues in SL1). Even when you click the help button in the "restriction" mode in the player to get more information, you get no indication that you are also deactivating the NEXT button. The only way to regain control over the NEXT button and still be in restricted mode is to edit the code after publishing. I have decided to spend the many hours to go back and create custom NEXT/PREV navigating buttons so I don't have a repeat of this issue when a programmer decides to muddle with the fundamental aspects of the software, again. I now wish I had the ability to copy/paste groups of triggers because my custom nav will take 5 new triggers a new variable for each slide. Lots of work copy/paste one at a time.

The amount of time I have wasted in the last year, I could have learned Adobe...

Very disappointing

Thank you for your assistance Leslie,