Hi,
I've been trying the Octane demo for the last week or so and am pretty impressed. Everything seems to work really well, except -- I get a black render viewport it seems when I hit a certain GPU memory point.
Octane says 261/495 MB used, and I get a black viewport. When I go below around 255/495 MB used, everything is fine. The black viewport still allows me to color-pick and show materials in the node inspector, it just renders an entirely black view.
Should I be able to use all my GPU memory or just half?
I'm on an 9800 GT that is also my display card. All my drivers/cuda drivers are up to date.
thanks,
Steve
black render window - means?
Forum rules
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
I think what's happening is that your OS is using the remaining memory.
Can you provide details, eg octane version, your operating system type and version and the drivers you have installed ?
Thnx,
Radiance
Can you provide details, eg octane version, your operating system type and version and the drivers you have installed ?
Thnx,
Radiance
Win 7 x64 & ubuntu | 2x GTX480 | Quad 2.66GHz | 8GB
CPU: Intel Core2 Quad Q9300 w/ 8 gigs ram.
OS: Windows Vista home premium edition 64-bit w/service pack 2.
GPU: Nvidia GeForce 9800 GT w 512mb, 112 cuda cores.
Octane: 1.022 Beta 2.2
GPU & CUDA drivers were updated when I downloaded Octane to try it out. The Nvidia control panel gives these now as:
Driver version: 197.13
CUDA 3.0.1 driver
I'm running display at 1920x1200 if that matters. Problem still exists where I get black screen after about half of GPU memory used. Can display possibly be using 250 mb?
thanks,
Steve
OS: Windows Vista home premium edition 64-bit w/service pack 2.
GPU: Nvidia GeForce 9800 GT w 512mb, 112 cuda cores.
Octane: 1.022 Beta 2.2
GPU & CUDA drivers were updated when I downloaded Octane to try it out. The Nvidia control panel gives these now as:
Driver version: 197.13
CUDA 3.0.1 driver
I'm running display at 1920x1200 if that matters. Problem still exists where I get black screen after about half of GPU memory used. Can display possibly be using 250 mb?
thanks,
Steve
Last edited by sck5000 on Fri Nov 05, 2010 4:53 am, edited 1 time in total.
- enricocerica
- Posts: 1012
- Joined: Wed Nov 25, 2009 7:32 pm
- Contact:
Yeah, I experimented the same issue several times, your scene exeeds the remaining memory, try to stop programs consuming video memory, for example your modelling application. You may also try to reduce the size of the image maps used in the scene.
Modeling system : I7 32GB Windows 10 & Fujitsu Celsius H720
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
I don't have any image maps in the scene yet, I'm hitting this problem before I have even begun to texture. Does the licensed beta version of Octane manage video memory better than the demo? And I still don't really believe that my video card uses fully half of its memory just for the display?
Also, the .obj file is only 50 mb. Is it normal that a 50 mb file would take up 250 mb of gpu memory after Octane has processed?
Thanks.
Also, the .obj file is only 50 mb. Is it normal that a 50 mb file would take up 250 mb of gpu memory after Octane has processed?
Thanks.
Maybe I'm wrong. But I believe I've seen this too.
and I think the initial camera position is dollied in infintesimally too close to an (the) object.
I'll go back to my parent app. and make sure the scene is where I need it nearest the 0,0,0 coordinate, set my camera the distance I want, and re-export it back out as an obj. and viola' it comes out o.k.
Maybe this is happening with your circumstance as well?
In my case I find that 'saving' preserves the scene positioning, while 'export'ing doesn't.
and I think the initial camera position is dollied in infintesimally too close to an (the) object.
I'll go back to my parent app. and make sure the scene is where I need it nearest the 0,0,0 coordinate, set my camera the distance I want, and re-export it back out as an obj. and viola' it comes out o.k.
Maybe this is happening with your circumstance as well?
In my case I find that 'saving' preserves the scene positioning, while 'export'ing doesn't.
MSI NF980-G65 AM3 NVIDIA nForce 980a AMD Motherboard - AMD Athlon II X4 620 (Overclocked to 3.2ghz)
(2)GTX460's, (1)BFG gtx260, OCZ 60GB SSD, KINGWIN 1000W Power, HAF 932 Full Tower, XP64
Octane V1 - 2.46 - CUDA 4.11 - OBJ's from Rhino4
(2)GTX460's, (1)BFG gtx260, OCZ 60GB SSD, KINGWIN 1000W Power, HAF 932 Full Tower, XP64
Octane V1 - 2.46 - CUDA 4.11 - OBJ's from Rhino4