OctaneRender® 1.024 beta 2.49 TEST (lin/mac/win) [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.
Post Reply
User avatar
Saramary
Licensed Customer
Posts: 147
Joined: Tue Jul 19, 2011 3:42 pm
Location: Auckland, New Zealand
Contact:

t_3 wrote:
Zay wrote:to be precise, a limitation of CUDA, not Octane ;)

AFAIK there are a max. number of 64 image and 32 float textures, as well as 4/4 HDRI rgba and greyscale textures possible.
Written by JimStar:

128, "Maximum number of textures that can be bound to a kernel": http://en.wikipedia.org/wiki/CUDA
But why use CUDA textures in Octane kernels if CUDA has such a limitation? Why not regular array and just not get data from it in kernels something like "float c = texture_array[y*width+x]" instead of convenient but limited "float c = tex2D(tex, x, y)"? In this case this CUDA limitation does not matter (as long as there is enough GPU memory), only plain data will be loaded to GPU and only kernel will know what type of data it is... You can't limit "plain data" with number of textures in it if you don't know what that data contains and just get it loaded to GPU memory as bite sequence...
This is only my assumptions, I'm not CUDA programmer, so sorry if I wrote something wrong...:) But so shame that this limit exists when you have 3GB of GPU memory and when CUDA allows you to load it full of plain data...((
One more sorry if I'm wrong...:oops:

Anyway Octane is great, I respect this excellent work of RS team.
Win 8.1 x64, i7-4930K 64GB, 2 x GTX-690
User avatar
abstrax
OctaneRender Team
Posts: 5508
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

Refracty wrote:In older versions it was easier to work with CPU/Ram based Modelling Packes parallel. No Octane seems to keep the CPU busy while rendering. Any ideas why?
Could you please be more specific? What exactly do you mean with "older versions"? Beta 2.48 or 2.47 or something older?

What is the setup you are using? I.e.:
- Which graphics cards do you have?
- Which graphics cards are used as display cards?
- Which graphics cards are used for rendering?

Thanks,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
abstrax
OctaneRender Team
Posts: 5508
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

matej wrote:My GTX 460 has suddenly only 400 MB of memory :shock:
oct-mem.jpg
I cannot render older projects that require more memory:

Code: Select all

CUDA device 0: Not enough memory to allocate buffer of 15399600 bytes for texture 11
CUDA device 0: KERNEL FAILED!!!
CUDA device 0: Not enough memory to allocate buffer of 15399600 bytes for texture 10
CUDA device 0: KERNEL FAILED!!!
ERROR: Program executed illegal instruction.. terminating
Did you have another Octane running? Are you working on Linux or Windows? If you are working on Windows: Are you using Aero? If you reboot, does the problem persist?

Cheers,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
abstrax
OctaneRender Team
Posts: 5508
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

matej wrote:Also, why is the GUI in 2.49 (again, like in older 2.3) so sluggish? In 2.47 is quite responsive and smooth even on higher render resolutions, but in 2.49 is laggy already on lower resolutions. It also consumes 100% of all my CPU cores when rendering (2.47 uses only one core at 100% during rendering).
Did it get worse compared to beta 2.48, i.e. is it a new problem or is it the same as in beta 2.48*?

Thanks,
Marcus
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
User avatar
roeland
OctaneRender Team
Posts: 1823
Joined: Wed Mar 09, 2011 10:09 pm

infernoVFX wrote:Greetings, i have a bug to report. Portal doesn't work with the pathtracing, here's the images:

Pathtracing
OctanePTwPortals.png
PMC
OctanePMCwPortals.png
It's exactly the same scene, just different rendering engine and these are the results.... BTW i didn't have any problems ruining this version, no extra firewall setup

I love what you did with the direct lighting, that defuse option paired with the occlusion that respects transparency is a pure awesomeness :). Now, if we get a 32-bit output in the next version it will be a huge step forward - Great job Refractive team

All the best,
Voja
The render done in path tracing seems to have a lot of fireflies, can you do some renders with firefly reduction off (hotpixel_removal set to 1.0)?

If you send the scene files to [email protected], we can take a look at it and try to find the problem.
User avatar
matej
Licensed Customer
Posts: 2083
Joined: Fri Jun 25, 2010 7:54 pm
Location: Slovenia

abstrax wrote: Did you have another Octane running? Are you working on Linux or Windows? If you are working on Windows: Are you using Aero? If you reboot, does the problem persist?
Hm, today it's showing 1790 MB (+ - a few megabytes each time I reopen Octane). I did not have another Octane instance running. I'm on Linux and I don't have any system 3D effects running, like Compiz, just plain "2D" Gnome desktop.

I'm not sure what happened yesterday. I'll pay attention the next time this happens, to see if I can reproduce it.
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
grimm
Licensed Customer
Posts: 1332
Joined: Wed Jan 27, 2010 8:11 pm
Location: Spokane, Washington, USA

matej wrote:My GTX 460 has suddenly only 400 MB of memory :shock:
I did a check on my system but I didn't have the same problem. I see all of the memory for my GTX460 (2 GBytes). I'm running the same driver and cuda version you are? The only difference that I can see is that I have two cards in my system, are you just running one? Maybe the OS is tying up the memory for some reason?
Last edited by grimm on Wed Aug 03, 2011 7:39 am, edited 1 time in total.
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
grimm
Licensed Customer
Posts: 1332
Joined: Wed Jan 27, 2010 8:11 pm
Location: Spokane, Washington, USA

matej wrote:Also, why is the GUI in 2.49 (again, like in older 2.3) so sluggish? In 2.47 is quite responsive and smooth even on higher render resolutions, but in 2.49 is laggy already on lower resolutions. It also consumes 100% of all my CPU cores when rendering (2.47 uses only one core at 100% during rendering).
I looked at this too and I also see two CPU's being heavily used. One is always slammed at 100%, the other floats between 70% to 99%. My other CPU's are fine and look normal. The GUI doesn't feel sluggish to me at all, could this be a problem with a single card system?
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
matej
Licensed Customer
Posts: 2083
Joined: Fri Jun 25, 2010 7:54 pm
Location: Slovenia

abstrax wrote:
matej wrote:Also, why is the GUI in 2.49 (again, like in older 2.3) so sluggish? In 2.47 is quite responsive and smooth even on higher render resolutions, but in 2.49 is laggy already on lower resolutions. It also consumes 100% of all my CPU cores when rendering (2.47 uses only one core at 100% during rendering).
Did it get worse compared to beta 2.48, i.e. is it a new problem or is it the same as in beta 2.48*?

Thanks,
Marcus
It's the same as 2.48c which is already more laggy than 2.47.

Of course the GUI is always a little laggy, since I have only one graphic card, but the latest two updates (2.48 & 2.49) are noticeably more laggy than the previous ones - to the point that the whole system is very unresponsive. I think it has to do with the fact that the latest two versions use all my CPU power (2 cores at 100%) when rendering, while the previous ones used only one core while rendering. With 2.46 & 2.47 I'm able to satisfactory navigate the GUI (it's slow, but it's not a pain), while with 2.48 & 2.49 it becomes much more unresponsive - to the point when I click on another tab, it refreshes it in blocks. The system is also unusable, while on the previous versions I could still slowly browse the net, while Octane was rendering...

The older versions like 2.3 also used all my CPU power (I think this is a Linux problem*), then you guys corrected something so that Octane has been using only one core, now in the latest two versions this problem is back again. :)

*although Refracty who is on Win it seems, is reporting the same thing a few posts back.
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

grimm wrote:I looked at this too and I also see two CPU's being heavily used. One is always slammed at 100%, the other floats between 70% to 99%. My other CPU's are fine and look normal. The GUI doesn't feel sluggish to me at all, could this be a problem with a single card system?
Yes, the sluggishness is a problem with one card system, but the last two versions are much more sluggish that the previous ones. It seems that having more than two CPU cores it's beneficial for running Octane, since you experience the same thing but as you have more than 2 cores, your system is still usable. Well, I plan to update my computer sometime this year... :)
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
Post Reply

Return to “Development Build Releases”