OctaneRender® 1.024 beta 2.48 TEST (win) [OBSOLETE]

[radiance]

I think we have enough to do for the next update,
we will post our intentions in a few hours, when everyone is arrived at the office.
we will likely try to release the b version very soon.

radiance

[Ayertosco]

I'm having some problems importing the geometry on 2.48, it seems it can't load some polygons. This is what happens, tried to load the mesh on 2.47 and 2.46 and it gives absolutely no problem

Hmm, that is weird. We haven't changed much in that area. Could you please send a scene (OBJ/MTL file), that doesn't load correctly to [email protected] ?

Thanks,
Marcus

Hi, i did some other tests. It behaves this way only when i reload\relink the mesh on my scene, because loading the mesh on a new project from scatch seems to work flawlessy

[Timmaigh]

I'm having some problems importing the geometry on 2.48, it seems it can't load some polygons. This is what happens, tried to load the mesh on 2.47 and 2.46 and it gives absolutely no problem

Hmm, that is weird. We haven't changed much in that area. Could you please send a scene (OBJ/MTL file), that doesn't load correctly to [email protected] ?

Thanks,
Marcus

Hi, i did some other tests. It behaves this way only when i reload\relink the mesh on my scene, because loading the mesh on a new project from scatch seems to work flawlessy

There was the same issue on 2.47 already. in my case the it would either load, but geometry would be broken (missing polygons like on the posted pic) or Octane would shut down at the moment, when voxelising ends and new meshnode shoud appear. Loading the mesh on a new project, as has been said, works fine... so does relinking of the same mesh in 2.46b. ROUBAL was talking about this before, he just thought its down to insufficient memory during reloading, as his scene was big. In my case, the mesh was only 30MB obj file, so it was definitely not lack of RAM.

[Ayertosco]

There was the same issue on 2.47 already. in my case the it would either load, but geometry would be broken (missing polygons like on the posted pic) or Octane would shut down at the moment, when voxelising ends and new meshnode shoud appear. Loading the mesh on a new project, as has been said, works fine... so does relinking of the same mesh in 2.46b. ROUBAL was talking about this before, he just thought its down to insufficient memory during reloading, as his scene was big. In my case, the mesh was only 30MB obj file, so it was definitely not lack of RAM.

Strange, never had this problem on 2.47 and as you said, is 99% not a RAM issue, 'cause it's the same scene and with the same weight (only 2-3 simple portals more). I'll try to reduce the scene wieght leaving out some heavy textures and see what happens.

[Timmaigh]

There was the same issue on 2.47 already. in my case the it would either load, but geometry would be broken (missing polygons like on the posted pic) or Octane would shut down at the moment, when voxelising ends and new meshnode shoud appear. Loading the mesh on a new project, as has been said, works fine... so does relinking of the same mesh in 2.46b. ROUBAL was talking about this before, he just thought its down to insufficient memory during reloading, as his scene was big. In my case, the mesh was only 30MB obj file, so it was definitely not lack of RAM.

Strange, never had this problem on 2.47 and as you said, is 99% not a RAM issue, 'cause it's the same scene and with the same weight (only 2-3 simple portals more). I'll try to reduce the scene wieght leaving out some heavy textures and see what happens.

It happened to me on 2 different scenes, once as i said the geometry was broken, the other time Octane shut down. Thought its more common issue, when i saw ROUBALs thread, but now i see maybe not.
Well, there is a possibility, its a problem with textures, not geometry. New mesh with 2.47 loads for me with no textures, even if they applied with modelling app..and there is never an issue. Only when you try to replace meshnode.

[abstrax]

To recap the last posts: Do I understand it correctly, that the geometry is loaded correctly, but materials during relinking not? How do you relink - using the export plugin or using the reload button?

Thanks for your help,
Marcus

[abstrax]

do you want us to keep testing this or should we wait for test 'b'?

Well, if you find new issues that weren't reported yet, you are very welcome to report them of course. Tomorrow (Tuesday) we will release a version quite a few bug fixes and then Octane hopefully starts to become useful again.

Cheers,
Marcus

[ROUBAL]

For me I relink through the relink button in Octane.

I confirm that when relinking, both geometry is broken (only some parts of objects are shown), and materials settings are lost as well.

On my big city scene, after relinking I had only some parts of one car remaining, with broken materials ! Sorry, I didn't make a screen shot.

In a same object, some parts with some materials are missing. In my case, there are not always textures on these missing meshes or parts of meshes.

[Ayertosco]

The scene was created on 2.46. On 2.47 it loads correctly, both textures\materials and mesh.

On 2.48, if i load the same scene it behaves as shown on my pics, it seems a mesh problem because there are polygons missing but the textures are loaded. If i create a new scene and load the mesh on 2.48, it's loaded correctly. When i'm at home i'll try to load the scene on 2.47, erase some heavy textures and save the scene as a duplicate to see if it's a ram problem.

I reload the mesh using the "reload button" on Octane. All the textures\materials assignment have been made on Octane.

[abstrax]

Could you send us a scene that is broken when you open the OCS file, but works correctly, if the OBJ is loaded as a new mesh node? Please send it to [email protected] . Without an example scene and just some vague descriptions/screenshots on the forum it's extremely hard to fix this issue.

Thanks,
Marcus