BUG: Storyline 'Save' Issues?
I've had a strange and growing issue that I recently noticed, and has persisted across several updates and projects. The 'Save' icon at the top-left of the screen will be grayed out, in a disabled state, UNLESS I manually save the course - then it will return to a Normal state. If I click on it again, or potentially after some time, it grays out and disables again. I didn't pay much mind to it, as it was more annoying than troublesome, however something happened today that raised some flags. One time, I was going to close out of Storyline and reopen it so I could move the file I was working on. Simple, easy, common task. The floppy icon is grayed out, so I click File > Save. Storyline thinks for a minute as it saves the course, and I let it do its thing. Once I see it has saved, I go to exit and suddenly; Do you want to save the changes you made to [Project File].story? Well, I had just saved the file, and immediately clicked the Close/X button to exit out of Storyline, so... why did I receive the prompt? Nothing had changed in the file, and all signs pointed to it being saved. I checked the folder the file is in; the 'current' file was last modified 10 minutes before, or the time before my last save. So, Storyline acted like it saved the project, and... what happened? Where did that file go? Where did it save to? Regardless, I was able to save the file after doing a Save As, and while I haven't experienced that specific issue, after multiple updates the grayed out Save icon still persists. As mentioned, and for support purposes, I have been able to duplicate this issue in a new project file. I'm unsure exactly what triggers it, but it isn't exclusive to one project or file.BUG: Can't 'Preview' Storyline Timeline.
It's about as straight-forward as it sounds; without any rhyme or reason, I will suddenly be unable to 'preview' the timeline of a slide or layer in the Storyline editor. I can click 'Play' or press Space and... nothing happens. So far, my workaround has been to 'Select All' (CTRL + A), 'Copy' (CTRL + C), and then open a new Storyline project, and then go to the 'Paste' option and right-click to retain all durations, start times, options, etc. 'Oh, so the issue must be with the project file!' Wrong. Halfway through editing a copied single slide in a 'new' project file, I was once again unable to preview the timeline. So, I copied it into a new project and it was fine. I could finish the slide without issue. I did the same for two more slides, no issues, but then it occurred again on a slide after that. Additionally, this issue has occurred on multiple project files for entirely different projects, implying that it shouldn't be an issue with a single asset or project file, as its being reoccurring across various instances with different variables. I thought the issue might've been with a recent update, and so I hesitated to update Storyline again today, as I have multiple projects I am attempting to get out the door and don't want even more Storyline-related obstacles to go through. So, I updated Storyline and... the issue is still there. Once I am wrapped up with this set of projects, I plan on doing a 'full'/'deep' uninstall of Storyline 360 (including running the batch file to hunt down any remaining files) and reinstalling it again, and will update if it makes a difference, but in the meantime, I'm posting to see if anyone has any solutions, workarounds, or similar experiences that have been occurring as of recent. I know to file a ticket with support, but I also know 3, 5, maybe even 7 years from now someone may have the same issue and hopefully this post will eventually contain some solution and save them some time.BUG: Storyline inputting random values in fields
I have encountered a bug within Storyline 360, which I can consistently trigger. I can't tell if it's another bug Storyline 360 has with states, or if its another bug Storyline 360 has with cropping, as both are prone to issues. Here is a link to a video of the bug in real time. (Google Drive) Scenario: I have an image with X amount of states. Each state is identical, except for the position of the image. This isn't anything big or complex for Storyline 360. Now I need to 'Crop' said image, and consistently crop it across each state. That shouldn't be too hard either. I just go an select Picture Tools - Format > Size and Position Window > Crop from, and then enter the appropriate values. In this case; 1428, 224, 1209, 124. Issue: However, that's where the error comes in. The first state/image crops without issue, and then I go to the second state/image and then mysteriously, and without reason, after inputting the value into the Crop from - Left field, Storyline will suddenly change the value to something entirely random (i.e.: 1428 to 4081), and only for that field. In turn, this also somehow causes issues with the image that may not even appear until after I close the window. This means I have to then hit undo several times, waiting for Storyline to undo each edit, and then redo everything for that state/image all over again. For example: I am cropping each image with 1428, 224, 1209, 124. For some reason, Storyline edits the first number to be 4081, 224, 1209, 124. It has done this consistentlywith several other images and different values in the Crop From field. I even went as far as using a hotkey to try and work around it, and Storyline still forces random values to be inputted into the Crop from - Left field. Additional Concerns: Aside from doubling the time of this already tedious task, this poses an additional concern and risk. After learning from Support that states can become corrupted and cause the course to act volatile, I'm worried that whatever issue Storyline is having with states and cropping might corrupt one of the states, and cause potential issues later on. Additionally, it has already caused some other states to change without prompt, such as to disproportionally resize, and even causing Storyline to crash altogether. To be clear; this issue isn't exclusive to this single image. It is occurring across any image with states that I try this with, and can be easily recreated in a new course.
