Bug: Use Project Frame Rate anomoly

[andymanaws]

Describe the bug

version 2025.3.3
Looks like ticking the 'Use Project Frame rate' box in the redshift render settings does not transfer the project frame rate to the deadline nodes.
Instead they will default to the 30fps.

Expected Behaviour

Use Project Frame rate should adhere to the frame rate.

Current Behaviour

Seems to not use the project frame rate - defaults to 30.

If you explicitly define Frame Rate in the Output setting, then it adheres to that.

Reproduction Steps

Submit a job with a frame rate not at 30, elect to use project frame and compare the result.

Environment

At minimum:

1. Operating system (e.g. Windows Server 2022; Amazon Linux 2023; etc.)
2. Version of Cinema 4D
3. Version of this package
4. If this is from a version installed by the Deadline Cloud Submitter installer, then what version of the submitter installer?

Please share other details about your environment that you think might be relevant to reproducing the bug.

[karthikbekalp]

Thanks for raising this issue.
I believe this could be because we don't send or set this parameter at the adaptor side.

To fix the issue we would have to do the following:

1. Check our assumption that regardless of the frame rate defined in the render setting, the adaptor defaults to 30 FPS. Maybe we can use the doc.GetFPS() to check that in the adaptor?
   1. Are all the render settings (not just FPS) somehow also getting set to a default? If so we would have to fix that.
2. Once we have confirmed above, we should send this value from the submitter in init data similar to other settings and set this value at the adaptor. The setting seems to be named RDATA_FRAMERATE according to https://developers.maxon.net/docs/py/2024_2_0/modules/c4d.documents/RenderData/index.html

[karthikbekalp]

As this issue is fixed by the above PR, I'm closing this ticket.