Octane 1.0 Beta 1 Overview Video Posted
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.
-
enricocerica
- Posts: 1012
- Joined: Wed Nov 25, 2009 7:32 pm
- Contact:
Very cool video, great work Phil.
Modeling system : I7 32GB Windows 10 & Fujitsu Celsius H720
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
GPU : 1x Gigabyte GTX580 3GB + 1x MSI GTX780 3GB + 1x PALIT GTX780 6GB +1x Asus Stix GTX1070 8GB
http://www.myline.be
Gaussianspectrum works fine. You must choose a narrow width to get the color that you want. The default width of 400 is too wide. Try 50 or so and then slide the wavelength value to see the color change.
Regarding the floatimage versus the image data type, it is in the manual on page 23. Sometimes people will use a full color image as a diffuse and bump map / specular map when they don't have separate maps for each. Or, they could be using a full color image that only contains greyscale data.
The diffuse map needs all the color data so it should be loaded using the "image" data type. All the RGB data will be used by Octane Render. If the user then used that same image for a specular map or bump map (which only requires a greyscale image) then it would be a waste of video ram. If the user loads the full color image using the floatimage data type, the image is converted to a greyscale image which results in much lower video ram being used.
Here's an example.
I have a map of rusty steel that is 3.12 MB. When loaded into Octane using an "image" type, it takes up 43 MB. When that same image is loaded as a floatimage data type, then it takes up 11 MB.
Does that clarify the usage?
Regarding the floatimage versus the image data type, it is in the manual on page 23. Sometimes people will use a full color image as a diffuse and bump map / specular map when they don't have separate maps for each. Or, they could be using a full color image that only contains greyscale data.
The diffuse map needs all the color data so it should be loaded using the "image" data type. All the RGB data will be used by Octane Render. If the user then used that same image for a specular map or bump map (which only requires a greyscale image) then it would be a waste of video ram. If the user loads the full color image using the floatimage data type, the image is converted to a greyscale image which results in much lower video ram being used.
Here's an example.
I have a map of rusty steel that is 3.12 MB. When loaded into Octane using an "image" type, it takes up 43 MB. When that same image is loaded as a floatimage data type, then it takes up 11 MB.
Does that clarify the usage?
Win7 64| Two GTX 470s | Phenom II 920 | 8 GB
Win7 32| GTX 260 | Athlon X2 5000+ BE | 2 GB
Win7 32| GTX 260 | Athlon X2 5000+ BE | 2 GB
and the demo is coming.... when?
Im not 100% sure we need Radiance to answer but...and the demo is coming.... when?
I think its coming with the beta 2, wich is coming very soon
That mean its gonna be a demo with the features of the beta 2
Because the only difference between current demo and current beta is save / load + bugfixes etc...
http://Kuto.ch - Samuel Zeller - Freelance 3D Generalist and Graphic designer from Switzerland