From the current manual: Month / Day / GMT Offset / Local Time: These parameters can be used to accurately place the sun in the sky according to the date / time for the sun at the current longitude / latitude
It seems there are too many variables here. Having to manually set the GMT offset introduces human error potential if we want to get accurate 3D shadow/light studies.
Would it not be simpler if Octane sets the GMT offset automatically based on the geo-location (i.e. remove the control)? It would save us from having to find out if a client in Reykjavik has daylight saving time or not - and if so, having to change the GMT once we cross over the daylight savings dates. We have North offset geo-location for artistic freedom and full time/date control.
Perhaps others have uses for the GTM Offset setting that I am missing?
Best,
Seeker
Any point still having GMT offset?
- Seekerfinder
- Posts: 1600
- Joined: Tue Jan 04, 2011 11:34 am
Win 8(64) | P9X79-E WS | i7-3930K | 32GB | GTX Titan & GTX 780Ti | SketchUP | Revit | Beta tester for Revit & Sketchup plugins for Octane
I think it makes sense to have it in there. You could be doing an arch-vis for a customer in LA and you are in NY.
As Kavorka indicated, I tend to use for just tweaking shadows. Rarely is the actual location/time of any real consequence for me.
As Kavorka indicated, I tend to use for just tweaking shadows. Rarely is the actual location/time of any real consequence for me.
AMD-1100T 6 core, GTX-590 & GTX-480 1.5GB, 16GB 1600MHz RAM, 1TB WD 6GB/s, Win7 64bit, Blender 2.68a for Octane 2.2, Octane 1.20, Blender/Octane Server 2.2
I wish there was a north offset as well. Some times you just want to point the sun where you want it and not have to hunt and peck to get it pointed right.
Linux Mint 21.3 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 535.171
- Seekerfinder
- Posts: 1600
- Joined: Tue Jan 04, 2011 11:34 am
We've got date settings and north offset to do that to the nth degree.kavorka wrote:I use it to fine tune where my shadows are going
How is the Octane user's location relevant? If your customer is in LA, you set the scene location to LA, not NY, no?ephdot wrote:I think it makes sense to have it in there. You could be doing an arch-vis for a customer in LA and you are in NY.
Grimm, I just arranged that for you and installed it on your version of Octane overnight. If you look between the power and daylight model settings (in Daylight Environment), you will now find a north offset... (thank me later) - though I did mention that small detail in my original post.grimm wrote:I wish there was a north offset as well. Some times you just want to point the sun where you want it and not have to hunt and peck to get it pointed right.
Ok, seems like the message is not getting across. Lets try again...
The default GMT offset is that of Auckland, which is GMT+12. However, when we move the location, it stays GMT+12... This should not be. It should be computed in a 'physically based' piece of software, relevant to both location and time of year (taking into account local daylight savings adjustments). Again (for those not reading the full post) there are other ways of tweaking shadows / daylight to get the exact effect you want. GMT offset should not be one of them...
Best,
Seeker
You do not have the required permissions to view the files attached to this post.
Win 8(64) | P9X79-E WS | i7-3930K | 32GB | GTX Titan & GTX 780Ti | SketchUP | Revit | Beta tester for Revit & Sketchup plugins for Octane
*sigh* Ya know, I don't know how many times I have looked at that panel.Seekerfinder wrote:Grimm, I just arranged that for you and installed it on your version of Octane overnight. If you look between the power and daylight model settings (in Daylight Environment), you will now find a north offset... (thank me later) - though I did mention that small detail in my original post.grimm wrote:I wish there was a north offset as well. Some times you just want to point the sun where you want it and not have to hunt and peck to get it pointed right.
Seeker


Although it would be nice if they would put in the day/night terminator on the world display.
Linux Mint 21.3 x64 | Nvidia GTX 980 4GB (displays) RTX 2070 8GB| Intel I7 5820K 3.8 Ghz | 32Gb Memory | Nvidia Driver 535.171
How is the Octane user's location relevant? If your customer is in LA, you set the scene location to LA, not NY, no?ephdot wrote:I think it makes sense to have it in there. You could be doing an arch-vis for a customer in LA and you are in NY.
My bad with regard to the location. Somehow I read your post as setting it automatically based upon the location (locale settings) of the PC running Octane. That'll teach me to reply when I'm a few glasses of wine deep.

AMD-1100T 6 core, GTX-590 & GTX-480 1.5GB, 16GB 1600MHz RAM, 1TB WD 6GB/s, Win7 64bit, Blender 2.68a for Octane 2.2, Octane 1.20, Blender/Octane Server 2.2