Are you ever going to share something?
Are you ever going to share something?
I don't get it, why did you give up on releasing your cutscene lighting mod after KNG released his?
While I don't agree with downgrades in general how can they give "options" in this instance. If Hairworks work with special code giving options to users can be impossible since they would have to implement all different codes for all those different versions. It is too much hassle.Also, seriously? They'be been downgrading the hairworks feature? I had my suspicions but I wasn't really sure. Is that reversible? The fps drop wasn't that bad (to me) and it wasn't bothering me at all. Why can't they keep things optional, customizable?
I'm getting lost, here. People are complaining about the downgrade the game has suffered since the demos (and I'm not talking about you, since I don't know how you feel about any of this) but are praising the hairworks downgrade because they favor performance over quality?While I don't agree with downgrades in general how can they give "options" in this instance. If Hairworks work with special code giving options to users can be impossible since they would have to implement all different codes for all those different versions. It is too much hassle.
because he did the same thing, minus the fact the i had working raining weather, wich he fixed later anyways , so releasing two mods doing the same thing is uselessI don't get it, why did you give up on releasing your cutscene lighting mod after KNG released his?
I don't think anybody is praising it. As for me, I was just explaining why it happened and why, imo, in this case CDPR had nothing better. For hairworks (as for all that concerns gameworks) the blame is mostly on Nvidia and their closed box approach at the thing. You cannot simply release, as a dev company, an option that's playable only by a single card release (Maxwell Nvidia cards) when it's not really tied to raw performance of your system but just purely bogging down everything else for the fault of business machinations.I'm getting lost, here. People are complaining about the downgrade the game has suffered since the demos (and I'm not talking about you, since I don't know how you feel about any of this) but are praising the hairworks downgrade because they favor performance over quality?
because he did the same thing, minus the fact the i had working raining weather, wich he fixed later anyways , so releasing two mods doing the same thing is useless
the weather in that gif is a custom one, but it has a very annoying bug that i cant correct right now, KNG and some crazy talented guys are working on decrypting the ENV files, once thats done i will be able to correct it and release it, for the moment am just trying to find good combinations , but i can already reveal the name of my mod, behold ....:
UNREALISTIC LIGHTING MOD
![]()
you don't get it, do you? It's literally the same thing. And you can't fix get back dark heavy clouds using the cutscene lighting. it just doesnt have the settings for dark heavy rainy clouds. They use a specific environment setup just to achieve dark heavy rainy clouds, the cutscene lighting settings "REPLACE" these settings. so what ever you try to do, you can't have these clouds, using the cutscene settings.No, hi does not fixed raining weathers, there is still cutscene lighting just everywhere.
Please, release your mod.
Hairworks was a janky little titbit thrown to the PC users. It was never used properly so might as well reduce its disproportionate effect on framerate.I'm getting lost, here. People are complaining about the downgrade the game has suffered since the demos (and I'm not talking about you, since I don't know how you feel about any of this) but are praising the hairworks downgrade because they favor performance over quality?
But what's the bug you talk about in your custom weather mod? Even if you don't release it publicly for now you could just give it here, internally, just to test (I personally like the colors that different weather gives, so just to see in action it would be fun as screenshots and videos are not the same thing). All in all we are modders, you know, and we love to dabble in these thingsyeah to be more clear, i didnt find a " proper " fix for the raining/storm weather, like KNG said, its just impossible now, what i did is simply not use cut scene light env file on theme, thats it
no.Is it possible to atleast fix the colours? Cutscene lighting has good colours, hair is white and not blue etc
There must be values for this?
the sun goes ape shit at down for like one or two hours, and unless someone fully decrypte the env files/compression ther's no way to fix it, i used master effect its not natural in game colors, but it still look better than default colors even without master effectBut what's the bug you talk about in your custom weather mod? Even if you don't release it publicly for now you could just give it here, internally, just to test (I personally like the colors that different weather gives, so just to see in action it would be fun as screenshots and videos are not the same thing). All in all we are modders, you know, and we love to dabble in these things![]()
Alright, thank youno.
at least, not yet.
yeah, I added some options to the install script for the mod on nexus. where you basically enter your own values:In the meantime just use this..
http://forums.cdprojektred.com/threads/36987-Witcher-3-Graphics?p=1776431&viewfull=1#post1776431
I set envblend to 0.8, its 0.7 in the zip, 0.7 is for no white problems (it doesnt remove any fog in the base game...) vs stronger ambient occlusion at 0.8. Yes you do have to hunt around all the csv's and replace the values intelligently to change them.
Something better is always nice but i'm not left wanting for any more.
Awesome. I haven't considered this myself, but asmodan also considered quickbms truncating the weather files (in his set you don't have to type force 7 times). Not sure if that makes a difference..?yeah, I added some options to the install script for the mod on nexus. where you basically enter your own values:
![]()