Metal gear solid V: The panthom pain
  14 / 15    
I can not launch the game on Windows 10 build 14390 if I roll back to built 10584.494 it works. So the problem is the Windows insider build. This build is not RTM. This could all change with final build so why don't we just wait till the final Windows build.
I can not launch the game on Windows 10 build 14390 if I roll back to built 10584.494 it works.

So the problem is the Windows insider build. This build is not RTM.

This could all change with final build so why don't we just wait till the final Windows build.

Gigabyte Z370 Gaming 7 32GB Ram i9-9900K GigaByte Aorus Extreme Gaming 2080TI (single) Game Blaster Z Windows 10 X64 build #17763.195 Define R6 Blackout Case Corsair H110i GTX Sandisk 1TB (OS) SanDisk 2TB SSD (Games) Seagate EXOs 8 and 12 TB drives Samsung UN46c7000 HD TV Samsung UN55HU9000 UHD TVCurrently using ACER PASSIVE EDID override on 3D TVs LG 55

Posted 07/17/2016 06:40 PM   
[quote="zig11727"]I can not launch the game on Windows 10 build 14390 if I roll back to built 10584.494 it works. So the problem is the Windows insider build. This build is not RTM. This could all change with final build so why don't we just wait till the final Windows build.[/quote] This confirms the issue being the insider preview I'm running. Thanks. But perhaps, this issue being looked into now, may provide some insight into what's in store for the RTM? It may even provide some insight into anything with the RTM that may cause issues for this game and other game fixes. But I gave in. I've rolled back, with macrium reflect, to an old image so I'm going to try that. Thanks DarkStarSword for your help. Hopefully the upcoming Anniversary update doesn't bonk a whole bunch of fixes and games.
zig11727 said:I can not launch the game on Windows 10 build 14390 if I roll back to built 10584.494 it works.

So the problem is the Windows insider build. This build is not RTM.

This could all change with final build so why don't we just wait till the final Windows build.


This confirms the issue being the insider preview I'm running. Thanks. But perhaps, this issue being looked into now, may provide some insight into what's in store for the RTM? It may even provide some insight into anything with the RTM that may cause issues for this game and other game fixes.

But I gave in. I've rolled back, with macrium reflect, to an old image so I'm going to try that. Thanks DarkStarSword for your help. Hopefully the upcoming Anniversary update doesn't bonk a whole bunch of fixes and games.

Posted 07/17/2016 09:55 PM   
Well, thanks for the heads up - hopefully this won't be as bad as the Evil update was to Win7, but it looks like we may have a headache coming in two weeks time.
Well, thanks for the heads up - hopefully this won't be as bad as the Evil update was to Win7, but it looks like we may have a headache coming in two weeks time.

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

Posted 07/18/2016 07:31 AM   
How easy is it to roll back from the insiders build if I want to test this? Do I need to make a backup or system restore point, or is it as easy as uninstalling a KB update?
How easy is it to roll back from the insiders build if I want to test this? Do I need to make a backup or system restore point, or is it as easy as uninstalling a KB update?

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

Posted 07/18/2016 08:30 AM   
@DarkStarSword I roll back with Aomei Backupper before I update anything I image my system drive but here is a link for the Microsoft roll back method. http://www.thewindowsclub.com/go-back-to-an-earlier-build-of-windows-10 Another word of advice once you update to the new build don't run disk clean with admin privileges on the system drive this will deleted the Microsoft rollback also I think today the final Windows 10 build will be released. I will update to the final build and post my results. Same problem with build 14393 doesn't load.
@DarkStarSword


I roll back with Aomei Backupper before I update anything I image my system drive but here is a link for the Microsoft roll back method.

http://www.thewindowsclub.com/go-back-to-an-earlier-build-of-windows-10

Another word of advice once you update to the new build don't run disk clean with admin privileges on the system drive this will deleted the Microsoft rollback also I think today the final Windows 10 build will be released.

I will update to the final build and post my results.

Same problem with build 14393 doesn't load.

Gigabyte Z370 Gaming 7 32GB Ram i9-9900K GigaByte Aorus Extreme Gaming 2080TI (single) Game Blaster Z Windows 10 X64 build #17763.195 Define R6 Blackout Case Corsair H110i GTX Sandisk 1TB (OS) SanDisk 2TB SSD (Games) Seagate EXOs 8 and 12 TB drives Samsung UN46c7000 HD TV Samsung UN55HU9000 UHD TVCurrently using ACER PASSIVE EDID override on 3D TVs LG 55

Posted 07/18/2016 09:51 AM   
@DarkStarSword: Log looks normal to me. The error code for the QueryInterface is not unusual, games often look for bizarre/unknown UUIDs and get errors. It's specified to run in windowed mode, and at a weird resolution. As a general idea I think it should be doing full screen, even if it's borderless. There are window occlusion and clipping events that I have no idea if they would continue to work. Also, it was my impression this game required fullscreen mode and would not work in 3D windowed. For the crashing state, assuming it's not introduced by the odd window state, it would be worth trying the allow_ d3dx.ini options to see if that can help. Since the crash was in dxgi, it's worth trying allow_dxgi1_2=1.
@DarkStarSword: Log looks normal to me. The error code for the QueryInterface is not unusual, games often look for bizarre/unknown UUIDs and get errors.

It's specified to run in windowed mode, and at a weird resolution. As a general idea I think it should be doing full screen, even if it's borderless. There are window occlusion and clipping events that I have no idea if they would continue to work. Also, it was my impression this game required fullscreen mode and would not work in 3D windowed.

For the crashing state, assuming it's not introduced by the odd window state, it would be worth trying the allow_ d3dx.ini options to see if that can help. Since the crash was in dxgi, it's worth trying allow_dxgi1_2=1.

Acer H5360 (1280x720@120Hz) - ASUS VG248QE with GSync mod - 3D Vision 1&2 - Driver 372.54
GTX 970 - i5-4670K@4.2GHz - 12GB RAM - Win7x64+evilKB2670838 - 4 Disk X25 RAID
SAGER NP9870-S - GTX 980 - i7-6700K - Win10 Pro 1607
Latest 3Dmigoto Release
Bo3b's School for ShaderHackers

Posted 07/18/2016 11:57 AM   
I agree with Zig as I always make an image before doing any kind of major upgrade. I use Macrium Reflect free, but it's personal choice. I hope the rollback works for you DarkStarSword and if you've got the storage space, make an image on your next reformat and reinstall. You'll be glad you did. In one way, I'm glad to see it's an issue with the upgrade and nothing related to my hardware going faulty or whatever. And I really appreciate those of you who are looking into this issue and hopefully it's not too much to come to a resolution before the final build is released. Your work is very much appreciated by all of us I'm sure. :)
I agree with Zig as I always make an image before doing any kind of major upgrade. I use Macrium Reflect free, but it's personal choice. I hope the rollback works for you DarkStarSword and if you've got the storage space, make an image on your next reformat and reinstall. You'll be glad you did.

In one way, I'm glad to see it's an issue with the upgrade and nothing related to my hardware going faulty or whatever. And I really appreciate those of you who are looking into this issue and hopefully it's not too much to come to a resolution before the final build is released. Your work is very much appreciated by all of us I'm sure. :)

Posted 07/18/2016 11:32 PM   
Fix is updated to work with Windows 10 anniversary. I've added a new workaround in the hooking features of 3DMigoto 1.2.43 for this game - skip_dxgi_device. MGSV:GZ will probably need the same done to it, but I haven't checked yet.
Fix is updated to work with Windows 10 anniversary. I've added a new workaround in the hooking features of 3DMigoto 1.2.43 for this game - skip_dxgi_device. MGSV:GZ will probably need the same done to it, but I haven't checked yet.

2x Geforce GTX 980 in SLI provided by NVIDIA, i7 6700K 4GHz CPU, Asus 27" VG278HE 144Hz 3D Monitor, BenQ W1070 3D Projector, 120" Elite Screens YardMaster 2, 32GB Corsair DDR4 3200MHz RAM, Samsung 850 EVO 500G SSD, 4x750GB HDD in RAID5, Gigabyte Z170X-Gaming 7 Motherboard, Corsair Obsidian 750D Airflow Edition Case, Corsair RM850i PSU, HTC Vive, Win 10 64bit

Alienware M17x R4 w/ built in 3D, Intel i7 3740QM, GTX 680m 2GB, 16GB DDR3 1600MHz RAM, Win7 64bit, 1TB SSD, 1TB HDD, 750GB HDD

Pre-release 3D fixes, shadertool.py and other goodies: http://github.com/DarkStarSword/3d-fixes
Support me on Patreon: https://www.patreon.com/DarkStarSword or PayPal: https://www.paypal.me/DarkStarSword

Posted 08/08/2016 12:52 PM   
hi, Just after windows anniversary update yesterday, No 3D can be activate in game with default or Max Payne 3 profiles even with or without the 3d fix patch by DSS Update v1.5... Anybodyelse?
hi,

Just after windows anniversary update yesterday, No 3D can be activate in game with default or Max Payne 3 profiles even with or without the 3d fix patch by DSS Update v1.5...

Anybodyelse?

http://photos.3dvisionlive.com/chtiblue/album/530b52d4cb85770d6e000049/3Dvision with 55" LG OLED EG920 interlieved 3D (3840x2160) overide mode, GTX 2080 Ti XC Ultra EVGA, core i5 @4.3GHz, 16Gb@2130, windows 7&10 64bit, Dolby Atmos 5.1.4 Marantz 6010 AVR

Posted 11/04/2016 12:12 PM   
[quote="chtiblue"]hi, Just after windows anniversary update yesterday, No 3D can be activate in game with default or Max Payne 3 profiles even with or without the 3d fix patch by DSS Update v1.5... Anybodyelse?[/quote] It only means that your game have change your screen to "windowed". Just go to Graphic Menu and change it back to "Fullscreen". Game/3Dfix works fine under Win10 Aniv.
chtiblue said:hi,

Just after windows anniversary update yesterday, No 3D can be activate in game with default or Max Payne 3 profiles even with or without the 3d fix patch by DSS Update v1.5...

Anybodyelse?

It only means that your game have change your screen to "windowed".
Just go to Graphic Menu and change it back to "Fullscreen".

Game/3Dfix works fine under Win10 Aniv.
Thanks SKAUT but I already thought about that, but no it was already fullscreen, I switched to windowed and back to full screen but no 3dvision at all and no 3dvision overlay... last dirver 375.76
Thanks SKAUT but I already thought about that, but no it was already fullscreen, I switched to windowed and back to full screen but no 3dvision at all and no 3dvision overlay...
last dirver 375.76

http://photos.3dvisionlive.com/chtiblue/album/530b52d4cb85770d6e000049/3Dvision with 55" LG OLED EG920 interlieved 3D (3840x2160) overide mode, GTX 2080 Ti XC Ultra EVGA, core i5 @4.3GHz, 16Gb@2130, windows 7&10 64bit, Dolby Atmos 5.1.4 Marantz 6010 AVR

Posted 11/04/2016 06:28 PM   
[quote="chtiblue"]Thanks SKAUT but I already thought about that, but no it was already fullscreen, I switched to windowed and back to full screen but no 3dvision at all and no 3dvision overlay... last dirver 375.76[/quote] I found another issue with Win10. Some games doesn't start in 3D if you install them on system drive. I had that with Fallout and some other game which I don`t remember. Definitely try to put this on another drive. You don`t have to download again. Just copy all to another drive then delete on Steam and them start installation on new destination. Steam will "Discover" existing files and installation will be over in few seconds. Try that.
chtiblue said:Thanks SKAUT but I already thought about that, but no it was already fullscreen, I switched to windowed and back to full screen but no 3dvision at all and no 3dvision overlay...
last dirver 375.76

I found another issue with Win10. Some games doesn't start in 3D if you install them on system drive. I had that with Fallout and some other game which I don`t remember. Definitely try to put this on another drive.

You don`t have to download again. Just copy all to another drive then delete on Steam and them start installation on new destination. Steam will "Discover" existing files and installation will be over in few seconds.

Try that.
Thanks, but It already isn't on system disk :(
Thanks, but It already isn't on system disk :(

http://photos.3dvisionlive.com/chtiblue/album/530b52d4cb85770d6e000049/3Dvision with 55" LG OLED EG920 interlieved 3D (3840x2160) overide mode, GTX 2080 Ti XC Ultra EVGA, core i5 @4.3GHz, 16Gb@2130, windows 7&10 64bit, Dolby Atmos 5.1.4 Marantz 6010 AVR

Posted 11/04/2016 07:56 PM   
[quote="chtiblue"]Thanks, but It already isn't on system disk :([/quote] Click right mouse button on desktop and choose "Display Settings". In new window under "Display" go to "Advanced Display Settings" and in there check if you have "3D Display mode" set to "On". In any case I would use DDU and make a fresh new drivers installation.
chtiblue said:Thanks, but It already isn't on system disk :(

Click right mouse button on desktop and choose "Display Settings". In new window under "Display" go to "Advanced Display Settings" and in there check if you have "3D Display mode" set to "On".

In any case I would use DDU and make a fresh new drivers installation.
Hello everyone! Sorry for reopening such a long-dead thread, but I have an issue which is driving me crazy and I have run out of ideas on how to solve it, so I thought I could ask the very knowledgeable people around here for help... :) The facts are these: I had bought the game back in september last year (price had gone down enough for me not to be able to pass on it anymore) and I immediately tried it with the magnificent DarkStarSword fix: everything was perfect, this game is truly amazing in 3D once properly fixed - huge thanks to DarkStarSword and everybody else working to keep 3DVision alive despite nVIDIA. Unfortunately after a couple of weeks of playing, I had to uninstall it since I had no time to play it... Three days ago I installed the game again to show a friend how MGSV in 3DVision compared to (outclassed) Ghost Recon Wildlands (and its 3DVision-less flatness). To my surprise, the game now shows several inconsistencies in 3D: - there is a very noticeable halo on everything (and it's not the CM halo: I made sure I was in true 3D mode) it's like something from the right-eye image sticks on the left-eye one... Something similar happens when SSAO or bloom aren't fixed, but I am almost 100% sure this wasn't happening back in september, I'm sure I would have noticed as it's very distracting - some objects (like some patches of grass and some clutter on the ground for example) are rendered on one eye but not on the other: this one I'm 100% sure wasn't happening back in september as it almost hurts the eyes This is what I tried so far, unfortunately with no appreciable result: 1. uninstalled & reinstalled DarkStarSword's fix via 3D Fix Manager (discarding backup and resetting every change in the 3D Fix and Settings tabs) 2. manually downloaded and installed the 3Dfix-MGSV_TPP-1.6.zip indicated on the HelixMod MGSV page 3. updated 3DMigoto version (ignoring the warning about this potentially breaking the fix, at least to give it a try) 4. (since I noticed the game had been patched on November 6, 2018 and I thought the patch could have introduced some changes in the shaders): reinstalled the september 2018 version of the game using the download_depot command from Steam console, before retrying steps 1 to 3 5. checked DarkStarSword's GitHub site: noticed there is a new 1.7 patch available which is not yet implemented by 3D Fix Manager, which is supposed to support a newer version of 3DMigoto - [s]unfortunately for the love of me I was unable to make it work, so I couldn't try it[/s] silly me, hadn't noticed I had to manually copy over the 3DMigoto 1.3.14 DLLs as the ones in there are just placeholders: in any case, even with the new fix, the halo is still there: darker areas of the image rendered on the left eye "carry over" to the right eye... The halo is still there... As I said, this has been driving me crazy for the last 3 days. Could this be an issue introduced by nVIDIA driver updates or Windows updates? Is anyone else having the same issue? Thanks a lot in advance for any information and/or help in this regard... P.S.: i tried lowering the shutter speed of my glasses to 100Hz and this seems to help so probably the halo is due to very high ghosting - although I cannot understand how it can increase... Is there something hardware/software related which can increase ghosting? I know it wasn't like this last september, and I never had to touch the 120Hz glass refresh setting before... Moreover, the grass & debris on the ground still look completely off, like when a game hasn't received the HelixMod treatment for the shaders... Does anybody have any clue on this? Again, thanks in advance... (Edit to report success in installing 1.7 version of DarkStarSword, to no avail) (2nd Edit to report issue partially due to ghosting, but grass & debris seeming to be shader related)
Hello everyone!

Sorry for reopening such a long-dead thread, but I have an issue which is driving me crazy and I have run out of ideas on how to solve it, so I thought I could ask the very knowledgeable people around here for help... :)

The facts are these: I had bought the game back in september last year (price had gone down enough for me not to be able to pass on it anymore) and I immediately tried it with the magnificent DarkStarSword fix: everything was perfect, this game is truly amazing in 3D once properly fixed - huge thanks to DarkStarSword and everybody else working to keep 3DVision alive despite nVIDIA.
Unfortunately after a couple of weeks of playing, I had to uninstall it since I had no time to play it...

Three days ago I installed the game again to show a friend how MGSV in 3DVision compared to (outclassed) Ghost Recon Wildlands (and its 3DVision-less flatness). To my surprise, the game now shows several inconsistencies in 3D:
- there is a very noticeable halo on everything (and it's not the CM halo: I made sure I was in true 3D mode) it's like something from the right-eye image sticks on the left-eye one... Something similar happens when SSAO or bloom aren't fixed, but I am almost 100% sure this wasn't happening back in september, I'm sure I would have noticed as it's very distracting
- some objects (like some patches of grass and some clutter on the ground for example) are rendered on one eye but not on the other: this one I'm 100% sure wasn't happening back in september as it almost hurts the eyes

This is what I tried so far, unfortunately with no appreciable result:
1. uninstalled & reinstalled DarkStarSword's fix via 3D Fix Manager (discarding backup and resetting every change in the 3D Fix and Settings tabs)
2. manually downloaded and installed the 3Dfix-MGSV_TPP-1.6.zip indicated on the HelixMod MGSV page
3. updated 3DMigoto version (ignoring the warning about this potentially breaking the fix, at least to give it a try)
4. (since I noticed the game had been patched on November 6, 2018 and I thought the patch could have introduced some changes in the shaders): reinstalled the september 2018 version of the game using the download_depot command from Steam console, before retrying steps 1 to 3
5. checked DarkStarSword's GitHub site: noticed there is a new 1.7 patch available which is not yet implemented by 3D Fix Manager, which is supposed to support a newer version of 3DMigoto - unfortunately for the love of me I was unable to make it work, so I couldn't try it silly me, hadn't noticed I had to manually copy over the 3DMigoto 1.3.14 DLLs as the ones in there are just placeholders: in any case, even with the new fix, the halo is still there: darker areas of the image rendered on the left eye "carry over" to the right eye...

The halo is still there... As I said, this has been driving me crazy for the last 3 days. Could this be an issue introduced by nVIDIA driver updates or Windows updates? Is anyone else having the same issue?

Thanks a lot in advance for any information and/or help in this regard...

P.S.: i tried lowering the shutter speed of my glasses to 100Hz and this seems to help so probably the halo is due to very high ghosting - although I cannot understand how it can increase... Is there something hardware/software related which can increase ghosting? I know it wasn't like this last september, and I never had to touch the 120Hz glass refresh setting before...
Moreover, the grass & debris on the ground still look completely off, like when a game hasn't received the HelixMod treatment for the shaders... Does anybody have any clue on this?

Again, thanks in advance...

(Edit to report success in installing 1.7 version of DarkStarSword, to no avail)
(2nd Edit to report issue partially due to ghosting, but grass & debris seeming to be shader related)

Posted 05/28/2019 09:52 AM   
  14 / 15    
Scroll To Top