If you are using overlays at all and having problems they should be disabled. That said I am in fact using MSI afterburner and from my testing it doesn't matter if its on or off I still get the same issues.
Last night I tried with the shader cache on in SLI after rolling back to the .65 driver per lostis directions and aero off and it did not work for me. I think there is some randomness to this whole thing which I think likely points to the drm again.
So if it doesn't work for you I would say no.
btw that broken crestwood shader I attached in a save in my last post also occurs in the Crestwood bandit fortress
If you are using overlays at all and having problems they should be disabled. That said I am in fact using MSI afterburner and from my testing it doesn't matter if its on or off I still get the same issues.
Last night I tried with the shader cache on in SLI after rolling back to the .65 driver per lostis directions and aero off and it did not work for me. I think there is some randomness to this whole thing which I think likely points to the drm again.
So if it doesn't work for you I would say no.
btw that broken crestwood shader I attached in a save in my last post also occurs in the Crestwood bandit fortress
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
[quote="necropants"]Broken Shader in Crestwood. Its a pretty obscure place out of the way and I don't think I have seen this particular effect anywhere else so I can see why it may have been missed.
Cheers.
[/quote]
Thank you - I will sort this out, it's a decal shader and the fix is routine fortunately.
necropants said:Broken Shader in Crestwood. Its a pretty obscure place out of the way and I don't think I have seen this particular effect anywhere else so I can see why it may have been missed.
Cheers.
Thank you - I will sort this out, it's a decal shader and the fix is routine fortunately.
[quote="necropants"]If you are using overlays at all and having problems they should be disabled. That said I am in fact using MSI afterburner and from my testing it doesn't matter if its on or off I still get the same issues.
Last night I tried with the shader cache on in SLI after rolling back to the .65 driver per lostis directions and aero off and it did not work for me. I think there is some randomness to this whole thing which I think likely points to the drm again.
So if it doesn't work for you I would say no.
btw that broken crestwood shader I attached in a save in my last post also occurs in the Crestwood bandit fortress
[/quote]
As much as I hate those long loading screens I think I am going to stick with shader cache off and SLI for now. I just finished playing through from the beginning to the first tutorial for the tactical cam with the party of four without any crashes. Now, I know there was no loading there, but at least it did not crash. Not sure if it mattered but I did disable Aero just in case.
Now I did run into two 3D display issues. At the point of the first wraith the portion of the HUD that displays your abilities choices was at different positions in each eye (I have HUD at 0.0). But, after a little walking around it sorted itself out. Then at the point that I meet Solas and Varric after the fairly long cutscene the 3D was messed up. I may be totally off on this but it almost seemed like certain areas that get HBAO were rendering in only one eye and dark in the other. I saved, did Alt-F4 and reloaded without issue (though that is a slow process). I then played on through the first combat with the tactical cam with no issues. At that point I saved and am calling it a night for the game.
Hopefully it will continue to behave at least this well. Oh, all of this was with MSI Afterburner running.
And despite all the controversy about the mouse controls, I decided to try playing with my Xbox controller just out of curiosity and I think I actually prefer it for this game over the mouse. I mainly mention this because I am not sure if any others have used the 3D fix with the controller HUD. I am not sure if that is why I had that momentary issue with the abilities displaying in the bottom right corner at different positions in each eye. I never noticed that before with the mouse and keyboard HUD, but I played further in the game tonight than I had before.
And, yes, I definitely agree there is a lot of randomness to this, and I would not be surprised if the DRM is at least partially at fault. Unfortunately I think we will be stuck with DRM in most games for a while.
Thanks again for the assistance.
necropants said:If you are using overlays at all and having problems they should be disabled. That said I am in fact using MSI afterburner and from my testing it doesn't matter if its on or off I still get the same issues.
Last night I tried with the shader cache on in SLI after rolling back to the .65 driver per lostis directions and aero off and it did not work for me. I think there is some randomness to this whole thing which I think likely points to the drm again.
So if it doesn't work for you I would say no.
btw that broken crestwood shader I attached in a save in my last post also occurs in the Crestwood bandit fortress
As much as I hate those long loading screens I think I am going to stick with shader cache off and SLI for now. I just finished playing through from the beginning to the first tutorial for the tactical cam with the party of four without any crashes. Now, I know there was no loading there, but at least it did not crash. Not sure if it mattered but I did disable Aero just in case.
Now I did run into two 3D display issues. At the point of the first wraith the portion of the HUD that displays your abilities choices was at different positions in each eye (I have HUD at 0.0). But, after a little walking around it sorted itself out. Then at the point that I meet Solas and Varric after the fairly long cutscene the 3D was messed up. I may be totally off on this but it almost seemed like certain areas that get HBAO were rendering in only one eye and dark in the other. I saved, did Alt-F4 and reloaded without issue (though that is a slow process). I then played on through the first combat with the tactical cam with no issues. At that point I saved and am calling it a night for the game.
Hopefully it will continue to behave at least this well. Oh, all of this was with MSI Afterburner running.
And despite all the controversy about the mouse controls, I decided to try playing with my Xbox controller just out of curiosity and I think I actually prefer it for this game over the mouse. I mainly mention this because I am not sure if any others have used the 3D fix with the controller HUD. I am not sure if that is why I had that momentary issue with the abilities displaying in the bottom right corner at different positions in each eye. I never noticed that before with the mouse and keyboard HUD, but I played further in the game tonight than I had before.
And, yes, I definitely agree there is a lot of randomness to this, and I would not be surprised if the DRM is at least partially at fault. Unfortunately I think we will be stuck with DRM in most games for a while.
Thanks again for the assistance.
CPU: i7 5930K, 4.5 (125x36) with Corsair H100i | MB: Asus Rampage V Extreme (1401 Bios) | GPU: NVIDIA RTX 2080 Ti | RAM: Corsair Vengeance 32 GB DDR4 2666MHz (4x8GB) | Storage: Crucial MX100 512 GB SSD (OS & Apps), 2 Seagate 1TB Serial ATA HD 7200/32MB/SATA-3G (Data - RAID 1) | PSU: Corsair HX1000W | Chassis: Cooler Master HAF X | OS: Win 10 Pro 1809
[quote="mike_ar69"][quote="necropants"]Broken Shader in Crestwood. Its a pretty obscure place out of the way and I don't think I have seen this particular effect anywhere else so I can see why it may have been missed.
Cheers.
[/quote]
Thank you - I will sort this out, it's a decal shader and the fix is routine fortunately.[/quote]
[color="orange"][b]** UPDATED TO V7[/b][/color]
Fixes more decal shaders, and in particular the reported Crestwood location. I ran around a bit and did not see any additional decal issues.
necropants said:Broken Shader in Crestwood. Its a pretty obscure place out of the way and I don't think I have seen this particular effect anywhere else so I can see why it may have been missed.
Cheers.
Thank you - I will sort this out, it's a decal shader and the fix is routine fortunately.
** UPDATED TO V7
Fixes more decal shaders, and in particular the reported Crestwood location. I ran around a bit and did not see any additional decal issues.
Awesome mike, sorry I think I just found another problem. There is a dungeon at the dam area in the bandit fortress which has the grey screen issue.
Save attached at area entrance, looks fine when you load but take a few steps...
Awesome mike, sorry I think I just found another problem. There is a dungeon at the dam area in the bandit fortress which has the grey screen issue.
Save attached at area entrance, looks fine when you load but take a few steps...
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
[quote="necropants"]Awesome mike, sorry I think I just found another problem. There is a dungeon at the damn area in the bandit fortress which has the grey screen issue.
Save attached at area entrance, looks fine when you load but take a few steps...[/quote]
Hi - no problem, thanks for the save game :-) I will do it tomorrow though, it's 2am here and I'm beat (my MBA course is a lot of work lol).
necropants said:Awesome mike, sorry I think I just found another problem. There is a dungeon at the damn area in the bandit fortress which has the grey screen issue.
Save attached at area entrance, looks fine when you load but take a few steps...
Hi - no problem, thanks for the save game :-) I will do it tomorrow though, it's 2am here and I'm beat (my MBA course is a lot of work lol).
If you restart your PC or start your PC it is necessary to do this with a clean C:\Users\USERNAME\AppData\Local\Temp\NVIDIA Corporation\NV_Cache folder. So delete all files before restarting or shut down. Otherwise with shader-cahce=on the game did not work (broken 3D).
Confirmed that 2 times.
If you restart your PC or start your PC it is necessary to do this with a clean C:\Users\USERNAME\AppData\Local\Temp\NVIDIA Corporation\NV_Cache folder. So delete all files before restarting or shut down. Otherwise with shader-cahce=on the game did not work (broken 3D).
Confirmed that 2 times.
Like my work? Donations can be made via PayPal to: rauti@inetmx.de
Yeah, still doesn't work for me. Was doing this anyway. Such a wierd situation...
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
[quote="necropants"]Yeah, still doesn't work for me. Was doing this anyway. Such a wierd situation...[/quote]For me Windows 7 reinstallstion helps. May you have the posebilety to do this on a new partition, just to check it out.
[quote="LordK77"]since V7 i've got in the right corner the fps in green, normal ? How disable it ?[/quote]PerfOverlay.DrawFps 0 in User.cfg
[quote="necropants"]Awesome mike, sorry I think I just found another problem. There is a dungeon at the dam area in the bandit fortress which has the grey screen issue.
Save attached at area entrance, looks fine when you load but take a few steps...[/quote]
Hi found it and fixed it, will update the blog shortly.
necropants said:Awesome mike, sorry I think I just found another problem. There is a dungeon at the dam area in the bandit fortress which has the grey screen issue.
Save attached at area entrance, looks fine when you load but take a few steps...
Hi found it and fixed it, will update the blog shortly.
[quote="Losti"][quote="necropants"]Yeah, still doesn't work for me. Was doing this anyway. Such a wierd situation...[/quote]For me Windows 7 reinstallstion helps. May you have the posebilety to do this on a new partition, just to check it out.
[quote="LordK77"]since V7 i've got in the right corner the fps in green, normal ? How disable it ?[/quote]PerfOverlay.DrawFps 0 in User.cfg[/quote]
I am actually upgrading motherboard and CPU tomorrow so I will start with a fresh install as per your recommendations in a previous post and.... fingers crossed :P
Cheers Mike you legend. Will continue to post a save for any issues I find but hopefully that's the last of it.
necropants said:Yeah, still doesn't work for me. Was doing this anyway. Such a wierd situation...
For me Windows 7 reinstallstion helps. May you have the posebilety to do this on a new partition, just to check it out.
LordK77 said:since V7 i've got in the right corner the fps in green, normal ? How disable it ?
PerfOverlay.DrawFps 0 in User.cfg
I am actually upgrading motherboard and CPU tomorrow so I will start with a fresh install as per your recommendations in a previous post and.... fingers crossed :P
Cheers Mike you legend. Will continue to post a save for any issues I find but hopefully that's the last of it.
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
[quote="necropants"][quote="Losti"][quote="necropants"]Yeah, still doesn't work for me. Was doing this anyway. Such a wierd situation...[/quote]For me Windows 7 reinstallstion helps. May you have the posebilety to do this on a new partition, just to check it out.
[quote="LordK77"]since V7 i've got in the right corner the fps in green, normal ? How disable it ?[/quote]PerfOverlay.DrawFps 0 in User.cfg[/quote]
I am actually upgrading motherboard and CPU tomorrow so I will start with a fresh install as per your recommendations in a previous post and.... fingers crossed :P
Cheers Mike you legend. Will continue to post a save for any issues I find but hopefully that's the last of it.
[/quote]
I hope it works for you. I have not posted the last fix yet (it will be "v8"), hopefully tonight.
necropants said:Yeah, still doesn't work for me. Was doing this anyway. Such a wierd situation...
For me Windows 7 reinstallstion helps. May you have the posebilety to do this on a new partition, just to check it out.
LordK77 said:since V7 i've got in the right corner the fps in green, normal ? How disable it ?
PerfOverlay.DrawFps 0 in User.cfg
I am actually upgrading motherboard and CPU tomorrow so I will start with a fresh install as per your recommendations in a previous post and.... fingers crossed :P
Cheers Mike you legend. Will continue to post a save for any issues I find but hopefully that's the last of it.
I hope it works for you. I have not posted the last fix yet (it will be "v8"), hopefully tonight.
[quote="necropants"]
I am actually upgrading motherboard and CPU tomorrow so I will start with a fresh install as per your recommendations in a previous post and.... fingers crossed :P
Cheers Mike you legend. Will continue to post a save for any issues I find but hopefully that's the last of it.
[/quote]
In addition: I have updated DX11 in Windows 7 (not only installed from DAI_Install folder), this brings more performance and wont afflict stability or behavior of the FIX (V7).
________________________________________________________________________________________________________________
I have also noticed that LOADING a game did not need ALT+TAB for 3D is ok. It is some random issue if 3D is ok or not. Even with traveling. BUT ALT+TAB prevents trave-crashes!! But seems not to be necessary for correct 3D kick in.
The most errors for wrong 3D is only in some textures, not the whole 3D. Like the hair of a chars, the dors or some equipment like bags, weapons or tents in camps. Kicking in 3D correctly after travel or loading seems to be a 50 % chance for me, optimistically i would say 66 % (2 of 3 cases).
Also there seems to be no constant working issue for when you ALT+TAB or kick in 3D again, neither with timings. ALT+TAB is also working with the same results in beeing OK if you do it in the first period of the loading screen, and if you wait 10 seconds or 5 seconds, it is working if you do it on the card-loading-screen right after it appears or after 2 or 5 seconds. There is no constance. BUT: ALT+TAB on loading WILL prevent crashing. This is the only constance i have found out.
[b]In conclusion:[/b] Cleaning the Shader-Cache dir will make it possible to use shader-cahce=on and have no influence on the 3D is working or not after loading or traveling, even with shader-cache=off. But shader-cache=on will makes loading significant faster. Restarting with filled shader-cache-dir will lead you to broken 3D, so clean it before restarting and before starting a game. And ALT+TAB will prevent crashes after loading but do not try to figure out a "best point" to do this, or be affraid or unsure when you do it, because there is no constance and there is no "best moment" ....just do it, broken 3D is not an issue of the moment when or how long you ALT+TAB.
[b]==> This is what i can report after 1 week of playing the game with the FIX an may not be the law! [/b]
necropants said:
I am actually upgrading motherboard and CPU tomorrow so I will start with a fresh install as per your recommendations in a previous post and.... fingers crossed :P
Cheers Mike you legend. Will continue to post a save for any issues I find but hopefully that's the last of it.
In addition: I have updated DX11 in Windows 7 (not only installed from DAI_Install folder), this brings more performance and wont afflict stability or behavior of the FIX (V7).
I have also noticed that LOADING a game did not need ALT+TAB for 3D is ok. It is some random issue if 3D is ok or not. Even with traveling. BUT ALT+TAB prevents trave-crashes!! But seems not to be necessary for correct 3D kick in.
The most errors for wrong 3D is only in some textures, not the whole 3D. Like the hair of a chars, the dors or some equipment like bags, weapons or tents in camps. Kicking in 3D correctly after travel or loading seems to be a 50 % chance for me, optimistically i would say 66 % (2 of 3 cases).
Also there seems to be no constant working issue for when you ALT+TAB or kick in 3D again, neither with timings. ALT+TAB is also working with the same results in beeing OK if you do it in the first period of the loading screen, and if you wait 10 seconds or 5 seconds, it is working if you do it on the card-loading-screen right after it appears or after 2 or 5 seconds. There is no constance. BUT: ALT+TAB on loading WILL prevent crashing. This is the only constance i have found out.
In conclusion: Cleaning the Shader-Cache dir will make it possible to use shader-cahce=on and have no influence on the 3D is working or not after loading or traveling, even with shader-cache=off. But shader-cache=on will makes loading significant faster. Restarting with filled shader-cache-dir will lead you to broken 3D, so clean it before restarting and before starting a game. And ALT+TAB will prevent crashes after loading but do not try to figure out a "best point" to do this, or be affraid or unsure when you do it, because there is no constance and there is no "best moment" ....just do it, broken 3D is not an issue of the moment when or how long you ALT+TAB.
==> This is what i can report after 1 week of playing the game with the FIX an may not be the law!
Like my work? Donations can be made via PayPal to: rauti@inetmx.de
Last night I tried with the shader cache on in SLI after rolling back to the .65 driver per lostis directions and aero off and it did not work for me. I think there is some randomness to this whole thing which I think likely points to the drm again.
So if it doesn't work for you I would say no.
btw that broken crestwood shader I attached in a save in my last post also occurs in the Crestwood bandit fortress
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
Thank you - I will sort this out, it's a decal shader and the fix is routine fortunately.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
As much as I hate those long loading screens I think I am going to stick with shader cache off and SLI for now. I just finished playing through from the beginning to the first tutorial for the tactical cam with the party of four without any crashes. Now, I know there was no loading there, but at least it did not crash. Not sure if it mattered but I did disable Aero just in case.
Now I did run into two 3D display issues. At the point of the first wraith the portion of the HUD that displays your abilities choices was at different positions in each eye (I have HUD at 0.0). But, after a little walking around it sorted itself out. Then at the point that I meet Solas and Varric after the fairly long cutscene the 3D was messed up. I may be totally off on this but it almost seemed like certain areas that get HBAO were rendering in only one eye and dark in the other. I saved, did Alt-F4 and reloaded without issue (though that is a slow process). I then played on through the first combat with the tactical cam with no issues. At that point I saved and am calling it a night for the game.
Hopefully it will continue to behave at least this well. Oh, all of this was with MSI Afterburner running.
And despite all the controversy about the mouse controls, I decided to try playing with my Xbox controller just out of curiosity and I think I actually prefer it for this game over the mouse. I mainly mention this because I am not sure if any others have used the 3D fix with the controller HUD. I am not sure if that is why I had that momentary issue with the abilities displaying in the bottom right corner at different positions in each eye. I never noticed that before with the mouse and keyboard HUD, but I played further in the game tonight than I had before.
And, yes, I definitely agree there is a lot of randomness to this, and I would not be surprised if the DRM is at least partially at fault. Unfortunately I think we will be stuck with DRM in most games for a while.
Thanks again for the assistance.
CPU: i7 5930K, 4.5 (125x36) with Corsair H100i | MB: Asus Rampage V Extreme (1401 Bios) | GPU: NVIDIA RTX 2080 Ti | RAM: Corsair Vengeance 32 GB DDR4 2666MHz (4x8GB) | Storage: Crucial MX100 512 GB SSD (OS & Apps), 2 Seagate 1TB Serial ATA HD 7200/32MB/SATA-3G (Data - RAID 1) | PSU: Corsair HX1000W | Chassis: Cooler Master HAF X | OS: Win 10 Pro 1809
** UPDATED TO V7
Fixes more decal shaders, and in particular the reported Crestwood location. I ran around a bit and did not see any additional decal issues.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
Save attached at area entrance, looks fine when you load but take a few steps...
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
Hi - no problem, thanks for the save game :-) I will do it tomorrow though, it's 2am here and I'm beat (my MBA course is a lot of work lol).
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
Core i7-4700 HQ - GTX 970 - Windows 7 - VG248QE - 3Dvision 2
Confirmed that 2 times.
Like my work? Donations can be made via PayPal to: rauti@inetmx.de
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
Core i7-4700 HQ - GTX 970 - Windows 7 - VG248QE - 3Dvision 2
PerfOverlay.DrawFps 0 in User.cfg
Like my work? Donations can be made via PayPal to: rauti@inetmx.de
Hi found it and fixed it, will update the blog shortly.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
I am actually upgrading motherboard and CPU tomorrow so I will start with a fresh install as per your recommendations in a previous post and.... fingers crossed :P
Cheers Mike you legend. Will continue to post a save for any issues I find but hopefully that's the last of it.
i7-4790K CPU 4.8Ghz stable overclock.
16 GB RAM Corsair
ASUS Turbo 2080TI
Samsung SSD 840Pro
ASUS Z97-WS3D
Surround ASUS Rog Swift PG278Q(R), 2x PG278Q (yes it works)
Obutto R3volution.
Windows 10 pro 64x (Windows 7 Dual boot)
I hope it works for you. I have not posted the last fix yet (it will be "v8"), hopefully tonight.
Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278
In addition: I have updated DX11 in Windows 7 (not only installed from DAI_Install folder), this brings more performance and wont afflict stability or behavior of the FIX (V7).
________________________________________________________________________________________________________________
I have also noticed that LOADING a game did not need ALT+TAB for 3D is ok. It is some random issue if 3D is ok or not. Even with traveling. BUT ALT+TAB prevents trave-crashes!! But seems not to be necessary for correct 3D kick in.
The most errors for wrong 3D is only in some textures, not the whole 3D. Like the hair of a chars, the dors or some equipment like bags, weapons or tents in camps. Kicking in 3D correctly after travel or loading seems to be a 50 % chance for me, optimistically i would say 66 % (2 of 3 cases).
Also there seems to be no constant working issue for when you ALT+TAB or kick in 3D again, neither with timings. ALT+TAB is also working with the same results in beeing OK if you do it in the first period of the loading screen, and if you wait 10 seconds or 5 seconds, it is working if you do it on the card-loading-screen right after it appears or after 2 or 5 seconds. There is no constance. BUT: ALT+TAB on loading WILL prevent crashing. This is the only constance i have found out.
In conclusion: Cleaning the Shader-Cache dir will make it possible to use shader-cahce=on and have no influence on the 3D is working or not after loading or traveling, even with shader-cache=off. But shader-cache=on will makes loading significant faster. Restarting with filled shader-cache-dir will lead you to broken 3D, so clean it before restarting and before starting a game. And ALT+TAB will prevent crashes after loading but do not try to figure out a "best point" to do this, or be affraid or unsure when you do it, because there is no constance and there is no "best moment" ....just do it, broken 3D is not an issue of the moment when or how long you ALT+TAB.
==> This is what i can report after 1 week of playing the game with the FIX an may not be the law!
Like my work? Donations can be made via PayPal to: rauti@inetmx.de