Cruise altitude porpoising

[CheckRide1341]

Aircraft Version

Development

Build info

{
    "built": "2024-10-31T14:33:02+00:00",
    "ref": "refs/tags/v0.12.0",
    "sha": "f26029363ad3edeeafbed20aa79c13b32c8090f8",
    "actor": "FoxtrotSierra6829",
    "event_name": "manual",
    "pretty_release_name": "stable/v0.12.0",
    "version": "a380x-v0.12.0-HEAD.f260293"
}

Describe the bug

My initial cruise altitude was FL370 for about an hour then (didnt notice the porpoising then but I also wasnt directly looking for it) stepped up to FL410 and I've been there for 4 ish hours now, and began to see the V/S needle move slowly up and down maybe an hour after I got to FL410, nothing super super bad, but a little bit of it chasing after the cruise altitude, I followed SOPs and everything so I doubt its user error, though knowing my luck it might be. I haven't seen the needle move much more than +/- 500 fpm but I will continue to monitor it since I have another 3 or so hours in the flight

Expected behavior

talking with Straks on the FBW Discord A380 chat and he said it shouldnt be there expected behavior is to maintain the flight level

Steps to reproduce

1. perform normal SOPs cold & Dark to cruise
2. monitor V/S needle on the capt. PFD

remarks: Alts I was at before seeing the anomally: FL370 Step up to FL410, unknown what time after the anomaly happens. needle should slowly move up and down +/- a couple hundred FPM, nothing experienced more than +/- 500 FPM. no major effect on the flight.

References (optional)

https://github.com/user-attachments/assets/6e45bec0-d12b-447f-b843-ee47aec81f2b

Additional info (optional)

nothing major, just a little "huh thats funny" thing.

Discord Username (optional)

shadowride1341

[CheckRide1341]

hit top of descent, the altitude chasing was there, still not anything over +/- 500 FPM

[Stucun84]

Same version, same issue, +/- 400/500fpm porpoising at CRZ FL