Forum Discussion
Overlapping States
I've been noticing a randomly occurring, but frequent, issue since the newest update. On some objects, the Normal/Original state will overlap with any other state (Hover, Visited, custom states, etc.)
So when you hover over a button, the text might change color, or an image might change, but the original text or original image can still be seen underneath.
Here is a quick example, a side by side screenshot from a published example:
On the Hover state, the icon is changed so that the bars on the chart sit a little higher when hovered over, though you can still see the original icon being used underneath when this happens. Additionally, you can see the stroke thickness looks more intensified as the images are overlapping. If I did this with a lighter text color on the hover state, and made it bold, you could still see bits of the original text peeking out from behind. I've tried testing this with .PNG, .SVG, .GIF, and other transparent files, but it happens with Storyline assets as well.
Here's another example using an icon built into Storyline. On Hover, the icon should just rotate 90 degrees, however, when in Preview or Published mode - the icon overlaps, and instead of having horizontal lines, we're left with a waffle/grid. Each example was made using a new Storyline file.
What's strange (or stranger) is that I can make a new state, set it to hover, delete all the objects on that new state, copy and paste in place the original assets used, and then swap the icon - and it will still happen.
The only workaround I have is to paste in place the base of the button (in this case the white rounded rectangle) two or three times, depending on any shape effects (e.g. drop shadows), which adding a bunch of objects to one state doesn't always yield the smoothest results once published. Additionally, in some circumstances, doing this causes a flicker effect on the hover state where the new button base flashes in before the rest of the other objects do, or the drop shadow will flicker when hovered over.
Fixes? Workarounds? Is this a known issue that needs to be patched?
107 Replies
Hello, does anyone solved this issue? Yesterday and today I worked on two different files from two different courses, and still facing this unexpected behavior :(
I attached an image where you can see a yellow border, wich should be the hover status, a green icon which belongs to Visited status, and a white mark behind the green icon which belongs to the Normal status :D
I'm using Storyline 64bit v.3.90.32893.0
I'm going to submit a new case attaching my file.
Thank you!
Hi Giulia,
I'm sorry to hear you've hit this snag!
It looks like you're working with Philam in a support case. We can continue the conversation there if you have any questions.
This is still happening and really causing lost time trying to work around or having to change my plans to allow for the bug... I've used shapes with states hundreds of times over the past 5 years and never ran into this until today...
(Edit: I see that other people have already suggested this, but I wanted to throw this out there anyway for anyone new to the thread.)
There may be a workaround using custom states. I was having the same issue when using Storyline's built-in states (hover, down, visited, etc.) and created a custom state with a trigger to simulate the built-in state I wanted.
Ex: The Normal state was overlapping the Hover state
My steps:
1. Create a new state by typing in a name different from the built-in options (Ex: Object Custom State)
2. Edit the custom state as desired
3. Create a trigger with the "Change state of" Action (In my case: "Change state of Object to Object Custom State when the user hovers over Object")
4. Select the "Restore previous state when the user hovers out" option
This showed no overlapping in Edit or Preview Mode
(From intern Anna Miller, working under Brandon Horn)
Hi all
I also need to add a grievance to this list,
I added a layer and inserted a shape with specific text that is to display when the shape is in its normal state. I then created a unique state for this shape called 'Story' which displays another set of text. I set a trigger to change the shape state to Story when the user clicks, which it does but the text in the normal state also remains visible behind the story state text. I deleted the shape from the Story state and inserted a new shape and added the story text to this state. However when I test it the normal text remains visible behind the story state text!!Hi, having the same issue here. I have been using Storyline since it was released and this is the first time I am experiencing this.
The funny thing is that it happens with some elements, and some other is not. This erratic behaviour makes it so difficult to identify and correct, because it is not happening on preview mode, only when publised :(
Adding my vote here to have a solid look into this.
Thanks @spencer for the follow up.
Hello Victor,
Sorry to hear you're having issues with your project file related to overlapping states. It sounds like some random elements in your slides may be causing the issue for some objects but not for others.
Could I have you connect with us in a case so we can determine what's happening? Our support engineers may request a copy of the affected Storyline project to aid in the investigation. You can share it with them privately within the support case. We'll reach out soon after we hear from you!
I'll add my vote to that. There are many fixes that would help with accomplishing basic tasks in StoryLine and Rise that don't seem to be a priority. I guess it's not as sexy a selling point as AI.
Thanks for adding your voice to this feature request, Nick! I've updated the feature report with your comments.
Seeing things like AI Video being added to Rise 360 before fixing a major technical issue with Storyline 360, that's existed for years now, feels rather disheartening. While I'm excited for all of the new features, and appreciative of Articulate, I also want all the features that have existed to work as intended.
Could we please have some transparency on where this is at? I think it would help all of the users being affected, especially those still stumbling into this topic years later looking for answers, if they at least knew where things stood on the matter. Just the occasional comment providing any update would be highly appreciated!
Agreed! Especially as this is not a free product.
I'm actually surprised & dismayed at the lack of attention to customer issues.
Hopefully this will be a priority soon!
Articulate, please, we are begging you! This issue has been ongoing for YEARS! I've had to go back and use triggers instead of built in states to get the effects I want. :(
Agreed. It diminishes the use of the product, makes it not work as intended, and causes issues for customers. This literately happened after an update, and instead of rolling back and fixing it where it started, we just keep moving forward with no solution in sight.
There was another recent update that broke another feature, which I won't get into details here; for the sake of relevancy, but now I have an additional support ticket that I fear will remain open for years to come alongside this one. I have never had a support ticket/bug report open this long, and this is coming from someone who also used to work in IT.
I appreciate Articulate staff and support, and I'm trying to be patient about my growing list of issues and requests, but when they keep piling up, with no solutions (just "Your voice has been added...") it gets a bit frustrating.
For all of our sake's - I hope a solution is in sight!
Sorry but I'm encountering the same issue.
A very simple example attached: text overlaps and style of hover (bold) is not respected.
Quite annoying!Hi Marco,
Thanks for reaching out! I've added your voice to the report mentioned in this thread so we can notify you if there are any changes to the behavior. As a workaround, you can use the "mouse hover" trigger combined with a custom state to achieve the same effect with your image. I've attached a sample project file so you can test the workaround.
Hope this helps!
I am also experiencing the same issue on my end and would appreciate Articulate looking into this and fixing the problem.
