FIXED: Camera index limited to 0-15

Bugs
,
1

Continuing the discussion from FIXED: Render TOP Image Output + Multi-Camerax17 = Crash:

Thanks a lot for the quick fix in the new update! TD doesn’t crash anymore, but apperently the TDCameraIndex() is still limited to the magical number of 15 (takes values from 0-15). It actually behaves as if it’s take modulo 16. See example:

cameraIndexIssue.tox (1.9 KB)

Best,
Josef

2

Hi Josef,

Maybe this info is helpful Multi Camera render ( more than 100 ) - #6 by malcolm

3

Danke!

But is there a way to get the actual camera index?

4

It’s a missing piece of information right now. Currently the TDCameraIndex() is used to lookup into the uTDMats[] array, so it needs to be 0 based

5

I understand that it’s zero based and it should be. But it shouldn’t be taken modulo 16, I think.

6

We’ll need a new function for the value you want. Currently its the index within the current pass, as we can’t do all of the cameras at the same time. So we usually group them into batches of 16, but it may be something else.

7

Would it be possible to just get the batch number too?

8

Hmm, what would you do with the batch number?

9

TDTrueCameraIndex() will be available in the next build of the 2022 series we post.

1 Like
10

Awesome, thanks!