PDA

View Full Version : How to write a plugin that uses/extends tape

Oogst
04-06-2006, 09:47 AM
There are two things I wish to do with a tape in MAXscript that I do not know how to do. I am using 3D Studio MAX 8.

The first is that I want to write a plugin that extends the Tape-object. However, MAX totally seems to ignore my code. I have written this:

plugin Helper PBForceDir
name:"PBForceDir"
classID:#(0x47a07068, 0x73e23198)
category:"PaintBall"
extends:Tape
replaceUI:true
(
)

Now the PBForceDir is in the menu and I can create it, but the result of the creation is a normal tape. The UI is not replaced and classOf $ tells me it is a Tape and not a PBForceDir. If I would create the same thing based on a SphereGizmo, everything works fine, so the problem is specific for extending the tape. Does anyone know how to do this?

My second problem is that I want to create a plug-in that extends the BoxGizmo Helper, but has a taper as well. I want the following behaviour: the base of the Tape is not selectable and always at the same position as the base of the BoxGizmo. The target of the Tape however is normally selectable and movable by the user. I want to do this, because I am making objects that will be used in a game I am coding and this is a force-area-trigger. So when the player is in the BoxGizmo, a force pushes him in the direction of the target. How can I make such an object in 3dsmax?

Thanks in advance for looking at my question!
Wahooney
04-06-2006, 10:11 AM
Your first question:
TFM says that you cannot extend all plugins, targeted lights and cameras in particular and since the Tape object has a similar creation behavior it's fair to assume that it is not extendable.

TFM also says: "You can tell if a plug-in is not extendable if your new rollouts do not appear."

So sorry, you're either going to have to create your own system or be content with a tape.

As for your second question:
You may have more success making your own object by extending the dummy object. All helper objects allow you to build your own custom mesh to display. With some cunning you'll be able to get your system working with a single object instead of two.
Oogst
04-07-2006, 07:06 PM
OK, that's clear, thanks for the quick answer!

I am trying to create my own taper-like object now, but creating a target-object does not seem to work right now. I have a couple of problems with it.

This is what I have right now:

plugin Helper PBSpawnTarget
name:"PBSpawnTarget"
classId:#(0x23a5b32, 0x6dab7c30)
extends:Point
replaceUI:true
(
parameters main
(
creator type:#node
)
)

plugin Helper PBSpawner
name:"PBSpawner"
classId:#(0x1c772150, 0x41fe57f6)
category:"PaintBall"
extends:SphereGizmo
replaceUI:true
(
parameters main
(
target type:#node
)
tool create
(
on mousePoint click do
(
nodeTM.translation = gridPoint
delegate.radius = 1
target = PBSpawnTarget()
target.delegate.size = 1.4
target.creator = this
in coordsys grid move target gridPoint
#stop
)
)
)

The line "target.creator = this" is not allowed, for 3dsmax tells me PBSpawner is not a node. How can I give the PBSpawnTarget a pointer to the PBSpawner?

So I removed this line and tried again. 3dsmax does not give an error now, but when I select the PBSpawner and ask for $.target, 3dsmax tells me it is undefined. Why is it not set by this line: "target = PBSpawnTarget()"?

I think both of these problems come from the special state an object is in during its creation, but I do not see how to fix this.

Thanks in advance!
Oogst
04-10-2006, 09:23 AM
Does no one have a clue what I am doing wrong here?
Oogst
04-10-2006, 07:34 PM
Ah, I found out what the problem was: I used a parameter called "target" in the plug-in, which is a word that already has a meaning in MAXscript. Changing this name to "targetObject" fixed the problem. :)
CGTalk Moderation
04-10-2006, 07:34 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.