Camera render failed at specific position or high output resolution

[futengda]

I am developing a feature for programmatically placing camera positions. Strangely, I found that when the camera appears at specific angles, the rendering fails and throws a "Known system exception":

```log

-- Known system exception
-- Desc: EXCEPTION_ACCESS_VIOLATION The thread tried to read from or write to a virtual address for which it does not have the appropriate access.

```

I have test on Max2023 and Max2020, both of them have the same issue. 

The AI spam filter always deletes my posts, so I have to split them into several parts to post.

[futengda]

The AI spam filter always deletes my posts, so I have to split them into several parts to post.

part1

Here are some test cases based on the attached max file(3 camera):

• camera1：the origin issue camera [853.087463,853.087402,696.542969]
• camera2: move a lot from origin camera1's position [853.087463,853.087402,19.429382], 
  
• camera1ReduceFloatPrecision: same with camera1 but reduce precision [853.086975,853.086975,696.543030]
  it's position was set using copied text like this, not directly using the variable:

[futengda]

part2

So, the test results are:

Displaying only $some-complex-object:

1. Rendering fails: `render camera:$camera1 outputsize: [1024,1024]`

2. Rendering succeeds: `render camera:$camera1 outputsize: [512,512]`

3. Rendering succeeds: `render camera:$camera2 outputsize: [1024,1024]`

4. Rendering succeeds: `render camera:$camera1ReduceFloatPrecision outputsize: [1024,1024]`

Displaying only $some-simple-object:

5. Rendering succeeds: `render camera:$camera1 outputsize: [1024,1024]`

So, it is very strange that the failure seems to be related to the camera position, the rendering resolution, the complexity of the rendered object, and even the float precision. 

System Info:

1. Max 2023.3.4
2. Windows11
3. 16GB RAM
4. i5-11260H @ 2.60GHz 2.61 GHz
5. GPU1: Intel(R) UHD Graphics
6. GPU2: NVIDIA RTX3050 Laptop (latest driver)

[denisT.MaxDoctor]

If you want as many people as possible to help you, save the example scene in the most commonly used version—probably 2020 today. But hey, if it's a topic for a select few, go ahead and save the scene in the 2025 version.

[futengda]

Okay, I have uploaded the 2023 and 2020 versions of the max files.

[denisT.MaxDoctor · Accepted solution]

Yes, I can confirm that the render from camera1 is not working.

Well... but what's the problem? Call it an “unexplained non-anthropogenic phenomenon”, mod the camera a bit, and forget about it...

ooh... "mod the camera a bit, and forget about it..." sounds like lyrics. 😊👍

[futengda]

Haha, this is somewhat inelegant. For now, I have to manually reduce the floating-point precision to temporarily bypass this issue.

[denisT.MaxDoctor]

Inelegant? Inelegant is when, after a month of investigation, you are fired for not doing your job. 😜

[futengda]

Haha, you are right. Let's leave this issue here. I hope it will be helpful to others.