3DsMax2017 Vray3.5 rrKSO... something is going on

[Thomas Volkmann]

Hi,

our clients crash when rendering 3DsMax2017 Vray3.5 using the kso config vray-s

. 

Would probably be easy to track down when it was just like this, but here is the thing:

1. Clients running Windows7 never crash (all others running win10 are crashing)

2. Some existing scenes don't crash (a fresh scene with cube,cam,light always crashes)

3. Not using the kso config doesn't crash

4. No problems with Max2016 using the same submitter and config files

So, where lies the problem here?

The log result from a crashing machine:

R 69| |' 11:10.17 rrMax - DBG: executing render vfb: false frame: 150 renderType: #normal
R 70|
R 71| >"C:\Program Files\rrService\lc64\rrCheckexitcode.exe" 0 0 0 150 3dsmax.exe
R 72| |
R 73| | Error executing render script!
R 74| |-- Runtime error:
R 75| |Traceback (most recent call last):
R 76| | File "C:\RR_localdata\renderscripts\kso_3dsmax.py", line 556, in <render_KSO>
R 77| | File "C:\RR_localdata\renderscripts\kso_3dsmax.py", line 550, in <rrKSOStartServer>
R 78| | File "<string>", line 1, in <<module>>
R 79| | File "C:\RR_localdata\renderscripts\kso_3dsmax.py", line 509, in <ksoRenderFrame>
R 80| | File "C:\RR_localdata\renderscripts\kso_3dsmax.py", line 494, in <render_frame>
R 81| | File "C:\Program Files\Autodesk\3ds Max 2017\MaxPlus.py", line 37370, in <EvalMAXScript>
R 82| |RuntimeError: MAXScript evaluation failed

and further down:

C 0| ************************* LOCAL RENDER INFORMATION *************************
C 1| Total render files found: 1
C 2| Files successful copied: 0
C 3| Files broken/not copied: 1
C 4| Total render files found (main pass only): 0
C 5| List of files: (C=copied R=successfully read X=Exr cropped F=image verify failed V=rrViewer cache created) FileSize CopySpeed
C 6| 150 + : 0B \_render\3D\max_rrTest\2016to2017_2xxx.RGB_color.0150.exr
C 7| ************************* CLIENT REPORTS DURING THIS RENDER *************************
C 8| ******Message/dialog box 40*** found: ***prc: '3DSMAX.EXE' Class: 'wxWindowNR' Title: 'V-Ray frame buffer - [100% of 640 x 480]' Controls: 'wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, '
C 9| Frame pre-processing time: 00.42 m.s
C 10| ******Message/dialog box 42*** found: ***prc: '3DSMAX.EXE' Class: 'wxWindowNR' Title: 'panel' Controls: 'wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, '
C 11| ******Message/dialog box 44*** found: ***prc: '3DSMAX.EXE' Class: 'wxWindowNR' Title: 'V-Ray Frame Buffer' Controls: 'wxWindowNR:panel, '
C 12| Handling window: '3DSMAX.EXE' ' Error' '' '|Can't create window of class wxWindowNR (error 1406: cannot create a top-level child window.)|' click on: 'Button'-'OK'
C 13| clicked OK
C 14| Error in this log file: | error executing render script!
C 15| Error in this log file: |-- runtime error:
C 16| Error in this log file (340): |runtimeerror: maxscript evaluation failed
C 17| Error in log this file: [2017/may/13|11:10:11] warning: 0 error(s), 3 warning(s)
C 18| Error in this log file: handling window: '3dsmax.exe' ' error' '' '|can't create window of class wxwindownr (error 1406: cannot create a top-level child window.)|' click on: 'button'-'ok'
C 19| Error found in this log

Compared to a non-crashing win7 machine:

R 97| ************************* CLIENT REPORTS DURING THIS RENDER *************************
R 98| ******Message/dialog box 10*** found: ***prc: '3DSMAX.EXE' Class: '#32770' Title: 'Command Panel' Controls: 'QWidget:3dsmax, '
R 99| ******Message/dialog box 40*** found: ***prc: '3DSMAX.EXE' Class: 'wxWindowNR' Title: 'V-Ray frame buffer - [100% of 640 x 480]' Controls: 'wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, '
R100| Frame pre-processing time: 01.40 m.s
R101| ******Message/dialog box 40*** found: ***prc: '3DSMAX.EXE' Class: 'wxWindowNR' Title: 'V-Ray frame buffer - [100% of 320 x 240]' Controls: 'wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, wxWindowNR:panel, '

I really have no Idea what's going on...

We are using the non-kso config now, which is fine for now.

[RR, Schoenberger]

Ok, so far the crash seems to be related to "Can't create window of class wxWindowNR".

And it crashes while it executes the render command.

 

We are still using VRay 3.4. I will update some machines and do some tests.

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

---

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of Thomas Volkmann
Sent: Saturday, May 13, 2017 12:39 PM
To: Royal Render Knights Tavern
Subject: [rrKnights] 3DsMax2017 Vray3.5 rrKSO... something is going on

--
If you reply, the message is send to the user group which is sufficient.
("Reply All" just sends the message twice to the last author which is not required)
---
You received this message because you are subscribed to the Google Groups "Royal Render Knights Tavern" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rrKnights+...@googlegroups.com.
Visit this group at https://groups.google.com/group/rrKnights.
For more options, visit https://groups.google.com/d/optout.

[RR, Schoenberger]

Hi

 

We have not yet found the issue.

Please check the vray log file (in rrControl named .._sep) for any "Error" (They are marked red).

[Thomas Volkmann]

If there is an error in the VrayLog it's this:

[2017/May/12|12:42:47] Preparing direct light manager.
[2017/May/12|12:42:47] Initializing built-in VFB.
[2017/May/12|12:42:48] error: UNHANDLED EXCEPTION: Rendering frame
Last marker is at ./src/vrayrenderer.cpp, line 3916: Preparing direct light manager

But other scenes show no errors in the Vray-log and still are crashing with the "Can't create window...."-error.

Have you been able to reproduce the crashing?

[RR, Schoenberger]

Hi

 

Yes, I got one scene that crashes.

VRay support is informed.

 

If I set sequence divide to 1/1, then it renders.

If I disable the VFB, then it renders as well.

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of Thomas Volkmann

Sent: Monday, May 22, 2017 7:16 PM

To: Royal Render Knights Tavern

Cc: schoen...@royalrender.de
Subject: Re: [rrKnights] 3DsMax2017 Vray3.5 rrKSO... something is going on

--

[RR, Schoenberger]

FYI: Chaosgroup support is still busy and was not able to check the issue yet.

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

---

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of RR, Schoenberger
Sent: Monday, May 22, 2017 8:17 PM
To: rrKn...@googlegroups.com
Subject: RE: [rrKnights] 3DsMax2017 Vray3.5 rrKSO... something is going on

[RR, Schoenberger]

Update: Still in contact with Chaosgroup.

[Thomas Volkmann]

Is there an update on this? Don't really know what I should look out for in the latest Vray bugfix release logs....

[RR, Schoenberger]

Hi

 

I checked last week and the reply was

“The issue is not yet resolved.

What we have found so far is that it doesn't occur on windows 7, maybe it is something related to windows also.

I'll remind our dev guys that you are waiting for those fix.”

 

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

 

Is there an update on this? Don't really know what I should look out for in the latest Vray bugfix release logs....

 

[Thomas Volkmann]

Do you have a ticket number for this?

We get crashes now on our newer machines which look similar as the kso related crashes, except the difference now is the graphicscard. Newer crash, older render. We are wondering if it has to do with the framebuffer changes that they introduced in 3.5....

[RR support, Schoenberger]

Hi

FYI: I wrote a little bit angry email to ChaosGroup 2 days ago that it
is not acceptable to wait that long time for a crash fix.

The chaosgroup ticket ID is [#749249].
The issue is that the second frame does not render (on windows 10).
But the first frames send to 3dsmax works.
Do you have the same issue?

By graphicscard related, do you mean machines with no (real/usable) GPU crash?


Holger Schönberger
Binary Alchemy - digital materialization

[Thomas Volkmann]

Do you have the same issue?

 

Not exactly, but similar. The last vray log entries are

[2017/Oct/13|10:40:06] Preparing global light manager.

[2017/Oct/13|10:40:06] Using 0.61 MB for adaptive lights buffer

[2017/Oct/13|10:40:06] Irradiance sample size is 84 bytes

[2017/Oct/13|10:40:06] Cannot use fast GI because secondary engine is not brute force or none

[2017/Oct/13|10:40:06] Broadcasting NOTIFY_PRE_RENDERFRAME.

I remember the light manager being at the end of the others crashes logs, too.

Other than that we just get the famous:  An unexpected exception

Not much to work with

By graphicscard related, do you mean machines with no (real/usable) GPU crash?

No, it's only 'newer' workstations that crash while the older ones render. All of these have real/usable GPUs. 

It was just a shot in the dark.

We're going to test 2018 now and see if that makes a difference (and hopefully switching to arnold)

[RR, Schoenberger]

Vray support just send this:

“We finally got to the bottom of it and as we expected this is a Windows issue.

In the latest version of Windows, Microsoft limited some service parameters and because of that V-Ray crashes when it tries to create VFB window for the second frame.

 

We found a way to workaround those limitations but we cannot guarantee that this solution would work fine if Microsoft deside to change that”

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of Thomas Volkmann
Sent: Monday, October 16, 2017 8:49 AM
To: Royal Render Knights Tavern <rrKn...@googlegroups.com>
Subject: Re: [rrKnights] 3DsMax2017 Vray3.5 rrKSO... something is going on

 

--

[RR, Schoenberger]

More information about the next official version with a fix:
„We are preparing now the next official service pack 3.60.04 that will have fix for that issue but we don't know when exactly it will be released.“

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

[Thomas Volkmann]

So the new 

VRAY_VFB_GUI=0

will work on the new VRay version when they release it someday soon?

[RR, Schoenberger]

Hi

 

Your issue with more than 1 frame was fixed with the vray release 3.60.04.

 

But we found another issue with a Windows 10 update last month.

And this crashes VRay every time it starts to render within a service.

 

About the second error, the message is from 16.11: „the issue has been resolved using the latest stable nightly and the env variable VRAY_VFB_GUI=0“

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

From: rrkn...@googlegroups.com [mailto:rrkn...@googlegroups.com] On Behalf Of Thomas Volkmann
Sent: Wednesday, November 22, 2017 12:06 PM
To: Royal Render Knights Tavern <rrKn...@googlegroups.com>
Subject: Re: [rrKnights] 3DsMax2017 Vray3.5 rrKSO... something is going on

 

So the new