JBird, wouldn't it be easier to simply rename the app_info and test? This way everything should run as intended by the project. Then you know how it should work like and can try again to recreate this via an app_info, if you want to use the new beta app for all tasks. Otherwise simply use the much easier app_config to set the number of concurrent tasks.
Hopefully what Richard wrote was clear enough. It's basically what Gary tried to explain in more length and that was not understood.
Now before JBird's app_config.xml starts to spread confusion again ... It does not (and cannot) do what the user wants to achieve and what it really does was probably not intended that way. I advise to just DELETE it and set the GPU utilization factor to 0.5 through project preferences if that's not already happened. There may be some subtle changes in behaviour but I think the user won't even notice them. And there's one less opportunity to shoot yourself in the foot.
JBird, wouldn't it be easier
)
JBird, wouldn't it be easier to simply rename the app_info and test? This way everything should run as intended by the project. Then you know how it should work like and can try again to recreate this via an app_info, if you want to use the new beta app for all tasks. Otherwise simply use the much easier app_config to set the number of concurrent tasks.
MrS
Scanning for our furry friends since Jan 2002
Or just recognise that an API
)
Or just recognise that an API (Application Programming Interface) is a different beast from a driver, and not under your control.
Computers which are carefully managed by people who know exactly what they are doing - like archae86's GTX 970 - also report
[19:57:38][5500][INFO ] Version of installed CUDA driver: 6050
[19:57:38][5500][INFO ] Version of CUDA driver API used: 3020
in stderr_txt - that's the way the application was written. It's not under our control. Any of us.
Hopefully what Richard wrote
)
Hopefully what Richard wrote was clear enough. It's basically what Gary tried to explain in more length and that was not understood.
Now before JBird's app_config.xml starts to spread confusion again ... It does not (and cannot) do what the user wants to achieve and what it really does was probably not intended that way. I advise to just DELETE it and set the GPU utilization factor to 0.5 through project preferences if that's not already happened. There may be some subtle changes in behaviour but I think the user won't even notice them. And there's one less opportunity to shoot yourself in the foot.