not really, i didnt touch cubemaps nor water reflection settings wich are in crypted ENV to begin with ( you can read them tho ), even if i wanted i cant edit the water settings in general
CEnvGlobalSkyParameters
CEnvDialogLightParameters
CEnvGlobalLightParameters
CEnvWaterParameters
CEnvSunAndMoonParameters
CEnvGlobalFogParameters
CEnvWindParameters
CEnvFlareColorParameters
CEnvToneMappingParameters
CEnvBloomNewParameters
CEnvDistanceRangeParameters
CEnvColorModTransparencyParameters
CEnvShadowsParameters
CEnvNVSSAOParameters
CEnvMSSSAOParameters
CEnvSharpenParameters
CEnvMotionBlurParameters
CEnvRadialBlurParameters
CEnvDepthOfFieldParameters
just to name a few of the classes that are used to set up the environment definitions
all of which are not scriptable.
Imagine if we had a proper env editor what we could do with these classes and and their variables. but instead CDPR (who know this, since this has been a topic of discussion since day 0). Give us only a mod tools "light" kit that doens't allow us to properly edit environment definitions. which leaves us with brute forcing around with the files to hack in some nice settings which are obviously possible, but currently not really editable to our full desire.
i don't see why this should be a problem and not be possible by CDPR? If we can mess up the game with some "shitty" unicorn horse texture replacement then why not let us mess around with the environment definitions? Really makes no sense to me why they would prohibitively stop us from editing these settings.
unfortunately so far we will not get the the better fog, the far draw distance, the better lighting, etc. in at the same time. since all these are spread in different definitions and cant be used together while still looking cool but also not without causing problems like mentioned by essenthy.
Last edited: