ATI / CPU compatibility - When?
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
ATI / CPU compatibility - When?
AMD has a copy of Octane 3 to test with, which was working on their previous drivers from a year ago. They are looking into how to include a fix in the next driver update (hopefully). CPU is just experimental right now:
https://twitter.com/JulesUrbach/status/ ... 76/photo/1
Of note, we get 4x better performance using the Intel integrated GPU than the CPU x86 cores on the same chip.
https://twitter.com/JulesUrbach/status/ ... 76/photo/1
Of note, we get 4x better performance using the Intel integrated GPU than the CPU x86 cores on the same chip.
Hi Goldorak,
so why is AMD not pushing to make this working ?
It should be in their interest.
Please keep us updated about the progress (CPU and AMD GPU).
Thanks a lot
so why is AMD not pushing to make this working ?
It should be in their interest.
Please keep us updated about the progress (CPU and AMD GPU).
Thanks a lot
It seems they are now making a real effort to fix the driver issue.
now these are great news!
Progress. We got OR working on latest AMD driver, now we need to make sure AMD doesn't break it after/when we release 
To clarify, there was a 6+ month stretch where our cross compiler wasn't working at all on a series of their driver releases. This was an issue above and beyond newer drivers breaking older releases (as we posted about before). The former now seems resolved, and the latter may be as well. We'll let everyone know as soon as we have some meaningful updates on this topic.
-
roberthpaige
- Posts: 12
- Joined: Fri Oct 23, 2015 2:21 pm
Thanks! We appreciate the hard work!Goldorak wrote:To clarify, there was a 6+ month stretch where our cross compiler wasn't working at all on a series of their driver releases. This was an issue above and beyond newer drivers breaking older releases (as we posted about before). The former now seems resolved, and the latter may be as well. We'll let everyone know as soon as we have some meaningful updates on this topic.
Latest update:
This morning we validated that Octane 3.00 AMD test builds are working with the current/latest public win10 drivers (and resolved why it was breaking before - which is good). We're now focused on updateing the test builds to 3.06+. We found one of the features in 3.04/5/6 is not running and are looking into it. We think there is a workaround. We have reported the issue to AMD. We hope they fix it soon. The workaround shouldn't be needed, it's just a bandaid. It won't allow full usage of all GPU cores, so we'll have to see how speed is affected once we get this build done.
This morning we validated that Octane 3.00 AMD test builds are working with the current/latest public win10 drivers (and resolved why it was breaking before - which is good). We're now focused on updateing the test builds to 3.06+. We found one of the features in 3.04/5/6 is not running and are looking into it. We think there is a workaround. We have reported the issue to AMD. We hope they fix it soon. The workaround shouldn't be needed, it's just a bandaid. It won't allow full usage of all GPU cores, so we'll have to see how speed is affected once we get this build done.