Slower and buggy

[frodopytlicek]

Has V-Ray become slower and more buggy than it used to be? Or am I more demanding? :/ Have anyone similar experience?

[Mr.Mxyzptlk]

Has V-Ray become slower and more buggy than it used to be? Or am I more demanding? :/ Have anyone similar experience?

VRay is in a great place right now. Better than ever. Maybe if you can explain what you are experiencing it might be helpful?

[frodopytlicek]

Its not that easy to explain its more like feeling, I dont know... so much bugs especialy in vray for 3ds max. I just want to know is anyone else have same feeling.

[glorybound]

I am not having any issues. It is rock solid as it has always been for me.

[Joelaff]

For me the big bugs are with standalone. Been trying to report all I can, but there are a ton of little inconsistencies and gotchas that make working with standalone difficult, especially once you start adding render elements, which we can’t do without. Why bother? Because cloud rendering is about 1/5th the cost on Linux thanks to the Microsoft tax.

Vray inside Max has been pretty stable. There is still the risk of crashing when making big changes with IPR open in a complex scene.

[^Lele^]

Its not that easy to explain its more like feeling, I dont know... so much bugs especialy in vray for 3ds max. I just want to know is anyone else have same feeling.

I usually run my Max *extra* lean: most of the work i do has to do with V-Ray exclusively, and so that's what i generally install as plugins.
Unless needed, I'll install max without any addon (civil view/substance, etc etc), and will not install *any* other plugin unless specifically required.
When V-Ray runs alone in a lean Max, my startups are quick (i mean to first active click in the viewport.), Max is responsive, there is never any undue delay, no matter the scene size.

Of late, i have my Max install going the very other way, as i have to process client scenes for conversion to standalone and the AutoMSR project, and as a consequence i am installing nigh any plugin under the sun.
My startup time is about three-fold (again, i speak of after the splash screen is gone.), the number and extent of delays, slowdowns, single-core CPU blasting for no apparent reason and other such annoyances is often overwhelming.

With this, i do not mean to discount us from being part of the problem, mind you, but the way Max is built, as a plugin container, invites the kind of hobbling behaviour that's often experienced by users: there is a *lot* of background messaging that goes on in Max as a result of most user interaction, and those avenues can get well clogged by more than one plugin trying to use them.

F.e., if you go and type "callbacks.show()" in the maxscript listener, you'll see there are dozens of PhysX callbacks (i.e. always active, reactive watchers to the scene).
A callback could be "when the user selects a node of class sphere, print this line into the listener", or as it's the case for the physX ones, if a specific node is deleted, re-evaluate the node list.
When and how those will fire is hard to fathom without looking at the code, and the callbacks approach is used far and wide, and often impossible to avoid.

Besides these, which can be somehow witnessed from the Max side, there are unfathomables in code as well: years ago i built an Arnold translator for internal use, and when i tried and convert 10000 lights in a test scene, the background messaging in Max would mean that *after* the node translation was completed, Max would hang for -brace for it- 10 hours of single-core activity, without returning user control. Skipping the background message-passing would finish the conversion instantly, but sadly the converted lights wouldn't be recognised as such.
I expect these issues to have been mitigated in the while, but I offer them as a form of insight into the inner workings of Max, for which we can do little.

This said, if there is some specific combo that is giving you issues, and it's reproducible (even just on your side), do let us know. Tech support can -with your permission- connect for remote sessions to check -live- the environment you're working in.

[Vizioen]

Is it Max acting slow and buggy or V-Ray though? As Lele said: Vanilla 3DsMax runs quite smooth, untill you install a couple of plugins and then it just runs as it would 10 years ago on an older workstation.

Which plugins do you have installed? Also which 3ds Max version are you running?

[Joelaff]

What I want to know is why, even on a 96 core 7995wx, can multiple copies of Max still slow down? They must be pinning certain threads to processor 0 or something ignorant. I just don’t get how you can have a bunch of apps open with no problem, but start using two or three copies of Max and things slow down. Minimizing the other copies solves most, but not all of it.

Maybe some viewport refinement settings or some such. I don’t care about the viewport. Always looks like crap anyway.

[^Lele^]

What I want to know is why, even on a 96 core 7995wx, can multiple copies of Max still slow down? They must be pinning certain threads to processor 0 or something ignorant. I just don’t get how you can have a bunch of apps open with no problem, but start using two or three copies of Max and things slow down. Minimizing the other copies solves most, but not all of it.

Maybe some viewport refinement settings or some such. I don’t care about the viewport. Always looks like crap anyway.

Try running it in the older graphics mode, like LegacyD3D, from the specific startup link.
If you think it's Nitrous playing up, running it as Legacy ought to show some difference in behaviour.
Fair warning: you may not be able to open big scenes that way and/or performance may be super degraded.
Further, you won't have access to in-viewport IPR.
The mode has been legacied for good reasons.