OctaneRender™ Standalone v1.0 RC 3 (obsolete)

[carbon]

Hi,
Just two questions. Does priority in medium work? And if not, when it will be?
Thanks
c.

[balt]

Hi guys,

as pointed out in the OS X section of the commercial forum, I can't get Octane to find any CUDA devices any longer. System details: Macbook Pro (5,1) with GT330M GPU, OS X 10.7.5, CUDA 5.0.37 (also tried 5.0.32 as well as downgraded to 4.2.10 but all with the same result).

Octane (any version) now starts and can't find any CUDA devices. Any hints appreciated!

Cheers

- Balt

[pixelrush]

Hi guys,
I see you have updated the manual for the demo release.
Its much better but I think it still lacks enough detail for the uninitiated and isnt esp logical/consistent...

For instance I would put in a 'loading your first scene' early on using a demo scene just so the user can play with some of the controls, verify it is working and follow along the discussion/introduction. This might mean a bit of reorganisation of the manual though centred more around that process. That is more work though, but I think it would pay off. Missing is 'saving a pic' etc. More simple walk and talk required IMO.
This helps understand nodes a little too. In fact I would make a 'Introductory Scene' demo file with a few simple elements in it I think for the purpose. p39 etc is a bit too complex to suddenly drop people into for example.
Move the 'Troubleshooting' to after this first play session.

Some further things I spotted here and there:
p14. at the end -> should be unticked(off) in CUDA devices in the Device Manager/Preferences (see p43-45)
p17. probably call this Three or more slot PCI-E mobo. Maybe mention risers and some expensive mobo available with 8 pci-e for people wanting to be power users.
you are still calling the demo suite beta246, update the filename to v1 demo suite.zip in the downloads and here.
p27. at end -> spelling = application
p43 wait 1 hour inconsistent with p21 30 mins and somewhere else it was said but that only may be a delay.
p46 make mention of saving of customisation where,how... save preferences as default blah blah
p49 state that 3dmax is illustrated but other apps will have the same parameters discussed here in their UI.
p112 hdri shoulds be rectangular
p116 talks of 2.58d this note not needed for v1
p125 no mention of stereo dist effect. also mention quick colour match for glasses by holding up to white area of the screen and adjusting the RGB. no mention of lens shift either.
p127 hot pixel removal needs to be done at render completion?
p132 can also drag and drop material on header in the node inspector EDIT also mention copy and paste
p150 probably change name to say benchmark for v1.ocs or whatever.
p175 update website to otoy

probably other stuff too but sorry I'm pushed for time ATM to read too closely and its not my job

edit: Btw while you are cleaning up the website click on 'the team' under 'mark forums read' on index page - some redundant names and a few missing

[merid888]

thank you for new release
regards

[abstrax]

Hi guys,

as pointed out in the OS X section of the commercial forum, I can't get Octane to find any CUDA devices any longer. System details: Macbook Pro (5,1) with GT330M GPU, OS X 10.7.5, CUDA 5.0.37 (also tried 5.0.32 as well as downgraded to 4.2.10 but all with the same result).

Octane (any version) now starts and can't find any CUDA devices. Any hints appreciated!

Cheers

- Balt

Hmm, we tried it on that hardware and Octane didn't have issues. Do RC1, RC2 or beta 3.03 work?

Cheers,
Marcus

[balt]

Hi,

beta 2.57 crashes when trying to open with CUDA 5.0.37 drivers. Downgrading to 4.2 then results in "Your CUDA driver is too old, please install a version that supports at least CUDA 4.00".
beta 3.03 does the same thing with 4.2 installed, but with a bit different wording. And it can't even get the version number of the installed CUDA by the looks of it (displays version 0.00 installed).
RC3 ditto.

Installing 5.0.36 (the latest downloadable release driver from nvidia):
beta 2.57 crashes on start (a CUDA library is on the stack, hence looks like that's where it goes down in flames)
beta 3.03 and RC3 both display version 5.00 installed, but the list of CUDA devices is empty.

I have the CUDA 5 SDK installed, all samples there I have tried compile and run just fine.

Any help in resolving this greatly appreciated!

Cheers

- Balt

[balt]

Here's the output of deviceQuery, the utility to find your CUDA capable devices that comes with the CUDA SDK. This confirms that there's no reason Octane doesn't find any CUDA devices...
Still no further ideas on what else to try from across the Tasman? Might this perhaps be the time to take this to a support email rather than a public forum? This obviously is a problem that is not affecting any other users at present.

I also checked which modules are being used by Octane and by the deviceQuery task that successfully sees my GPU. Interesting things I found there:

• Octane appears to make use of OpenCL as well as CUDA libraries (!).

• There appears to be one small difference in which libraries are used: Octane loads /usr/local/cuda/lib/libcuda.dylib, this is not loaded by the CUDA SDK samples. Conversely, libcudart.dylib is not loaded by Octane but used by the SDK samples. Perhaps there's a versioning problem there?

• CUDA framework, libcuda_295.10.20.dylib, libgpucomp.dylib are identical in both processes

deviceQuery uses (I removed non CUDA references):

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
deviceQue 84911 balt txt REG 14,4 160752 27815705 /Library/Frameworks/CUDA.framework/Versions/A/CUDA
deviceQue 84911 balt txt REG 14,4 963544 27601438 /Developer/NVIDIA/CUDA-5.0/lib/libcudart.dylib
deviceQue 84911 balt txt REG 14,4 34132 27601466 /Developer/NVIDIA/CUDA-5.0/lib/libtlshook.dylib
deviceQue 84911 balt txt REG 14,4 9688032 27815725 /Library/Frameworks/CUDA.framework/Versions/A/Libraries/libcuda_295.10.20.dylib
deviceQue 84911 balt txt REG 14,4 18378480 27815732 /Library/Frameworks/CUDA.framework/Versions/A/Libraries/libgpgpucomp.dylib

Octane uses:
octane 85972 balt txt REG 14,4 24648 27815745 /usr/local/cuda/lib/libcuda.dylib
octane 85972 balt txt REG 14,4 160752 27815705 /Library/Frameworks/CUDA.framework/Versions/A/CUDA
octane 85972 balt txt REG 14,4 9688032 27815725 /Library/Frameworks/CUDA.framework/Versions/A/Libraries/libcuda_295.10.20.dylib
octane 85972 balt txt REG 14,4 18378480 27815732 /Library/Frameworks/CUDA.framework/Versions/A/Libraries/libgpgpucomp.dylib
octane 85972 balt txt REG 14,4 166096 27706031 /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupport.dylib
octane 85972 balt txt REG 14,4 134336 27710034 /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib
octane 85972 balt txt REG 14,4 9461088 27709094 /System/Library/Extensions/AppleIntelHDGraphicsGLDriver.bundle/Contents/MacOS/AppleIntelHDGraphicsGLDriver

And here's the output from deviceQuery:

CUDA Device Query (Runtime API) version (CUDART static linking)

Detected 1 CUDA Capable device(s)

Device 0: "GeForce GT 330M"
CUDA Driver Version / Runtime Version 5.0 / 5.0
CUDA Capability Major/Minor version number: 1.2
Total amount of global memory: 512 MBytes (536543232 bytes)
( 6) Multiprocessors x ( 8) CUDA Cores/MP: 48 CUDA Cores
GPU Clock rate: 1100 MHz (1.10 GHz)
Memory Clock rate: 790 Mhz
Memory Bus Width: 128-bit
Max Texture Dimension Size (x,y,z) 1D=(8192), 2D=(65536,32768), 3D=(2048,2048,2048)
Max Layered Texture Size (dim) x layers 1D=(8192) x 512, 2D=(8192,8192) x 512
Total amount of constant memory: 65536 bytes
Total amount of shared memory per block: 16384 bytes
Total number of registers available per block: 16384
Warp size: 32
Maximum number of threads per multiprocessor: 1024
Maximum number of threads per block: 512
Maximum sizes of each dimension of a block: 512 x 512 x 64
Maximum sizes of each dimension of a grid: 65535 x 65535 x 1
Maximum memory pitch: 2147483647 bytes
Texture alignment: 256 bytes
Concurrent copy and kernel execution: Yes with 1 copy engine(s)
Run time limit on kernels: Yes
Integrated GPU sharing Host Memory: No
Support host page-locked memory mapping: Yes
Alignment requirement for Surfaces: Yes
Device has ECC support: Disabled
Device supports Unified Addressing (UVA): No
Device PCI Bus ID / PCI location ID: 1 / 0
Compute Mode:
< Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >

deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 5.0, CUDA Runtime Version = 5.0, NumDevs = 1, Device0 = GeForce GT 330M

[pixelrush]

Hi, if this is Windows you just need the Nvidia driver, it comes with Cuda.
I notice that you have a 330m and that has 48 cuda cores.
This is not really suitable for Octane. It would really be too slow even to run the demo just for a look see.
Plus it has to handle the Windows UI as well simultaneously.
The crashes may be related to this, or perhaps your drivers are a little messed up. Try uninstalling and using driver cleaner.
You would be much better running Octane on something faster and I think overall it would be better strategy to utilise a desktop with 2 cards, one for the UI, and another card dedicated to Cuda(Octane).

[balt]

pixelrush - as you might notice by looking at my library paths, I'm on OS X, not windows. And yes, I don't render for production on that machine... however, very much unlike you state, the performance is good enough for setting up scenes before rendering them on my dedicated render machine, a dual GTX590 equipped beast.

[pixelrush]

No I didn't notice and it would be helpful if you put your specs in your forum signature.
Your first post didn't contain any useful info to help people help you.
As to your problem you seem to know more than I do so feel free to solve your own issues.