Philipp Oeser
457cccd964
Fix #139782 : USD MeshSequenceCache modifier using the wrong frame
...
It would run into using the same frame twice, looking like "freeze
frames"
Apparently we had a similar issue before, see 3f8ec963e3
Just a PoC to show that this looks like a precision/rounding issue when
getting a "working" `UsdTimeCode`.
In the modifier code, we are doing a roundtrip going from frame >> time
(in seconds -- via `BKE_cachefile_time_offset`) and then back to frame
before we store that in `USDMeshReadParams`.
To avoid the precision loss, this PR introduces
`BKE_cachefile_frame_offset` to stay in the "frame" domain and
circumvent going through FPS alltogether.
There might be better ways to let USD handle the "sightly off"
`UsdTimeCode` better though.
Pull Request: https://projects.blender.org/blender/blender/pulls/139793
2025-06-04 11:04:37 +02:00
..
2025-05-02 15:08:29 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-13 17:27:30 +02:00
2025-05-20 17:32:49 +02:00
2025-06-02 17:13:56 -04:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-13 17:27:30 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-06-02 17:13:56 -04:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-06-02 17:13:56 -04:00
2024-11-05 16:35:16 +01:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-23 14:03:20 +10:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-23 01:07:12 +02:00
2025-05-20 17:32:49 +02:00
2025-05-13 17:27:30 +02:00
2025-01-31 17:03:17 +01:00
2024-08-23 13:09:20 +10:00
2025-01-31 17:03:17 +01:00
2025-01-07 12:39:13 +01:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-06-04 11:04:37 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-06-02 13:50:07 +02:00
2025-01-31 17:03:17 +01:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-01-31 17:03:17 +01:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-13 17:27:30 +02:00
2025-04-21 17:59:41 +02:00
2025-03-12 15:43:33 +01:00
2025-01-07 12:39:13 +01:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-28 14:38:54 +02:00
2025-05-13 17:27:30 +02:00
2025-02-12 23:01:08 +01:00
2023-09-22 03:18:17 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-13 17:27:30 +02:00
2025-05-13 17:27:30 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-08 20:45:37 +02:00
2025-01-07 12:39:13 +01:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00
2025-05-20 17:32:49 +02:00