I think you may misunderstand.  If the user clicks the Retake Quiz button, their score will be reset to 0 again.  That's the way Captivate quizzes work. How did you want it to work? ... View more

Are you working on locally stored project files on your hard drive, or are they stored on a LAN server or virtualised web storage (e.g. OneDrive or similar)? ... View more

Perhaps you could take some screenshots of the issue and upload them here so that we can see what you see.   ... View more

  If the Jump to Slide action is not doing what you expect, perhaps the issue is that the slide you are trying to jump to is not allowed for some reason.  E.g.  If the slide being jumped from is inside the quiz and the slide you want to jump to is BEFORE the quiz starts, AND you have Backward Movement disabled, then the Jump to action would fail.  That's just one failure scenario.  If you want to test whether the action is failing due to this type of issue, change the Jump to target slide to another one in a different part of the project and see if it works then.   I cannot see why the background colour would matter unless those slides are actually hidden slides and that's why he background is grey.  IF that IS the reason for their colour then this would also explain why you are unable to jump to them.   ... View more

Unfortunately no.  Many years ago there used to be a small software app you could buy or download that would package valid SCORM zip files into a multi-SCORM package.  But that seems to have disappeared, probably because Captivate stole the market. ... View more

If you have a subscription license for Captivate 12 then you automatically also have a license to download and install Captivate Classic.  That installation will also contain the MultiSCORM packaging tool, however only content created in Captivate Classic will work with it. Download Trial | Adobe Captivate ... View more

Some LMSs register completion more reliably when you set it to be measured by achieveing a passing score, rather than number of slides viewed.    If all your users will be doing is just clicking through the slides, just put a button on the final slide that is set to report a score of 1 point to the quiz and set its action to Exit so that clicking the button not only exits the course but also gives the user a passing score.  If that button is the only scored object in the entire project then clicking it will give the user the passing score the LMS requires. ... View more

No problem.  This is how we learn. ... View more

It could also be that some of your customisations to the mouse object have caused it to be corrupted.  Try a test with a new blank project file with just a couple of blank slides.  Add a default mouse movement added to one slide (no customisations) and your custom mouse movement to the other slide.  Publish to see whether the mouse movements appear on both slides. ... View more

One other thing I just remembered about some versions of Captivate 2019. Sometimes even though it LOOKED like the mouse layer was at the very top of the layer order it wasn't.  So sometimes I had to manually select the layer and use the right-click action to Arrange > Bring to Front before it would then publish as expected.  Maybe you could try that as well. ... View more

Couple of things to check: Are the mouse layers at the very top of the layer order? Are they set to be shown?  (The 'eye' column must not have an X.) ... View more

Are you trying to view your published project from a web server environment, or are you just going to the folder where you published it and then launching the content via the index.html file?   If the latter, do the former instead. ... View more

First time I have been called a 'Dinosaur".  Sounds ominous, considering what happened to them.   To be quite honest, although I have supported Captivate since it first came out many years ago, I cannot in all conscience recommend it to anyone right now as the app they should invest years of time creating e-learning.   There is no future for Captivate Classic.  And Captivate 12 is far too limited to be the tool of choice for most of the e-learning companies and government organisations want.   I really feel that Adobe dropped the ball with the entire direction they have gone with Captivate 12.   The only reason I am still creating e-learning with Captivate Classic is that the clients I currently have still use it as their tool of choice.  But I have warned them continuously about the danger of not looking elsewhere for their future tool.  Sadly, many learning managers just tend to "kick the can down the road" until they land in deep proverbial one day when everything stops working overnite.   Maybe THEY are the real dinosaurs. ... View more

The courses should still work on the internet. Whether you can continue creating new courses with Captivate Classic is likely to be dependent on whether or not it continues to work with your Operating System.  The main thing that tends to completely stop Captivate from working is a new OS release with which it is not compatible.  This happens to MacOS users all the time because their major OS updates seem to be more frequent than Windows.   So this potential limitation (Captivate ceasing to work) would also prevent you from being able to modify those older projects at some point.   Your only hope would be that one day Adobe DOES provide a way for Captivate 12 to open and upgrade Captivate Classic projects.  But I have not seen any date given for when (or if) that might occur. ... View more

Captivate's HTML5 output requires a web server environment for everything to work properly.   When you Preview in Captivate you are viewing it from a temporary localhost web server.   If you just publish and then double-click to launch the index.html files you are not going to be viewing the content from a web server environment and lots of things will not work.     Upload your published output (all the files, not just the index.html) to a web server and then view it. ... View more

This may be the reason for your problem: Cross origin blocking in modern web browsers https://www.chromium.org/Home/chromium-security/corb-for-developers/   https://www.telerik.com/blogs/all-you-need-to-know-cors-errors#:~:text=CORS%20errors%20happen%20when%20a,by%20the%20server's%20CORS%20configuration.   To test if this is the issue, follow instructions here to disable CORS in your web browser: https://www.descope.com/blog/post/cors-errors     ... View more

My question was what happens if you select YES to let Captivate adjust the settings?  It looks to me like the default settings are NOT what you need so you will either need to let Captivate make automatic changes or else try lots of different manual settings to try and find out WHICH ones work.    There must be something about either the content in your project or the settings you have chosen that is preventing video output.  Does the project contain anything that would NOT be appropriate for video?  E.g is the content requiring interactivity? (MP4 is not interactive.)  Is the stage size too large? ... View more

If you allow Captivate to adjust the settings, does it then publish? ... View more

I would suggest you send a message to Saurav Ghosh at Adobe via this page: About Saurav_Ghosh - Adobe Community ... View more

Sadly Lilybiri is no longer with us.  But you are correct that at this point in time files created in Captivate Classic and earler versions cannot be opened or edited in Captivate 12. ... View more

That must be one very complicated process.   In any case, you should then be able to launch a second capture session to complete the process, then import both into Captivate.   Have you tried that? ... View more

I'm assuming you did not have backups selected in your project settngs?  If you did then there should be a file in the same folder as your project with the .bak file ending.  You can just remove that ending to get a cptx file that is from the previous save and close.   If you do not have that option, take a look at this rather old post that might provide some suggestions: https://www.infosemantics.com.au/how-to-recover-corrupted-adobe-captivate-projects/   Ignore the part in the post about using the Dcache app.  That is no longer supported. ... View more

As you have found, it's not really possible to predict to the split second when the video will download and be ready so that external Closed Caption text can appear in sync.   With event videos the only reliable way to make sure closed captions appear in sync with the video is to have them in the video itself.  Slide video is likely to be a better option because it is locked to the slide timeline. But even then the download times can cause the CC and video to be slightly out of sync. ... View more

Basically, if you want to avoid issues with file corruption, have your files stored somewhere that requires Check-out and Check-in so that no two developers will ever be able to work on the same file at the same time.  Each person that needs to touch and edit the project file has to check it out and download it to their own computer hard drive, then save changes and upload it back to the repository before checking it in again.  Never work on a Captivate project file over a cloud connection.  The CPTX (and I suspect CP is the same) file format is really just a renamed ZIP archive.  When Captivate is working on it there may be hundreds of small files involved.  Having more than one person involved in the editing is asking for problems. ... View more

Again they seem to be fond of giving vague answers  ("some network and security issues").   Just keep pushing them for specifics.  Let them know that if you don't understand their answers then you will be posting the question here on the forum where there are people that DO understand technobabble. ... View more

I would certainly suggest that you DO update your Captivate 2019 version to the latest available (11.8.x).   But that isn't necessarily going to automatically fix what your IT department are complaining about.   I am assuming by their statement about "outdated versions of Javascript" they are probably referring to the fact that Captivate 2019 still uses some JavaScript functions that modern browsers no longer support.  However, that doesn't mean that anything bad is going to happen as a result.  I would be asking your IT department to specify exactly WHICH JavaScript issues they object to.  Their statement is vague.   As regards their other complaint about "proprietary Javascript files" this too is somewhat ridiculous.  The cpm.js file is a huge Javascript file that is constructed directly from your Captivate CPTX project file and of course it must be properly loaded for everything to work properly.  The cpXHRLoader.js file is also custom generated at publish time.  But if your IT department had actually opened that JS file they would have seen that permission is given for the file to be used in output.  So in what way are these files unable to be used?   A typical Captivate HTML5 output ensures that all required files are encapsulated inside the output folder.  When you test Preview the project on your development computer (yes it could be called a 'local environment') you are basically just running the output inside a temporary localhost webserver that Captivate creates for the occasion.  If the content can run in your localhost webserver then it should also work on your organisation's web server as well.  Did the IT department actually TRY to copy the output to a folder on their TEST webserver to see if it worked?  It does not appear that they have done so.   Honestly, I think your IT department are just being difficult to deal with. ... View more

My pleasure.   ... View more