Geopappas
I ran the test tonight using driver 260.99 on both the old version of the software and the current version,using exactly the same scene.So the base line test was exactly the same.
OctaneRender® pre-Beta 2.4 (win x64) [OBSOLETE]
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
- Jaberwocky
- Posts: 976
- Joined: Tue Sep 07, 2010 3:03 pm
CPU:-AMD 1055T 6 core, Motherboard:-Gigabyte 990FXA-UD3 AM3+, Gigabyte GTX 460-1GB, RAM:-8GB Kingston hyper X Genesis DDR3 1600Mhz D/Ch, Hard Disk:-500GB samsung F3 , OS:-Win7 64bit
Yup, we willJaberwocky wrote:Abstrax
will you be re re releasing this windows x64 build again along with the other builds once the current list of bugs are sorted ? and if so how will we know ?

Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
- Jaberwocky
- Posts: 976
- Joined: Tue Sep 07, 2010 3:03 pm
GeoPappas
I think the thing to point out is that although the previous version said that it only saw 224 of the 336 cores.It was infact using the full GPU.I assumed like everyone else before running this test that as it was only reporting seeing 2/3rds of the available cores, it therefore must have been running at 2/3rds speed without testing it.If I had run CPU Z before now i would have realised that it was just a reporting error and was in actual fact using the whole GPU to render.
I think the thing to point out is that although the previous version said that it only saw 224 of the 336 cores.It was infact using the full GPU.I assumed like everyone else before running this test that as it was only reporting seeing 2/3rds of the available cores, it therefore must have been running at 2/3rds speed without testing it.If I had run CPU Z before now i would have realised that it was just a reporting error and was in actual fact using the whole GPU to render.
CPU:-AMD 1055T 6 core, Motherboard:-Gigabyte 990FXA-UD3 AM3+, Gigabyte GTX 460-1GB, RAM:-8GB Kingston hyper X Genesis DDR3 1600Mhz D/Ch, Hard Disk:-500GB samsung F3 , OS:-Win7 64bit
@abstrax, you are doing a great job, patching stuff in real-time!
I was kinda disappointed this morning not finding a Linux build, but I see it's better this way - Windows users lead the way into the jungle, catching the majority of mosquito bites, while we thread safely behind
Just make a Linux build before the end of the competition. 
I was kinda disappointed this morning not finding a Linux build, but I see it's better this way - Windows users lead the way into the jungle, catching the majority of mosquito bites, while we thread safely behind


SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
cgmo.net
I am pretty sure that there were people that reported that not all cores were being used on the GTX 460. Also, I remember people stating that they could easily use their computer while rendering with Octane (which implied that not all GPU cores were being used).Jaberwocky wrote:GeoPappas
I think the thing to point out is that although the previous version said that it only saw 224 of the 336 cores.It was infact using the full GPU.I assumed like everyone else before running this test that as it was only reporting seeing 2/3rds of the available cores, it therefore must have been running at 2/3rds speed without testing it.If I had run CPU Z before now i would have realised that it was just a reporting error and was in actual fact using the whole GPU to render.
You (or someone else) might want to test Octane 2.3v5 with an older NVIDIA driver (prior to 260.99). It might be that the newer NVIDIA driver has increased the number of cores used.
EDIT: Here is a thread where someone states that not all of the cores of the GTX 460 are being used:
http://www.refractivesoftware.com/forum ... &start=120
1st pageElvio wrote:Where´s the download link?

My Portfolio
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
windows 10 Pro. |1070 + 1070 + 1070 + 1070 | i7 @4.5Ghz
Whether or not you could use the computer while rendering depended on the scene and settings. Using direct lighting and low resolution yeah then you could surf the Internet or whatever. I don't think there's hard evidence suggesting one or the other (using all cores or not before 2.4).GeoPappas wrote:I am pretty sure that there were people that reported that not all cores were being used on the GTX 460. Also, I remember people stating that they could easily use their computer while rendering with Octane (which implied that not all GPU cores were being used).Jaberwocky wrote:GeoPappas
I think the thing to point out is that although the previous version said that it only saw 224 of the 336 cores.It was infact using the full GPU.I assumed like everyone else before running this test that as it was only reporting seeing 2/3rds of the available cores, it therefore must have been running at 2/3rds speed without testing it.If I had run CPU Z before now i would have realised that it was just a reporting error and was in actual fact using the whole GPU to render.
You (or someone else) might want to test Octane 2.3v5 with an older NVIDIA driver (prior to 260.99). It might be that the newer NVIDIA driver has increased the number of cores used.
EDIT: Here is a thread where someone states that not all of the cores of the GTX 460 are being used:
http://www.refractivesoftware.com/forum ... &start=120
Win 7 64bit, GF 460 2GB, Intel quad, 4GB memory