☁ Weather Maker ☁ AAA Clouds, Sky, Weather, Water, Volumetric Light & More!

You say in the set-up video tutorial that the player needs a kinematic Rigidbody and small sphere collider to properly trigger the zone and water call backs. I use Invector's third person controller, shooter-melee variety, and it has already set the Player up with a non-kinematic Rigidbody and capsule collider. Is this going to be a problem? How would you recommend I handle the player setup?

EDIT: The Invector Main Camera is not a child of the "Player," therefore, I am thinking I can place the kinematic Rigidbody and the tiny sphere collider on the Main Camera. I am assuming the Player and Main Camera will not interfere with each other because they are separate non-parented game objects. Will this work with Weather Maker?

EDIT: My thought above works, but when exiting a weather zone, the camera shifts oddly for a brief moment. I have the camera correctly set up, but I have not been able to solve this.

 

Can you put colliders on different layers? I like to have a control layer in addition to a physics layer, for example. On the control layer there will be the trigger colliders that set off music, sfx, etc.

 

I haven't tried that yet. For now, I brought Weather Maker into an Invecor demo scene. I have a non-Kinematic RidgedBody on the main camera with a tiny .001 dia. sphere colider set "Is Trigger." I have more testing to do, but the weather is working so far, including with the Post Processing Stack. Next, I will test a weather zone, and see if it triggers. Unfortunately the configurationCanvasPrefab does not work in a scene with the Invector 3rd person controller. Ultimately, this may not matter, as the ConfigurationCanvas is only for testing.

 

After spending many hours with Weather Maker, I have tested its features in an Invector Shooter demo scene, and then finally, brought Weather Maker into my asset filled scene. I figured out how to control ambient lighting with the ambient colors day in the day night cycle profile. Probably seems obvious to you. Unless changed, the default lighting leaves almost total darkness inside buildings, despite open doorways and windows, and under clouds.

F.Y.I. - Unity Plugin links on your digitalruby web site go to the old asset store, and therefore are broken.

 

WeatherMakerPrefab -> DayNightCycle -> Profile -> Ambient properties

 

I'm going to use it for VR. Is this single pass mode available?

 

I don’t support vr anymore.

 

That's very unfortunate. I'm currently using Weather Maker in my current project. Once I'm done a big chunk of my game development (almost there) I'm moving it to VR. Should I pull out Weather Maker and use a different asset then?

 

All the VR code I added is still in there. But due to constant Unity breakage I decided to drop support. If it does not work out of the box, send me the order number for a refund.

 

I completely understand your reasoning. It bugs me that Unity is so free with making breaking changes. And don't worry about a refund. I love the asset and I can use it for non-VR project. A lot of my current work is going to be used for a non-VR game.

 

I have a feature request. I like your provided events very much, but I would love to also have an on rain start, on rain end, and on snow start, on snow end. I would use then to trigger effects on my player such as wetness and cold.

 

Thanks for the feedback! You could start by monitoring the rain intensity value on the precipitation manager script and take action when it changes from zero to non-zero and vice versa. I will look into adding events for precipitation changing in the future.

 

FYI all Unity 2020.1.16 has broken a bunch of shader stuff, I am looking into it but this may be a Unity issue...

 

Hi,

Many errors are showing in Unity 2020.2.0f1.

I isolated the errors by creating an empty project with only importing Weather Maker.

When loading the "DemoScene" in editor:


Runtime of the "DemoScene" in editor:


It works fine with Unity 2019.4.6f1 on an empty project with only Weather Maker imported, and has no errors from "DemoScene".

Can you confirm if you can duplicate these errors on Unity 2020.2.0f1 ?

Thank you.

 

Please redownload latest version of asset. I have had to hack around some Unity breakages in their most recent updates.

 

I have redownloaded, but the same errors occur. I did a CRC SHA 256 on the new downloaded package and it is the same as the previous. Can you confirm?

 

You may have to clear out your app data folder C:/Users/[User]/AppData/Roaming/Unity/AssetStore*

 

Many days ago I had already cleared that folder even before doing the CRC SHA 256 hash and even before redownloading, but the same errors showed. Today, there seems to be an updated version of the package; the asset store shows December 21, 2020 as the date. I installed the new package but the errors are still there.

 

Hmmm. What target platform are you doing, just desktop with standard pipeline in a blank project?

I loaded Unity 2020.2 latest version with the asset store Weather Maker and didn't see these errors in standard pipeline Windows desktop.

 

Hey everyone, quick question. I'm using Weather Maker with the Opsive UCC, everything seems to be working but the null zones. Even with a simple set up, the null zones don't seem to have any effect. Anyone have any ideas? Thanks!

 

Yes, just Windows Desktop. I will wait and try again using in the next upcoming Unity 2020.2.* release to see what happens.

 

I've not tested that integration, if this is a deal breaker email me your order number for a refund at support@digitalruby.com

 

Today, I tried Weather Maker again with the new Unity 2020.2.2f1, but the errors still show. Again, it's in a blank project running the Weather Maker demo. Windows desktop using Unity built-in pipeline. And yes, I had cleared the download folder and redownloaded.

 

I will try with this new version and make sure. I had tried with 2020.2.1.

 

Here is what I see. I will force a new version on asset store and see if it helps.

 

Yes, I just redownloaded your new release v5.9.16 and the errors are still there when running.

But, after importing, many other new messages appeared which may help you identify further:



Assets\WeatherMaker\Prefab\Scripts\Weather\WeatherMakerPrecipitationProfileScript.cs(81,10): warning CS0618: 'ColorUsageAttribute.ColorUsageAttribute(bool, bool, float, float, float, float)' is obsolete: 'Brightness and exposure parameters are no longer used for anything. Use ColorUsageAttribute(bool showAlpha, bool hdr)'

Assets\WeatherMaker\Prefab\Scripts\Weather\WeatherMakerPrecipitationProfileScript.cs(86,10): warning CS0618: 'ColorUsageAttribute.ColorUsageAttribute(bool, bool, float, float, float, float)' is obsolete: 'Brightness and exposure parameters are no longer used for anything. Use ColorUsageAttribute(bool showAlpha, bool hdr)'

Assets\WeatherMaker\Prefab\Scripts\Weather\WeatherMakerPrecipitationProfileScript.cs(91,10): warning CS0618: 'ColorUsageAttribute.ColorUsageAttribute(bool, bool, float, float, float, float)' is obsolete: 'Brightness and exposure parameters are no longer used for anything. Use ColorUsageAttribute(bool showAlpha, bool hdr)'

Component at index 3 could not be loaded when loading game object 'MainCamera'. Removing it!

Component at index 2 could not be loaded when loading game object 'Camera2D'. Removing it!

Component at index 2 could not be loaded when loading game object 'Camera2D'. Removing it!

Shader warning in 'WeatherMaker/WeatherMakerFullScreenCloudsShader': WeatherMaker/WeatherMakerFullScreenCloudsShader shader is not supported on this GPU (none of subshaders/fallbacks are suitable)


Shader warning in 'WeatherMaker/WeatherMakerAtmosphericScatteringLookupShader': WeatherMaker/WeatherMakerAtmosphericScatteringLookupShader shader is not supported on this GPU (none of subshaders/fallbacks are suitable)


Shader error in 'WeatherMakerCloudProbeShader': Expected ',' between macro parameter names. at WeatherMakerCloudNoiseShaderInclude.cginc(424)

Shader error in 'WeatherMakerCloudProbeShader': Expected ',' between macro parameter names. at kernel CSMain at WeatherMakerCloudNoiseShaderInclude.cginc(424)

Shader error in 'WeatherMakerCloudProbeShader': Unterminated conditional expression. at WeatherMakerCloudNoiseShaderInclude.cginc(424)

Shader error in 'WeatherMakerCloudProbeShader': Unterminated conditional expression. at kernel CSMain at WeatherMakerCloudNoiseShaderInclude.cginc(424)

Shader error in 'WeatherMakerAtmosphereComputeShader': Expected ',' between macro parameter names. at WeatherMakerCloudNoiseShaderInclude.cginc(424)

Shader error in 'WeatherMakerAtmosphereComputeShader': Expected ',' between macro parameter names. at kernel WeatherMakerInscatteringLUT at WeatherMakerCloudNoiseShaderInclude.cginc(424)

Shader error in 'WeatherMakerAtmosphereComputeShader': Expected ',' between macro parameter names. at kernel WeatherMakerSkyboxLUT at WeatherMakerCloudNoiseShaderInclude.cginc(424)

Shader error in 'WeatherMakerAtmosphereComputeShader': Unterminated conditional expression. at WeatherMakerCloudNoiseShaderInclude.cginc(424)

Shader error in 'WeatherMakerAtmosphereComputeShader': Unterminated conditional expression. at kernel WeatherMakerInscatteringLUT at WeatherMakerCloudNoiseShaderInclude.cginc(424)

Shader error in 'WeatherMakerAtmosphereComputeShader': Unterminated conditional expression. at kernel WeatherMakerSkyboxLUT at WeatherMakerCloudNoiseShaderInclude.cginc(424)

 

What directx are you targeting?

 

DirectX 11 and above

 

Hello!
I can't do without URP in my project. Maybe there is an easy way to fix this please? If not, it's a pity. I have to look again for a weather asset with URP support.
The demo scene with URP on 2019.3.5.f1 works fine, but in 2019.4.14.f1 I get this. Changing the project version can be very painful for me =(

 

If I import the refresh update will it change any settings?
Also, I get these warnings?

 

I use Invector's 3rd person controller. When my player character dies, the scene resets. When the scene resets, a 2nd copy of Global Weather Zone and Weather Maker Prefab appear beneath Don't Destroy On Load in the Hierarchy. The console reacts with a group of duplicate instances red warnings and the scene lighting doubles, etc.

 

Hi Jeff - I'm having an issue with cloud shadow distance, where terrain beyond the player is brightly lit despite it being overcast and raining. The unity manual recommends using fog to hide distant terrain to negate this effect, which seems a good idea. Is there a way to do this with Weathermaker?

 

I'm also having an issue with cloud shadows disappearing when I look down - when I look towards the sky the shadows reappear. This doesn't happen with shadows cast by other objects. I have two scenes in the project, and this only happens in the second scene. The first scene is a single terrain, the second is multi-terrain. The second scene is extremely simple, and the problem occurs with different controllers/cameras, so I'm stumped.