Maya 2022.3 Crashing On Second Render

[thebizon]

Hi guys,

I'm a student new to Maya and I'm having a strange issue occur. I am able to Arnold render an image of my model and everything works fine (except it always leaves the last rendering square somewhere on the image, but that's another issue), but when I try to re-render, Maya crashes every single time, without fail. No error message pops up, and no report that I'm aware of is sent to Autodesk.

Any ideas as to what's going on, or suggestions on how to fix the problem would be most appreciated.

Thanks in advance,

James

[polarOz]

Same problem

[valentin-rosset]

Downgrading to 2022.1 seems to have worked for me ( maya crashed after 2 frames before on 2022.3 ).

It would be nice to have the last stable release suggested when downloading maya, instead of downloading a broken version and getting headaches trying to find a solution.

[wstoutB7RGT]

We are having this trouble as well. 
The one thing I see in the render log is that the tx files say BROKEN.

00:01:32 2418MB | Image file statistics:
00:01:32 2418MB | opens tiles MB read --redundant-- I/O time res File
00:01:32 2418MB | BROKEN C:/Users/wstout/Downloads/2022_1_28_Room_HW_Mustain/2022_1_28_Room_HW_Mustain/sourceimages/Chair_Texture.jpeg
00:01:32 2418MB | 2 1 22 0.5 0.0s 275x 183x3.f16 C:/Users/wstout/Downloads/2022_1_28_Room_HW_Mustain/2022_1_28_Room_HW_Mustain/sourceimages/Chair_Texture.tx MIP-COUNT[8,6,2,1,1,1,1,1,1]
00:01:32 2418MB | BROKEN C:/Users/wstout/Downloads/2022_1_28_Room_HW_Mustain/2022_1_28_Room_HW_Mustain/sourceimages/Coffe_Table_Base_Hw_Texture.jpg
00:01:32 2418MB | 4 1 6 0.1 0.0s 1024x 768x3.f16 C:/Users/wstout/Downloads/2022_1_28_Room_HW_Mustain/2022_1_28_Room_HW_Mustain/sourceimages/Coffe_Table_Base_Hw_Texture.tx MIP-COUNT[0,0,0,0,0,1,1,1,1,1,1]
00:01:32 2418MB | BROKEN C:/Users/wstout/Downloads/2022_1_28_Room_HW_Mustain/2022_1_28_Room_HW_Mustain/sourceimages/Inclass_couch_texture.jpg
00:01:32 2418MB | 6 1 10 0.2 0.0s 800x 800x3.f16 C:/Users/wstout/Downloads/2022_1_28_Room_HW_Mustain/2022_1_28_Room_HW_Mustain/sourceimages/Inclass_couch_texture.tx MIP-COUNT[0,0,1,3,1,1,1,1,1,1]
00:01:32 2418MB | BROKEN

[Semple007]

why hasn't this been picked up by Autodesk yet?
It's a terrible bug for such an important feature 😕

[Stephen.Blair]

---

@Semple007 wrote:

why hasn't this been picked up by Autodesk yet?
It's a terrible bug for such an important feature 😕

---

Please post Arnold logs for the frames, and if possible, a scene that reproduces the problem.

So far, every scene I've got from a user has rendered without crashing. Some times there was just one thing to change. Sometimes nothing to change.

[Semple007]

thanks for your reply Stephen.
atm I have to hit a deadline, so best fix is to do  a roll back (and that works)
When I am finished  I will do a test and share the Arnold logs

cheers,

[julietta.zamoralam]

I am experiencing the exact same problem currently!! Such a shame that this is an issue. I'll try switching to 2022.1 but hopefully they fix this. I was worried my machine was causing issues, switched machines, same thing happened. So odd that it happens so consistently when trying to render a second time.

[Timmy88]

I've the some problem too . I'm using backburner and Redshift. 2022.1 is working just fine for me .... Where're the Autodesk officer ? it's shame .

[simondebrun]

Just upgraded to 2022.3 today. Having this same issue. Fails on the second Arnold render.

Seems like I'll have to roll back a version. Doesn't fail on simple test scenes. Fails on a project scene (automotive). Diagnostic logs look fine. Normal, no difference. 

[simondebrun]

2022.2 working fine

[ctedin3]

This is by no means a solution, but I did find that I can render sequences in 2023... I think they stabilized some things in this release.

[simondebrun]

Great to hear it's getting under control again. I'll look forward to trying 2023.

I'll probably stick with 2022.2 for this project. 

[kaanbizer]

Download Maya version 2023 that recently came out. It solved this issue. I was literally going to go nuts over this. Hope this helps lol. 

[iamhacklife]

Bravo! Autodesk, we pay money for your product, and it crashes when rendering itself with Arnold, there is no solution, and you stupidly ignore the questions of users, when will you start working on the money you take from people? what a shame