Stuck on Parsing Scene

[dotty92]

Hi,

The past couple of months I have had an issue when sending of a render and it stays on parsing scene - however once I click back on the render viewport it starts rendering fine. So for example, if I hit render and I have a another window on top (whether it's a file explorer or web browser etc) it will carry on parsing scene until I click back on Max. This has never been an issue before - it's especially annoying when sending off a batch render over night and then see it's been parsing the same camera over night, but once I click on the max file it instantly renders fine (I know it's not an issue with the file size, as when I send off a single render and I'm by my PC it renders fine).

Hope this makes sense and if anyone has found a solution to this problem?

[GeorgeK]

Hi,

The past couple of months I have had an issue when sending of a render and it stays on parsing scene - however once I click back on the render viewport it starts rendering fine. So for example, if I hit render and I have a another window on top (whether it's a file explorer or web browser etc) it will carry on parsing scene until I click back on Max. This has never been an issue before - it's especially annoying when sending off a batch render over night and then see it's been parsing the same camera over night, but once I click on the max file it instantly renders fine (I know it's not an issue with the file size, as when I send off a single render and I'm by my PC it renders fine).

Hope this makes sense and if anyone has found a solution to this problem?

Hi, we are aware of this issue and it is being looked into. Can you please clarify if you are using any remote desktop application, or any render manager to submit the jobs?

(Report ID=CRMAX-1135)

[dotty92]

Thanks for the response.

I have been using Parsec to remote log in. Could this be causing it? Or could it be a Corona 7 issue? (As I've been using remote logging in for the past two years, and only noticed it since upgrading to Corona 7)

[Stan_Bates]

Hi, just joining in the conversation and very keen to follow up on this issue.

This is happening within the company I work with and on multiple machines since Corona 7 and now 8 as well.
When I start a production render it will stay stuck in "parsing scene" forever until I click on the "framebuffer to bring it to the top.

It happens both when I work on the machine itself and remotely.

Regards,
Stan

[GeorgeK]

Hi everyone, we have reports that the issue can possibly get fixed after a windows update, even internally, while we were able to reproduce this initially now it's not possible any more. Can you please make sure you have updated your windows for both server and nodes and try again?

[Stan_Bates]

I just updated windows and am able to recreate the issue. (it did take me 3 attempts.)
This scene usually starts rendering immediately. I left it for 6 minutes and it was still parsing scene. The second image is when I click on the framebuffer and it immediately moves on to render.
In this instance i clicked render and alt-tab to do some browsing on chrome so max is in the background.

[GeorgeK]

I just updated windows and am able to recreate the issue. (it did take me 3 attempts.)
This scene usually starts rendering immediately. I left it for 6 minutes and it was still parsing scene. The second image is when I click on the framebuffer and it immediately moves on to render.
In this instance i clicked render and alt-tab to do some browsing on chrome so max is in the background.

Unfortunate, can you please clarify what the corona error log posted?

[Frankienov]

Im still having this problem when after i updated the windows . After i click on the framebuffer it will render for a couplemof minutes then will stop again.

[Stan_Bates]

Unfortunate, can you please clarify what the corona error log posted?

Only errors about normal maps using the incorrect gamma. 20 of them.

[arhitoma]

Having the same issue from time to for years now, I stumbled on it once again while working on 900 frames animation.
So I started trying all the basics and found the workaround that is working for now..
It looks like it's the Windows thing (combined with Corona or Max issues probably...)
When the render is started at first frame, I hit the Windows button + D (show the desktop) and from there I continue working on my Pc, not getting back to the 3Ds Max instance that renders.
I just monitor if the program is working by monitoring it through the Task Menager.
After switching to it from time to time, I just repeat the procedure.
So far it's working for me.
Maybe someone smart can figure out what is causing this?