Fallout 4
  19 / 44    
[quote="mike_ar69"] 5. Set the following - bComputeShaderDeferredTiledLighting=0 - bForceIgnoreSmoothness=0 - iPresentInterval=0 [/quote] I think this have to be changed in main game directory as well. Right in here: steamapps\common\Fallout 4\Fallout4. There is exactly the same file: Fallout4Prefs.ini
mike_ar69 said:
5. Set the following
- bComputeShaderDeferredTiledLighting=0
- bForceIgnoreSmoothness=0
- iPresentInterval=0


I think this have to be changed in main game directory as well. Right in here: steamapps\common\Fallout 4\Fallout4. There is exactly the same file: Fallout4Prefs.ini
[quote="helifax"] The ones that I am using are: - SLI compat bit (DX1x): "0x280000F5 (Lord of the Rings Online: Shadow of Angmar, Lost Planet 2, Pollen Demo)" - GPU count: 4 - SLI Mode on DirectX 10: AFR (NOT AFR2) [/quote] OMG, Helifax! YOU ARE MY HERO! I've tried like 5 different configurations for SLI and neither worked at all. And your solution makes both my 970's to be used on 90% and FPS is stable 60 with alpha 3D fix! Without SLI bits you provided I've got 35 FPS in same place! OMG OMG OMG!!! :D THANK YOU VERY MUCH!!! And HUGE thanks goes to DHR and DarkStarSword for fix! So far it looks incredible! Power Armor is 3D again :D
helifax said:
The ones that I am using are:
- SLI compat bit (DX1x): "0x280000F5 (Lord of the Rings Online: Shadow of Angmar, Lost Planet 2, Pollen Demo)"
- GPU count: 4
- SLI Mode on DirectX 10: AFR (NOT AFR2)


OMG, Helifax! YOU ARE MY HERO! I've tried like 5 different configurations for SLI and neither worked at all. And your solution makes both my 970's to be used on 90% and FPS is stable 60 with alpha 3D fix! Without SLI bits you provided I've got 35 FPS in same place! OMG OMG OMG!!! :D
THANK YOU VERY MUCH!!!
And HUGE thanks goes to DHR and DarkStarSword for fix! So far it looks incredible! Power Armor is 3D again :D

ASUS Prime z370-A, i5 8600K, ASUS GTX 1080 Ti Strix, 16 GB DDR4, Corsair AX860i PSU, ASUS VG278HR, 3D Vision 2, Sound Blaster Z, Astro A50 Headphones, Windows 10 64-bit Home

Posted 11/18/2015 06:34 PM   
There is a wrong light-shader in the vault 111. Savegame is attached. [url]http://web396.inetseite.de/Save3_467B86C6_4C6F737469_PrewarVault111_000047_20151118185049_1_2.fos[/url] [img]http://web396.inetseite.de/Fallout412_50.jps[/img]
There is a wrong light-shader in the vault 111. Savegame is attached.

http://web396.inetseite.de/Save3_467B86C6_4C6F737469_PrewarVault111_000047_20151118185049_1_2.fos

Image

Like my work? Donations can be made via PayPal to: rauti@inetmx.de

Posted 11/18/2015 06:56 PM   
Damn... I enjoyed good performance until I get out of factory to the roof... Once there, FPS dropped exactly twice, with each GPU topping at 40% usage. CPU usage is at 70% each core. Lowering everything to LOW gave me exactly +10 FPS with the same GPU/CPU load scale. Disabling 3D effectively doubles FPS. Disabling SLI gaves EXACTLY same result, not a single FPS less, only single GPU topping at 60-70% usage. What. The. Heck?... Any ideas? Anyone? :/ [b]UPDATE:[/b] Removing 3D fix doesn't do any difference as well.
Damn... I enjoyed good performance until I get out of factory to the roof... Once there, FPS dropped exactly twice, with each GPU topping at 40% usage. CPU usage is at 70% each core. Lowering everything to LOW gave me exactly +10 FPS with the same GPU/CPU load scale. Disabling 3D effectively doubles FPS. Disabling SLI gaves EXACTLY same result, not a single FPS less, only single GPU topping at 60-70% usage. What. The. Heck?...
Any ideas? Anyone? :/

UPDATE: Removing 3D fix doesn't do any difference as well.

ASUS Prime z370-A, i5 8600K, ASUS GTX 1080 Ti Strix, 16 GB DDR4, Corsair AX860i PSU, ASUS VG278HR, 3D Vision 2, Sound Blaster Z, Astro A50 Headphones, Windows 10 64-bit Home

Posted 11/18/2015 07:29 PM   
HINT: for 3rd person aiming change the d3dx.ini settings for X-box controller or keyboard for the aiming ([KeyAimingKeyboard] or [KeyAimingXboxController]) to: 220 [KeyAimingKeyboard] Key = RBUTTON convergence = 220 type = hold release_transition = 150 release_transition_type = cosine [KeyAimingXboxController] Key = XB_LEFT_TRIGGER convergence = 220 type = hold release_transition = 150 release_transition_type = cosine The values in the Fallout 4 3D Vison Profile is best (4 me) @ StereoSeparation=0.02472453 (3cca8b18) StereoConvergenceBias=0.00000000 (0) StereoConvergence=128.63789368 (4300a34d) (C:\Users\USERNAME\Documents\NVStereoscopic3D.LOG\Fallout4) ==> FOR 3rd PERSON, getting no broken UI, max 3D stero effect. VATS is pretty good @ this settings, without changes. HINT2: Define 2 NEW toggle keys if your eyes are bleeding caused by the convergence while interacting with terminals: [Key5] Key = XB_BACK convergence = 5 type = toggle release_transition = 150 release_transition_type = cosine [Key6] Key = F3 convergence = 128.63789368 type = toggle release_transition = 150 release_transition_type = cosine Clicking X-Box-Controller back-key will make convergence much more "smooth" for your eyes interacting with terminals. If you will leave the terminal you will end up in first person (NORMALY) so this key will switch to 3rd person and "restore" your normal convergence for 3rd person. If you leave a terminal in first person (happens sometimes), hit x-box-back key to witch to 3rd person and hit F3 key to toggle your normal convergence (written in C:\Users\Rauti\Documents\NVStereoscopic3D.LOG\Fallout4 file, in my example it is: StereoConvergence=128.63789368 (4300a34d) <--- 128.63789368 Of cause you can define one key to cycle between "terminal" and normal convergence" for example: [Key5] Key = F3 convergence = 5, 128.63789368 type = cycle release_transition = 150 release_transition_type = cosine ==> This can be made for any keys you prefere even if you are using keyboard/mouse. Just set to the keys/settings you prefere. Playing with some changes makes this alpha verry playable in any situation. The thing that is left is the low separation which is needed to play without a broken HUD (max: 21 %).
HINT:

for 3rd person aiming change the d3dx.ini settings for X-box controller or keyboard for the aiming ([KeyAimingKeyboard] or [KeyAimingXboxController]) to: 220

[KeyAimingKeyboard]
Key = RBUTTON
convergence = 220
type = hold
release_transition = 150
release_transition_type = cosine


[KeyAimingXboxController]
Key = XB_LEFT_TRIGGER
convergence = 220
type = hold
release_transition = 150
release_transition_type = cosine

The values in the Fallout 4 3D Vison Profile is best (4 me) @

StereoSeparation=0.02472453 (3cca8b18)
StereoConvergenceBias=0.00000000 (0)
StereoConvergence=128.63789368 (4300a34d)

(C:\Users\USERNAME\Documents\NVStereoscopic3D.LOG\Fallout4)

==> FOR 3rd PERSON, getting no broken UI, max 3D stero effect.

VATS is pretty good @ this settings, without changes.

HINT2:

Define 2 NEW toggle keys if your eyes are bleeding caused by the convergence while interacting with terminals:

[Key5]
Key = XB_BACK
convergence = 5
type = toggle
release_transition = 150
release_transition_type = cosine

[Key6]
Key = F3
convergence = 128.63789368
type = toggle
release_transition = 150
release_transition_type = cosine

Clicking X-Box-Controller back-key will make convergence much more "smooth" for your eyes interacting with terminals. If you will leave the terminal you will end up in first person (NORMALY) so this key will switch to 3rd person and "restore" your normal convergence for 3rd person. If you leave a terminal in first person (happens sometimes), hit x-box-back key to witch to 3rd person and hit F3 key to toggle your normal convergence (written in C:\Users\Rauti\Documents\NVStereoscopic3D.LOG\Fallout4 file, in my example it is: StereoConvergence=128.63789368 (4300a34d) <--- 128.63789368

Of cause you can define one key to cycle between "terminal" and normal convergence" for example:

[Key5]
Key = F3
convergence = 5, 128.63789368
type = cycle
release_transition = 150
release_transition_type = cosine


==> This can be made for any keys you prefere even if you are using keyboard/mouse. Just set to the keys/settings you prefere.

Playing with some changes makes this alpha verry playable in any situation. The thing that is left is the low separation which is needed to play without a broken HUD (max: 21 %).

Like my work? Donations can be made via PayPal to: rauti@inetmx.de

Posted 11/18/2015 07:49 PM   
With helifax's SLI instructions I get very good scaling, pretty much 100% indoors and 60-90% outdoors. Turning vsync OFF (with SLI on) fixes the de-sync issue from before. So, working SLI now for the most part! :) edit: as I play further, especially in towns when it's raining, the performance drops significantly to sometimes only 20-40% per card. But overall still better than single I would say. Found my first broken light (renders in only one eye), which is only broken when it's actually not visible, i.e. hidden behind a building. As soon as you go around the side of the building and can actually see the light itself it renders perfectly. Screenshot and savegame attached. Enjoying this game/fix immensely so far, aside from Preston stealing my power armor... LOL. Thanks Mike(!!), Darkstar, helifax, DHR, and anyone else I might have missed!
With helifax's SLI instructions I get very good scaling, pretty much 100% indoors and 60-90% outdoors. Turning vsync OFF (with SLI on) fixes the de-sync issue from before. So, working SLI now for the most part! :) edit: as I play further, especially in towns when it's raining, the performance drops significantly to sometimes only 20-40% per card. But overall still better than single I would say.

Found my first broken light (renders in only one eye), which is only broken when it's actually not visible, i.e. hidden behind a building. As soon as you go around the side of the building and can actually see the light itself it renders perfectly. Screenshot and savegame attached.

Enjoying this game/fix immensely so far, aside from Preston stealing my power armor... LOL. Thanks Mike(!!), Darkstar, helifax, DHR, and anyone else I might have missed!

i7-6700k @ 4.5GHz, 2x 970 GTX SLI, 16GB DDR4 @ 3000mhz, MSI Gaming M7, Samsung 950 Pro m.2 SSD 512GB, 2x 1TB RAID 1, 850w EVGA, Corsair RGB 90 keyboard

Posted 11/18/2015 09:01 PM   
Anybody else experience crashes? I've just finished reinstalling game and in 5 minutes it crashed 2 times... :(
Anybody else experience crashes? I've just finished reinstalling game and in 5 minutes it crashed 2 times... :(

ASUS Prime z370-A, i5 8600K, ASUS GTX 1080 Ti Strix, 16 GB DDR4, Corsair AX860i PSU, ASUS VG278HR, 3D Vision 2, Sound Blaster Z, Astro A50 Headphones, Windows 10 64-bit Home

Posted 11/18/2015 10:07 PM   
Thanks Losti! - I really needed to know where I could find my dialled in (normal) convergence setting for the game in order to make some changes in the .ini file. Turns out mine is set at 346 while I thought the scale was 1-100% no wonder my settings made little difference to the 'depth'. Love Extreme 3D.
Thanks Losti!

- I really needed to know where I could find my dialled in (normal) convergence setting for the game in order to make some changes in the .ini file. Turns out mine is set at 346 while I thought the scale was 1-100% no wonder my settings made little difference to the 'depth'. Love Extreme 3D.

Win7 64 16GB I5-4570 Asus Z87-A
GTX 1080 Benq XL 27" 3DVision 2

Posted 11/18/2015 11:01 PM   
[quote="Seregin"]Anybody else experience crashes? I've just finished reinstalling game and in 5 minutes it crashed 2 times... :([/quote] Yes! For me it crashes from anywhere from 2 minutes to 30 minutes... Funny only when 3D Vision is enabled;) If I disable it (CTRL+T) it works perfectly fine... Need to do more testing to see if is the wrapper or just 3D Vision that is crashing... Right there is definitely an error somewhere! I enabled logging in 3DMigoto and this is the last lines before it crashes: [code] nvapi fetched screen width: 5760.000000, height: 1080.000000 error during creation of stereo staging texture. result = 887a0005. [/code] Now I am unsure if this error is generated by the wrapper or the 3D Vision driver. Bo3b/DarkStarSword will know more;) (Attached the log as well. Trying the verbose mode will give me 5 fps at which basically I can't play the game long enough to get a crash:( ) Edit: Yup, Every time I get the exact same crash (replicated it like 5 times in the last 30 minutes.. :( ): [code] nvapi fetched screen width: 5760.000000, height: 1080.000000 error during creation of stereo staging texture. result = 887a0005. [/code] I see the error is generated by 3Dmigoto here: [code] HRESULT ret = pDevice->CreateTexture2D(&desc, &sysData, &staging); if (ret != S_OK) { LogInfo(" error during creation of stereo staging texture. result = %x.\n", ret); } delete sysData.pSysMem; return staging; [/code] I wonder if that "delete" doesn't break things? I dunno... I am just saying/asking. Didn't look at the rest of the code. But from what I currently see this is the error that triggers the silent crash to desktop. That error translates to: [code] DXGI_ERROR_DEVICE_REMOVED 0x887A0005 // The video card has been physically removed from the system, or a driver upgrade for the video card has occurred. The application should destroy and recreate the device. For help debugging the problem, call ID3D10Device::GetDeviceRemovedReason. [/code] So now I am wondering who is crashing exactly? the driver? I'm gonna remove the wrapper and try to play the game in 3D Vision (depth 1% for obvious reasons) and see if I can replicate the crash now... EDIT 3: Hmm, so I managed to replicate this issue WITHOUT the wrapper... It looks like the 3D Vision driver is the one that actually generates the crash.. Hmm... I wonder if it has to do with SLI....
Seregin said:Anybody else experience crashes? I've just finished reinstalling game and in 5 minutes it crashed 2 times... :(


Yes! For me it crashes from anywhere from 2 minutes to 30 minutes... Funny only when 3D Vision is enabled;) If I disable it (CTRL+T) it works perfectly fine... Need to do more testing to see if is the wrapper or just 3D Vision that is crashing...

Right there is definitely an error somewhere! I enabled logging in 3DMigoto and this is the last lines before it crashes:
nvapi fetched screen width: 5760.000000, height: 1080.000000
error during creation of stereo staging texture. result = 887a0005.


Now I am unsure if this error is generated by the wrapper or the 3D Vision driver.
Bo3b/DarkStarSword will know more;)
(Attached the log as well. Trying the verbose mode will give me 5 fps at which basically I can't play the game long enough to get a crash:( )

Edit:
Yup, Every time I get the exact same crash (replicated it like 5 times in the last 30 minutes.. :( ):
nvapi fetched screen width: 5760.000000, height: 1080.000000
error during creation of stereo staging texture. result = 887a0005.


I see the error is generated by 3Dmigoto here:
HRESULT ret = pDevice->CreateTexture2D(&desc, &sysData, &staging);
if (ret != S_OK)
{
LogInfo(" error during creation of stereo staging texture. result = %x.\n", ret);
}
delete sysData.pSysMem;
return staging;


I wonder if that "delete" doesn't break things? I dunno... I am just saying/asking. Didn't look at the rest of the code. But from what I currently see this is the error that triggers the silent crash to desktop.

That error translates to:
DXGI_ERROR_DEVICE_REMOVED
0x887A0005

// The video card has been physically removed from the system, or a driver upgrade for the video card has occurred. The application should destroy and recreate the device. For help debugging the problem, call ID3D10Device::GetDeviceRemovedReason.


So now I am wondering who is crashing exactly? the driver?

I'm gonna remove the wrapper and try to play the game in 3D Vision (depth 1% for obvious reasons) and see if I can replicate the crash now...

EDIT 3:
Hmm, so I managed to replicate this issue WITHOUT the wrapper... It looks like the 3D Vision driver is the one that actually generates the crash.. Hmm... I wonder if it has to do with SLI....
Attachments

d3d11_log.rar.jpg

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)

Posted 11/18/2015 11:35 PM   
To the guys who keep 3D going strong, a big thank you. Looks great. Now, the issue I'm running into which is sort of 3D related: [KeyAimingXboxController] Key = XB_LEFT_TRIGGER convergence = 220 type = hold release_transition = 150 release_transition_type = cosine That works perfectly for Xbox One, anybody got any idea what the "Key" is called for PS4? Works natively out of the box btw.
To the guys who keep 3D going strong, a big thank you. Looks great.

Now, the issue I'm running into which is sort of 3D related:

[KeyAimingXboxController]
Key = XB_LEFT_TRIGGER
convergence = 220
type = hold
release_transition = 150
release_transition_type = cosine

That works perfectly for Xbox One, anybody got any idea what the "Key" is called for PS4? Works natively out of the box btw.

i7 3770K
970
8GB

Posted 11/18/2015 11:45 PM   
[quote="helifax"][quote="jessesomogyi"]I greatly admire all the work you guys put into this (on your own time, no less). You're the best. I think I have the fix working, but some of the shadows look odd. Not all, but some. I would upload screen grabs, but I'm not hugely into this (being part of the community, sharing info/screen grabs, etc.) Any pointers? I've been using 3D vision for a bit over 2 years. Another question, how do I get "SEP: / CONV:, as well as VS: 0/0, CS: 0/0 off of the bottom and top of the screen? I noticed this displayed after I applied this new fix. Thank you for your help.[/quote] WRONG!!! You didn't apply any fix. READ AGAIN THE INSTRUCTIONS!!!! (Carefully this time !) Hint: You need to download a jpg file from that post and remove the .jpg extension (so It remains etc.rar) Then extract the content OVER the 3DMigoto wrapper. /sigh.... (I swear, some people should NOT use computers...) [color="orange"](Or instead of making useless posts like these, familiarize yourself with how the wrapper works and how we deliver an ALPHA FIX.[/color] Not targeting you in particular, but look up! Last posts are from people who "can't read !" So, don't be a Jar Jar Binks;) Use the "Force" Luke ! ) Note to self: Man, I start to sound very angry lately LOL! =)) and this is NOT the intention! Guess, I'll need to work a bit on delivering the information in a much "sweeter" tone rather than "On Point" ^_^.[/quote] Hello, I followed Helifax' advise and now I have the alpha fix properly installed. Thank you, Helifax for your advise. I'm a big boy now!
helifax said:
jessesomogyi said:I greatly admire all the work you guys put into this (on your own time, no less). You're the best. I think I have the fix working, but some of the shadows look odd. Not all, but some. I would upload screen grabs, but I'm not hugely into this (being part of the community, sharing info/screen grabs, etc.) Any pointers? I've been using 3D vision for a bit over 2 years. Another question, how do I get "SEP: / CONV:, as well as VS: 0/0, CS: 0/0 off of the bottom and top of the screen? I noticed this displayed after I applied this new fix. Thank you for your help.


WRONG!!! You didn't apply any fix.
READ AGAIN THE INSTRUCTIONS!!!!
(Carefully this time !)

Hint: You need to download a jpg file from that post and remove the .jpg extension (so It remains etc.rar) Then extract the content OVER the 3DMigoto wrapper. /sigh.... (I swear, some people should NOT use computers...)

(Or instead of making useless posts like these, familiarize yourself with how the wrapper works and how we deliver an ALPHA FIX. Not targeting you in particular, but look up! Last posts are from people who "can't read !"
So, don't be a Jar Jar Binks;) Use the "Force" Luke ! )

Note to self: Man, I start to sound very angry lately LOL! =)) and this is NOT the intention! Guess, I'll need to work a bit on delivering the information in a much "sweeter" tone rather than "On Point" ^_^.





Hello,

I followed Helifax' advise and now I have the alpha fix properly installed. Thank you, Helifax for your advise. I'm a big boy now!

Posted 11/19/2015 12:27 AM   
[quote="jessesomogyi"][quote="helifax"][quote="jessesomogyi"]I greatly admire all the work you guys put into this (on your own time, no less). You're the best. I think I have the fix working, but some of the shadows look odd. Not all, but some. I would upload screen grabs, but I'm not hugely into this (being part of the community, sharing info/screen grabs, etc.) Any pointers? I've been using 3D vision for a bit over 2 years. Another question, how do I get "SEP: / CONV:, as well as VS: 0/0, CS: 0/0 off of the bottom and top of the screen? I noticed this displayed after I applied this new fix. Thank you for your help.[/quote] WRONG!!! You didn't apply any fix. READ AGAIN THE INSTRUCTIONS!!!! (Carefully this time !) Hint: You need to download a jpg file from that post and remove the .jpg extension (so It remains etc.rar) Then extract the content OVER the 3DMigoto wrapper. /sigh.... (I swear, some people should NOT use computers...) [color="orange"](Or instead of making useless posts like these, familiarize yourself with how the wrapper works and how we deliver an ALPHA FIX.[/color] Not targeting you in particular, but look up! Last posts are from people who "can't read !" So, don't be a Jar Jar Binks;) Use the "Force" Luke ! ) Note to self: Man, I start to sound very angry lately LOL! =)) and this is NOT the intention! Guess, I'll need to work a bit on delivering the information in a much "sweeter" tone rather than "On Point" ^_^.[/quote] Hello, I followed Helifax' advise and now I have the alpha fix properly installed. Thank you, Helifax for your advise. I'm a big boy now![/quote] Cheers! Now you know how to do it for all the future Alpha releases that might come;) Once an Alpha gets to Beta or Gold we normally make a full archive release and stick it on the blog;) The Alpha is more for "internal testing" to see if we can tweak stuff even more for a better experience;) Hence the somewhat "not so straight" approach;)
jessesomogyi said:
helifax said:
jessesomogyi said:I greatly admire all the work you guys put into this (on your own time, no less). You're the best. I think I have the fix working, but some of the shadows look odd. Not all, but some. I would upload screen grabs, but I'm not hugely into this (being part of the community, sharing info/screen grabs, etc.) Any pointers? I've been using 3D vision for a bit over 2 years. Another question, how do I get "SEP: / CONV:, as well as VS: 0/0, CS: 0/0 off of the bottom and top of the screen? I noticed this displayed after I applied this new fix. Thank you for your help.


WRONG!!! You didn't apply any fix.
READ AGAIN THE INSTRUCTIONS!!!!
(Carefully this time !)

Hint: You need to download a jpg file from that post and remove the .jpg extension (so It remains etc.rar) Then extract the content OVER the 3DMigoto wrapper. /sigh.... (I swear, some people should NOT use computers...)

(Or instead of making useless posts like these, familiarize yourself with how the wrapper works and how we deliver an ALPHA FIX. Not targeting you in particular, but look up! Last posts are from people who "can't read !"
So, don't be a Jar Jar Binks;) Use the "Force" Luke ! )

Note to self: Man, I start to sound very angry lately LOL! =)) and this is NOT the intention! Guess, I'll need to work a bit on delivering the information in a much "sweeter" tone rather than "On Point" ^_^.





Hello,

I followed Helifax' advise and now I have the alpha fix properly installed. Thank you, Helifax for your advise. I'm a big boy now!


Cheers! Now you know how to do it for all the future Alpha releases that might come;) Once an Alpha gets to Beta or Gold we normally make a full archive release and stick it on the blog;) The Alpha is more for "internal testing" to see if we can tweak stuff even more for a better experience;) Hence the somewhat "not so straight" approach;)

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)

Posted 11/19/2015 12:31 AM   
I have no crashes with the fix... Maybe couse i´ve some modded textures in game as "touch of Green", hwo knows... My problema is a poor performance with de fix, but no ctds.
I have no crashes with the fix... Maybe couse i´ve some modded textures in game as "touch of Green", hwo knows...
My problema is a poor performance with de fix, but no ctds.

Posted 11/19/2015 01:21 AM   
[quote="MJ1911"]That works perfectly for Xbox One, anybody got any idea what the "Key" is called for PS4? Works natively out of the box btw.[/quote]3DMigoto uses xinput, which only works with 360 and Xbone controllers. You might be able to get it working with one of the various compatibility layers that make the PS4 controller work with xinput games (I'm not very familiar with these), or by using something like xpadder, antimicro or joy2key to assign a keyboard key to the trigger. I have thought about bringing DirectInput support back in 3DMigoto to allow non-xbox controllers to be used directly, but we used to have some DirectInput support in very old versions of 3DMigoto and it just caused nothing but trouble.
MJ1911 said:That works perfectly for Xbox One, anybody got any idea what the "Key" is called for PS4? Works natively out of the box btw.
3DMigoto uses xinput, which only works with 360 and Xbone controllers.

You might be able to get it working with one of the various compatibility layers that make the PS4 controller work with xinput games (I'm not very familiar with these), or by using something like xpadder, antimicro or joy2key to assign a keyboard key to the trigger.

I have thought about bringing DirectInput support back in 3DMigoto to allow non-xbox controllers to be used directly, but we used to have some DirectInput support in very old versions of 3DMigoto and it just caused nothing but trouble.

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 11/19/2015 03:00 AM   
[quote="Losti"]There is a wrong light-shader in the vault 111. Savegame is attached. [url]http://web396.inetseite.de/Save3_467B86C6_4C6F737469_PrewarVault111_000047_20151118185049_1_2.fos[/url] [img]http://web396.inetseite.de/Fallout412_50.jps[/img][/quote] It's lensflare. DHR made some correction for that, maybe there are several shaders, I'm not sure. You can turn lens flare off in the game settings though, I think (and certainly in the Fallout4Prefs.ini file).
Losti said:There is a wrong light-shader in the vault 111. Savegame is attached.

http://web396.inetseite.de/Save3_467B86C6_4C6F737469_PrewarVault111_000047_20151118185049_1_2.fos

Image

It's lensflare. DHR made some correction for that, maybe there are several shaders, I'm not sure. You can turn lens flare off in the game settings though, I think (and certainly in the Fallout4Prefs.ini file).

Rig: Intel i7-8700K @4.7GHz, 16Gb Ram, SSD, GTX 1080Ti, Win10x64, Asus VG278

Posted 11/19/2015 03:55 AM   
  19 / 44    
Scroll To Top