Beta 0.5.9 (SDK 1.17 ) (old version)
Moderators: ChrisHekman, aoktar
I just noticed that with the plugin installed (no octane preview or anything opened), Cinema is using one Core at a 100% all the time. With the plugin removed from the plugin folder, this disappears immediately. Something's using up a lot of power doing nothing...
Hi ron908,ron908 wrote:I just noticed that with the plugin installed (no octane preview or anything opened), Cinema is using one Core at a 100% all the time. With the plugin removed from the plugin folder, this disappears immediately. Something's using up a lot of power doing nothing...
this is possible because it's test release and there is some tweaks on main algoritms. If it's annoying for you please stay older release until fixed
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Thanks for that, i'll do some tweaks. When it's ok you'll get a updateron908 wrote:Nope, not annoying as such, I just wanted to make sure you're aware of it.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Hi Aoktar,
Found a problem with 0.5.7 that wasn't there earlier. Histogram combing. I installed 0.5.7 yesterday and noticed that all my renders had "combed" histograms (meaning there is small amounts of data loss in the output file of some tone values). This wasn't happening with 0.5.0 and before.
The histogram in Picture Viewer should be smooth and not "spiky" like this. Here's a screengrab:

It could be that it's the 1.16 SDK Standalone that's causing this (it's definitely something in the render end) rather than the plug-in functionality? I don't have the 1.16 Standalone installed. Could someone that has check to see if the renders from 1.16 are combing the histogram (when opened in an image editor like Photoshop) too?
Thanks for all your hard work so far, enjoying the new functions!
Found a problem with 0.5.7 that wasn't there earlier. Histogram combing. I installed 0.5.7 yesterday and noticed that all my renders had "combed" histograms (meaning there is small amounts of data loss in the output file of some tone values). This wasn't happening with 0.5.0 and before.
The histogram in Picture Viewer should be smooth and not "spiky" like this. Here's a screengrab:

It could be that it's the 1.16 SDK Standalone that's causing this (it's definitely something in the render end) rather than the plug-in functionality? I don't have the 1.16 Standalone installed. Could someone that has check to see if the renders from 1.16 are combing the histogram (when opened in an image editor like Photoshop) too?
Thanks for all your hard work so far, enjoying the new functions!
Win 7 x64 | 1 x EVGA GTX680 Classified & 1 x Quadro FX1800 (display) | i7 920 o/c 3.04Ghz | P6TD Deluxe | 24GB | AX860 PSU
Can you send your file?Jaybee wrote:Hi Aoktar,
Found a problem with 0.5.7 that wasn't there earlier. Histogram combing. I installed 0.5.7 yesterday and noticed that all my renders had "combed" histograms (meaning there is small amounts of data loss in the output file of some tone values). This wasn't happening with 0.5.0 and before.
The histogram in Picture Viewer should be smooth and not "spiky" like this. Here's a screengrab:
It could be that it's the 1.16 SDK Standalone that's causing this (it's definitely something in the render end) rather than the plug-in functionality? I don't have the 1.16 Standalone installed. Could someone that has check to see if the renders from 1.16 are combing the histogram (when opened in an image editor like Photoshop) too?
Thanks for all your hard work so far, enjoying the new functions!
i'll check it
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Attached,aoktar wrote:
Can you send your file?
i'll check it
Thanks!
- Attachments
-
- octane_057_histogram_comb.zip
- Here's the simple file from the screengrab.
- (91.68 KiB) Downloaded 204 times
Win 7 x64 | 1 x EVGA GTX680 Classified & 1 x Quadro FX1800 (display) | i7 920 o/c 3.04Ghz | P6TD Deluxe | 24GB | AX860 PSU
Hi Aoktar-
I've run into a big issue. There seems to be a HUGE memory leak in this version (.5.7). Attached is a screen shot of the issue. As you can see, this animation ran for a little while and then stalled on a frame and continued to "render" that frame for 15 hours. Now look at the memory usage. Over 30 gigs! It flat out ran out of memory. This is a very simple scene too. 18K polygons.
This is a classic memory leak that needs fixing quick. I had two machines rendering this and both froze.
I think it was Immortalarts that was posting similar issues with his scene. This is a deal breaker here.
Can you check this out?
Thanks
Alec
I've run into a big issue. There seems to be a HUGE memory leak in this version (.5.7). Attached is a screen shot of the issue. As you can see, this animation ran for a little while and then stalled on a frame and continued to "render" that frame for 15 hours. Now look at the memory usage. Over 30 gigs! It flat out ran out of memory. This is a very simple scene too. 18K polygons.
This is a classic memory leak that needs fixing quick. I had two machines rendering this and both froze.
I think it was Immortalarts that was posting similar issues with his scene. This is a deal breaker here.
Can you check this out?
Thanks
Alec
Alec Syme
http://www.fuseanimation.com
-Gigabyte X79-UP4 - Intel i7 3930 3.4 - Windows 8.1 Pro 64bit - EVGA TITAN X7 - 32 Gigs Corsair 1600 4 channel RAM -
http://www.fuseanimation.com
-Gigabyte X79-UP4 - Intel i7 3930 3.4 - Windows 8.1 Pro 64bit - EVGA TITAN X7 - 32 Gigs Corsair 1600 4 channel RAM -
yes, if you attach file will be helpASyme1 wrote:Hi Aoktar-
I've run into a big issue. There seems to be a HUGE memory leak in this version (.5.7). Attached is a screen shot of the issue. As you can see, this animation ran for a little while and then stalled on a frame and continued to "render" that frame for 15 hours. Now look at the memory usage. Over 30 gigs! It flat out ran out of memory. This is a very simple scene too. 18K polygons.
This is a classic memory leak that needs fixing quick. I had two machines rendering this and both froze.
I think it was Immortalarts that was posting similar issues with his scene. This is a deal breaker here.
Can you check this out?
Thanks
Alec
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I have checked, there is a problem. I'm try to found problem.Jaybee wrote:Attached,aoktar wrote:
Can you send your file?
i'll check it
Thanks!
Thanks
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw