I've looked around the forum and found this related thread which you also happened to be involved in. It seems you are still using SL2 and one of the forum moderators indicated that due to the significant rewrite in the code for SL360, the previous ability to modify some of the hard coded visual elements has been impacted. So it looks like those on SL360 will need to wait for another workaround to accomplish this.
I've not had this problem myself. As has been pointed out before - my solution doesn't seem to work with Storyline 3 or 360 files, so it may be down to that if you're using an up-to-date version of the software. If you're still using Storyline 2 (like me), then it could be that there's still a file that needs altering as per the original workaround - if one gets missed, that could mess it up.
28 Replies
This post was removed by the author
I've looked around the forum and found this related thread which you also happened to be involved in. It seems you are still using SL2 and one of the forum moderators indicated that due to the significant rewrite in the code for SL360, the previous ability to modify some of the hard coded visual elements has been impacted. So it looks like those on SL360 will need to wait for another workaround to accomplish this.
Hi Pete,
I saw your solution and got so excited! I followed the steps you outlined and previewed the course. Success! No red crosses on my light boxes.
However, when I publish the file as SCORM 1.2 and load into an LMS the red crosses reappear.
Any idea where I'm going wrong?
Hi Stu,
I'm not sure if Pete is still subscribed here, but hopefully he'll be able to chime in and help you out here.
You are certainly welcome to reach out to the user directly via the 'Contact Me' option on the user profile if you do not hear back soon.
Hi Stu,
I've not had this problem myself. As has been pointed out before - my solution doesn't seem to work with Storyline 3 or 360 files, so it may be down to that if you're using an up-to-date version of the software. If you're still using Storyline 2 (like me), then it could be that there's still a file that needs altering as per the original workaround - if one gets missed, that could mess it up.
Hope that helps,
Pete
This discussion is closed. You can start a new discussion or contact Articulate Support.