Announcement

Collapse
No announcement yet.

3DS Max and Titan X

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 3DS Max and Titan X

    So I wanted to know if anyone else out there is rendering with Titan X and 3DS Max and if you have had a problem with the CUDA cards not being found. I have handled it with unchecking the "In-process RT Engine" which means that VRay RT GPU will work as a standalone at which point the Titan X reads just fine. I have checked with NVidia and they brought it up to Level 2 support and this is their latest reply:

    "At this point, we are trying to determine whether or not if the 3DSmax and iRay combination is supported on the TitanX. If we can get it to work here, then we know our GPU and CUDA is likely not the culprit. Hopefully we'll have test result in the next few days. "

    It says iRay because iRay can't find the cards inside of 3DS Max. I have even downloaded Arion plug-in for 3DS Max to test if it would read the cards, and again, no luck. I'm sure if I was to download Arion Standalone, just like VRay it would read them perfectly. Anyone else out there? I'll update as soon as I have an answer from Nvidia.

  • #2
    i use a titan x and it works flawlessly with 3dsmax and in-process RT cuda.

    Comment


    • #3
      Originally posted by super gnu View Post
      i use a titan x and it works flawlessly with 3dsmax and in-process RT cuda.
      Thanks! OK, so then I guess it is something in my computer, some incompatibility issue, perhaps with the hardware. You use the latest Driver for Titan X, right?

      Edit: The latest news from NVidia is that all drivers and cards work perfectly. I got with the vendor of my rig and they are in touch with Supermicro. It may be an issue with the motherboard or some driver from Supermicro and they are willing to replace the motherboard if it comes to that. Will update as needed.
      Last edited by padre.ayuso; 02-05-2016, 07:20 PM.

      Comment


      • #4
        http://forums.chaosgroup.com/showthr...enabled-device
        If it was that easy, it would have already been done

        Peter Matanov
        Chaos

        Comment


        • #5
          Thanks Peter, I use that workaround and I'm tracking, I think Tashko sent me that link a few weeks back. However, I'm trying to find the actual cause and it maybe a hardware issue. I want to post the solution on this thread once we find the reason and want to make it know what the issue was so as to prevent others to fall into the same mistake I made, whatever that mistake is.

          Comment


          • #6
            In the nVidia control panel, when you check the options for the 3dsmax.exe process, is it set to use all available GPUs as CUDA devices?

            Best regards,
            Vlado
            I only act like I know everything, Rogers.

            Comment


            • #7
              Originally posted by vlado View Post
              In the nVidia control panel, when you check the options for the 3dsmax.exe process, is it set to use all available GPUs as CUDA devices?

              Best regards,
              Vlado
              Hey Vlado,
              Yes it is. This is currently the weirdest thing ever. But I'm getting my last workstation and the company has agreed to verify against 3DS Max and not turn it over until the CUDAS are recognized, at which point they will implement the solution to my other two workstations. We have a feeling that it may be the SuperMicro motherboard, or some setting in the BIOS. If you do have any other ideas, please do let me know, I have tried many things, but who knows. As said earlier, VRay works beautiful when I check off "In Process RT engine" so we know that the cards are being recognized somewhere, just not by 3DS Max.

              Comment


              • #8
                Update and in case anyone else finds to have this problem.

                So it turns out that NVidia's Titan X works like a dream, but it would not show on my VRay Tab. The reason for this I guess is a bad driver from Nvidia, which it was, but which one. When buying a new machine and installing Titan X as your first card, you will install PhysX Driver for the first time. It seems that Titan X PhysX Driver is not fully compatible, and thus will cause this problem I had. The company putting my machine together, God Bless them, tried out everything and uninstalled and re-installed the drivers a dozen times until they found out that if you use DDU utility to remove all NVidia drivers, and then perform a clean install under Custom BUT don't install the PhysX driver, then it will be all fine and the Titan X will read under VRay RT Render Devices Select.

                Question out there, does anyone know what PhysX driver does and if it affects at all with VRay or any of the GPU renderers?

                Comment


                • #9
                  Huh, so it was PhysX? We need to check with the other users that had the same issue.

                  Best regards,
                  Vlado
                  I only act like I know everything, Rogers.

                  Comment


                  • #10
                    PhysX is used in games for real time physics, so you don't need it for rendering.
                    Thanks a lot for sharing that!
                    V-Ray fan.
                    Looking busy around GPUs ...
                    RTX ON

                    Comment


                    • #11
                      Originally posted by vlado View Post
                      Huh, so it was PhysX? We need to check with the other users that had the same issue.

                      Best regards,
                      Vlado
                      Yeah, but does PhysX get used at all in VRay or anything else related to Max as far as you know?

                      Comment


                      • #12
                        Originally posted by savage309 View Post
                        PhysX is used in games for real time physics, so you don't need it for rendering.
                        Thanks a lot for sharing that!
                        OK great, thank you so much for your guys help during these times of utter madness while I was trying to figure this out, at least you helped me continue rendering with GPU while I solved it. Otherwise my boss would have been plenty mad with buying these cards and new workstations. I also just wrote to NVidia and gave them a piece of my mind as they told me it was not related to their drivers, so for the gamers out there, I hope they come up with a solution to the problem. Additionally, if anyone wants to try it out, GTX 970 did not have that problem (I own these cards as well), so if you want to give it a try and install the 970 drivers, the PhysX drivers for those cards may just work fine for the Titan X and may solve the problem and you can keep on gaming. (Note, I have not tried them, these computers are not for gaming, so I don't mind going on without PhysX.)

                        Cheers!
                        Alex

                        Comment


                        • #13
                          V-Ray does not need PhysX, but the MassFX plugin for 3ds Max uses it, as far as I remember...

                          Best regards,
                          Vlado
                          I only act like I know everything, Rogers.

                          Comment


                          • #14
                            This thread was initially encouraging to see. I've been working with Chaos Group on this issue as it relates to me Quadro K5200 adapter. http://forums.chaosgroup.com/showthr...viewport/page3


                            Unless I missed something in this thread and the related ones, this is still only a workaround and not a fix. I do a little game work and I use several games for inspiration and research. Without PhysX, those games will be compromised. Plus, MassFX will not function in Max properly without PhysX.

                            So, this new info forces us to decide what’s more important. Keep PhysX and lose the ‘In-Process’ advantages or delete PhysX and lose game and MassFX physics. Neither is a good solution. I do hope NVidia can resolve it soon.

                            Thanks for the update but it appears to be just a different kind of workaround.
                            ------------------------------------------------------------
                            V-Ray 6.20.06, 3ds Max (3D Studio thru Max 2025), GIGABYTE X570 AORUS Master Motherboard, Ryzen 9 3950x CPU, Noctua NH-D15S CPU Cooler, 128 GB G.SKILL Trident Z Neo DDR4 Ram, NVidia RTX 4090, Space Pilot Pro, Windows 11, Tri-Monitor, Cintiq 13HD
                            -----------------------------------------
                            Autodesk Expert Elite Member
                            ------------------------------------------------------------

                            Comment


                            • #15
                              Yes definitely a workaround. Don't you want to try to install the GTX 970 or any of the previous cards once you have re-installed the Titan X without PhysX? I don't need PhysX right now and that may solve the problem, as I explained below. I may try this in a couple of days and tell you if it works.

                              Comment

                              Working...
                              X