New plugin set should be out tonight or tomorrow , check the download page for the update when its out

kmsravindra

No problem! thanks for buying Q3D, the new updates should be a bit easier to use

i think a nice solution would be to have a param where you can let users select multiple types or none at all at once for certain conditions, and then the param in the run-time function is an array of the types which a user has selected? this way we could make flexible functions that operate on many types, but only as many as the user selects, circumventing the issue of slowdown proportional to a large number of types in the project for stuff like this?

https://dl.dropboxusercontent.com/u/829 ... %20cap.png

I made a small example for you. I'm not sure if you'll be able to get it to work cause i used a new version of the Q3D plugin which i've been working on (whoops) so i made a screenshot just in case. It should run though since this component of the plugin wasn't heavily modified. you might get a warning about versions or whatever.

https://dl.dropboxusercontent.com/u/829 ... ample.capx

How is a plugin bogging down your system? some kind of memory leak?

This is how i was doing it but i didn't know what the type's list was called so i was grabbing all the children's types through the instances that were children. gonna try this now and see what happens.

Is there a convenient way that i can empty every SOL ? i have a condition that picks objects in an advanced way that first requires all the sols for all objects except the one calling the condition to be empty (it then picks a specific subset of objects).

the condition basically needs to work as follows

Condition:

"Main object -> pick children"

{

wipe all SOLs except possibly the sol of "Main object" which is calling the condition.

iterate over children of main object, adding them to sol.instances.

return true.

};

You can't really protect yourself from pirates, if people have the plugin files they can use them, there's no way to work around that fact.

this is basically a goto, which is something you really avoid in all programming languages because it makes code horrendously spaghetti like and hard to manage. You need to give a good use case to justify something like this, and you're example wasn't one, no example for goto's ever are. you could use the stop loop condition, or simply use a variable to choose the right sound. there are ways around goto's and goto's should be avoided.

you can use javascript objects as hashtables/dictionaries, with each key being a branch of a tree, and each key can in turn store another object which is also a hastable/dictionary. This wouldn't be difficult at all so read about javascript!

definitely possible, although the caveats to get it to interact with constructs collision system would probably limit the usability. It's one thing to have a nice tech demo without much interaction, and another to have it usable in a game. I might take a look at trying to implement it eventually though, it seems like an interesting challenge.

Since it's pushing stuff onto the gpu and construct doesn't facilitate very low level access to the context i'd probably do it similar to Q3D on an external canvas.

use paster...