Give the "I" in IPR some serious investigation and attention

V-Ray IPR in 3ds Max has been experiencing significant performance issues for a substantial number of users and this has been going on for years, across multiple versions of both V-Ray and 3ds Max.
Countless forum posts describe the same frustrating symptoms: sluggish viewport updates, poor responsiveness, and a general feeling that the renderer is fighting against the user rather than working with them. This is ironic for a tool that promises interactivity.
What makes this particularly difficult to address is that these reports almost always reach a dead end. No reliable reproduction case, no clearly identifiable root cause, no official acknowledgment. Users are left troubleshooting in the dark, and the threads fade away unresolved.
Some recurring suspects emerge from the community: AMD Ryzen processors, specific chipset driver versions, NUMA architecture behavior, or IRQ conflicts — but none of these have been officially corroborated or ruled out. The fact that the issue seems hardware-dependent makes it harder to reproduce in a controlled environment, but that is precisely why it warrants a dedicated, structured investigation from the development team.

V-Ray IPR is a flagship feature. It deserves to work reliably for everyone, not just users who happen to have the right hardware configuration. Please give this the attention it has long deserved.