@juriaan THAT WORKED! I had ended those tasks earlier trying it, but I think I might have missed one earlier. Works wonderfully now thanks!

I found the problem and sorted it. You should be all set.

I thought it was an issue with the date but that turned out not to be the case. The issue is that, as stated on the store, "for each Buy-to-Own or Subscription license you purchase you can activate Isadora on up to two online or offline computers, though you may only use the license on one of those two computers at a time. ... In all cases, you may deactivate a license on one computer in order to activate it on a different machine."

I can tell by inspecting your license's installation history in our database that you have already activated your license on two computers. If you want to put the license on another computer, you'll need to physically access one of the two computers you've got the license active on and then deactivate your license on one of them so that you can activate the license on a new computer, or (if you don't have access to the two other machines at the moment), use the Online License Portal to remotely deactivate your license on one of the two computers already using the license.

Best wishes,

Woland

Please submit a support ticket. You can be helped more directly through the help system.
The links are in my signature below.

@nest

I no PC user. But for PC users to help you, please post your computer specs, Windows version and Isadora version.

Best Michel

Thanks

Jean-François

@jfg

This seems to be a bug, please file a bug report via form on the website https://support.troikatronix.c...

Best Michel

...sorry and the last thing for today,

in the software toolkit from ms for the 1414 (1.8.0) , is a very simple example where you can see from where( in degree from -90 to 90) and with what beam angle and i think how far away? or how loud a sound is. all in numbers. this coud be a very unique feature. we can't find it in any software, to easy get this data to osc or midi. also nimate can not do it, we think.

thanks.

r.h.

@weston

It may have to do with the resolution settings in the mapper window. By default its set to 1920x1080 (bottom right corner of the mapping window), you should put it to the resolution you are inputing to the projector.

Best Michel

@draganno said:

I noticed now however that the Scene Editor lags/stutters when adding a mouse watcher.

I cannot reproduce this behavior. Adding a Mouse Watcher actor, Stage Mouse Watcher actor, and dragged either of them around doesn't cause my fps to drop, my Scene Editor to lag, or my video output to skip. Could you please create a support ticket using the link in the signature and provide a screen recording of the issue?

@mark said:

a bug that the Stage Preview and Monitor controls do not respect the FPS setting.

 I have logged this issue in our bug-tracker

@mark Hi Mark, the model is a sphere with a video texture on it.

@woland

You are welcome to

@Woland Hi there, thank you for your quick response. 

It's a MacBook Pro 15" late 2016 which I thought was in its default resolution of 1680 x 1050 - when I go into "System Preferences" and "Displays" it's in default mode and this corresponds to 1680 x 1050 in my Screen Res app.

However, looking on the internet it says the native resolution for this Mac is 2880 x 1800, gosh have I been working at the wrong res all this time?! 😳 When I change to this resolution Isadora workspace looks fine - even if I then return to 1680 x 1050.

Many thanks for your help!

@woland (and Mark)

Thank you for correcting this!

I would like to add an information: I have been able to correct similar issues with "spots" in Max/Jitter by forcing textures from "char" to "float32". Would there be a way to do something similar in Isadora?

Thanks!

Best wishes,

jbb

@rollinlikethunda said:

the file name being too long

 Ah, OK thanks for pointing that out. I have had the same issues when using Blender to create 3ds files. Keeping associated file names short has become a habit for me. Although, I don’t have that problem with other 3D modelling software, like Cheetah 3D. Because of this I don’t know if it is a bug in Isadora, or in the way some 3D software writes to the 3ds file.

Best Wishes

Russell 

Hi,

I have been prototyping a slow particle technique that allows a rudimentary 3D scene to be constructed in Isadora. I am getting inconsistent rendering of transparent texture on mesh instances when using 3D Model Particles. Some of the particles appear with transparent texture and other particles generating from the same source appear opaque. I know it is associated with the back face rendering and possibly not much can be done. But here's hoping. You can see in the screen grab of of the stage that one sphere is rendered with transparency and others are opaque.

If you are interested to have a look at this slow particles technique the file package is attached here: Slow Particles.zip

Best Wishes

Russell

@dusx Thanks, Ryan, it was what I suspected, best! AZ.

This is a bug that it doesn't work the same way when triggering it with MSC vs using the Spacebar. I will add this to our tracker.

For now, here's the easiest workaround I could come up with: This file (Fade Demo.izz) will make it behave the way you want it to (and also led me to discover a different bug involving trying to deactivate an activated Scene you're transitioning into mid-transition). If you're clicking around to deactivate Scenes mid-transition that you've already activated you may get an assertion dialog about failing to deactivate the Scene, but it you press "Continue" everything is fine.

The trick is to put a MIDI Show Control Watcher paired with a Text Comparator looking for the cue number of the next Scene (the one you want to "bump" in). When you hit that cue, it'll trigger the Activate Scene actor and bump the next Scene in.

Best wishes,

Woland

Thanks, it's ok !

Best