Showstopping bugs and hassle-laden rework upgrading to Studio '13
I was excited to upgrade to the new suite, mainly for HTML5 support. However, within an hour or two after upgrading and trying to convert a project done in Studio '09, I uncovered several bugs, which were all later reproduced by Articulate Support.
1. When uploading to an LMS, the personalized logo added does not show up. At all. This happens in Saba, and Support replicated the issue using the SCORM Cloud test site. I am baffled as to how this got by QA, as product branding and LMS use is a pretty big deal, isn't it? I was told by support that the workaround is to disable HTML5 output. So the biggest reason I upgraded is now invalid?
2. If you use a custom player tab interaction in the topbar right area of your player, you cannot properly reorder the items you have in there. For example, I have an Engage interaction as HELP, then RESOURCES and EXIT. We always have EXIT as the last link (on the right). As long as the Engage interaction is there, it will not let me put EXIT on the right, but instead, puts RESOURCES there. The only fix is to remove the Engage interaction, thereby changing the layout/interaction of every project we do.
3. Notes text in the first few slides of a presentation gets resized for a few slides until it finally displays correctly. For example, out notes text is always Arial 11pt. font. Yet the second slide in a project renders at 9pt., then the next slide at 10pt., then the third slide finally is correct. I can resize those other 2 slides at other font sizes (which display correctly), but not the correct 11pt. Minor, and not the end of the world, but still noticeable.
4. Not a bug, but a hassle: custom templates. Why is there not a converter from old templates in '09 to the new XML format in '13? There is also almost a 1:1 match between the Storyline custom template color schemes and Presenter '13. Why not at least make those interchangeable for customers using both? Instead, I had to do a side-by-side recreation of our entire color scheme for the player template, 1 field at a time (and there are, it seems, about 100 individual custom color fields to modify, and it's not the easiest interface to use, either).
While issues 3 and 4 are not showstoppers, items 1 and 2 are, and I am now stuck with the '13 suite and unable to work because of the bugs. I've been a big supporter of the software, but this has been a big letdown, in all honesty..
I was told it's up to the developers what issues they choose to fix. Studio '09 had a lot of known issues that never got fixed, so I really can't guess with any confidence if these will get fixed or not (and neither could Support). I also don't think crippling your projects to get something to work without bugs is a reasonable request or expectation for a software developer to make.
Anyone out there that can save the day and know of actual workarounds for those issues without disabling a major feature of the software? Or am I going to have to wait until I can downgrade back to '09 and hope these issues get fixed?