tag:blogger.com,1999:blog-7277449027963623452.post2543052088440536560..comments2023-12-07T05:43:10.401-08:00Comments on Ray Tracey's blog: OpenCL path tracing tutorial 1: Firing up OpenCLSam Laperehttp://www.blogger.com/profile/05688552048697970050noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7277449027963623452.post-87146700915738089332018-07-20T15:16:41.936-07:002018-07-20T15:16:41.936-07:00Im in love with the way you explained everything.....Im in love with the way you explained everything.. <3 <br />Thank you for putting this tutorial up you have no idea how desperate i was for something like this.. Anonymoushttps://www.blogger.com/profile/15156219550666866275noreply@blogger.comtag:blogger.com,1999:blog-7277449027963623452.post-15496389958959475212017-11-12T21:16:49.691-08:002017-11-12T21:16:49.691-08:00I think for OpenCL 2.0, a preprocessor definition ...I think for OpenCL 2.0, a preprocessor definition need to be added: CL_USE_DEPRECATED_OPENCL_2_0_APIS. Because the OpenCL C++ wrapper as I can find from AMD website: http://developer.amd.com/tools-and-sdks/opencl-zone/, is using 2.0 deprecated function.GeekMyPlayhttps://www.blogger.com/profile/06899396483606358489noreply@blogger.comtag:blogger.com,1999:blog-7277449027963623452.post-60710044791584333612016-11-19T07:56:17.161-08:002016-11-19T07:56:17.161-08:00I had a problem using debugging on Visual Studio, ...I had a problem using debugging on Visual Studio, which had nothing at all to do with the code in the tutorial. <br /><br />The problem was that I was using intel integrated graphics, but installed a AMD graphics card later on, so both drivers were present and one graphics card was not installed. When I went to debug (clicking the green arrow in VS), it would crash on the first OpenCL call with an "access violation" error. However if I ran the program without debugging, it ran fine.<br /><br />Looking at the call stack during the crash, it showed the crash in the Intel graphics driver. I tried various things, in the end I just uninstalled the Intel graphics driver, HOWEVER, in Windows this does not completely remove the driver. First, uninstall the graphics driver normally. Then we need to remove the driver from device manager. If you are running <b>Windows 7 or lower </b>, you must add an environment variable to show hidden devices - follow these instructions: https://msdn.microsoft.com/en-us/windows/hardware/drivers/install/viewing-hidden-devices<br /><br />After this, open device manager, and click in the toolbar "view -> show view hidden devices". Then expand the "Display Adapters" screen, right click the intel graphics (should be greyed out), then click uninstall.<br /><br />I'm still not sure why the crash only occurs if you enable debugging in Visual Studio, but the program runs fine without debugging. Maybe when debugging is enabled it catches more errors, and running normally it ignores the access violation error.anonymous psuedonymhttps://www.blogger.com/profile/15202181140455099385noreply@blogger.comtag:blogger.com,1999:blog-7277449027963623452.post-18931095302218909582016-11-07T04:38:06.750-08:002016-11-07T04:38:06.750-08:00Thanks for the tutorial Sam, I have always been in...Thanks for the tutorial Sam, I have always been interested in learning OpenCL and will try and follow along with your tutorials :)Anonymousnoreply@blogger.com