Hello Ventuzians!
THE FORUMS ARE CLOSED!

Please join our discord server HERE!! << click me :D

We are shutting our Ventuz Forum, but don't worry, it will all be archived for you to search in if you have a query. From now on, please add all your comments, questions or observations into our Discord Server

Thanks for the great time - see you on discord!!
Dee, Karol, Daniel and the whoooole Product and Support team!

Search found 34 matches

by craig
28 Oct 2016, 10:32
Forum: General Discussion
Topic: Ventuz Scene Instance IDs - remoting
Replies: 8
Views: 5630

Re: Ventuz Scene Instance IDs - remoting

Hi Karol, Thanks for the reply. I'm seeing the same behaviour running the Remoting4 Demo 1 application too - see screen grabs below. Again, I can close the scene in the designer, and still the renderer shows the loaded scene and I can still control it. SceneIID in Ventuz.png SceneIID in Visual Studi...
by craig
28 Oct 2016, 08:51
Forum: General Discussion
Topic: Ventuz Scene Instance IDs - remoting
Replies: 8
Views: 5630

Re: Ventuz Scene Instance IDs - remoting

I'd really appreciate some advice from the community on how the relationship between scenes and the IIDs work - there's nothing in the help files.

Anyone...????
by craig
17 Oct 2016, 11:45
Forum: General Discussion
Topic: Ventuz Scene Instance IDs - remoting
Replies: 8
Views: 5630

Re: Ventuz Scene Instance IDs - remoting

To follow up - I think there's something I'm not quite getting about the scene lifecycle. When I test my cluster to see if it's in Designer, I assume I have to attach to a running scene. (Me.VCluster.VentuzInfo.Value.Mode = MachineMode.Designer) I can enumerate the loaded scenes by calling Cluster.S...
by craig
17 Oct 2016, 11:03
Forum: General Discussion
Topic: Ventuz Scene Instance IDs - remoting
Replies: 8
Views: 5630

Ventuz Scene Instance IDs - remoting

Hi all, Kinetic Pixel are finally moving ahead with our migration to Ventuz 5, and we've ported our old Remoting libraries with some success so far. One thing that's confusing me though - When running a scene in designer, the IID I get back from Remoting in the FlaggedIID object is different to the ...
by craig
02 Aug 2013, 12:48
Forum: Bug Reports
Topic: XML Node Bug
Replies: 6
Views: 11552

Re: XML Node Bug

Thanks very much for the hotfix, guys. I think we can call this issue closed. :)

Cheers,
Craig.
by craig
31 Jul 2013, 11:24
Forum: How to...
Topic: Script node - unmanaged dependencies of a reference
Replies: 2
Views: 3082

Re: Script node - unmanaged dependencies of a reference

I think I've just found the solution - the \appdata\local\temp directory does appear to be correct I think. I was running as Administrator too in case there was a credentials issue accessing that folder.

Restarting Ventuz as a standard user seems to have fixed it for me. :)
by craig
31 Jul 2013, 11:11
Forum: How to...
Topic: Script node - unmanaged dependencies of a reference
Replies: 2
Views: 3082

Script node - unmanaged dependencies of a reference

I'm trying to prove a little demo using the Leap Motion controller. This isn't a Leap specific question, otherwise I would have tagged it onto one of the other threads. :) I've added the .NET 3.5 dll to the GAC, and referenced it from my Ventuz script. My implementation is sound, as it works in Visu...
by craig
29 Jul 2013, 11:24
Forum: Bug Reports
Topic: XML Node Bug
Replies: 6
Views: 11552

Re: XML Node Bug

Hi Karol,

How is the fix for this issue progressing?

Regards,
Craig.
by craig
24 Jul 2013, 09:20
Forum: Bug Reports
Topic: XML Node Bug
Replies: 6
Views: 11552

Re: XML Node Bug

I think we have identified the problem. I've tested with a simple scene that has just a string node exposed as an external. I tried looping through the XML file and setting the external to a substring of the entire file - I had a hunch it might be to do with the maximum buffer size of the GDI DrawSt...
by craig
23 Jul 2013, 17:34
Forum: Bug Reports
Topic: XML Node Bug
Replies: 6
Views: 11552

Re: XML Node Bug

Hi Karol, I'm working on this project with Joe, and we're finding that this error is preventing us from testing or debugging our scene effectively. Once it has occurred, we can no longer access the input properties of any node - so for us, this has become a critical issue. Is it possible for your gu...