This should never happend!!!!
OctaneRender® pre-Beta 2.42 (win/mac) [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.
- SamCameron

- Posts: 162
- Joined: Sun Jan 02, 2011 12:58 pm
Hey Octane developers, you really need to think about your anticopy method, is not fair to depend of your server to do our work, also some people cannot have internet connection, please think about it, cause the actual method is far from being good to work, right now I cannot render because your server is down or you have a problem with the connection, that's terrible.
I think the amount value of the mixed material is in the wrong direction.
Value0 gives me material2 and 1 gives me material1.
Most from us read from left to right, so the value0 should give us material1 and 1 should give us material2...
face
Value0 gives me material2 and 1 gives me material1.
Most from us read from left to right, so the value0 should give us material1 and 1 should give us material2...
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
Yes, it's so in v5 also. The mix material node mixes in the opposite direction of the mix texture node (which is the 'right' direction, imo).face wrote:I think the amount value of the mixed material is in the wrong direction.
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
cgmo.net
Hi,
Last night our servers were attacked by a DDOS attack, causing the database servers on all systems to be overloaded with hits.
All should be ok now, i've added some filters to hopefully protect against such an attack in the future.
Radiance
Last night our servers were attacked by a DDOS attack, causing the database servers on all systems to be overloaded with hits.
All should be ok now, i've added some filters to hopefully protect against such an attack in the future.
Radiance
Win 7 x64 & ubuntu | 2x GTX480 | Quad 2.66GHz | 8GB
Good to know its fixed. Its a pain when we cant check in here. Forum seems snappier too
It would be good if that Node Inspector bug introduced in 2.42 could be fixed if its going to be 6+ weeks until the next version....
It would be good if that Node Inspector bug introduced in 2.42 could be fixed if its going to be 6+ weeks until the next version....
Last edited by pixelrush on Sat Jan 22, 2011 8:51 am, edited 2 times in total.
i7-3820 @4.3Ghz | 24gb | Win7pro-64
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
tsk tsk, kids nowa days...radiance wrote:Hi,
Last night our servers were attacked by a DDOS attack, causing the database servers on all systems to be overloaded with hits.
All should be ok now, i've added some filters to hopefully protect against such an attack in the future.
Radiance
I'm glad you are on top of things, Radiance!
Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
You are wrong. That is really important for me (not only me of course). Now I have to write down all camera positions, targets, fovs. That is really annoying. BTW, BIG thanks to octane team for fixing external material node connection crash - now I don't need to pause octane before connection.suhail_spa wrote:its OK..this is not such a big issue anyway...abstrax wrote:Sorry, that wasn't meant with it. The change fixes the incorrect behaviour that when you reset your camera, the nodes in the node stack editor don't get updated. We didn't have time to look into the reconnection problem. Sorry. There are always gazillion thing to improve/fix/change, but we had to draw the line and focus on building the other platforms. I reckon Mac and Linux users will appreciate it.
But that's not the end of the development or the world
Cheers,
Marcus
