I'am sorry.
To think like a german ingenieur with less knowledge about English it is hard to explain.
But i think i got you.
Man this was difficult, mib
Octane Render 1.022 beta2.2 RC2 available [obsolete]
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.
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.
- mib2berlin
- Posts: 1194
- Joined: Wed Jan 27, 2010 7:18 pm
- Location: Germany
Opensuse Leap 42.3/64 i5-3570K 16 GB
GTX 760 4 GB Driver: 430.31
Octane 3.08 Blender Octane
GTX 760 4 GB Driver: 430.31
Octane 3.08 Blender Octane
Texture gamma input seems not working.
Vista 64 , 2x Xeon 5440 - 24GB RAM, 1x GTX 260 & I7 3930 water cooled - 32GB RAM, 1 x GTX 480+ 1x8800 GTS 512
CGsociety gallery
My portfolio
My portfolio2 - under construction
Web site
Making of : pool scene - part1
CGsociety gallery
My portfolio
My portfolio2 - under construction
Web site
Making of : pool scene - part1
This slow down happens on a scene with no texture at all and diffuse shaders only. Light comes from HDRI but I try sun/sky and default light - pure white and its the same..a little bit slowerradiance wrote:are you sure everything is configured identically ?andrian wrote:I am getting a little slow down with RC2, it gives me 2.48 samples vs 2.95 samples on beta 2.1 on a simple scene. All manually imported and textured, its a simple interior room with no textures, lit by sun/sky, on GTX 480.
the scene file format is not compatible, so you need to recreate it, and you might have differences.
also keep in mind that this version needs to do a bit more work than 2.1,
it has recursive textures, which is quite a bit of additional/complex code to run through on each ray.
In fact, i was expecting an bigger slowdown, quite happy with the results.
I think some scenes might be a bit slower, and others a bit faster depending on how you configure your mats.
Radiance
Vista 64 , 2x Xeon 5440 - 24GB RAM, 1x GTX 260 & I7 3930 water cooled - 32GB RAM, 1 x GTX 480+ 1x8800 GTS 512
CGsociety gallery
My portfolio
My portfolio2 - under construction
Web site
Making of : pool scene - part1
CGsociety gallery
My portfolio
My portfolio2 - under construction
Web site
Making of : pool scene - part1
- SheepFactory
- Posts: 66
- Joined: Sat May 15, 2010 7:50 am
Any idea what might be causing the loss of realtime interactivity on my end? 2.1 runs silkys mooth.
you mean the sunsky updates ?SheepFactory wrote:Any idea what might be causing the loss of realtime interactivity on my end? 2.1 runs silkys mooth.
it's because 2.2 is a major rewrite of large areas of the render kernel for multi-gpu.
there are some multi-threading synchronization issues that cause the delay in updating the sunsky currently,
which we're fixing.
Radiance
Win 7 x64 & ubuntu | 2x GTX480 | Quad 2.66GHz | 8GB
weird - tested with a new scene and it's fine in both methods. I can't test with the scene that was troublesome before because I can't open scenes I saved with dual GPUs on OS X (but you know about this).radiance wrote:and directlighting is ok ?cgbeige wrote:ah, ok. It's in pathtracing with filtering off.
Radiance
One thing that has never worked but I forgot to mention: if you change the resolution of the image, it resets your subsampling settings.
- SheepFactory
- Posts: 66
- Joined: Sat May 15, 2010 7:50 am
radiance wrote:SheepFactory wrote:
there are some multi-threading synchronization issues that cause the delay in updating the sunsky currently,
which we're fixing.
Radiance
You guys rock. Thank you for the update.
It is a good idea to have the reported errors as a list in a forum?
Maybe one under "Commercial Product News & Releases" and a mirrored one under " Plugin Discussion/Support"
They should have only read access.
So the user can read the reported bugs and know, his one is reported before.
face
Maybe one under "Commercial Product News & Releases" and a mirrored one under " Plugin Discussion/Support"
They should have only read access.
So the user can read the reported bugs and know, his one is reported before.
face
Win10 Pro, Driver 378.78, Softimage 2015SP2 & Octane 3.05 RC1,
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578
64GB Ram, i7-6950X, GTX1080TI 11GB
http://vimeo.com/user2509578