Nvidia Error Message upon Calculate Model

Development Asset Creation
1

I am trying out Reality Capture with the demo version. I aligned images, but when I hit Calculate Model, I got the following error:

“Your computer does not have NVIDIA graphics card. Some features of RealityCapture software require NVIDIA graphics card with at least 1000MB memory and at least 2.0 CUDA compute capability.”

My workstation has an Nvidia Quadro 4000 with 2GB of Graphics memory and CUDA abilities…not sure what’s going on?

Any help would be great, thanks!

2

I guess you need to disable the onboard vga chip. and you’ll can choose use which GPU in the software setting(REcon setting)

3

Hi Doron Kipper

Try to UPDATE your Quadro drivers… :smiley:

4

Wishgranter wrote:

Hi Doron Kipper

Try UPDATE you Quadro drivers… :smiley:

I am wondering what is so funny about it… :?:

5

Funny is that almost every Quadro user gets the CUDA error, it is mainly because they use OLD drivers, never updated…

6

I’m getting the same error message with new driver installed for Nvidia Quadro FX5800… any ideas on that?

7

Hi Paul Huston

first try to use only the RC and nothing else, when it is reconstructing a model, take a look at the temperature of the GPU with help of the MSI afterburner: https://www.youtube.com/watch?v=aqRhKA4EEaQ and set the fan speed to higher speed so that the card is cooled better.
These issues are mostly because the GPU is overheating and drivers try to down-clock the GPU to get it cooler, but then it can cause some synchronization issues and get into errors…

8

I am getting the same error. It worked a couple of weeks ago, but not anymore. I am using a Geforce 980 Ti and getting a non geforce error message.

GeForce GTX 980 Ti
Driver Version: 368.39

9

Aleksey Cheparev wrote:

I am getting the same error. It worked a couple of weeks ago, but not anymore. I am using a Geforce 980 Ti and getting a non geforce error message.

GeForce GTX 980 Ti
Driver Version: 368.39

Looks like restarting the computer fixes it.

10

hate to say it but this is a deal breaker

11

Getting the same error with a GTX765m running 368.69 pretty sure it was working on an earlier version. Going to roll back and see if that fixes the issue.

12

Just rolled back to NVidia drivers 350.12 and it’s all back up and running (I didn’t try the version inbetween this and the dodgy 368’s). Guys a CR might want to look into this.

13

Hi Paul Huston

hate to say it but this is a deal breaker

What you mean with deal breaker ?