Can you try playing around with the “responsiveness” and “max force” settings to see if you can get what you want with AlignPosition? It will automatically assign a damping constant that will be close to the number required for the system to be critcally damped. I’m pretty confident that this should cover 99% of use cases. If you need a system that is somehow noticably over/underdamped, using a AlignPosition or BodyPosition might not be the right approach for you.
You can DM me your placefile, I can take a look to see if anything isn’t working properly
At about October 17th, when I changed the Stepping Method from ‘Default’ to ‘Fixed’, the abnormal drop was gone and the subtle natural one was still there - this brought back the desired behaviour, fixing the issue!
Now (as of around 8/9 November) this subtle one is also gone, causing these new complications Some Test - 10 Nov.rbxl (73.4 KB)
In this placefile, the Sorcerer and a random NPC can be found. When playing, you used to be able to resist this force - essentially allowing the player to slowly push through, out of the range - instead of being stuck in one place.
Quoted from the previous message:
“I thought tweaking the Power, Damping and MaxForce would bring back the ability for the Player to resist this force, which after a lot of trying seemed to sort of work.
Something to the movement or force put towards it seemed off however. It felt as if the force wasn’t constant and that with every movement direction I took, I was able to manipulate the force to a point where sudden movements affected the force too much.”
The new behaviour appear identical on every Stepping Method. Perhaps one method could provide these new changes, whilst the other retains what the ‘Fixed’ method used to at 16/17th of October
It’s a month later and I’m still experiencing issues due to this new change.
The initial issue with the abnormal dropping/sinking was essentially fixed when on October 17th, I changed the PhysicsSteppingMethod to Fixed, thanks to RadioGamer’s helpful reply.
.
As of the changes November ~9th, the behaviour is left in a state where yes, the initial issue is gone, BUT another issue arose. I cannot alter between these methods at all to resolve this new issue as described in my previous messages.
Both the ‘Fixed’ and ‘Adaptive’ SteppingMethod result in the same BodyPosition physics.
Seeing how Adaptive is the new Default, it’d be great - and all issues would be fixed - if Adaptive continues with the new, current physics (~ November 9th) and Fixed kept the physics of how they used to be before this recent change.
If this may be done, the entire issue would be resolved and creators would have the option to pick between ‘Fixed’ Stepping and this new responsive ‘Adaptive’ method to better suit their work.
I still haven’t heard back on this and I’m still experiencing issues.
Feeling left in the dark as there hasn’t been a response on any of my messages regarding this newly arisen issue
Hey! Sorry for the late reply. I looked at the placefile you posted above but not sure what the procedure is to reproduce the issue. Lets start a DM so we can figure this out.
Ever since this DM was started, I haven’t heard anything back at all.
Sep. 14, '23
When initially getting this thread listed under Bug Reports I was optimistic about it getting attention and hopefully being resolved rather soon.
|
Sep. 15, '23
Being thanked for the report and told:
|
Oct. 13, '23
A ~month went by and no response…
|
Oct. 15, '23
Then Radiogamer comes out with a way (around it?) that fixes the issue. (thanks :D)
Case closed, right?
No.
|
Then, coincidentally the same day a staff response.
( mind it was fixed by now, despite some concerns and raised questions )
|
Nov. 9, '23
Issue… fixed?
…
Well, turns out this ‘fix’ did indeed fix the weakened power (again, this was already fixed by changing PhysicsSteppedMethod to ‘Fixed’…)
HOWEVER, it brought with it a new bug… So technically it fixed the problem, but as a result it created a new issue.
|
Nov. 10, '23
The day after the fix (that then broke something else) others and I who now face this newly create issue.
Being asked for the placefile, this was given the same day.
|
Nov. 28, '23
Nothing back yet.
|
Dec. 12, '23
Still nothing. “Suddenly no more responses?”
|
Jan. 11, '24
|
Mar. 28, '24
|
May. 1, '24
|
May. 14, '24
Finally a response half a year after seeming so involved in the matter back in November 2023.
Excited to finally hear back again, I eagerly respond the same day with a full explanation from beginning to end.
It’s been a year ever since this second issue started, and it’s tormented and troubled ever since.
Every time I open the DevForum again I’m hoping to finally see a response, but all I’m getting is:
I had hopes it’d finally started getting fixed as soon as I read this
It’s been half a year since and I’m feeling – just as I said back in January – left in the dark and forgotten about. It makes me regret sending a message ever after Radiogamer helped me out. “If only I hadn’t sent another message, then maybe it would’ve been done and fixed in October 2023.”
Thanks to their solution it worked again, but then the ‘proper/official’ fix came which broke something else
I don’t even know what to write at this point, as any call appears to get ignored and it seems that the issue will never be fixed.
@Hajimalago, would you please respond and help fix the issue at last, as again, the newly created bug as well as the thought of ‘being responsible for the second bug’ have been haunting me in my head ever since.
Unfortunately a single engineer cannot always champion the issue to completion, there’s a lot of competing priorities that a single engineer will end up facing, and they may simply not have time for an involved back-and-forth anymore. Not to mention, you’re the only one having a large issue, and there’s not really any code changes that need to happen on the Roblox side. In terms of value created versus time investment, you’re better helped by someone else.
You appear to have missed the point.
If there hadn’t been a ‘fix’ in the first place, Radiogamer’s solution would’ve solved it.
But since they did follow up, essentially causing a another problem to arrise and then go radio silent, leaving this in a broken state whilst still promising to figure it out. Not hearing back again feels like a broken promise - especially for something that wouldn’t have been necessary if it hadn’t been broken.
About these issues, I would highly suggest not to comment on it without properly reading up; my latest message in particular. If you had done so, you would’ve found this “summary of the remaining issues”.
That is a private DM. You are not helping yourself by being snarky. You’re not going to get further help from staff at this point without a new bug report. It’s clear this issue is out of scope of the original topic and has been dropped. Recommend having a little respect for the people who choose to engage with you, if there’s anything non staff can do to help mitigate your issues, they sure don’t want to try with a messy reply chain and that attitude.
