Page MenuHome

2.8 Follow Path bug
Closed, ResolvedPublic


System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: Quadro K620/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 386.01

Blender Version
Broken: version: 2.80 (sub 48), branch: master, commit date: 2019-03-13 19:14, hash: rBbbc3ee09e44b
Worked: (optional)

Short description of error


When I did the same thing at 2.79
Objects will not have an offset

Exact steps for others to reproduce the error
ctrl+P > Follow Path
......Abnormal offset

Event Timeline

我都是用 google 的翻譯
My native language is Traditional Chinese.
I use google's translation
If there is something unclear, or misunderstanding in translation
Please also bear

Seems dependent on state of the 'Follow' check box:

  • selected v2.79 OK, v2.8 broken
  • unselected v2.79 broken, v2.8 OK

Tbh I don't even see why we should keep this feature at all. For many years we have had a constraints system for this kind of thing.

This is one of the features that is a remnant from before we had constraints inside Blender.

@Campbell Barton (campbellbarton) What do you think? Is there a reason we've kept this around?

Think we could remove, check w/ other devs & guys in the studio?

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 50.Mar 15 2019, 11:43 AM

I am against REMOVAL of features at bcon3. Might consider REPLACING them, with proper do-versioning.

To me it doesn't seem to be an issue with "Follow" option. It appears to be working correct to me. What doesn't appear correct to me is the calculation of an inverse parent matrix (which sound similar to T60623).

To me it doesn't seem to be an issue with "Follow" option. It appears to be working correct to me.

Yes, I only listed cases where the initial offset (this bug) appears.

Seems indeed very similar to T60623.
This time the flag on the evaluated curve CU_FOLLOW is no set, leading to a different behaviour in ob_parcurve()

(possible) fix incoming...