I'm gonna throw some requests for the SDK out there:

- Built in edit-time message pump. I can't figure out how to set this up without gutting one of the plugins that has one (e.g. physics, bones, etc...)
• Dynamic parameters list for actions and conditions. For example, you have three parameters such as a combo box(with two values such as "Set position" and don't set position) and two values. If the combo box is set to the "Set position" option, then you could have the other two parameters appear. This would keep useless parameters from being shown to the user and sucking up space.

I think these would be great additions to the SDK.

I have a question. What uses more CPU? Adding abs(x1 - x2) + (repeat for y,z) or using the square root?

The square root calculation, definitely. Finding the square root of a number requires the use of multiplication and division, both of which are slower than addition and subtraction.

I can't think of anyway you could do this with the current version of the plugin. I'll see if I can get functionality like this into the rewrite.

Unfortunately, there's no support for the "Music" folder at the moment. You need to put all of your music and sound files into the "Files" folder.

Would it clear from VRAM as soon as all instances of the bullet are gone? Oh, hmm. I could manually load the storage layout and keep it loaded couldn't I?

From my testing, it seems that textures are removed from VRAM as soon as all instances of the object using it are gone.

Here's an example showing a similar setup to what was in the video:

Yay for shadows!

And in case you don't have a PS2 capable graphics card:

Yay for (not as cool)shadows!

Sorry to sound like a noob.

But how do you install this.

Download the .fx file and place it in the "Effects" folder inside of the Construct folder. You should find the Construct folder under the Scirra folder in Program Files, assuming you didn't change the installation path.

Lost my Keys - Yes, it's an old topic, but he's asking a question relative to the topic at hand, so there's nothing wrong.

None of these bugs are likely to be fixed for the current version. The code base is crap and fixing anything is a huge pain.

The good news is that I'm currently in the process of writing from scratch the next version of this plugin. The bad news is that it won't be compatible with the current plugin because I want to make some changes to how it works, so events will have to be changed over to the new version. With any luck, though, the rewrite should fix any bugs, or at the very least make it easier to find them.

The first effect you mentioned is done using the bumpmapping shader, which is explained on this wiki page.

The shadows are done using the shadow casting behavior and the light object. You put the shadow casting behavior on the objects you want to cast shadows, then the shadows will be cast based on where the light objects are.

Hope that helped.

> Ashley seems pretty opposed to the idea and I guess she's free to work on the project in the way she's most comfortable with

>

*Cough*... Ok, honest mistake.

Maybe I should make a thread about this to alleviate all of the confusion.

Does the SpriteFont.Width value even work? I'm trying to set my graphical dialog box - a speech bubble sprite - to the width of the SpriteFont textbox, but it appears at a width lesser than the width of the textbox.

Take a look at this to see what I mean.

Um... I don't think you posted this in the right topic. :

I have no idea where the debug problems are coming from. I'm going to start completely rewriting this plugin sometime within the next week or so. Hopefully that will knock out all of these annoying problems.