Screen Bleed - Wrong Screen Shows Up When Playing Project

Question

I'm on Captivate 6.
Creating a demo simulation with a lot of buttons that "Go to Next Slide" or "Go to specific slide.  Also have some auto-advance slides based on timing.
When editing, screens look fine.  After adding some buttons and hightlight boxes, I then either PREVIEW (both in or out of browser) or PUBLISH (SWF / HTML5 / EXE) and when I play it back, I occasionally will get the wrong background or pieces of the wrong background showing up on the wrong slide.
In one specific case, I took a screen shot of an application with a drop down box in it.   When I play it back, I see just the drop down, but it's superimposed on SLIDE 1.   But, as mention, in the editor, everything looks perfectly fine. 
I also have a auto-advance slide that moves forward after a half-second... when I play back and get to that slide, I see a portion of the top of another slide for about 1/4 second... then I see the actual slide.. .and then it moves forward to the next slide.
There is no rhyme or reason as to why and / or when this occurs.   And I can sometimes be 100% fine, but then maybe I cut / paste some buttons / hightlight boxes from one slide to another, and then that slide (which was working fine before) might start having this issue.
I'd like to know if there is a way to easily fix this.  It's making it nearly impossible for me to use Captivate to create these, what should be very "simple" demo simulations.

Answer 1

While I never resolved this issue, I did find a viable workaround, better than "republishing several times" (and then having to re-verify every single screen in my demo was correct), which was initially the only way I could get around the problem.
What I have found is if you do a "select all" slides (i.e. click on first slide and then CNTL-A) and then right click and "Mouse - Show Mouse" to show mouse, then follow that up with a right click "Mouse - Show Mouse" to hide mouse... save project and re-publish, that seems to consistently and completely take care of the bleed issue for that particular publish.  It's almost as if that does some sort of re-calibration of the entire project to "fix" any issues.  (Makes me wonder if "recalibration" should not be a menu option in Captivate that does whatever it is my workaround does to fix the issue?)
Few comments about my workaround:
I want the mouse hidden on ALL my slides, thus the "show mouse / hide mouse".  If your project requires the mouse to exist on all slides, do the opposite.
On projects with many slides, this "show" and "hide" on all slides at once can take a bit of time to complete.
Whenever I "show mouse", the default mouse timing many times lengthens my slide time from what I actually desire.  So the very first time I "show mouse", I go thru and manually size them all to 0.1 seconds.   Guessing there's probably an easier way to do this, but I got tired of always having to re-adjust my slides after hiding the mouse before publishing.
If your project has mouse visible on some slides and not on others, I have not tried my workaround solution to that.  But I'd suspect you'd have to selectively choose slides (instead of CNTL-A) and then "show / hide" or "hide / show" based on whether or not you want the mouse.   On big projects, this could be annoying!
I am attaching a screen print to illustrate my issue.  I've had two others in my company on different computers that experience this exact same issue.  I was a bit surprised to not find more "complaints" about this online as, at least for me, it's more than just a random happening.   I am publishing to SWF and HTML5.
I have also noticed a similar thing occuring when using the "MEDIA" publish to an .exe file.  In at least one of those cases, my "hide / show mouse" workaround did not seem to work.
At least for me, this was a workaround solution that made using Captivate viable for my needs.  Otherwise, due to my large number of projects with many slides, I would have had to investigate and change to a different solution.   The "republishing several times" option would have taken too long and also not have provided me comfort knowing my problem was actually fixed on every slide.