[quote="DHR"]@helifax
I don't know what you fix for that issue, but also when you automatic inject fixing code to shaders, that fixing code sometimes apply in the wrong shader, only because the pattern or the constant use to "search" are the same.
This happens when you use lua script on Helix wrapper. Helix fix that issue in 2 ways:
1) You have to add some lines in the ini to bypass specific shaders hashes, or
2) Copy-Paste the shader untouch in the fixing folder[/quote]
Yupp:)
I am using the second variant:
- Automatic injection all the way
- Find shaders that are broken and "un-correct" them back to original form;)
The thing with this engine is that is loading the exact same shaders over and over again to create new Programs used by the game for different things. One thing I noticed is that even if the shaders are the same (vertex and pixel) it "combines" them in sets of unique "vertex + pixel = Program" sets.
So, I am eliminating or "un-correcting" based on this combination of unique Ps+Vs. It might not solve 100% of the cases but it should solve 90%.
The ID engine on the other hand it worked completely different when creating shaders (the source code was deleted after compilation and linkage) and there it was easier to cope with fixing things;))
Every engine adds a new thing to the puzzle I guess;)) (and is what makes things even more fun;) )
DHR said:@helifax
I don't know what you fix for that issue, but also when you automatic inject fixing code to shaders, that fixing code sometimes apply in the wrong shader, only because the pattern or the constant use to "search" are the same.
This happens when you use lua script on Helix wrapper. Helix fix that issue in 2 ways:
1) You have to add some lines in the ini to bypass specific shaders hashes, or
2) Copy-Paste the shader untouch in the fixing folder
Yupp:)
I am using the second variant:
- Automatic injection all the way
- Find shaders that are broken and "un-correct" them back to original form;)
The thing with this engine is that is loading the exact same shaders over and over again to create new Programs used by the game for different things. One thing I noticed is that even if the shaders are the same (vertex and pixel) it "combines" them in sets of unique "vertex + pixel = Program" sets.
So, I am eliminating or "un-correcting" based on this combination of unique Ps+Vs. It might not solve 100% of the cases but it should solve 90%.
The ID engine on the other hand it worked completely different when creating shaders (the source code was deleted after compilation and linkage) and there it was easier to cope with fixing things;))
Every engine adds a new thing to the puzzle I guess;)) (and is what makes things even more fun;) )
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Using latest version of the fix I just saw something similar like SEREGIN wrote (actually saw with previous version too). It must be noted that it is not a game breaking issue.
Save and screenshots for you.
(move looking at window and you will see it when objects are between you and window)
hm,take a look at second screenshot in [u]2D[/u]so to see them side by side,
you will see that double/buggy panel's edge is captured only from the left image, while double/buggy trolley's handle is only on the right image.
Don't know if it has to do with just sync/time captured or would help you at all.
Using latest version of the fix I just saw something similar like SEREGIN wrote (actually saw with previous version too). It must be noted that it is not a game breaking issue.
Save and screenshots for you.
(move looking at window and you will see it when objects are between you and window)
hm,take a look at second screenshot in 2Dso to see them side by side,
you will see that double/buggy panel's edge is captured only from the left image, while double/buggy trolley's handle is only on the right image.
Don't know if it has to do with just sync/time captured or would help you at all.
Yes the glass refraction is calculated very strange. In some places it works better than others.
Are you using the version released after Seregin reported the problems?
It is possible some glass refraction will look weird... I noticed a couple of them myself. I can remove the fix for the glass refraction altogether but then you will either get windows half white, half transparent.. miss-aligned etc. With the fix at least they render correctly from the geometry point of view, but some of them have a different refraction depth:)
Just try with the latest fix from the website as I already did fix a few issues with the glass, yesterday!
That problem should be solved in the last release, but let me know if it still isn't!
Yes the glass refraction is calculated very strange. In some places it works better than others.
Are you using the version released after Seregin reported the problems?
It is possible some glass refraction will look weird... I noticed a couple of them myself. I can remove the fix for the glass refraction altogether but then you will either get windows half white, half transparent.. miss-aligned etc. With the fix at least they render correctly from the geometry point of view, but some of them have a different refraction depth:)
Just try with the latest fix from the website as I already did fix a few issues with the glass, yesterday!
That problem should be solved in the last release, but let me know if it still isn't!
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
@Helifax, yesterday i play Omicron and all the windows are broken very bad, and the stage have a lot of windows.
Same issue than Seregin pictures. I play that way anyways (can't stop playing), my last savegame is not there...i will look at previous auto save to attach here is necessary.
@Helifax, yesterday i play Omicron and all the windows are broken very bad, and the stage have a lot of windows.
Same issue than Seregin pictures. I play that way anyways (can't stop playing), my last savegame is not there...i will look at previous auto save to attach here is necessary.
[quote="DHR"]@Helifax, yesterday i play Omicron and all the windows are broken very bad, and the stage have a lot of windows.
Same issue than Seregin pictures. I play that way anyways (can't stop playing), my last savegame is not there...i will look at previous auto save to attach here is necessary. [/quote]
This is with the last version of the fix from 17 hours ago? If it is, a savegame would be most helpful.
Thx
PS: you can make a quicksave by pressing F9:) and send it to me;)
DHR said:@Helifax, yesterday i play Omicron and all the windows are broken very bad, and the stage have a lot of windows.
Same issue than Seregin pictures. I play that way anyways (can't stop playing), my last savegame is not there...i will look at previous auto save to attach here is necessary.
This is with the last version of the fix from 17 hours ago? If it is, a savegame would be most helpful.
Thx
PS: you can make a quicksave by pressing F9:) and send it to me;)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....
Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....
[quote="ProgNoizes"]Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....[/quote]
Save your desired convergence using nvidia save convergence bound keys.
You can also modify the default start convergence in the ini file.
Alternatively use nvidia inspector and write your desired convergence in the SOMA profile.
ProgNoizes said:Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....
Save your desired convergence using nvidia save convergence bound keys.
You can also modify the default start convergence in the ini file.
Alternatively use nvidia inspector and write your desired convergence in the SOMA profile.
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
[quote="helifax"][quote="ProgNoizes"]Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....[/quote]
Save your desired convergence using nvidia save convergence bound keys.
You can also modify the default start convergence in the ini file.
Alternatively use nvidia inspector and write your desired convergence in the SOMA profile.[/quote]
That is the CTRL + F7 key? save in-game changes???
ProgNoizes said:Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....
Save your desired convergence using nvidia save convergence bound keys.
You can also modify the default start convergence in the ini file.
Alternatively use nvidia inspector and write your desired convergence in the SOMA profile.
That is the CTRL + F7 key? save in-game changes???
[quote="ProgNoizes"][quote="helifax"][quote="ProgNoizes"]Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....[/quote]
Save your desired convergence using nvidia save convergence bound keys.
You can also modify the default start convergence in the ini file.
Alternatively use nvidia inspector and write your desired convergence in the SOMA profile.[/quote]
That is the CTRL + F7 key? save in-game changes???[/quote]
I believe you are new to 3D Vision then...
- Under "Setup Stereoscopic 3D" change the keyboard keys.
- Be sure that Enable Advanced in-game settings are enabled
Use the keys from there to whatever values you have them set to.
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/66190/[/img]
ProgNoizes said:Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....
Save your desired convergence using nvidia save convergence bound keys.
You can also modify the default start convergence in the ini file.
Alternatively use nvidia inspector and write your desired convergence in the SOMA profile.
That is the CTRL + F7 key? save in-game changes???
I believe you are new to 3D Vision then...
- Under "Setup Stereoscopic 3D" change the keyboard keys.
- Be sure that Enable Advanced in-game settings are enabled
Use the keys from there to whatever values you have them set to.
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
here is the save game...
grab one savegame from the middle....maybe you have to look around....but there a lot of windows and glasses, all with the same issue.
here is the save game...
grab one savegame from the middle....maybe you have to look around....but there a lot of windows and glasses, all with the same issue.
[quote="DHR"]here is the save game...[/quote]
Big thanks;)
I'll give it a look when I get home this evening;) Probably is another shaders that needs "un-corrected":)
But all these save games will help me fix as many things as possible.
Obviously I am also playing the game but currently I am in Theta:) I believe Omicron is after:)
Thank you again!
Big thanks;)
I'll give it a look when I get home this evening;) Probably is another shaders that needs "un-corrected":)
But all these save games will help me fix as many things as possible.
Obviously I am also playing the game but currently I am in Theta:) I believe Omicron is after:)
Thank you again!
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
[quote="helifax"][quote="ProgNoizes"][quote="helifax"][quote="ProgNoizes"]Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....[/quote]
Save your desired convergence using nvidia save convergence bound keys.
You can also modify the default start convergence in the ini file.
Alternatively use nvidia inspector and write your desired convergence in the SOMA profile.[/quote]
That is the CTRL + F7 key? save in-game changes???[/quote]
I believe you are new to 3D Vision then...
- Under "Setup Stereoscopic 3D" change the keyboard keys.
- Be sure that Enable Advanced in-game settings are enabled
Use the keys from there to whatever values you have them set to.
[/quote]
Well, new new... couple of months now but yea, i already had advanced settings on and yes it was CTRL + F7 then... i wasn't sure as the game hang a bit when i hit CTRL + F7 and then just go on, so i didn't know sure if that saved the convergence because it not say save convergence but "save in-game changes" so i was thinking oh thats maybe some settings in-game and not saving convergence while CTRL + F7 is in the NVidia settings so i was confused a bit... but thanks
Though its a very short game, so this CTRL + F7 comes a bit late for me for this game anywayzzz,,,,,
ProgNoizes said:Hmm, i have another issue now related to the 3D fix i guess.....
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....
Save your desired convergence using nvidia save convergence bound keys.
You can also modify the default start convergence in the ini file.
Alternatively use nvidia inspector and write your desired convergence in the SOMA profile.
That is the CTRL + F7 key? save in-game changes???
I believe you are new to 3D Vision then...
- Under "Setup Stereoscopic 3D" change the keyboard keys.
- Be sure that Enable Advanced in-game settings are enabled
Use the keys from there to whatever values you have them set to.
Well, new new... couple of months now but yea, i already had advanced settings on and yes it was CTRL + F7 then... i wasn't sure as the game hang a bit when i hit CTRL + F7 and then just go on, so i didn't know sure if that saved the convergence because it not say save convergence but "save in-game changes" so i was thinking oh thats maybe some settings in-game and not saving convergence while CTRL + F7 is in the NVidia settings so i was confused a bit... but thanks
Though its a very short game, so this CTRL + F7 comes a bit late for me for this game anywayzzz,,,,,
The game is about 10-12 hours long. This is definitely not a short game. A short game is around 4-6 hours (yeah we have games around 4-6 hours length). It's defo not 100+ hours long but still it's an average length game.
Glad that this solved the issue for you. You can always replay the game if you liked it:) I know I will replay it quite a few times:) I am still to finish my first playthrough though:)
The game is about 10-12 hours long. This is definitely not a short game. A short game is around 4-6 hours (yeah we have games around 4-6 hours length). It's defo not 100+ hours long but still it's an average length game.
Glad that this solved the issue for you. You can always replay the game if you liked it:) I know I will replay it quite a few times:) I am still to finish my first playthrough though:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
[quote="helifax"]Yes the glass refraction is calculated very strange. In some places it works better than others.
Are you using the version released after Seregin reported the problems?
It is possible some glass refraction will look weird... I noticed a couple of them myself. I can remove the fix for the glass refraction altogether but then you will either get windows half white, half transparent.. miss-aligned etc. With the fix at least they render correctly from the geometry point of view, but some of them have a different refraction depth:)
Just try with the latest fix from the website as I already did fix a few issues with the glass, yesterday!
That problem should be solved in the last release, but let me know if it still isn't![/quote]
Yes, I was already using the last version of the fix, uploaded save(and screenshots) are with latest fix.
Haven't be yet to Omicron, I am on Theta too. I assume DHR's save will be great with all these glasses etc.
I have to say that until Theta fix is excellent,regardless that small issue with transparent objects (and their mirroring effect..). Eventually I will reach "O" today.
helifax said:Yes the glass refraction is calculated very strange. In some places it works better than others.
Are you using the version released after Seregin reported the problems?
It is possible some glass refraction will look weird... I noticed a couple of them myself. I can remove the fix for the glass refraction altogether but then you will either get windows half white, half transparent.. miss-aligned etc. With the fix at least they render correctly from the geometry point of view, but some of them have a different refraction depth:)
Just try with the latest fix from the website as I already did fix a few issues with the glass, yesterday!
That problem should be solved in the last release, but let me know if it still isn't!
Yes, I was already using the last version of the fix, uploaded save(and screenshots) are with latest fix.
Haven't be yet to Omicron, I am on Theta too. I assume DHR's save will be great with all these glasses etc.
I have to say that until Theta fix is excellent,regardless that small issue with transparent objects (and their mirroring effect..). Eventually I will reach "O" today.
Is this the problem you guys are seeing? As seen in the screenshots?
Except for the fact that items seen through the window/glass appear to have a ZOOM in effect I can't see any double images...
Is this what you are referring to? If it is, this works as intended because I had to push the refraction coefficient at farPlane, otherwise you see half of the glass in one eye and half in the other eye...
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/66197/[/img]
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/66198/[/img]
[img]https://forums.geforce.com/cmd/default/download-comment-attachment/66199/[/img]
I have also re-packed the wrapper again... Maybe something didn't get copied in my last re-pack.
Can you try again and be sure you remove all the files from the previous wrapper?
Big thx!!!
Edit: Although now I see another shader in one of the pictures, that create a duplicate image. Notice that part of the bar is duplicated in the first image? I'll hunt that one down and kill the bugger;)
Is this the problem you guys are seeing? As seen in the screenshots?
Except for the fact that items seen through the window/glass appear to have a ZOOM in effect I can't see any double images...
Is this what you are referring to? If it is, this works as intended because I had to push the refraction coefficient at farPlane, otherwise you see half of the glass in one eye and half in the other eye...
I have also re-packed the wrapper again... Maybe something didn't get copied in my last re-pack.
Can you try again and be sure you remove all the files from the previous wrapper?
Big thx!!!
Edit: Although now I see another shader in one of the pictures, that create a duplicate image. Notice that part of the bar is duplicated in the first image? I'll hunt that one down and kill the bugger;)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
Yupp:)
I am using the second variant:
- Automatic injection all the way
- Find shaders that are broken and "un-correct" them back to original form;)
The thing with this engine is that is loading the exact same shaders over and over again to create new Programs used by the game for different things. One thing I noticed is that even if the shaders are the same (vertex and pixel) it "combines" them in sets of unique "vertex + pixel = Program" sets.
So, I am eliminating or "un-correcting" based on this combination of unique Ps+Vs. It might not solve 100% of the cases but it should solve 90%.
The ID engine on the other hand it worked completely different when creating shaders (the source code was deleted after compilation and linkage) and there it was easier to cope with fixing things;))
Every engine adds a new thing to the puzzle I guess;)) (and is what makes things even more fun;) )
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Save and screenshots for you.
(move looking at window and you will see it when objects are between you and window)
hm,take a look at second screenshot in 2Dso to see them side by side,
you will see that double/buggy panel's edge is captured only from the left image, while double/buggy trolley's handle is only on the right image.
Don't know if it has to do with just sync/time captured or would help you at all.
i5 4670K 4.4 Ghz H2O, G.skill 16GB @2.4 Ghz C10, 2xGTX970 G1 SLI, AOC G2460PG, G-sync+3D Vision 2, Win 7x64(ssd), Games on RAID-0
Are you using the version released after Seregin reported the problems?
It is possible some glass refraction will look weird... I noticed a couple of them myself. I can remove the fix for the glass refraction altogether but then you will either get windows half white, half transparent.. miss-aligned etc. With the fix at least they render correctly from the geometry point of view, but some of them have a different refraction depth:)
Just try with the latest fix from the website as I already did fix a few issues with the glass, yesterday!
That problem should be solved in the last release, but let me know if it still isn't!
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Same issue than Seregin pictures. I play that way anyways (can't stop playing), my last savegame is not there...i will look at previous auto save to attach here is necessary.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
This is with the last version of the fix from 17 hours ago? If it is, a savegame would be most helpful.
Thx
PS: you can make a quicksave by pressing F9:) and send it to me;)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
When i try to puch a button for example, (i take a button as example here)
i must click next to the button in order to click it. Like the mouse is offsetted from everything.
hmm, can this be saved ? its the convergence that changes back to very high everytime i start the game.....
Save your desired convergence using nvidia save convergence bound keys.
You can also modify the default start convergence in the ini file.
Alternatively use nvidia inspector and write your desired convergence in the SOMA profile.
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
That is the CTRL + F7 key? save in-game changes???
I believe you are new to 3D Vision then...
- Under "Setup Stereoscopic 3D" change the keyboard keys.
- Be sure that Enable Advanced in-game settings are enabled
Use the keys from there to whatever values you have them set to.
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
grab one savegame from the middle....maybe you have to look around....but there a lot of windows and glasses, all with the same issue.
MY WEB
Helix Mod - Making 3D Better
My 3D Screenshot Gallery
Like my fixes? you can donate to Paypal: dhr.donation@gmail.com
Big thanks;)
I'll give it a look when I get home this evening;) Probably is another shaders that needs "un-corrected":)
But all these save games will help me fix as many things as possible.
Obviously I am also playing the game but currently I am in Theta:) I believe Omicron is after:)
Thank you again!
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Well, new new... couple of months now but yea, i already had advanced settings on and yes it was CTRL + F7 then... i wasn't sure as the game hang a bit when i hit CTRL + F7 and then just go on, so i didn't know sure if that saved the convergence because it not say save convergence but "save in-game changes" so i was thinking oh thats maybe some settings in-game and not saving convergence while CTRL + F7 is in the NVidia settings so i was confused a bit... but thanks
Though its a very short game, so this CTRL + F7 comes a bit late for me for this game anywayzzz,,,,,
Glad that this solved the issue for you. You can always replay the game if you liked it:) I know I will replay it quite a few times:) I am still to finish my first playthrough though:)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)
Yes, I was already using the last version of the fix, uploaded save(and screenshots) are with latest fix.
Haven't be yet to Omicron, I am on Theta too. I assume DHR's save will be great with all these glasses etc.
I have to say that until Theta fix is excellent,regardless that small issue with transparent objects (and their mirroring effect..). Eventually I will reach "O" today.
i5 4670K 4.4 Ghz H2O, G.skill 16GB @2.4 Ghz C10, 2xGTX970 G1 SLI, AOC G2460PG, G-sync+3D Vision 2, Win 7x64(ssd), Games on RAID-0
Except for the fact that items seen through the window/glass appear to have a ZOOM in effect I can't see any double images...
Is this what you are referring to? If it is, this works as intended because I had to push the refraction coefficient at farPlane, otherwise you see half of the glass in one eye and half in the other eye...
I have also re-packed the wrapper again... Maybe something didn't get copied in my last re-pack.
Can you try again and be sure you remove all the files from the previous wrapper?
Big thx!!!
Edit: Although now I see another shader in one of the pictures, that create a duplicate image. Notice that part of the bar is duplicated in the first image? I'll hunt that one down and kill the bugger;)
1x Palit RTX 2080Ti Pro Gaming OC(watercooled and overclocked to hell)
3x 3D Vision Ready Asus VG278HE monitors (5760x1080).
Intel i9 9900K (overclocked to 5.3 and watercooled ofc).
Asus Maximus XI Hero Mobo.
16 GB Team Group T-Force Dark Pro DDR4 @ 3600.
Lots of Disks:
- Raid 0 - 256GB Sandisk Extreme SSD.
- Raid 0 - WD Black - 2TB.
- SanDisk SSD PLUS 480 GB.
- Intel 760p 256GB M.2 PCIe NVMe SSD.
Creative Sound Blaster Z.
Windows 10 x64 Pro.
etc
My website with my fixes and OpenGL to 3D Vision wrapper:
http://3dsurroundgaming.com
(If you like some of the stuff that I've done and want to donate something, you can do it with PayPal at tavyhome@gmail.com)