Hmmm... I don't have this game and had no idea that there was such a thing as "elusive targets" in it.
"Heads Up" for those that participate, one is available now, but this one doesn't seem to unlock anything new from what I read on the Steam Forums
https://www.gamecrate.com/hitman-2-how-complete-politician-elusive-target/22412
[quote="DHR"]I check and some recent update break those....already re-fix the clipping/culling...need to re-fix the mirror reflections and light shafts.....probably will do today.
Yep there are multiples mirror reflections shaders.[/quote]
Thanks a lot, DHR!
DHR said:I check and some recent update break those....already re-fix the clipping/culling...need to re-fix the mirror reflections and light shafts.....probably will do today.
Yep there are multiples mirror reflections shaders.
[quote="DHR"]Game is updated![/quote]
Paris looks perfect now, great job!
There's some light issue in the first mission of Hitman 2 however. It flickers when I look around.
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/77471/[/img]
I tried the previous version of the fix again, and it doesn't happen with it.
[quote="DHR"]Yep...was a typo in 1 shader...now is OK
redownload the fix.[/quote]
I can confirm that it's fixed now, thank you!
At first I thought it was something with my system and tried to install the latest driver to troubleshoot. Unfortunately I noticed that the error on exist that I saw in Hitman 1 ([url]https://forums.geforce.com/default/topic/917895/3d-vision/hitman-2016/post/6001386/#6001386[/url]) also exists here. It's not as easily reproducible like there, most likely because mirrors are disabled. But running the benchmark almost always causes it at the end.
Same way as with Hitman 1, it was related to the mirror shader override. As here it's disabled anyway, commenting it like
[code]
; new due a game update 3
[ShaderOverride_Mirror_Reflections18]
Hash=af001b724a721eef
Handling=skip
;ps-t100 = resolve_msaa ps-t39
;ps-t100 = stereo2mono ps-t100
;post ps-t100 = null
[/code]
is a good solution. But unfortunately it's not enough in case of Hitman 2. After a long troubleshooting, I found that another thing that triggers the error is the "GLACIER ENGINE: SHADOWS LIGHTS AND REFLECTIONS" section in ShaderFixes\Glacier2_DHR.ini. If I remove it, it also disables an important part of the fix, so it's not a good workaround.
Have you ever seen this issue? For example if you run the benchmark a couple of times? Sorry if it sounds like I'm complaining. It's really a minor inconvenience as it only happens after exiting the game. But I'm worried that 419.xx might be the last driver with 3D Vision support, and it would be good to find if there's a driver bug and maybe report it. It doesn't happen with 38x drivers.
DHR said:Yep...was a typo in 1 shader...now is OK
redownload the fix.
I can confirm that it's fixed now, thank you!
At first I thought it was something with my system and tried to install the latest driver to troubleshoot. Unfortunately I noticed that the error on exist that I saw in Hitman 1 (https://forums.geforce.com/default/topic/917895/3d-vision/hitman-2016/post/6001386/#6001386) also exists here. It's not as easily reproducible like there, most likely because mirrors are disabled. But running the benchmark almost always causes it at the end.
Same way as with Hitman 1, it was related to the mirror shader override. As here it's disabled anyway, commenting it like
; new due a game update 3
[ShaderOverride_Mirror_Reflections18]
Hash=af001b724a721eef
Handling=skip
;ps-t100 = resolve_msaa ps-t39
;ps-t100 = stereo2mono ps-t100
;post ps-t100 = null
is a good solution. But unfortunately it's not enough in case of Hitman 2. After a long troubleshooting, I found that another thing that triggers the error is the "GLACIER ENGINE: SHADOWS LIGHTS AND REFLECTIONS" section in ShaderFixes\Glacier2_DHR.ini. If I remove it, it also disables an important part of the fix, so it's not a good workaround.
Have you ever seen this issue? For example if you run the benchmark a couple of times? Sorry if it sounds like I'm complaining. It's really a minor inconvenience as it only happens after exiting the game. But I'm worried that 419.xx might be the last driver with 3D Vision support, and it would be good to find if there's a driver bug and maybe report it. It doesn't happen with 38x drivers.
Hi fellas. Sorry to jump in but has anyone managed to get SLI working?.
I'm having a hard time keeping 60fps with 3D vision on with medium settings from the get go. Dense populated areas are obviously going to be worse.
Hi fellas. Sorry to jump in but has anyone managed to get SLI working?.
I'm having a hard time keeping 60fps with 3D vision on with medium settings from the get go. Dense populated areas are obviously going to be worse.
@john105
strange..don't have a single crash playing this game. I'm using 417.35 drivers.
Today night i will run the benchmark multiples times to try to reproduce it.....but i play the entire game without a single crash...including ALT-TAB the game severals times to fix it, that normally put on risk the stability.
@john105
strange..don't have a single crash playing this game. I'm using 417.35 drivers.
Today night i will run the benchmark multiples times to try to reproduce it.....but i play the entire game without a single crash...including ALT-TAB the game severals times to fix it, that normally put on risk the stability.
Hi john105...i run the Benchmark (miami and bombay) several times....but i don't have a crash.
Also tested with 417.35 driver and 419.35 driver....i'm using win7....maybe is a win10 issue?
Hi john105...i run the Benchmark (miami and bombay) several times....but i don't have a crash.
Also tested with 417.35 driver and 419.35 driver....i'm using win7....maybe is a win10 issue?
[quote="DHR"]Hi john105...i run the Benchmark (miami and bombay) several times....but i don't have a crash.
Also tested with 417.35 driver and 419.35 driver....i'm using win7....maybe is a win10 issue?[/quote]
Thanks for trying. I'm also using win7.
It looks like it's something specific to my system then. But it's strange that it never happens with older drivers or with the changes I mentioned in [url]https://forums.geforce.com/default/topic/1079897/3d-vision/hitman-2/post/6008311/#6008311[/url]. Do you think something in the "GLACIER ENGINE: SHADOWS LIGHTS AND REFLECTIONS" section of Glacier2_DHR.ini can cause an issue? This part wasn't present in the Hitman 1 fix, so all I needed to do there was to disable mirrors (or leave them unfixed) to avoid this crash. It's clearly the same problem in both Hitman 1 and 2, because it only happens after exiting the game. I never seen such behavior in any other game.
DHR said:Hi john105...i run the Benchmark (miami and bombay) several times....but i don't have a crash.
Also tested with 417.35 driver and 419.35 driver....i'm using win7....maybe is a win10 issue?
Thanks for trying. I'm also using win7.
It looks like it's something specific to my system then. But it's strange that it never happens with older drivers or with the changes I mentioned in https://forums.geforce.com/default/topic/1079897/3d-vision/hitman-2/post/6008311/#6008311. Do you think something in the "GLACIER ENGINE: SHADOWS LIGHTS AND REFLECTIONS" section of Glacier2_DHR.ini can cause an issue? This part wasn't present in the Hitman 1 fix, so all I needed to do there was to disable mirrors (or leave them unfixed) to avoid this crash. It's clearly the same problem in both Hitman 1 and 2, because it only happens after exiting the game. I never seen such behavior in any other game.
So I played a little bit, and everything really looks perfect! I initially started playing Hitman 1, but when I learned that all Hitman 1 missions are included in Hitman 2 and the clipping/culling issue was nearly 100% fixed here, I decided to switch to it instead. Thanks again DHR for making it possible!
The only issue is the crash after exiting the game, but it's really a very minor thing.
[quote="unix_43"]Hi fellas. Sorry to jump in but has anyone managed to get SLI working?.
I'm having a hard time keeping 60fps with 3D vision on with medium settings from the get go. Dense populated areas are obviously going to be worse.[/quote]
I don't have SLI, but with my GTX 1080 fps is mostly in the 45-60 range with 1080p and everything on max (except HDR that my monitor doesn't support). Sometimes it goes as low as 35. But I only played training missions and Paris so far. I'm not sure if it gets worse after it. I'm fine with just >30 fps, so it's not a problem for me.
You can try to set export_shaders to 0 in d3dx.ini. I think it can affect the performance, but I didn't notice much of a difference myself.
So I played a little bit, and everything really looks perfect! I initially started playing Hitman 1, but when I learned that all Hitman 1 missions are included in Hitman 2 and the clipping/culling issue was nearly 100% fixed here, I decided to switch to it instead. Thanks again DHR for making it possible!
The only issue is the crash after exiting the game, but it's really a very minor thing.
unix_43 said:Hi fellas. Sorry to jump in but has anyone managed to get SLI working?.
I'm having a hard time keeping 60fps with 3D vision on with medium settings from the get go. Dense populated areas are obviously going to be worse.
I don't have SLI, but with my GTX 1080 fps is mostly in the 45-60 range with 1080p and everything on max (except HDR that my monitor doesn't support). Sometimes it goes as low as 35. But I only played training missions and Paris so far. I'm not sure if it gets worse after it. I'm fine with just >30 fps, so it's not a problem for me.
You can try to set export_shaders to 0 in d3dx.ini. I think it can affect the performance, but I didn't notice much of a difference myself.
If the sub titles and hud are out of screen and nothing else is, you can try just adding a stereo cutoff to the games profile. If included 3Dmigoto profile add the setting in d3dx.ini
Try this under the [Profile} section if d3DX ini or import to existing Nvidia profile.
Setting ID_0x709a1ddf = 0x4b1cd96b InternalSettingFlag=V0
This will not help if they are in screen though.
DHR made a post about this somewhere, but I can't remember where. If I can find it, I'll link it, but I'm unsure if it's viable when regex is used
If the sub titles and hud are out of screen and nothing else is, you can try just adding a stereo cutoff to the games profile. If included 3Dmigoto profile add the setting in d3dx.ini
Try this under the [Profile} section if d3DX ini or import to existing Nvidia profile.
Setting ID_0x709a1ddf = 0x4b1cd96b InternalSettingFlag=V0
This will not help if they are in screen though.
DHR made a post about this somewhere, but I can't remember where. If I can find it, I'll link it, but I'm unsure if it's viable when regex is used
@D-Man11
thank you but It doesn't work. The sub titles is auto-focusing Influenced by the geometry in its range,if looks down from the top of the character.sub titles got screen depth ,because it's close to the ground.
@D-Man11
thank you but It doesn't work. The sub titles is auto-focusing Influenced by the geometry in its range,if looks down from the top of the character.sub titles got screen depth ,because it's close to the ground.
"Heads Up" for those that participate, one is available now, but this one doesn't seem to unlock anything new from what I read on the Steam Forums
https://www.gamecrate.com/hitman-2-how-complete-politician-elusive-target/22412
Thanks a lot, DHR!
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
Paris looks perfect now, great job!
There's some light issue in the first mission of Hitman 2 however. It flickers when I look around.
I tried the previous version of the fix again, and it doesn't happen with it.
redownload the fix.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
I can confirm that it's fixed now, thank you!
At first I thought it was something with my system and tried to install the latest driver to troubleshoot. Unfortunately I noticed that the error on exist that I saw in Hitman 1 (https://forums.geforce.com/default/topic/917895/3d-vision/hitman-2016/post/6001386/#6001386) also exists here. It's not as easily reproducible like there, most likely because mirrors are disabled. But running the benchmark almost always causes it at the end.
Same way as with Hitman 1, it was related to the mirror shader override. As here it's disabled anyway, commenting it like
is a good solution. But unfortunately it's not enough in case of Hitman 2. After a long troubleshooting, I found that another thing that triggers the error is the "GLACIER ENGINE: SHADOWS LIGHTS AND REFLECTIONS" section in ShaderFixes\Glacier2_DHR.ini. If I remove it, it also disables an important part of the fix, so it's not a good workaround.
Have you ever seen this issue? For example if you run the benchmark a couple of times? Sorry if it sounds like I'm complaining. It's really a minor inconvenience as it only happens after exiting the game. But I'm worried that 419.xx might be the last driver with 3D Vision support, and it would be good to find if there's a driver bug and maybe report it. It doesn't happen with 38x drivers.
I'm having a hard time keeping 60fps with 3D vision on with medium settings from the get go. Dense populated areas are obviously going to be worse.
strange..don't have a single crash playing this game. I'm using 417.35 drivers.
Today night i will run the benchmark multiples times to try to reproduce it.....but i play the entire game without a single crash...including ALT-TAB the game severals times to fix it, that normally put on risk the stability.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
Also tested with 417.35 driver and 419.35 driver....i'm using win7....maybe is a win10 issue?
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
Thanks for trying. I'm also using win7.
It looks like it's something specific to my system then. But it's strange that it never happens with older drivers or with the changes I mentioned in https://forums.geforce.com/default/topic/1079897/3d-vision/hitman-2/post/6008311/#6008311. Do you think something in the "GLACIER ENGINE: SHADOWS LIGHTS AND REFLECTIONS" section of Glacier2_DHR.ini can cause an issue? This part wasn't present in the Hitman 1 fix, so all I needed to do there was to disable mirrors (or leave them unfixed) to avoid this crash. It's clearly the same problem in both Hitman 1 and 2, because it only happens after exiting the game. I never seen such behavior in any other game.
The only issue is the crash after exiting the game, but it's really a very minor thing.
I don't have SLI, but with my GTX 1080 fps is mostly in the 45-60 range with 1080p and everything on max (except HDR that my monitor doesn't support). Sometimes it goes as low as 35. But I only played training missions and Paris so far. I'm not sure if it gets worse after it. I'm fine with just >30 fps, so it's not a problem for me.
You can try to set export_shaders to 0 in d3dx.ini. I think it can affect the performance, but I didn't notice much of a difference myself.
stable screen depth ?
Try this under the [Profile} section if d3DX ini or import to existing Nvidia profile.
Setting ID_0x709a1ddf = 0x4b1cd96b InternalSettingFlag=V0
This will not help if they are in screen though.
DHR made a post about this somewhere, but I can't remember where. If I can find it, I'll link it, but I'm unsure if it's viable when regex is used
thank you but It doesn't work. The sub titles is auto-focusing Influenced by the geometry in its range,if looks down from the top of the character.sub titles got screen depth ,because it's close to the ground.