Describe the bug
Utilizing fadeInOut as the value for the config.body.transition.name variable in the vars section prevents passage links from actually displaying the targeted passage.
To Reproduce
Add config.body.transition.name: 'fadeInOut' to the vars section of any passage.
Expected behavior
I expected the previous passage to fade out upon clicking a passage link and then the new passage to fade in, starting with the one I set the variable in.
Environment
I am seeing this problem on Windows 11, using Twine 2.8.1.
Additional context
If you place config.body.transition.name: 'fadeInOut' in a passage greater than the second level of interaction, you should see that the untouched passages do, in fact, transition properly. But once you attempt to reach the modified passage with a link, its contents will not display - yet it will be listed as part of the trail.
Thanks for reporting this! This will be fixed in the next release. Unfortunately, I don't think there is a workaround for this in the meantime other than using a different transition type.
Describe the bug Utilizing
fadeInOut
as the value for theconfig.body.transition.name
variable in the vars section prevents passage links from actually displaying the targeted passage.To Reproduce Add
config.body.transition.name: 'fadeInOut'
to the vars section of any passage.Expected behavior I expected the previous passage to fade out upon clicking a passage link and then the new passage to fade in, starting with the one I set the variable in.
Stories and screenshots fadeInOut_bugTest.zip
Environment I am seeing this problem on Windows 11, using Twine 2.8.1.
Additional context If you place
config.body.transition.name: 'fadeInOut'
in a passage greater than the second level of interaction, you should see that the untouched passages do, in fact, transition properly. But once you attempt to reach the modified passage with a link, its contents will not display - yet it will be listed as part of the trail.