Downloaded new Benchmark 1.0.7...... and.......

V-Ray V-Ray for 3ds Max Issues
1

… I had to press enter around 20 times to ‘read’ through the Eula Agreement ?

…then the Command Line Interface went ahead and tested both my CPU, then GPU, then immediately closed itself…

2

exact same experience here. not sure how to check my performance against the rest?

3

Me too. Maybe I’ll try again when I have a chance to read through instructions…assuming there are some.

4

I just downloaded it, too and it seems there may be some kind of misunderstanding or mislabeling? It#s definitely commandline-only and not the GUI version as it was the last time. Or maybe one has to start the commandline version with a GUI parameter for ultimate confusion purposes?

5

V-Ray Benchmarks, when used command-line, should be used with arguments according to your preferences. There are instructions in the docs - V-Ray Benchmark
Also - list of available options is presented with -help (or -h switch).

6

Weird problems you seem to have, guys, it works fine here !

7

Sorry for the misconfusion! Currently default version is console one and we’ll switch it to be GUI for Windows.
You could download GUI version here: https://download.chaosgroup.com/downloads/5145/vraybenchmark-standalone-107-free

8

Yeah. I was confused as hell. Extremely long ULA, test running, closed on its own, uhhh.. did I just install something?

9

Would love a more user friendly way to dump this to a logfile, just appending the date and time and benchmark.

Would be good to be able to note when slaves have software or hardware issues that crop up.

Right now if you upload the benchmark to Chaos you see fractions of a second, but I can’t see that fine detail anytime else - is there a local logfile?

PS: using this currently to output to file:

C:\Apps\vraybench_1.0.7_win_x64-cli.exe --quiet --mode=cpu > C:\Apps\output.txt

10

hm, GUI version should not close by itself. In what moment it closes?

11

Here you could see more info about debugging:
https://forums.chaosgroup.com/forum/…343#post833343

Basically you need to add “-debug=2” option and expect a log file in “%TEMP%/V-Ray Benchmark” folder.

12

Hi Varosi,

thanks for that, doesn’t seem to work for me:

C:\Apps>C:\Apps\vraybench_1.0.7_win_x64-cli.exe --debug=2 --mode=cpu
Installer debug log file:
        C:\Users\x\AppData\Local\Temp\installer_debug_2018_01_25_13_12.log
[V-Ray Benchmark 1.0.7]
Unknown command line arguments:
debug