Glad to be of help.

Best Wishes,
Mark

This solutions article tells you "what to do" when you have a crash on Windows. Make sure to submit a ticket so we can follow up.

https://support.troikatronix.c...

Best Wishes,
Mark

@Woland

I have a beta that we'll make into a release by Thursday. I've sent you an email with the links. I am 99% sure it will solve your issue, because it solved a  problem with the same description for two other users. Please let us know if the problems continue after upgrading.

Best Wishes,
Mark

@admin

Dear Mark

this is a plugin eight has developed. See post HERE.

Best Michel

LOL, that is in fact what I am doing, albeit with blackwrap!

I've just spent a bit of time looking at the themes. I think 'Paper' is a nice all rounder and there seems to be no issues with it. 

the javascript actor exectutes the loop twice when the value is triggered, e.g. with a "trigger value actor"

actor attached | izzy 2.5.1 | OSX 10.11.6

js_trigger_bug.izz

Submitted :D

I have seen this same (or very similar) issue, and a bug report has been entered, so it should be in the pipeline for fixing.
The issue seems to be related to media with identical names. (actually I have only experienced this with images, but suspect other media will have the same problem)

If you give your media unique names and reimport I suspect your media bin will be ok.
Obviously this is a lot of work, so please do a test in a new file.
First import a number of media, and sort them similar to how you had them before. Save, close, reopen (the issue should have recurred).
Next rename a number of the media that have matching names. Rebuild the media list and sequence. Save, close, reopen to be sure that the naming solves the problem.
If that confirms that the naming solves the issue, go ahead and rename all media to have unique names, and rebuild the show media bin.
Hopefully this issue is fixed soon.

sounds a bit like the activity I was getting in elcapitan and movie playback, it would just become unresponsive, I could click on a scene, but the scene contents would not change, no response at all. I was developing on Sierra, and playing on Elcapitan, eventually upgraded the Elcapitan machine to Sierra and went for the new beta.

Want to send a patch and see if it behaves?

@TroikaTronix what is the best way for you and for the community to report bugs ?

I expect that with the splitted way between freshdesk + our new forum it isn't so easy to transform a post into a bug report.

Like if we post a bug in the forum other users can react and give there feedback on a problem, but you have to manually enter them into the support system. If we enter it into the support system at https://support.troikatronix.c... it is easier for you to maintain it, but we loose the community feedback with the possibility of double / tripple reports on the same bug. And the community is not aware of certain issues. 

I am really glad we have the new forum system with all the old and new advantages. It would definitely help me to have a direction on this topic.

thanks in advance

clemens

@tombergner

I have confirmed this bug on my win 10 test machine, and passed it along for fixing.

I don't think there is much in the SDK for this unfortunately.

Numbers are usually good for me.. its edit text controls that cause me trouble.
Maybe try to limit the speed of some of the updates (it they are being regularly updated/drawn)

I use cmd+G show/hide stage a lot. When going through the other shortcuts, I immediately try to close the window by pressing a second time, for example cmd + ; show preferences, but that doesn´t work. So are there others that would like that behavior? Because for me a shortcut lets me avoid clicking around, when I have to click to close, then its a 1/2 shortcut, not the full time saver.

In the list is an error: collapse actor is not cmd ++, but it´s cmd +-

@Fred & @DusX 

I think the Counter actor really works as it should. It's all about how on thinks about the wrapping

For example, here's a graphic representation of a Counter with the 'min' input set to -3 and the max to +3, with the 'amount' amount set to 3.

As you can see, if you go up by three, and if you have both -3 and +3 as part of the cycle, then it works exactly as it should. Can you see why this makes sense?

It is true that the float counter works differently, so there is an inconsistency ,this I will admit. That's because the true upper limit is a fraction less than 'max'. For a Float Count with the 'min' input set to -3 and the max to +3, with the 'amount' amount set to 3, you get this pattern:

In fact, you never hit +3 because the actual limit is 2.99999999999.... (Try it and you'll see it's true.) Also not so intuitive.

Fred, if you want the Counter to work the way you want, you can set the 'max' value to the desired max value plus the amount value minus 1. So, for your case, if you set the 'min' input to -45, and the 'max' input to (45 + (5-1)) 49, you'll see that it goes 30, 35, 40, 45, -45, -40, -35, etc.

Now, I am open to changing this – we could have an "inclusive" input which would either include or exclude the maximum value. (The Counter is currently "inclusive" while the Float Counter is currently "exclusive.")

Do you have a different suggestion about how it should work to make it more logical? In the end, you probably want the behavior of the Float Counter in the normal, integer Counter. But then to get the results you desire, you'd have to set a range of -45 to 50. This also is not very intuitive. 

Waiting to hear your thoughts.

Best Wishes,
Mark

No problem with launching Isadora now with or without wifi With the 2.5.2b14

YES!

You're welcome. 

anyone wanting to install a current beta, please submit a support request.

@srubidge

Please send us a support ticket with these details. We'd be happy to help you find a solution.

@DusX

I finally just cut and pasted the elements into a new scene and they worked fine, so I'm wondering if there was something having to do with a competing set of fades I may have accidentally made between the scenes--one in the jump actor and one in the scene transition panel at the bottom of the frame. I'll pull in the Trigger Delay actors and make things simpler as well :)

Thanks!

The input values are saved the same as all actors inputs in Isadora. I suspect you might be experiencing the fact that if you have a Set globals actor in multiple scenes, updating one will not update the others, and they will in fact Set the values when you enter that scene.

A great way around this behaviour (which can be useful at times) is to Put your Set actor inside an User Actor, and update it so that all instances of the User Actro update throughout your project. 
This is much like the practice of putting Projectors with mapping inside a User actor, so that updating the mapping once will update thoughout the project.