Hi resident dummy here. I am totally confused by the wording of the instructions. Do I delete shaderpackage013 and then copy and rename shaderpackage017 to that? I don't even know why I'm asking BC I doubt anybody will respond but any help would be great. Thanks!
Create a backup of the shaderpackage of your number (for exemple, it was shaderpackage013 for him). Then, delete the original one and duplicate the shaderpackage017, and rename this copy with your shaderpackage number : shaderpackage013 in our exemple. Boom, it just works.
Just so everybody now knows, if you update your d3_d9.dll to the latest version on Boris Vorontsov's website (http://enbdev.com/mod_falloutnv_v0190.htm) this problem has now been fixed! Just copy the dll over and overwrite the original. It might be a good idea to back up the original but it shouldn't cause any problems. Then all of your setting should remain the same.
Oh... Well, I had trouble with weapons being transparent when aiming down sights even with this fix, but when I downloaded the new .dll everything was fixed. Maybe mine has been fixed because I disabled both Ambient Occlusion and Detailed Shadow. (I disabled Ambient Occlusion because it gives a massive performance hit whilst making very little visible difference, and Detailed Shadow because I was getting some weird effects from it.) I'll try playing with them then report back.
Well, it looks like the transparency problem does still persist with the new .dll, so apologies about my earlier excited message. If it is bothering people they can try disabling AO and Detailed Shadow, which should fix it, but your game will look quite different.
(mine happens to look a lot better without Detailed Shadow and perform far better without AO, I'm using Realism ENB v0.173 for anyone who wants to know.)
I'm using midhrastic enb and have come up on a conflict with this new mod: Fallout 3 - Enhanced Camera by LogicDragon.I think that camera mod alters the first person weapon models somehow. The imagespace modifier is active but doesn't apply to the first person weapon models and the transparency is back. Any suggestion for a fix?
No, it just moving the dof effect to your body when you look down, i have tested it, dont use it with this mod, i know.. less immersion but its whatever.
I have the same problem. As long as you are not aiming down the sights, the fix works. However, when you do aim down the sights, the gun as well as you hand become transparent.
it's not entirely without transparency but almost, this involved also changing some settings in the enbseries.ini i'm not at home right now so i'd have to do it from the top of my head..
i set LightingCurveDay=0.1, LightingCurveNight=0.1,LightingCurveInterior=0.1 in enbseries, and compensated with other settings in environment to get the desired(same) look. I also duplicated & changed the setting on your ISM to only back, so not front/back and gave it a little higher DOF value. you had set it to 0.00001, i set it to 0.00002. I apply this if IsControlpressed 6 i believe.. could be 4 to, remember that i'm not at home so i can't verify the codenumber..
And i don't see any transparency anymore.
Edit: just checked it but i think it is due to SSAO which i disabled that the effect was gone.
Yes I'm New To ENB * New as in i do not Mess around or toggle with the ini's much How would you disable SSAO i looked in the ENB ini and i am not Familiar with how, PLease & Thanks.
Cool, thanks for the quick response, I've been fiddling with them a bit to try and get rid of the first person gun blur at certain angles, but most of them look phenomenal in 3rd person. Thanks for all the work you put into this stuff, definitely looking forward to future releases by you. Endorsed for sure.
Steps 4&5 make no sense, i made the backup of shaderpackage13.sdp (the number my shader package was) now it says i have to copy shaderpackage17 and rename it to 13? what am i suppose to do with 17? Im sorry if i sound rude, im just very confused...
Give Feedback
72 comments
Edit: NVM, I got it! I'm a dummy.
To explain in another way the step 5:
Create a backup of the shaderpackage of your number (for exemple, it was shaderpackage013 for him). Then, delete the original one and duplicate the shaderpackage017, and rename this copy with your shaderpackage number : shaderpackage013 in our exemple. Boom, it just works.
Good game lads!
I'll try playing with them then report back.
Well, it looks like the transparency problem does still persist with the new .dll, so apologies about my earlier excited message. If it is bothering people they can try disabling AO and Detailed Shadow, which should fix it, but your game will look quite different.
(mine happens to look a lot better without Detailed Shadow and perform far better without AO, I'm using Realism ENB v0.173 for anyone who wants to know.)
cheers nexus site is down for maintenance 24/7 enjoy loading download lists and slamming your head on the keyboards
Never mind! wrong mod! It was actually Mart's mutant mod. sorry !
but when i click on it windows asks me with what to open it.
what do i do then?
i'm not at home right now so i'd have to do it from the top of my head..
i set LightingCurveDay=0.1, LightingCurveNight=0.1,LightingCurveInterior=0.1 in enbseries, and compensated with other settings
in environment to get the desired(same) look.
I also duplicated & changed the setting on your ISM to only back, so not front/back and gave it a little higher DOF value.
you had set it to 0.00001, i set it to 0.00002.
I apply this if IsControlpressed 6 i believe..
could be 4 to, remember that i'm not at home so i can't verify the codenumber..
And i don't see any transparency anymore.
Edit: just checked it but i think it is due to SSAO which i disabled that the effect was gone.
How would you disable SSAO i looked in the ENB ini and i am not Familiar with how, PLease & Thanks.
AOAmount=0
AOAmountInterior=0
in the enbseries.ini and it works fine