Hello everyone,

Sorry for the lack of information on the original post, but I was in the middle of a call with a volunteer who was trying to help me debug a few things. Unfortunately he wsa being limited and our tests did not work. However, it did give me a few paths to take on potentially resolving some of the problems.

Just so everyone is aware, if intel gpu is still causing higher than acceptable error rates, we may hold it back from going to production. I was hoping to get additional data to look over on this beta test from these 9 batches that were for intel GPU only.

As for the double/single precision issue, the application should not have any double precision floats in it. I will go back over the code with a fine tooth comb to see if I can determine where this is getting the error from.

@Grumpy, I'm glad you were able to get some work. What was your minimum work buffer set to previously?

@Richard Haselgrove Can you change your settings to less than 0.25 to see if that helps your machine capture work for IGPU?

Thanks,
-Uplinger

My settings on the machine I tested were 0.1 + 0.01 days anyway. Have tried since, but still nothing.

Have also added the laptop with UHD 620 and no NV, Win 10. Nothing there either so far.

I got 9 so far on my windows 10 machine with an i7-4790, with Intel HD 4600.
First one completed ok in about 1.5 hours but the report only says CPU time 0.1 hour.
Running 2 at once, the estimated time is 1-2 hours each.

I had the same thought, and also got work after changing settings. I allowed both CPU and AMD work (although I don't have an AMD card), and got 3 CPU, 2 Intel_gpu tasks. Watching now.

Same here for CPU time vs. Elapsed time. It took 1.03 hours elapsed time on my i7-4770 with HD4600 graphics, but had 0.06 CPU time according to the task listing on the webpage. I think the elapsed time was pretty accurate for how much GPU work went into it. The PC wasn't doing anything else.