Also experiencing the parsing bug, sometimes will just hang there until I click the render window. Corona 7, don't know if that helps anything.
3Ds Max 2022.3
Corona 7 hotfix 1
Pulze Scene Manager 2.1.0
No Forest Pack
I think I read somewhere else other people having issues with a render parsing continuously until you click in the framebuffer - think it was something to do with Pulze plugin, but can't find the thread again. Just wanted to say that this still happens in v8 RC1 and the pulze 2.2.6 beta build.
Hi, i don't have the pulze plugin and this happened to me yesterday on two servers with backburner, Corona latest build.
Thanks for sharing this, I'll add a few facts about how the parsing issue looks here:
- I don't know exactly when the issues started, I tried Max 2021, 2018, 2020, 2022 after abandoning 2016 finally. Same issue.
- It happens on various nodes with varying hardware/Windows versions and also on fully updated W10 boxes.
- FPP may be one cause of it but I had contact with Itoo support; they seem not to be aware of a possible parsing issue due to FPP. And if you activate debug logging for FFP, you see that the hang occurs after FPP has done its job and Corona takes over control.
- The hang happens only if rendering more than one frame at once. The first render after loading always succeeds:
- The hang does not happen if using material override
- A backburner job would render one frame, then changes to the next and halts at parsing the scene (and the process looks like this as mentioned)
- If I collect all assets into a single directory: no issues.
- And to make it board compatible: using corona 8 doesn't change anything.
So I looked at a max process of a scene which always gets stuck with process monitor (not process explorer), seeing 3ds max register filechange callback notifications a lot of times (for every single used asset directory). Sooner or later there will be a "too many commands" response listed when trying to register a change callback which may lead to this blocking FileWatchCallback thread - and parsing is stuck.
It's my only lead in this issue. It would fit that using FFP is at least worsening the situation (many additional directories) and to the fact that it seems to work if assets are collected into a single directory and relinked - or using material override.
Good Luck
Hi Everyone,
Thanks for reporting this issue to us, it is a nightmare to debug as we are not able to reproduce it here in the office.
Can I ask that if you have a scene where you experience this, you send it over to me. As well as the hardware specification of the machine + Windows + Corona + Max versions (This is really important).
Can I also ask that when you do manage to reproduce this, can you capture a minidump during the time when parsing is frozen. This will give the devs some info on what has gone wrong and enable us to see where a problem may lie.
Instructions on how to obtain a minidump can be found in my signature. (Point 2 in How to report bugs).
Thanks for your cooperation in this, I know the bug is super annoying and I'd like to be able to get it fixed.
Rowan