Parenting an info_target to a cube
I have parented a info_target to a cube, but the info target isn't moving when I move the cube. I have tried turning it into a prop_dynamic, it still didn't work, then I tried having it be a prop dynamic with a visible model, it worked, tried it with an invisible model, it didn't work, and the info_target seems to make all models invisible. What do I do, since I don't want the info target to have a model.
Thank You,
Sound Logic
Make sure the Always transmit, ignore PVS box is checked. That makes info_targets randomly not work sometimes.
It still isn't working. Not sure what is up. Should I upload my vmf?
Thank You,
Sound Logic
The info_target is a point entity usually made for another entity to reference it. Of course it is going to be invisible when being parented to the cube.
Why don't you parent a visible brush entity (or a visible model entity) to the info_target which is parented to the cube and see if its working.
The info target is moving, it would appear that the problem is in the constraint system. I am disabling it when the cube is moving, and when it is enabled, it tries to move it back to the start location. Any idea why this is occurring?
Why is it nessary to even parent the info_target to the prop_weighted_cube?
VDC User PageI'm assuming from this: post41285.html#p41285
Actually no chickenmobile. That system is working. The setup I am working on now is a cube that can only be moved when it is picked up. I have a constraint system that constrains the cube to the info target when it isn't picked up so that the cube doesn't move. When it is picked up the constraint is turned off. However, despite the fact that the info target is moving with the cube, when I let go of the cube, it snaps back to its starting location.
Thank You,
Sound Logic
So what's going back? the info_target?
You are probably making things a lot more complicated than they are. First of all, if the info_target is not doing what you want, try something else. If a point entity isn't parenting when you disable it, then try disabling a relay that the constraint system will refer to. Also I don't see how a cube can move much without the player picking it up in the first place either (unless you are talking about a sphere).
I would also look at another input called "disablemotion" (OnPlayerPickup, !self addoutput enablemotion). I'm pretty sure that a cube will have this input because all physics objects have this input.
Also please try not to be so vague, explain in detail so we can describe the best possible solution instead of trying very hard to fix a very complicated problem.
Sorry if I am communicating less than ideally. The enabling and disabling of motion is exactly what I am going for. The point entity is being parented, but the constraint doesn't seem to be updating or something like that. The cube doesn't seem to have a disable/enable motion input. The goal is to make a cube that can be placed anywhere (including in mid air) and will stay there regardless of forces acting on it. For DND players it would be an immovable rod. The current set up is thus:
The info target is parented to the cube
There is a constraint attaching the cube to the info target
When the cube is picked up the constraint is turned off
When the cube is dropped the constraint is turned on
The info target is moving, but the entire system is being snapped back to the start location when I let go. The constraint doesn't seem to understand that the info target has moved.
Thank You for your patience,
Sound Logic