Currently working on: reading sun rise/set time from MSTS environment file
PerryPlatypus, on 06 January 2023 - 03:34 PM, said:
Related to time zone, it would be really nice if we could input into the TRK file the time zone (using UTC format). And in the event that that line is not in the TRK file, then OR would do its own calculation that you propose to determine time zone (would that be based on Start Tile for simplicity's sake, or some geographic average of the extreme lat/lons for the route?)
Agreed, putting the time zone into the route data would mean we don't need the sun rise/set times and can instead calculate them - which also means they can vary based on where you are in the route (primarily long east/west routes I guess)
scottb613, on 06 January 2023 - 04:45 PM, said:
I think we need the weather system to have control of the shadow system to be able to deactivate it when overcast. Shadows look silly on overcast days.
I think the weather system should also have access to the brightness slider to represent various conditions. The image above is 100.
The shadows do disappear in more overcast scenarios, but this relationship likely needs to be evaluated along with all the other colour and brightness interactions
railguy, on 06 January 2023 - 05:14 PM, said:
Time Zone is not the only parameter necessary to achieve proper sunrise/sunset times, though. Latitude also must be in the calculation. For example (using the U.S.), both south-central Texas and central North Dakota are in the Central Time Zone, but sunrise/sunset times will be markedly different for each on the same day because of the difference in latitude, even though they are at similar longitude. Days are longer in the summer and shorter in the winter as one goes away from the equator at the same longitude.
We always have latitude and longitude because that's encoded into the terrain/world tile system, so with the addition of time zone I believe we have enough to calculate correct sun position for a given season
PerryPlatypus, on 06 January 2023 - 05:19 PM, said:
In the absence of the info in the TRK file, then ORTS can just have local/solar noon occurs at 12:00 p.m. on the clock.
I am going to try using the environment files as fallback, since the information is already there for sun rise/set, and it'll match MSTS
scottb613, on 08 January 2023 - 11:00 AM, said:
Would it be too much to have (4) hemispheres for clouds?
- Overcast Layer
- High Cloud Layer
- Middle Cloud Layer
- Low Cloud Layer
The "flattened dome" we have now in testing seems it would be good candidate for the Low Cloud Layer. The Overcast Layer should probably be the highest - so any cloud details included on the other layers could still be visible. Obviously - if performance is an issue - we can combine whatever layers are necessary to keep good performance.
This sounds interesting and multiple textured cloud domes certainly seems like the next logical progression for sophistication of the sky
This sort of change will necessarily come
after some of the more basic issues are addressed, but I would be encouraged to see people experimenting with new cloud textures (as has already happened!) that would be compatible with this
If you want a primitive test, you can put higher clouds onto SkyDome1 and lower clouds onto Clouds01 and see if it works (obviously limited by sky not moving, etc.)