OctaneRender™ Standalone v1.0 beta2.58e (obsolete)

[roeland]

So the Kepler build works, but my 3ds Max plugin still fails. Is there a Kepler build of the plugin? I was expecting the standalone fix would be all I need and that the plugin made calls out to the standalone. Guess that is not true?

No, the plugin uses a different build than the standalone, it is included in the plugin release.

--
Roeland

[pixelrush]

Roeland,
Any chance you could do an 2.58f following along from the recent copy/paste Xmas present to allow the user to allocate the total number of textures as they wish (as discussed in a thread here previously). I think this would be a good usability enhancement while we wait patiently for a few months for instancing. I'm guessing/hoping it wouldn't be too much work. After that would make a good place to pause and publish a stable I think.

[roeland]

No, this version is intended to be the final commercial 2.58 release.

We have planned some work on the texturing system, but this will come in a next release, before or after instancing depending on how long it takes to finish instancing.

--
Roeland

[pixelrush]

Yeah ok. Pity, I think many people looking to buy Octane perceive this to be an *issue* and it neednt be quite as restrictive as it is.
See you again then when ever instancing arrives....

[gbambo]

Does "it is included in the plugin release" refer to Kepler support in the plugin? Because it hangs for me.

If there is not Kepler support in the plugin, could you suggest when there might be?

[smicha]

I am running this under Windows 7 x64 with an nVidia 301.42 WHQL driver and a GeForce GTX 670 - 4mb video card. It merely announces "GTX 670 (failed)" while displaying a uniform grey screen.

http://www.refractivesoftware.com/forum ... 14&t=21272

if it helps...

[treddie]

Everything is fixed. Woohoo!

Bubtest, No Headpad, C4D Clean Now (View 1, 2, 3).jpg

These images do not show any of the prior issues. To do it, I adjusted my work flow so that Lightwave is no longer in the loop. Even though this means extra vertices in the OBJ file that Creo exports (these have nothing to do with the normals), I will just have to accept the larger file size. So now I go the following route:
CREO > C4D > Octane.

To make it work though, I have to go around C4Ds import function and use Riptide's importer. This makes it possible to get around C4D's faulty importer. But then I cannot use Riptide's exporter. It crashes Octane! So I use the OctaneExporter to get the file out of C4D and ready for Octane.

Thank you Roeland for your help on the "watercolor" problem. And thanks go out to Proupin and Jaberwocky, for suggesting Riptide and MeshLab, respectively. Although I am n ot using MeshLab at this point, it could very well get me out of a trouble spot in the future, so it is now part of my toolkit.

As soon as I add the fabric headpad and get my textures completed for the helmet and put it in the studio setup I made, I will post some final renders.

[ROUBAL]

Hello, I have noticed that I can't render beyond 7000x7000 in square format or 8192x6000, so it seems that there is a limit around 49 MB.

My ocs scene only requires 1191MB of 2877MB available on my 3GB VRAM cards, and I only use 37 % of my system RAM.

Same result with Octane 1.0258c, 1.0258e and 1.0257, but as the scene has been saved with recent 1.0258e, it may be normal in 1.0257.

However, almost the same scene (a vehicle I am modelling, with small detail variation) saved in 1.0258c shows the same problem.

In the past I rendered at full 8192x8192 without trouble.

Any idea ?

[eidy]

Hi
I hope this posting lands where it should be.
The only reason I broke my usual silence (as my Octane is gathering "rust" from a severe lack of work) IS to tell you that :

Octane Render version 2.58e (beta or release they seem to be one and the same) IS CONSIDERABLY SLOWER ON MY MACHINE (dual opteron 252 + 8800GTX + 4GBRAM / all drivers WHQL and up to date & no overclocking of any kind)

EXAMPLE:

Octane version 2.57 scores in the benchmark scene : 2.28Msamples/s (direct lighting) & 0.64Msamples/s (path tracing)
Octane version 2.58e scores in the benchmark scene : 1.57Msamples/s (direct lighting) & 0.42Msamples/s (path tracing)
aprox. 65-70% drop in performance

Dind't bother to try any other drivers for the gpu (now using CUDA 4.2 & 301.42 WHQL - latest 300 WHQL series, to my knowledge) as it does not seem to be a problem for the older version of Octane

Don't get me wrong ... I very much appreciate all the new features and improvements, BUT not at the expense of speed (or compatibility with "older" gpu's - a.k.a 8800GTX / or newer drivers) without visibly higher changes in quality.
Thanks for your time and patience and ...
PLEASE HELP !

[roeland]

Someone else reported a similar slowdown, it seems to be a problem on 8xxx, 9xxx and 2xx GPU's, see this thread.

--
Roeland