Another AlignPosition issue (feels like I run into issues frequently with these guys…)
I have an object that I am trying to move to be in front of my character. I want this object to be somewhat loose (so that it may rotate freely and collide with objects that can mess up its trajectory).
This is fine… Provided you wait a solid 30 or so seconds. The AlignPosition object has the right position, but the object does not move for a long time, regardless of whatever parameters it has. I can set this thing to have a gazillion in max force, velocity, 200 in responsiveness, or nada in all three, nothing changes. Size of the object does not matter, neither does mass.
Does anyone know why this is occurring? I will attach a video, a studio file, and the script itself (ignore the terrible naming conventions and conventions in general - this is just me messing around for a lackluster prototype).
PositionPart - An invisible part in from of your character (Welded to the HRP)
UniversalPart - Another invisible part that is connected to the PositionPart with a UniversalConstraint. Add a WeldConstraint and set Part1 to the UniversalPart.
Now, clone your Object and position it to the UniversalPart CFrame. Connect it to the Part0 of the WeldConstraint.
The Object will rotate freely as you move around.
If you want other movements you can try out other Constraints. Like maybe an invisible rope!
I’m not quite sure this would achieve my longterm goal with this system. Yes, it would be nice for the rotation, but it would unfortunately fail in other goals → like the “looseness” of interaction.
For example, here’s this video (again, I had to wait for anything to happen):
(This is intended behavior that I’d like to keep, for clarification)
I have reviewed that video and while it is useful, it still does not explain what is wrong with my initial code.
Imagine that I port this prototype to a more functional system with other components added to it. I would really like to know what is causing the issue instead of relying off of example code, especially if it bugs out again. In my eyes, my script does something relatively similar to their video (give or take some portions), and therefore is not very useful in diagnosis.
I understand if this may come off as a little unnecessary or ignorant, but I simply just wish to learn more about this issue.
Network Ownership is the behavior in which Roblox allocates physics calculations. If a block is not “owned” by a client, its calculated on the server until the server determines if it should be calculated by a client, typically by using distance and recognizing attachments and physics – which is slow and causes rubberbanding in unusual circumstances. This is an unusual circumstance. Set the block’s network owner via the example above to the player who is taking control of it. This is required to be done on the server.
also, your code is really messy, consider cleaning it up, and the way its doing any checks cause some latency of its own, but the actual physics latency youve been experience is fixed with the above.