NEW: OctaneRender 2.1 Released
Forum rules
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
For new users: this forum is moderated. Your first post will appear only after it has been reviewed by a moderator, so it will not show up immediately.
This is necessary to avoid this forum being flooded by spam.
I'm going to buy your product. I'm interested in OctaneRender plugin for CINEMA 4D, but If I do it now will this new version 2.1 or earlier version of the software? Or should I wait a little while to download updated version OctaneRender 2.1 with Cinema 4d Plugin? It will cost more or the same?
PLEASE, should respond my previous message!!
NOTE: I'm sorry for bad english due to mute 
i7-12700KF
2x16GB RAM@DDR4-3600
MSI PRO Z690-A DDR4
Zotac GF RTX 4090 <3
SSDs OCZ RD400 0.5TB and Crucial 2TB SATA3
HDD 1TB SATA2
LG BD-RE BH16NS40
PSU 1kW
CRT 19" Samtron 19"
i7-12700KF
2x16GB RAM@DDR4-3600
MSI PRO Z690-A DDR4
Zotac GF RTX 4090 <3
SSDs OCZ RD400 0.5TB and Crucial 2TB SATA3
HDD 1TB SATA2
LG BD-RE BH16NS40
PSU 1kW
CRT 19" Samtron 19"
hi,Maxim wrote:I'm going to buy your product. I'm interested in OctaneRender plugin for CINEMA 4D, but If I do it now will this new version 2.1 or earlier version of the software? Or should I wait a little while to download updated version OctaneRender 2.1 with Cinema 4d Plugin? It will cost more or the same?
As of this writing, the license available is v2.x (where 'x' may be 1, 20 or 999..). The v2.x commercial license of an OctaneRender edition is valid for previous releases, v2.x tests, and current v2.x releases of that specific edition.
So if you have v2 license of the C4D plugin edition, your v2.x updates are free for that edition. There is already a test release here http://render.otoy.com/forum/viewtopic.php?f=30&t=42607
i72630QM @ 2.00GHz | 6GB RAM | 2GB GeForce GT 540M | Win7 64bit
-
yaalimadad2006
- Posts: 2
- Joined: Tue Sep 30, 2014 8:24 pm
in the name of Allah.
Hello.
when you Supplies OpenCL 2.0 in order to Support AMD Graphics.
Please.
Thanks alot.
Ya Ali(A).
Hello.
when you Supplies OpenCL 2.0 in order to Support AMD Graphics.
Please.
Thanks alot.
Ya Ali(A).
No, no OpenCL support in future. And CUDA support is for NVIDIA GeForce cards only.yaalimadad2006 wrote:in the name of Allah.
Hello.
when you Supplies OpenCL 2.0 in order to Support AMD Graphics.
Please.
Thanks alot.
Ya Ali(A).
I!??Maxim wrote:thank you for information)) I love this software and I want to buy it soon
NOTE: I'm sorry for bad english due to mute
i7-12700KF
2x16GB RAM@DDR4-3600
MSI PRO Z690-A DDR4
Zotac GF RTX 4090 <3
SSDs OCZ RD400 0.5TB and Crucial 2TB SATA3
HDD 1TB SATA2
LG BD-RE BH16NS40
PSU 1kW
CRT 19" Samtron 19"
i7-12700KF
2x16GB RAM@DDR4-3600
MSI PRO Z690-A DDR4
Zotac GF RTX 4090 <3
SSDs OCZ RD400 0.5TB and Crucial 2TB SATA3
HDD 1TB SATA2
LG BD-RE BH16NS40
PSU 1kW
CRT 19" Samtron 19"
I believe I have found a bug
While editing mtl files for obj tree objects and testing resulting texture mappings in Octane , I discovered Octane still caches texture mapping information about each obj object node even once all instances are deleted.
This means if I re import a previously tested object into Octane after editing it's mtl file, the old mtl mapping is what still displays for that object (even though there is normal loading time to give appearance that tree object is in fact being loaded fresh rather than ‘remembered’)
This has cost me quite a bit of time in trying to figure out what I was doing wrong with my mtl scripting/or the alpha maps etc.
It seems mtl settings (at least) for obj object geometry are somehow cached or remembered by Octane even when object geometry itself is deleted?
Clicking to refresh or reload the node geometry makes no difference - the mtl mappings are not updated
The only workaround I found is to exit and restart Octane every time I want to test a mtl script.
To me this seems like a bug. Is it intended behaviour?
Following on from this, it would be fantastic if there could be an export node => obj+mtl+materials files option – because Octane has a much nicer way of setting up and testing mappings than manually scripting them directly in the obj mtl file.
Cheers
While editing mtl files for obj tree objects and testing resulting texture mappings in Octane , I discovered Octane still caches texture mapping information about each obj object node even once all instances are deleted.
This means if I re import a previously tested object into Octane after editing it's mtl file, the old mtl mapping is what still displays for that object (even though there is normal loading time to give appearance that tree object is in fact being loaded fresh rather than ‘remembered’)
This has cost me quite a bit of time in trying to figure out what I was doing wrong with my mtl scripting/or the alpha maps etc.
It seems mtl settings (at least) for obj object geometry are somehow cached or remembered by Octane even when object geometry itself is deleted?
Clicking to refresh or reload the node geometry makes no difference - the mtl mappings are not updated
The only workaround I found is to exit and restart Octane every time I want to test a mtl script.
To me this seems like a bug. Is it intended behaviour?
Following on from this, it would be fantastic if there could be an export node => obj+mtl+materials files option – because Octane has a much nicer way of setting up and testing mappings than manually scripting them directly in the obj mtl file.
Cheers
Octane Render for ArchiCAD 22 plugin v4.x | Octane Standalone 4.x
( 2x Nvidia 980 Ti) x 6MB VRAM | Intel I7 4470K | 32GB RAM | Windows 10
( 2x Nvidia 980 Ti) x 6MB VRAM | Intel I7 4470K | 32GB RAM | Windows 10