Fallout 4
  22 / 44    
I found the remaining Cloud shader....is another shader that is enabled in certain times of the day. The bad news is that shader have decompiler issues. bo3b can you help me with this? [code]cbuffer cb2 : register(b2) { float4 cb2[14]; } Texture2D<float4> StereoParams : register(t125); Texture1D<float4> IniParams : register(t120); void main( float4 v0 : POSITION0, float2 v1 : TEXCOORD0, float4 v2 : COLOR0, out float4 o0 : SV_POSITION0, out float2 o1 : TEXCOORD0, out float2 p1 : TEXCOORD1, out float4 o2 : COLOR0, out float4 o3 : POSITION0, out float4 o4 : POSITION1) { float4 r0,r1,r2,r3,r4; uint4 bitmask, uiDest; float4 fDest; r0.xyz = v0.xyz; r0.w = 1; r1.x = dot(cb2[0].xyzw, r0.xyzw); r1.y = dot(cb2[1].xyzw, r0.xyzw); r1.z = dot(cb2[3].xyzw, r0.xyzw); o0.xyzw = r1.xyzz; o1.xyzw = cb2[10].xyxy + v1.xyxy; r1.xyzw = cb2[7].xyzw * v2.xxxw; r2.xyz = cb2[8].xyz * v2.yyy + r1.xyz; r1.xyz = cb2[9].xyz * v2.zzz + r2.xyz; o2.xyzw = cb2[7].xyzw * float4(9.99999997e-007,9.99999997e-007,9.99999997e-007,9.99999997e-007) + r1.xyzw; o3.w = 1; o3.x = dot(cb2[4].xyzw, r0.xyzw); o3.y = dot(cb2[5].xyzw, r0.xyzw); o3.z = dot(cb2[6].xyzw, r0.xyzw); o4.w = 1; o4.x = dot(cb2[11].xyzw, r0.xyzw); o4.y = dot(cb2[12].xyzw, r0.xyzw); o4.z = dot(cb2[13].xyzw, r0.xyzw); r5.xyzw = t125.Load(float4(0,0,0,0)).xyzw; r4.w = r4.y * r4.x; o4.x = r4.w + o4.x; return; } /*~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ // // Generated by Microsoft (R) D3D Shader Disassembler // // using 3Dmigoto v1.2.9 on Thu Nov 19 22:24:08 2015 // // // Input signature: // // Name Index Mask Register SysValue Format Used // -------------------- ----- ------ -------- -------- ------- ------ // POSITION 0 xyzw 0 NONE float xyz // TEXCOORD 0 xy 1 NONE float xy // COLOR 0 xyzw 2 NONE float xyzw // // // Output signature: // // Name Index Mask Register SysValue Format Used // -------------------- ----- ------ -------- -------- ------- ------ // SV_POSITION 0 xyzw 0 POS float xyzw // TEXCOORD 0 xy 1 NONE float xy // TEXCOORD 1 zw 1 NONE float zw // COLOR 0 xyzw 2 NONE float xyzw // POSITION 0 xyzw 3 NONE float xyzw // POSITION 1 xyzw 4 NONE float xyzw // vs_5_0 dcl_globalFlags refactoringAllowed dcl_constantbuffer cb2[14], immediateIndexed dcl_input v0.xyz dcl_input v1.xy dcl_input v2.xyzw dcl_output_siv o0.xyzw, position dcl_output o1.xy dcl_output o1.zw dcl_output o2.xyzw dcl_output o3.xyzw dcl_output o4.xyzw dcl_temps 5 dcl_resource_texture2d (float,float,float,float) t125 mov r0.xyz, v0.xyzx mov r0.w, l(1.000000) dp4 r1.x, cb2[0].xyzw, r0.xyzw dp4 r1.y, cb2[1].xyzw, r0.xyzw dp4 r1.z, cb2[3].xyzw, r0.xyzw mov o0.xyzw, r1.xyzz add o1.xyzw, v1.xyxy, cb2[10].xyxy mul r1.xyzw, v2.xxxw, cb2[7].xyzw mad r2.xyz, cb2[8].xyzx, v2.yyyy, r1.xyzx mad r1.xyz, cb2[9].xyzx, v2.zzzz, r2.xyzx mad o2.xyzw, cb2[7].xyzw, l(0.000001, 0.000001, 0.000001, 0.000001), r1.xyzw mov o3.w, l(1.000000) dp4 o3.x, cb2[4].xyzw, r0.xyzw dp4 o3.y, cb2[5].xyzw, r0.xyzw dp4 o3.z, cb2[6].xyzw, r0.xyzw mov o4.w, l(1.000000) dp4 o4.x, cb2[11].xyzw, r0.xyzw dp4 o4.y, cb2[12].xyzw, r0.xyzw dp4 o4.z, cb2[13].xyzw, r0.xyzw ld_indexable(texture2d)(float,float,float,float) r5.xyzw, l(0, 0, 0, 0), t125.xyzw mul r4.w, r4.x, r4.y add o4.x, o4.x, r4.w ret // Approximately 0 instruction slots used ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~[/code] Error: [code]wrapper1349(31,3-9): error X3018: invalid subscript 'xyzw'[/code] is this line: [code]o1.xyzw = cb2[10].xyxy + v1.xyxy;[/code] I check the ASM code, but is the same.
I found the remaining Cloud shader....is another shader that is enabled in certain times of the day. The bad news is that shader have decompiler issues. bo3b can you help me with this?

cbuffer cb2 : register(b2)
{
float4 cb2[14];
}


Texture2D<float4> StereoParams : register(t125);
Texture1D<float4> IniParams : register(t120);

void main(
float4 v0 : POSITION0,
float2 v1 : TEXCOORD0,
float4 v2 : COLOR0,
out float4 o0 : SV_POSITION0,
out float2 o1 : TEXCOORD0,
out float2 p1 : TEXCOORD1,
out float4 o2 : COLOR0,
out float4 o3 : POSITION0,
out float4 o4 : POSITION1)
{
float4 r0,r1,r2,r3,r4;
uint4 bitmask, uiDest;
float4 fDest;

r0.xyz = v0.xyz;
r0.w = 1;
r1.x = dot(cb2[0].xyzw, r0.xyzw);
r1.y = dot(cb2[1].xyzw, r0.xyzw);
r1.z = dot(cb2[3].xyzw, r0.xyzw);
o0.xyzw = r1.xyzz;
o1.xyzw = cb2[10].xyxy + v1.xyxy;
r1.xyzw = cb2[7].xyzw * v2.xxxw;
r2.xyz = cb2[8].xyz * v2.yyy + r1.xyz;
r1.xyz = cb2[9].xyz * v2.zzz + r2.xyz;
o2.xyzw = cb2[7].xyzw * float4(9.99999997e-007,9.99999997e-007,9.99999997e-007,9.99999997e-007) + r1.xyzw;
o3.w = 1;
o3.x = dot(cb2[4].xyzw, r0.xyzw);
o3.y = dot(cb2[5].xyzw, r0.xyzw);
o3.z = dot(cb2[6].xyzw, r0.xyzw);
o4.w = 1;
o4.x = dot(cb2[11].xyzw, r0.xyzw);
o4.y = dot(cb2[12].xyzw, r0.xyzw);
o4.z = dot(cb2[13].xyzw, r0.xyzw);
r5.xyzw = t125.Load(float4(0,0,0,0)).xyzw;
r4.w = r4.y * r4.x;
o4.x = r4.w + o4.x;
return;
}

/*~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
//
// Generated by Microsoft (R) D3D Shader Disassembler
//
// using 3Dmigoto v1.2.9 on Thu Nov 19 22:24:08 2015
//
//
// Input signature:
//
// Name Index Mask Register SysValue Format Used
// -------------------- ----- ------ -------- -------- ------- ------
// POSITION 0 xyzw 0 NONE float xyz
// TEXCOORD 0 xy 1 NONE float xy
// COLOR 0 xyzw 2 NONE float xyzw
//
//
// Output signature:
//
// Name Index Mask Register SysValue Format Used
// -------------------- ----- ------ -------- -------- ------- ------
// SV_POSITION 0 xyzw 0 POS float xyzw
// TEXCOORD 0 xy 1 NONE float xy
// TEXCOORD 1 zw 1 NONE float zw
// COLOR 0 xyzw 2 NONE float xyzw
// POSITION 0 xyzw 3 NONE float xyzw
// POSITION 1 xyzw 4 NONE float xyzw
//
vs_5_0
dcl_globalFlags refactoringAllowed
dcl_constantbuffer cb2[14], immediateIndexed
dcl_input v0.xyz
dcl_input v1.xy
dcl_input v2.xyzw
dcl_output_siv o0.xyzw, position
dcl_output o1.xy
dcl_output o1.zw
dcl_output o2.xyzw
dcl_output o3.xyzw
dcl_output o4.xyzw
dcl_temps 5
dcl_resource_texture2d (float,float,float,float) t125
mov r0.xyz, v0.xyzx
mov r0.w, l(1.000000)
dp4 r1.x, cb2[0].xyzw, r0.xyzw
dp4 r1.y, cb2[1].xyzw, r0.xyzw
dp4 r1.z, cb2[3].xyzw, r0.xyzw
mov o0.xyzw, r1.xyzz
add o1.xyzw, v1.xyxy, cb2[10].xyxy
mul r1.xyzw, v2.xxxw, cb2[7].xyzw
mad r2.xyz, cb2[8].xyzx, v2.yyyy, r1.xyzx
mad r1.xyz, cb2[9].xyzx, v2.zzzz, r2.xyzx
mad o2.xyzw, cb2[7].xyzw, l(0.000001, 0.000001, 0.000001, 0.000001), r1.xyzw
mov o3.w, l(1.000000)
dp4 o3.x, cb2[4].xyzw, r0.xyzw
dp4 o3.y, cb2[5].xyzw, r0.xyzw
dp4 o3.z, cb2[6].xyzw, r0.xyzw
mov o4.w, l(1.000000)
dp4 o4.x, cb2[11].xyzw, r0.xyzw
dp4 o4.y, cb2[12].xyzw, r0.xyzw
dp4 o4.z, cb2[13].xyzw, r0.xyzw
ld_indexable(texture2d)(float,float,float,float) r5.xyzw, l(0, 0, 0, 0), t125.xyzw
mul r4.w, r4.x, r4.y
add o4.x, o4.x, r4.w
ret
// Approximately 0 instruction slots used

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Error:
wrapper1349(31,3-9): error X3018: invalid subscript 'xyzw'


is this line:
o1.xyzw = cb2[10].xyxy + v1.xyxy;


I check the ASM code, but is the same.

MY WEB

Helix Mod - Making 3D Better

My 3D Screenshot Gallery

Like my fixes? you can donate to Paypal: dhr.donation@gmail.com

Posted 11/20/2015 02:48 PM   
[quote]Error: [code]wrapper1349(31,3-9): error X3018: invalid subscript 'xyzw'[/code] is this line: [code]o1.xyzw = cb2[10].xyxy + v1.xyxy;[/code] I check the ASM code, but is the same.[/quote] Try this: [code] o1.xy = cb2[10].xy + v1.xy; p1.xy = cb2[10].xy + v1.xy; [/code] The reason is because TEXCOORD0 and TEXCOORD1 are two separate outputs that were combined into a single register in the assmbly (with different component masks), which confuses the decompiler: [code] void main( ... out float2 o1 : TEXCOORD0, out float2 p1 : TEXCOORD1, ... [/code] vs. [code] // Output signature: // // Name Index Mask Register SysValue Format Used // -------------------- ----- ------ -------- -------- ------- ------ ... // TEXCOORD 0 xy 1 NONE float xy // TEXCOORD 1 zw 1 NONE float zw ... dcl_output o1.xy dcl_output o1.zw ... [/code]
Error:
wrapper1349(31,3-9): error X3018: invalid subscript 'xyzw'


is this line:
o1.xyzw = cb2[10].xyxy + v1.xyxy;


I check the ASM code, but is the same.


Try this:

o1.xy = cb2[10].xy + v1.xy;
p1.xy = cb2[10].xy + v1.xy;


The reason is because TEXCOORD0 and TEXCOORD1 are two separate outputs that were combined into a single register in the assmbly (with different component masks), which confuses the decompiler:

void main( 
...
out float2 o1 : TEXCOORD0,
out float2 p1 : TEXCOORD1,
...

vs.
// Output signature:
//
// Name Index Mask Register SysValue Format Used
// -------------------- ----- ------ -------- -------- ------- ------
...
// TEXCOORD 0 xy 1 NONE float xy
// TEXCOORD 1 zw 1 NONE float zw
...
dcl_output o1.xy
dcl_output o1.zw
...

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/20/2015 03:12 PM   
Happened to be online at the moment, so I took a look. Should work if you break that instruction into two pieces. [code] o1.xy = cb2[10].xy + v1.xy; p1.xy = cb2[10].xy + v1.xy; [/code] There's some funny stuff with that shader though. The use of t125 is the register we always use for stereo texture, so the fact that this shows in the assembly is really weird, and bad. That means the shader was somehow reassembled or cross-matched, as we should never disassemble anything except the real version. Would be worth starting with a fresh copy of the shader to be sure some damage has not crept in.
Happened to be online at the moment, so I took a look.

Should work if you break that instruction into two pieces.

o1.xy = cb2[10].xy + v1.xy;
p1.xy = cb2[10].xy + v1.xy;


There's some funny stuff with that shader though. The use of t125 is the register we always use for stereo texture, so the fact that this shows in the assembly is really weird, and bad. That means the shader was somehow reassembled or cross-matched, as we should never disassemble anything except the real version.

Would be worth starting with a fresh copy of the shader to be sure some damage has not crept in.

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 11/20/2015 03:16 PM   
Thanks DarkStarSword and bo3b....i will try with those and with fresh copy of shaders. I also noticed that t125 in the code, really strange. I will report back.
Thanks DarkStarSword and bo3b....i will try with those and with fresh copy of shaders. I also noticed that t125 in the code, really strange. I will report back.

MY WEB

Helix Mod - Making 3D Better

My 3D Screenshot Gallery

Like my fixes? you can donate to Paypal: dhr.donation@gmail.com

Posted 11/20/2015 03:27 PM   
[quote="mistersvin"][quote="MJ1911"][quote="Mournz"] yes, it helped... until random crash outdoors, rolling back to 358.91 update: rolling back didnt help, still carshes. I didnt have a single crash using 358.91 until installing 359.00 driver[/quote][/quote][/quote] Used DDU ? This fixed my driver problems, even with 358.91. I have DDUed my old driver and installed 358.91 without NVGF-Exp. Working good without crashes. I do not using the 359.00. Be carefull with any mods using this alpha fix. Remember FO3, mods got to crash the game. May be there is an interaction between mods and the fix, or its just related to a mod. So try to sort it out !! I have installed "tons" of graphic mods, checked each for playing stable. even using SweetFX. But you have to test every mod, with the 3D fix wether it is working good or not. Start with no modifications. Be carefull with OC settings. If you havnt OCed anything and using no mods, THAN you can be say its a 3D-fix related issue, if this issue isnt appearing without 3D-fix. Vanilla: [img]http://web396.inetseite.de/Fallout4 2015-11-20 20-14-55.png[/img] "http://web396.inetseite.de/Fallout4 2015-11-20 20-14-55.png" Modded and SweetFXed: [img]http://web396.inetseite.de/Fallout4 2015-11-20 20-10-22.png[/img] "http://web396.inetseite.de/Fallout4 2015-11-20 20-10-22.png" BUT BE CAREFULL, do not report crashes or issues which may connected to a mod!! Report if you have this issue also in vanilla. For a Mod package PM me, its nearly compleeted with the needfullest things in graphics. But be patient, ill have to test it in final with the actual fix, plaing more than 30 minutes.
mistersvin said:
MJ1911 said:
Mournz said:

yes, it helped... until random crash outdoors, rolling back to 358.91
update: rolling back didnt help, still carshes. I didnt have a single crash using 358.91 until installing 359.00 driver


Used DDU ?

This fixed my driver problems, even with 358.91. I have DDUed my old driver and installed 358.91 without NVGF-Exp. Working good without crashes. I do not using the 359.00.

Be carefull with any mods using this alpha fix. Remember FO3, mods got to crash the game. May be there is an interaction between mods and the fix, or its just related to a mod. So try to sort it out !!

I have installed "tons" of graphic mods, checked each for playing stable. even using SweetFX. But you have to test every mod, with the 3D fix wether it is working good or not. Start with no modifications. Be carefull with OC settings. If you havnt OCed anything and using no mods, THAN you can be say its a 3D-fix related issue, if this issue isnt appearing without 3D-fix.

Vanilla:
Image
"http://web396.inetseite.de/Fallout4 2015-11-20 20-14-55.png"

Modded and SweetFXed:
Image
"http://web396.inetseite.de/Fallout4 2015-11-20 20-10-22.png"

BUT BE CAREFULL, do not report crashes or issues which may connected to a mod!! Report if you have this issue also in vanilla.

For a Mod package PM me, its nearly compleeted with the needfullest things in graphics.

But be patient, ill have to test it in final with the actual fix, plaing more than 30 minutes.

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

Posted 11/20/2015 06:58 PM   
[quote="MJ1911"][quote="Mournz"]I'm crashing every time I get to the loading screen after hitting continue. I just updated nvidia drivers to 359.00 Anyone else crashing after updating to the new drivers? I'll try rolling back see if that helps.. Or is there some setting that gets switched after updating that I need to turn? I did (as usual) have to go through the 3d vision set up after new drivers.. It will let me play with 3d turned off.. Have not tested older driver yet.. Edit: Rollback to 358.91 didn't help. Perhaps I need to reapply the fix after new drivers?[/quote] Try disabling V-Sync. If it's similar to the issue I had, it's because your last save was at a large open city, and the game only likes to load in a small room. If disabling V-Sync doesn't help, play without 3D until you find a small room and save, then turn on 3D and start from there.[/quote] MJ1911 and Losti (for DD thought), thanks for your help! MJ1911 was correct the problem was V-sync. After installing new drivers my nvidia settings for fallout 4 in control panel that I had switched to disable V-sync, reverted back to original settings (on). So anyone with this problem after updating drivers you may need to go back to the fallout 4 settings in control panel and disable vsync again. Fixed and happy!!!
MJ1911 said:
Mournz said:I'm crashing every time I get to the loading screen after hitting continue.

I just updated nvidia drivers to 359.00

Anyone else crashing after updating to the new drivers? I'll try rolling back see if that helps..
Or is there some setting that gets switched after updating that I need to turn?
I did (as usual) have to go through the 3d vision set up after new drivers..

It will let me play with 3d turned off.. Have not tested older driver yet..

Edit: Rollback to 358.91 didn't help. Perhaps I need to reapply the fix after new drivers?


Try disabling V-Sync. If it's similar to the issue I had, it's because your last save was at a large open city, and the game only likes to load in a small room. If disabling V-Sync doesn't help, play without 3D until you find a small room and save, then turn on 3D and start from there.


MJ1911 and Losti (for DD thought), thanks for your help! MJ1911 was correct the problem was V-sync. After installing new drivers my nvidia settings for fallout 4 in control panel that I had switched to disable V-sync, reverted back to original settings (on). So anyone with this problem after updating drivers you may need to go back to the fallout 4 settings in control panel and disable vsync again. Fixed and happy!!!

NZXT Noctis 450. Asus ROG Formula VIII, 6700k, NZXT Kracken x61. Avexir Core DDR4 (Red) 16g. Windows 10. Samsung Evo 1T & 2T SSD. Asus Strix 2080 ti. EVGA 1300w Modular Gold PSU.
Asus ROG Swift PG278Q Monitor: 1440p 3D Vision

Posted 11/20/2015 08:30 PM   
Glad to know. I suffered a crash again, which you may want to watch out for, this 3rd culprit: Window's 7 Aero Performance warnings. You know the one...your performance is slow...keep color settings and don't show this message again. I've gone through several driver updates and rollbacks and everytime, that message pops up. Except it won't be a message. While in 3D it CTDs. I only figured out it's the Aero Warinings when I turn off 3D, boot up the game, and then the game immediately Alt-Tabs me to desktop to inform me that the system wants to change my color scheme to improve performance. After selecting "dont show this message again" I boot up the game in 3D once again and it's mostly hassle free from there. Or you can disable it permanently by going to Control Panel, System Security, Action Center, Change Action Center Settings, untick Windows trouble shooting.
Glad to know. I suffered a crash again, which you may want to watch out for, this 3rd culprit: Window's 7 Aero Performance warnings. You know the one...your performance is slow...keep color settings and don't show this message again.

I've gone through several driver updates and rollbacks and everytime, that message pops up. Except it won't be a message. While in 3D it CTDs. I only figured out it's the Aero Warinings when I turn off 3D, boot up the game, and then the game immediately Alt-Tabs me to desktop to inform me that the system wants to change my color scheme to improve performance. After selecting "dont show this message again" I boot up the game in 3D once again and it's mostly hassle free from there.

Or you can disable it permanently by going to Control Panel, System Security, Action Center, Change Action Center Settings, untick Windows trouble shooting.

i7 3770K
970
8GB

Posted 11/20/2015 09:58 PM   
[quote="Mournz"][quote="MJ1911"][quote="Mournz"]I'm crashing every time I get to the loading screen after hitting continue. I just updated nvidia drivers to 359.00 Anyone else crashing after updating to the new drivers? I'll try rolling back see if that helps.. Or is there some setting that gets switched after updating that I need to turn? I did (as usual) have to go through the 3d vision set up after new drivers.. It will let me play with 3d turned off.. Have not tested older driver yet.. Edit: Rollback to 358.91 didn't help. Perhaps I need to reapply the fix after new drivers?[/quote] Try disabling V-Sync. If it's similar to the issue I had, it's because your last save was at a large open city, and the game only likes to load in a small room. If disabling V-Sync doesn't help, play without 3D until you find a small room and save, then turn on 3D and start from there.[/quote] MJ1911 and Losti (for DD thought), thanks for your help! MJ1911 was correct the problem was V-sync. After installing new drivers my nvidia settings for fallout 4 in control panel that I had switched to disable V-sync, reverted back to original settings (on). So anyone with this problem after updating drivers you may need to go back to the fallout 4 settings in control panel and disable vsync again. Fixed and happy!!![/quote] i dont rly understand.. are you playing with vsync off ??? Now, after installing 359 and rolling back to 358 driver i have crashes, turning off vsync doesnt help - i have to turn 3d off, go indoors, save, restart 3d and the game and go outdoors, only this way i can load the game without crashing (besides this does not resolve random crashes)
Mournz said:
MJ1911 said:
Mournz said:I'm crashing every time I get to the loading screen after hitting continue.

I just updated nvidia drivers to 359.00

Anyone else crashing after updating to the new drivers? I'll try rolling back see if that helps..
Or is there some setting that gets switched after updating that I need to turn?
I did (as usual) have to go through the 3d vision set up after new drivers..

It will let me play with 3d turned off.. Have not tested older driver yet..

Edit: Rollback to 358.91 didn't help. Perhaps I need to reapply the fix after new drivers?


Try disabling V-Sync. If it's similar to the issue I had, it's because your last save was at a large open city, and the game only likes to load in a small room. If disabling V-Sync doesn't help, play without 3D until you find a small room and save, then turn on 3D and start from there.


MJ1911 and Losti (for DD thought), thanks for your help! MJ1911 was correct the problem was V-sync. After installing new drivers my nvidia settings for fallout 4 in control panel that I had switched to disable V-sync, reverted back to original settings (on). So anyone with this problem after updating drivers you may need to go back to the fallout 4 settings in control panel and disable vsync again. Fixed and happy!!!


i dont rly understand.. are you playing with vsync off ???

Now, after installing 359 and rolling back to 358 driver i have crashes, turning off vsync doesnt help - i have to turn 3d off, go indoors, save, restart 3d and the game and go outdoors, only this way i can load the game without crashing (besides this does not resolve random crashes)

Posted 11/20/2015 11:31 PM   
[quote="mistersvin"][quote="Mournz"][quote="MJ1911"][quote="Mournz"]I'm crashing every time I get to the loading screen after hitting continue. i dont rly understand.. are you playing with vsync off ??? Now, after installing 359 and rolling back to 358 driver i have crashes, turning off vsync doesnt help - i have to turn 3d off, go indoors, save, restart 3d and the game and go outdoors, only this way i can load the game without crashing (besides this does not resolve random crashes)[/quote] Yes, against the instructions, we are playing with V-Sync off. It helps with framerate stutters and loading times. I think this is because the frame rate is somehow tied to how much processor power is used, so that if it is unlocked during loading screens, your processor goes into turbo mode and loads the assets faster. Also, the crashes that occur on my sytem happen during daylight hours in the middle of boston, when there are a lot of polygons to push. It seems it crashes because the engine can't cope and having it unlocked gives it a better chance. Still crashes in the middle of boston in the afternoon, but been working out ok so far, and when it doens't, just do what you do, turn off 3d, go into a small room, turn on 3d. iPresentInterval=0 still needs to be 0 in documents
mistersvin said:
Mournz said:
MJ1911 said:
Mournz said:I'm crashing every time I get to the loading screen after hitting continue.

i dont rly understand.. are you playing with vsync off ???

Now, after installing 359 and rolling back to 358 driver i have crashes, turning off vsync doesnt help - i have to turn 3d off, go indoors, save, restart 3d and the game and go outdoors, only this way i can load the game without crashing (besides this does not resolve random crashes)


Yes, against the instructions, we are playing with V-Sync off. It helps with framerate stutters and loading times. I think this is because the frame rate is somehow tied to how much processor power is used, so that if it is unlocked during loading screens, your processor goes into turbo mode and loads the assets faster. Also, the crashes that occur on my sytem happen during daylight hours in the middle of boston, when there are a lot of polygons to push. It seems it crashes because the engine can't cope and having it unlocked gives it a better chance.

Still crashes in the middle of boston in the afternoon, but been working out ok so far, and when it doens't, just do what you do, turn off 3d, go into a small room, turn on 3d.

iPresentInterval=0 still needs to be 0 in documents

i7 3770K
970
8GB

Posted 11/21/2015 12:00 AM   
[quote="MJ1911"][quote="mistersvin"][quote="Mournz"][quote="MJ1911"][quote="Mournz"]I'm crashing every time I get to the loading screen after hitting continue. i dont rly understand.. are you playing with vsync off ??? Now, after installing 359 and rolling back to 358 driver i have crashes, turning off vsync doesnt help - i have to turn 3d off, go indoors, save, restart 3d and the game and go outdoors, only this way i can load the game without crashing (besides this does not resolve random crashes)[/quote] Yes, against the instructions, we are playing with V-Sync off. It helps with framerate stutters and loading times. I think this is because the frame rate is somehow tied to how much processor power is used, so that if it is unlocked during loading screens, your processor goes into turbo mode and loads the assets faster. Also, the crashes that occur on my sytem happen during daylight hours in the middle of boston, when there are a lot of polygons to push. It seems it crashes because the engine can't cope and having it unlocked gives it a better chance. Still crashes in the middle of boston in the afternoon, but been working out ok so far, and when it doens't, just do what you do, turn off 3d, go into a small room, turn on 3d. iPresentInterval=0 still needs to be 0 in documents [/quote] well i know about this, but i cant play with vsync off since my eyes bleeding. What about urs ?
MJ1911 said:
mistersvin said:
Mournz said:
MJ1911 said:
Mournz said:I'm crashing every time I get to the loading screen after hitting continue.

i dont rly understand.. are you playing with vsync off ???

Now, after installing 359 and rolling back to 358 driver i have crashes, turning off vsync doesnt help - i have to turn 3d off, go indoors, save, restart 3d and the game and go outdoors, only this way i can load the game without crashing (besides this does not resolve random crashes)


Yes, against the instructions, we are playing with V-Sync off. It helps with framerate stutters and loading times. I think this is because the frame rate is somehow tied to how much processor power is used, so that if it is unlocked during loading screens, your processor goes into turbo mode and loads the assets faster. Also, the crashes that occur on my sytem happen during daylight hours in the middle of boston, when there are a lot of polygons to push. It seems it crashes because the engine can't cope and having it unlocked gives it a better chance.

Still crashes in the middle of boston in the afternoon, but been working out ok so far, and when it doens't, just do what you do, turn off 3d, go into a small room, turn on 3d.

iPresentInterval=0 still needs to be 0 in documents



well i know about this, but i cant play with vsync off since my eyes bleeding. What about urs ?

Posted 11/21/2015 01:19 AM   
The original instruction to have VSync ON was a result of a game bug whereby you can get stuck at terminals, unable to move away from them, with it turned off. I had this problem from the get go. An alternative that I did not try was to cap the game FPS in Nvidia Inspector.
The original instruction to have VSync ON was a result of a game bug whereby you can get stuck at terminals, unable to move away from them, with it turned off. I had this problem from the get go. An alternative that I did not try was to cap the game FPS in Nvidia Inspector.

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

Posted 11/21/2015 01:29 AM   
[quote="MJ1911"]Glad to know. I suffered a crash again, which you may want to watch out for, this 3rd culprit: Window's 7 Aero Performance warnings. You know the one...your performance is slow...keep color settings and don't show this message again. I've gone through several driver updates and rollbacks and everytime, that message pops up. Except it won't be a message. While in 3D it CTDs. I only figured out it's the Aero Warinings when I turn off 3D, boot up the game, and then the game immediately Alt-Tabs me to desktop to inform me that the system wants to change my color scheme to improve performance. After selecting "dont show this message again" I boot up the game in 3D once again and it's mostly hassle free from there. Or you can disable it permanently by going to Control Panel, System Security, Action Center, Change Action Center Settings, untick Windows trouble shooting.[/quote] I've had that message pop up (or one asking me if I wanted to change color scheme to basic) on occasion in this game and other 3d games, usually means a crash to desktop or other crash when that pops up.. The annoying thing for me was after selecting don't show this message again, yeah it would show again.. Thanks for that tip on disabling it in the control panel. Should help with this and other games!
MJ1911 said:Glad to know. I suffered a crash again, which you may want to watch out for, this 3rd culprit: Window's 7 Aero Performance warnings. You know the one...your performance is slow...keep color settings and don't show this message again.

I've gone through several driver updates and rollbacks and everytime, that message pops up. Except it won't be a message. While in 3D it CTDs. I only figured out it's the Aero Warinings when I turn off 3D, boot up the game, and then the game immediately Alt-Tabs me to desktop to inform me that the system wants to change my color scheme to improve performance. After selecting "dont show this message again" I boot up the game in 3D once again and it's mostly hassle free from there.

Or you can disable it permanently by going to Control Panel, System Security, Action Center, Change Action Center Settings, untick Windows trouble shooting.


I've had that message pop up (or one asking me if I wanted to change color scheme to basic) on occasion in this game and other 3d games, usually means a crash to desktop or other crash when that pops up.. The annoying thing for me was after selecting don't show this message again, yeah it would show again..

Thanks for that tip on disabling it in the control panel. Should help with this and other games!

NZXT Noctis 450. Asus ROG Formula VIII, 6700k, NZXT Kracken x61. Avexir Core DDR4 (Red) 16g. Windows 10. Samsung Evo 1T & 2T SSD. Asus Strix 2080 ti. EVGA 1300w Modular Gold PSU.
Asus ROG Swift PG278Q Monitor: 1440p 3D Vision

Posted 11/21/2015 01:35 AM   
[quote="mike_ar69"]The original instruction to have VSync ON was a result of a game bug whereby you can get stuck at terminals, unable to move away from them, with it turned off. I had this problem from the get go. An alternative that I did not try was to cap the game FPS in Nvidia Inspector.[/quote] Nice to know for clarification. I had used a mod previously to unlock fps, and before using 3d my fps went from 60 to like 90-130 fps (at 1440p). I did get stuck at a couple terminals so now I see that is tied to vsync in some way.. I'll deal with the terminal sticking if it happens again (only happened at certain terminals) and just fix it if I need to reload a stuck terminal. (Couple other side effects like really fast lockpicking and other faster movements) It also seemed to load graphics faster after unlocking fps..
mike_ar69 said:The original instruction to have VSync ON was a result of a game bug whereby you can get stuck at terminals, unable to move away from them, with it turned off. I had this problem from the get go. An alternative that I did not try was to cap the game FPS in Nvidia Inspector.


Nice to know for clarification. I had used a mod previously to unlock fps, and before using 3d my fps went from 60 to like 90-130 fps (at 1440p). I did get stuck at a couple terminals so now I see that is tied to vsync in some way.. I'll deal with the terminal sticking if it happens again (only happened at certain terminals) and just fix it if I need to reload a stuck terminal. (Couple other side effects like really fast lockpicking and other faster movements) It also seemed to load graphics faster after unlocking fps..

NZXT Noctis 450. Asus ROG Formula VIII, 6700k, NZXT Kracken x61. Avexir Core DDR4 (Red) 16g. Windows 10. Samsung Evo 1T & 2T SSD. Asus Strix 2080 ti. EVGA 1300w Modular Gold PSU.
Asus ROG Swift PG278Q Monitor: 1440p 3D Vision

Posted 11/21/2015 01:38 AM   
Losti - what is that SweetFX called ? I found one similar to yours but I don`t know if that is the right one - Ultra Realistic CiNE FX v1.3.
Losti - what is that SweetFX called ?

I found one similar to yours but I don`t know if that is the right one - Ultra Realistic CiNE FX v1.3.
[quote="SKAUT"]Losti - what is that SweetFX called ? I found one similar to yours but I don`t know if that is the right one - Ultra Realistic CiNE FX v1.3.[/quote] https://sfx.thelazy.net/games/preset/4671/ SweetFX is based on Reshade with SweetFX 2.0. The profile is made with 3D Vision-Light-Boost @ 100 % and Contrast @ 30.
SKAUT said:Losti - what is that SweetFX called ?

I found one similar to yours but I don`t know if that is the right one - Ultra Realistic CiNE FX v1.3.



https://sfx.thelazy.net/games/preset/4671/

SweetFX is based on Reshade with SweetFX 2.0.

The profile is made with 3D Vision-Light-Boost @ 100 % and Contrast @ 30.

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

Posted 11/21/2015 10:00 AM   
  22 / 44    
Scroll To Top