- Status
you must be doing something wrong, because we fixed these issue very early on
---------- Updated at 08:36 PM ----------
i think the problem will be more that we will have trouble re injecting an edited env file ( larger ) than the game rejecting it because it has a different size, did you notice anything that let you think the game will check bits in a given file ? might do it for *.bundle not sure for isolated/loaded files
that is simply because the lighting is different in the .env files used for the cutscenes, it's just much brighter than in the _specifically_ created .env file used for the (WT_Heavy_Clouds_Dark) weather preset called env_novigrad_dark_clouds_heavy.env.
You can't change that as of now, my mod just simply replaces all specific .env used for the weather presets with the file _specifically_ used files for the other weather presets.
As does exactly the other mod! Except that the envBlend value is set to 0.5 instead of 1.0. As in how much strength the environment settings file (cutscen_definition_global.env) blends in.
there is literally nothing different except the blend parameter only using 0.5, which isn't even the original cutscene value of 1.0.
Last edited:
Yeah, I know that, hope *.env files will be deserialized soon.)
No, it's just that cutscene lighting env file does not contain day darkening and dark sky in it like storm env files.
If Im wrong - will be very greatfull for help. Can you post screenshot with cutsceen light in rainstorm at 12am ingame?
of course it dosnt, and it shouldnt be used for raining/dark weather settings, its useless, they already have bright lighting and bloom, simple as that
---------- Updated at 08:46 PM ----------
**
Last edited:
So they are not editable in any meaningful way yet?
All of these values are controlled via curve in W2 REDkit. Curve that goes from 00.00 to 24.00h so that at any point during the ToD you can set a different value. Could these values point to that curve which is stored somewhere else?
I'd like something answered so we can reach full disclosure if you don't mind:
If you are able to blend cutscene env with the regular gamplay ones - does that mean that the "cutscene lighting" env is not different or has "improved lighting accuracy" and "higher quality ambient occlusion, and shadowing" than the gameplay env? It's just a different ToD setup that use the same variables with different values (more bloom, more AO, etc...), right?
you're not wrong. It can't be like the original since all he did, was exactly as in my mod replace every .env file used with cutscen_definition_global.env and then only using 0.5 half the strength the settings are blended.
It doesn't make any sense, you can't get the original dark heavy clouds to work using cutscen_definition_global.env, that's why they they load env_novigrad_dark_clouds_heavy.env for the weather preset.
you cant blend 2 env file, ther's one slot for one single env file in every weather preset, for example " clear " weather does not have any env file you can just slap it thereSo they are not editable in any meaningful way yet?
All of these values are controlled via curve in W2 REDkit. Curve that goes from 00.00 to 24.00h so that at any point during the ToD you can set a different value. Could these values point to that curve which is stored somewhere else?
I'd like something answered so we cane reach full disclosure if you don't mind:
If you are able to blend cutscene env with the regular gamplay ones - does that mean that the "cutscene lighting" env is not different or has "improved lighting accuracy" and "higher quality ambient occlusion, and shadowing" than the gameplay env? It's just a different ToD setup that use the same variables with different values (more bloom, more AO, etc...), right?
however you have 3 slot for fx/clouds, so can go crazy use any fx/clouds combination you want
you don't blend with regular ones. you REPLACE regular ones (specifically created for that specific weather preset) with cutscene.env, hence you can't achieve dark clouds since dark clouds are only dark because of different light used. and the light used in cutscene.env is just to bright to have the clouds appear as dark clouds. thats the point, you still load the same CLOUDS, all you change is the replaced .env files!!!
True, but in this way the effect is subtler so much part of, for example, the overexposed sky in certain circumstances is practically gone (as the too "brownish" filter). It is a simple but elegant trick, actually (many times the more efficacious things are simple ones).
oh ok then Asmodean shared his version not mine, that make more sense
I didn't mean blend and use both env's I meant blend them in a new env.
But still, I'd like like the answer to this:
But still, I'd like like the answer to this:
Thanks.
this table from fireundubh is based on what Sir_Kane decompiled from the game's scripts. I don't know if I can post that here, but what I'm talking about is the source of the game. Here's a snippet:
also, skomski, the guy who released the debug console mod already released a very early version of a script-loader that allows you to load your own scripts that you compiled using witcher 3's script compiler.
also pay attention to
InitializeEffectManager();
envMgr = new W3EnvironmentManager in this;
envMgr.Initialize();
btw, we're all hanging out on #gibbed on synIRC.
Last edited:
I actually think that he is talking of a different thing here. He simply sees no dark clouds at all (no less dark than default). He probably loaded a save with a storm going on and so the rain loads but the sky doesn't load properly (as all default saves loaded with the mod).
What it happens in the case is exactly what he describes: the sky is strange (opaque but lightened, it's difficult to explain), there are no clouds (as in all loaded save games from the default lightning scheme) but rain is actually there. So it seems like it is raining but without the "dark clouds" (as he puts it).
Storms definitely appear with the mod; they appears either on yours that has no "blending", they are just less dark than usual given the higher luminance of the cutscene lightning (but with the Asmodean changes they are almost the same as in the default game; still less dark but less noticeable, as for night).
Last edited:
Just updated the Cutscene Lighting Mod. You can now choose your own envBlend strength (lighting intensity) values to see what fits you best.
Download: http://www.nexusmods.com/witcher3/mods/154/
Download: http://www.nexusmods.com/witcher3/mods/154/
Attachments
Yes there is nothing wrong with those values. It will be quite an improvement, IMO.
You have to define what significant improvement means to you though. A CSDS0=3 is going to produce slightly blurrier shadows than CSDS0=1, but the benefit is in covering a larger area with C0.
So at 3072, here's a quick comparison of 1/1/1.5/1.5 vs 3/2/2/2
1/1/1.5/1.5 vs 3/2/2/2
Ultra: Cascades 0/1 don't even reach the house, placing the house in cascade 2 which is quite blurry.
Custom: Cascade 0 covers a much larger area and Cascade 1 expands to cover the house. Cascade 2 is limited to the distant shadows.
1/1/1.5/1.5 vs 3/2/2/2
Ultra: Cascade 1<->2 transition is highly visible. Tree shadows look bad in cascade 2.
Custom: Pushes the cascade transition far enough away from you so that you won't see it so closely.
I broke down each cascade and used some Photoshop trickery to isolate each cascade. So below is a visual representation of the cascade breakdown at each setting. Ignore the area where Geralt is... had to remove him because he changed position too much.
Cascade 0 is RED
Cascade 1 is GREEN
Cascade 2 is BLUE
1/1/1.5/1.5
3/2/2/2
You can see there is a much better cascade distribution. Since cascade 0 has higher texture resolution than cascade 1 (regardless of scale value), you want to try to make cascade 0 take up a good chunk of the screen. You want cascade 1 to take up slightly less, and cascade 2 even less than that. The default values aren't much of a problem outside of cities, but inside cities you have a lot of distant, tall buildings so the end up getting caught up in lower quality cascades and taking up a lot of the screen.
You'd have to define "best".
1. Do cascade transitions bother you? That is, do you notice the small object shadows pop in at the 0<->1 border?
2. Is "best" maximum sharpness or maximum distance? Which is more important if it's a blend?
3. Do you have FoliageDistanceScale at above-Ultra values?
I would say that setting FoliageDistanceScale to something as high as 6 is a requirement for "best shadows". Setting it to 3 is a good compromise. If you have FoliageDistanceScale set to 3-6 you need to assure your further cascades actually reach to cover them. You'd also want to increase FoliageShadowDistanceScale above Ultra as well, which covers smaller bushes and things.
If you do adjust the foliage distances, then something like 8/4/2/1 may simply not be far enough. So you may need 8/4/4/2. I just haven't gotten around to testing this yet because finding an extremely distant, clear view with lots of trees is kind of difficult. Right now I'm on an old video card while I wait for my Step-Up to a 980 Ti to get here.
So, if you want the highest possible shadow resolution,
1. Set CascadeShadowmapSize to 8192.
2. Set C0 scale to 4-8. Don't set C0 scale above 8 or you start losing significant spatial resolution in C0. Lower than 4 is probably a waste of the resolution.
3. Don't set C1 scale above C0's scale or you will worsen the resolution difference at the C0<->C1 cascade transition.
3a. Like I showed in my last post, setting C0+C1 too high can cause really weird looking distant LOD, especially buildings in Novigrad... So you may not want C1 to exceed 4.
4. C2 and C3, you only increase as far as you need to cover your foliage distance. Neither should need to exceed 4, and a minimum of 2 is wise.
Also, try setting CascadeShadowQuality to 4 if it was set at 1. I'm still trying to figure out if this is shadow multisampling or what. I simply can't replicate the enormous differences that Nvidia showed in their comparison (though they appear to have swapped the images).
---
A good balance for CascadeShadowMapSize=4096 is 4/3/3/2 if you want higher than Ultra foliage distance. You might get away with 4/3/2/2. If seeing the C0<->C1 transition that close to the camera absolutely destroys your immersion or whatever, you can set C0 to 5 or 6 but just realize that you're starting to harm shadow quality.
--
I personally think the benefits of 8192 vs 4096 are not worth it. I would say the difference is too subtle for the performance impact. The number of scenes where you would notice any difference is just too small, considering they have about the same spatial resolution (at the settings suggested).
I think that once REDKit 2 comes out, that we will see mods which increase the number of objects which will render in C1. It would then be more beneficial to stay at 4096 and keep C0 at 4 max. Because once you no longer see as much shadow pop-in there isn't much point in keeping C0 so large.
Last edited:
What values were by default in 0.3 mod?Just updated the Cutscene Lighting Mod. You can now choose your own envBlend strength (lighting intensity) values to see what fits you best.
Download: http://www.nexusmods.com/witcher3/mods/154/
- Status