That Nvidia card bests the AMD card in just about every way, and also (if the OP is into gaming) has real time ray tracing. It also has vastly improved OpenCL capabilities vs. previous Nvidia cards. That said, not of much use if Vegas can't even see it.

Have you updated drivers?

I'm running VP16 and an RTX 2070 and Vegas recognizes the card just fine.

I am running VP16 and VP15 with an RTX 2080ti and Vegas also recognizes the card just fine.

@OldSmoke aside of the vastly improved OpenCL in the Turing architecture, there is also the following improvements versus the older Pascal generation of Nvidia:

Turing GPUs also ship with an enhanced NVENC encoder unit that adds support for H.265 (HEVC) 8K encode at 30 fps. The new NVENC encoder provides up to 25% bitrate savings for HEVC and up to 15% bitrate savings for H.264.

Turing’s new NVDEC decoder has also been updated to support decoding of HEVC YUV444 10/12b HDR at 30 fps, H.264 8K, and VP9 10/12b HDR.

Turing improves encoding quality compared to prior generation Pascal GPUs and compared to software encoders. Figure 11 shows that on common Twitch and YouTube streaming settings, Turing’s video encoder exceeds the quality of the x264 software-based encoder using the fast encode settings, with dramatically lower CPU utilization. 4K streaming is too heavy a workload for encoding on typical CPU setups, but Turing’s encoder makes 4K streaming possible.

https://devblogs.nvidia.com/nvidia-turing-architecture-in-depth/
 

Pascal has 1 or 2 HW encoders (NVENC) build in (2 for the GeForce GTX 1070 and higher types), whilst the newer Turing "only" has 1 on most card types. This seems like a regression in the RTX, but according to Nvidia:

The video encoder in Turing GPUs has substantially improved quality and performance compared with Pascal. The overall encoding capacity of one NVENC in Turing is comparable to two NVENC’s in Pascal.

Pascal has 1 or 2 HW encoders (NVENC) build in (2 for the GeForce GTX 1070 and higher types), whilst the newer Turing "only" has 1 on most card types. This seems like a regression in the RTX, but according to Nvidia:

The video encoder in Turing GPUs has substantially improved quality and performance compared with Pascal. The overall encoding capacity of one NVENC in Turing is comparable to two NVENC’s in Pascal.

@bitman I will not dispute that the RTX is great GPU on paper and in benchmark but how does that translate to Vegas in a real world scenario? Keep in mind the OP is running it on a Z87 motherboard with a 4700k CPU.

@OldSmoke the real world scenario, that is the 1000 dollar question indeed?

@arthur-vanick

I was a bit deviating to your question, you have already a turing card, and Vegas (in your system) does not recognize it. I suspect (and this is speculation on my part) it may have to do with the fact you switched from amd videocard to nvidea on the same system, so there may be some amd driver stuff left over causing this, or the vegas cash/data or whatever init files still has some amd gpu stuff left over.

I would recommend :

1) finding some tools to purge amd driver left overs from your system

2) after the AMD purge, install the latest Nvidia drivers (especially important as this is a new card, and many bugs and optimizations are ongoing), best is to install the the drivers from Nvidia itself, not via the videocard manufacturer (they are lagging behind usually)

3) After the amd purge and nvidia install latest drivers, uninstall and re-install Vegas.

Pascal has 1 or 2 HW encoders (NVENC) build in (2 for the GeForce GTX 1070 and higher types), whilst the newer Turing "only" has 1 on most card types. This seems like a regression in the RTX, but according to Nvidia:

That's interesting. I have a GTX1070, get 103fps Nvenc encode on 720p render, 68%cpu. I opened a second vegas rendered the same project, that resulted in cumulative render fps of 158fps, however i was cpu bottle necked(100%). Although I've heard the gtx1070 is supposed to have 2 NVENC encoders, I've never seen any evidence to support that in the real world, only gtx1080/ti & probably gtx1070ti with dual Nvenc.

I think vegas must only use a single Nvenc thread for encoding & when I open another vegas a 2nd nvenc encode thread uses the remaining capacity, rather than the less likely idea that vegas can only use 1 nvenc at a time & opening 2nd vegas allows use of 2nd nvenc. Still interesting to see this unused capacity lying dormant, it's something people realise is the case with threadrippers etc but not nvenc.

@OldSmoke the real world scenario, that is the 1000 dollar question indeed?

@arthur-vanick

I was a bit deviating to your question, you have already a turing card, and Vegas (in your system) does not recognize it. I suspect (and this is speculation on my part) it may have to do with the fact you switched from amd videocard to nvidea on the same system, so there may be some amd driver stuff left over causing this, or the vegas cash/data or whatever init files still has some amd gpu stuff left over.

I would recommend :

1) finding some tools to purge amd driver left overs from your system

2) after the AMD purge, install the latest Nvidia drivers (especially important as this is a new card, and many bugs and optimizations are ongoing), best is to install the the drivers from Nvidia itself, not via the videocard manufacturer (they are lagging behind usually)

3) After the amd purge and nvidia install latest drivers, uninstall and re-install Vegas.

Thanks for the suggestions, and I tried all of them, but Vegas Pro 15 still doesn't see the new card. Not only did I remove all traces of the AMD drivers and related programs, as well as uninstall and re-install VP15, I removed any associated directories for AMD and VP15 and deleted whatever I found. I restarted after each step. Also, I was careful to install the latest card drivers straight from Nvidia and not MSI. In fact, the MSI installation disk directed me to the Nvidia site, so no problem there. Could this be a Windows 7 thing? Am running Windows 7 Pro. The only remaining step that I can see is to completely remove all of the Nvidia stuff and do a complete reinstall. Am open to any suggestions. It seems a monumental waste to have such a great card and the main program I use not to see it! My gamer son would love to have it, but that isn't going to happen.

@arthur-vanick
You are on the good track, I would not be surprised it is due to windows 7.
The RTX cards need windows 7 64 bit at least.
If you are using an RTX card on windows 7 you are missing out a lot of it's cards potential such as DirectX12, and the RTX itself (even needing the latest windows 10 fall edition 1809 for the DirectX 12 DXR).

You may want to try the Guru3D DDU (display driver uninstaller) for a "deep scrub." These low level things can be quite tenacious.

I know that Windows 7 Pro doesn't realize the full potential of the card but I'm not going to scrap my system at this point, or even go through the hassle of upgrading to Windows 10 at this point. Wow, can't wait to try out the new card!