OctaneRender™ Standalone v1.0 beta3.02a [obsolete]

A forum where development builds are posted for testing by the community.
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.
User avatar
grimm
Licensed Customer
Posts: 1332
Joined: Wed Jan 27, 2010 8:11 pm
Location: Spokane, Washington, USA

roeland wrote:
grimm wrote:I think I spoke a bit too soon. The only ocs file I have gotten to work has been the benchmark. I tried all of the other demo files and they all would start to work for just a couple of seconds before stopping. The errors are the same as before, here is a sample:
What is the first error shown?
I haven't been able to use Octane much this summer so I think it must have been 2.58 or thereabouts. "less responsive" is, when this version is working, things like button clicks take a second or two to register. Panning or rotating the camera is very slow and the rest of the interface is just not as snappy as it was before.

The only differences that I can think of from then to now, besides the OS upgrade and the new version of Octane, is that I have changed my desktop environment to Cinnamon. Cinnamon is a fork of Gnome 3 that now uses a lot of graphic effects that might affect the GPU more than before? The only other thing is that I had to do is a link to the libGLEW library to get Octane to run. Even though I'm running Fedora 17 the libGLEW in the repository is only up to version 1.6. So I linked /lib64/libGLEW.so.1.7 to the 1.6 version. Sometimes this works, other times not. In any case it might be an issue?
Maybe a graphical desktop indeed suffers more from running a CUDA application. Is it running much slower than with version 3.01? Were you using the PMC kernel back then? This kernel has less effect on the responsiveness of the desktop than the path tracing and direct lighting kernels.

We will try to remove the libGLEW dependency. I don't know if linking like this is a problem.

--
Roeland
Thanks Roeland,

Here is the start of one of the sessions, don't remember which one I was trying here:

Code: Select all

CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
    -> Kernel execution failed (mprev)
CUDA device 0: Preview failed
CUDA error 700 on device 0: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
    -> Failed to load symbol data to the device (kernel data)
If you would like me to test one of the demo/test scenes specifically, just let me know. I wasn't able to get version 3.01 to run, mostly because of libGLEW version miss-match with Fedora 15 I was running at the time. It's one of the reasons I upgraded to F17, that and F15 is not supported anymore. ;) The slow-down is very noticeable, I tried daylight, path tracing, and pmc, they were all very slow and unresponsive. The samples per second appeared to be the same from what I was getting before.

Jason
Linux Mint 21.3 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 535.171
User avatar
abstrax
OctaneRender Team
Posts: 5510
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

The problem with libglew is weird. I really thought that we now link against static libglew - need to have a look tomorrow.

The error just indicates that the material preview fails. Could have many reasons. Which driver are you using?

Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
matej
Licensed Customer
Posts: 2083
Joined: Fri Jun 25, 2010 7:54 pm
Location: Slovenia

I noticed just now that if you hit delete when you are in the preview configuration panel / tabs on the right, you actually delete the node (= selected tab), which practically means that you can delete parts of the GUI.

Maybe delete should work only when you are in GE (with your mouse), cause for someone who doesn't know what is happening behind the scenes, this can be an unexpected behavior.
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
User avatar
matej
Licensed Customer
Posts: 2083
Joined: Fri Jun 25, 2010 7:54 pm
Location: Slovenia

I did another comparison between 259 and 302 (Fermi card, Linux). I tried to compare "quality", but it's really hard to evaluate it, mainly because of the random noise seed. They kinda look the same, except in 302 there is different lighting, though the setting are the same in both cases. Have anything changed around HDRI lighting (or maybe it's the specular material?)? (notice also 302 eats less ram - same scene, no instances used)

PMC
259 -> 512 samples in 11:10
302 -> 512 samples in 12:40 (12.3% slower)
comp1.png
There is a huge difference in loading times, though:

259 -> 0:41
302 -> 2:46 !!!

The loading process freezes and resumes several times during "analyzing obj / parsing vertex" phase. I'm using Linux Mint with the old Gnome 2 desktop environment. Could this be related to the new way the info is showed in the window itself and not with popups anymore?
oct302-freeze1.png
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
User avatar
abstrax
OctaneRender Team
Posts: 5510
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

The loading time issue got fixed today and the fix will become available with the next release. (We were basically redrawing the status bar a gazillion times...)

Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
matej
Licensed Customer
Posts: 2083
Joined: Fri Jun 25, 2010 7:54 pm
Location: Slovenia

abstrax wrote:The loading time issue got fixed today and the fix will become available with the next release. (We were basically redrawing the status bar a gazillion times...)
Great thanks! :D
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
User avatar
bepeg4d
Octane Guru
Posts: 10393
Joined: Wed Jun 02, 2010 6:02 am
Location: Italy
Contact:

wow, interesting test matej ;)
the bubbles in the 3.02 version are extremely more pleasant for me, there is a completely different way to calculate the reflections but also the refraction :o
ciao beppe
User avatar
matej
Licensed Customer
Posts: 2083
Joined: Fri Jun 25, 2010 7:54 pm
Location: Slovenia

bepeg4d wrote:the bubbles in the 3.02 version are extremely more pleasant for me, there is a completely different way to calculate the reflections but also the refraction :o
Yeah, I agree, the water droplets in 302 look much more appealing. The material is a mix (mostly specular) between default specular & glossy, with both having lowered opacity too.

I think a ~10% speed drop for PMC is acceptable for all the new goodies in 302. Too bad DL shows a higher speed drop, something around 20% for the tests I did...
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
User avatar
abstrax
OctaneRender Team
Posts: 5510
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

matej wrote:
bepeg4d wrote:the bubbles in the 3.02 version are extremely more pleasant for me, there is a completely different way to calculate the reflections but also the refraction :o
Yeah, I agree, the water droplets in 302 look much more appealing. The material is a mix (mostly specular) between default specular & glossy, with both having lowered opacity too.

I think a ~10% speed drop for PMC is acceptable for all the new goodies in 302. Too bad DL shows a higher speed drop, something around 20% for the tests I did...
Why don't you use just one specular material for the droplets?

Regarding the speed drop: How does it compare to 3.01? 2.59 doesn't support instances which is probably the main reason why it's faster.

Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
pixelrush
Licensed Customer
Posts: 1618
Joined: Mon Jan 11, 2010 7:11 pm
Location: Nelson, New Zealand

>the next release.
Coming in a few days? ....that will give me time to sort out a modded driver for it. 8-)
I'm beginning to feel I'm downloading a gazillion times in preparation but I'll get there yet :lol:
i7-3820 @4.3Ghz | 24gb | Win7pro-64
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
Post Reply

Return to “Development Build Releases”