OctaneRender® pre-Beta 2.3 v4 (win/lin/mac) [OBSOLETE]

[kubo]

well, if it wasn't packed with this last release, check the pre 2.3_3 (I know its there for sure) or the 2.2b http://www.refractivesoftware.com/forum ... =24&t=2509

[simmsimaging]

Another texture related issue: still no joy getting them to import from Max, but some are not re-loading properly once I quit Octane and re-load a scene. I'm getting errors like the two attached images show. Some maps are fine still. Also had some nodes that I saved (materials) that did not save all the texture maps. In both cases it seems to be mostly bump maps that get wiped out or missed, but this current round of missing maps also includes at least one diffuse colour map.

b

[kubo]

besides what I told you about no spaces in file names, also right now Octane only speaks english, that is, non-english characters might not work correctly, check for those in your path and file names.

[simmsimaging]

thanks Kubo

The same image files load up in some scenes just fine, but occasionally it seems to get broken so I am not sure if that is the issue or not. Is the name space problem inconsistent or is it something else perhaps?

Files do not have spaces in the names and no non-english characters, but part of my main texture path does have spaces in the file structure. I can't change that now as too many other projects/material paths are dependent on that, and it has been working fine with Octane more often than not.

Anyway, is this space sensitivity something that can/will be fixed in Octane at some point?

b

[kubo]

I might have not explained myself correctly, what I meant is that currently, when importing from an .obj file there is this problem with textures with spaces in it's name. That's a obj file limitation, and only happens at import, once relinked from inside octane that won't happen again or you can rename those file names so there won't be any spaces they'll import right the first time. On the other hand octane has had problems with "weird" characters in filepaths or filenames (actually I've had no problems with the "ñ" character, it replaces it by a "n"), and it will be solved when the refractive guys have some time off from the current schedule and all the neat things that are coming. But they are usually consistent problems not random. Could your image file (if it's always the same one) be corrupt? try opening it in photoshop or the like and saving it again with different compression or extension and see if it fixes it. I've had corrupted images before due to a faulty HD or working with them and crashing windows at the same time.

[simmsimaging]

Thank you for the clarification and the help. The file is not corrupt and it is happening with at least three different images, but each one still loads fine in the (earlier) iterations of the same file, which seems to point to Octane or some kind of user error, at least to my mind


B

[iljubicic]

There is still a thin vertical line in the middle of the frame?!

[mib2berlin]

Hi, I have some issues with 23.4 and material nodes. Crash if i connect or disconnect material node to mesh in some cases.
In my test file it crash always i disconnect the specular material from mesh, click on mesh with material picker (node inspector is empty) -> change material to diffuse.

Cheers, mib

Edit: Could not upload a tar.gz file

http://www.simpleupload.net/download/52 ... ar.gz.html

[Nostromo]

thanks mib, we'll look at it, I think I know where it lies...

/M

[Synthercat]

Am I the only one with this bug:

sometimes (I think it has to do with the selected resolution) I get some random noise pixels that are on the far vertical part of the render
as you can

Since I think they are resolution related here are some quick test I did

1280 x 720 = 2 lines of pixels gone wrong
1024 x 512 = 4 lines of pixels gone wrong
material preview = 4 again (also seen in attached pic)

I thought it happens to others and is easily overcome by croping but a bug is still a bug and since I didn't saw anyone mentioning this one, here it is

Thank you for your efforts Refractive team!