Well, maybe this one is a better shot. ;)
[img]https://abload.de/img/falloutnv005_099.jpsobjrv.jpg[/img]
Shader-CRC's are the same but Texture-CRC's are different.
And I really have not much time at the moment. This fix progress had been frozen for the last two weeks, but maybe this weekend I can finish it for a release. :)
Shader-CRC's are the same but Texture-CRC's are different.
And I really have not much time at the moment. This fix progress had been frozen for the last two weeks, but maybe this weekend I can finish it for a release. :)
Desktop-PC
i7 870 @ 3.8GHz + MSI GTX1070 Gaming X + 16GB RAM + Win10 64Bit Home + AW2310+3D-Vision
Fallout NV. :)
Found this game for 5€ (Ultimate Edition uncut for Steam), so I try to adopt my FO3 fix. Seems to work, but I still have to find the correct texture CRC's.
New California seems to be a big mod for FoNV, so chances are high, that it works with my fix too. If they left the graphics-engine untouched *fingers crossed* .
Fallout NV. :)
Found this game for 5€ (Ultimate Edition uncut for Steam), so I try to adopt my FO3 fix. Seems to work, but I still have to find the correct texture CRC's.
New California seems to be a big mod for FoNV, so chances are high, that it works with my fix too. If they left the graphics-engine untouched *fingers crossed* .
Desktop-PC
i7 870 @ 3.8GHz + MSI GTX1070 Gaming X + 16GB RAM + Win10 64Bit Home + AW2310+3D-Vision
[b][color="orange"]New Fixes are out. :)
I proudly present the water-fix for Fallout New Vegas:[/color]
[/b]
[url]http://helixmod.blogspot.com/2017/08/fallout-3.html[/url]
[url]http://helixmod.blogspot.com/2018/06/fallout-new-vegas.html[/url]
-fixed another water shader (underwater)
-convergence preset for Terminal-View
So the fix is unfortunately crashing my game. Disabling 3D Vision and the fix stops the crashing.
Here's what I get in the nvac.log generated by the New Vegas Anti Crash mod. As you can see, multiple exceptions by the d3d9.dll, all at the timestamp of the crash:
03005737 _ NewVegasAntiCrash FalloutNV.exe
03005737 _ 036D0000 07050000 nvac.dll
03005737 _ 0D700000 05010040 nvse_1_4.dll
03005737 _ 778A0000 0A0042EE ntdll.dll
03005741 ; DEFAULT: Unknown file type on file 0
03005745 ; DEFAULT: Unknown file type on file 0
03010139 h 6F591DF9 8B088B51 d3d9.dll
03010139 ^ 00E68DD2 00000156 FalloutNV.exe
03010139 h 6F591DFB 8B510850 d3d9.dll
03010139 ^ 00E68DD2 00000156 FalloutNV.exe
03010139 n 00000000 6F591E01
03010139 r 6F591E01 00000000 d3d9.dll
03010139 ^ 00E68DD2 00000158 FalloutNV.exe
03010139 n 00000000 14CC4520
03010139 r 778E22D3 00000104 ntdll.dll
03010139 ^ 00E68DD2 0000004F FalloutNV.exe
03010139 n 00000000 00000000
03010139 r 00E68DD2 00000009 FalloutNV.exe
03010139 h 778E2144 807BFF05 ntdll.dll
03010139 ^ 00ECD2FF 00000012 FalloutNV.exe
03010139 h 7792EC4E 0FB64706 ntdll.dll
03010139 ^ 00ECD2FF 00000012 FalloutNV.exe
03010139 h 778E2151 F647073F ntdll.dll
03010139 ^ 00ECD2FF 00000012 FalloutNV.exe
03010139 h 00E68E48 8B178B82 FalloutNV.exe
03010139 h 00E68E4A 8B82B000 FalloutNV.exe
03010139 n 00000000 00E68E55
03010139 r 00E68E55 00000000 FalloutNV.exe
03010139 h 00E68E5F 894F0C89 FalloutNV.exe
03010139 h 00E68E62 89571084 FalloutNV.exe
03010139 h 00E68E6B 8B480856 FalloutNV.exe
03010139 n 00000000 00E68E71
03010139 r 00E68E71 00000000 FalloutNV.exe
03010140 q 00E68C2E C0000409 FalloutNV.exe
03010140 _ CRASHSAV E_THREAD FalloutNV.exe
03010140 ! CRASHSAV E_FAIL_0 FalloutNV.exe
Making it happen in game was fairly easy. From a new game saved just outside of Doc Mitchell's house, I'd run to Prospector's Saloon, entered fine. Ran back to and inside Doc Mitchell's, also fine. Then back out and into Prospector's Saloon again. Crash every time.
With 3D Vision (and fix) disabled, no crashing or exceptions at all. This is using the first person version, by the way, and no attempt to run ENBoost concurrently (setting proxy library didn't work for me).
I tried it with the older 2013 fix too, and that crashed me on entering Doc Mitchell's, so even worse.
Here's hoping I've provided enough information to nail it down.
EDIT: Profile information below is a bit outdated, I'm running on a single 1080Ti instead of 2 980Tis now.
So the fix is unfortunately crashing my game. Disabling 3D Vision and the fix stops the crashing.
Here's what I get in the nvac.log generated by the New Vegas Anti Crash mod. As you can see, multiple exceptions by the d3d9.dll, all at the timestamp of the crash:
03005737 _ NewVegasAntiCrash FalloutNV.exe
03005737 _ 036D0000 07050000 nvac.dll
03005737 _ 0D700000 05010040 nvse_1_4.dll
03005737 _ 778A0000 0A0042EE ntdll.dll
03005741 ; DEFAULT: Unknown file type on file 0
03005745 ; DEFAULT: Unknown file type on file 0
03010139 h 6F591DF9 8B088B51 d3d9.dll
03010139 ^ 00E68DD2 00000156 FalloutNV.exe
03010139 h 6F591DFB 8B510850 d3d9.dll
03010139 ^ 00E68DD2 00000156 FalloutNV.exe
03010139 n 00000000 6F591E01
03010139 r 6F591E01 00000000 d3d9.dll
03010139 ^ 00E68DD2 00000158 FalloutNV.exe
03010139 n 00000000 14CC4520
03010139 r 778E22D3 00000104 ntdll.dll
03010139 ^ 00E68DD2 0000004F FalloutNV.exe
03010139 n 00000000 00000000
03010139 r 00E68DD2 00000009 FalloutNV.exe
03010139 h 778E2144 807BFF05 ntdll.dll
03010139 ^ 00ECD2FF 00000012 FalloutNV.exe
03010139 h 7792EC4E 0FB64706 ntdll.dll
03010139 ^ 00ECD2FF 00000012 FalloutNV.exe
03010139 h 778E2151 F647073F ntdll.dll
03010139 ^ 00ECD2FF 00000012 FalloutNV.exe
03010139 h 00E68E48 8B178B82 FalloutNV.exe
03010139 h 00E68E4A 8B82B000 FalloutNV.exe
03010139 n 00000000 00E68E55
03010139 r 00E68E55 00000000 FalloutNV.exe
03010139 h 00E68E5F 894F0C89 FalloutNV.exe
03010139 h 00E68E62 89571084 FalloutNV.exe
03010139 h 00E68E6B 8B480856 FalloutNV.exe
03010139 n 00000000 00E68E71
03010139 r 00E68E71 00000000 FalloutNV.exe
03010140 q 00E68C2E C0000409 FalloutNV.exe
03010140 _ CRASHSAV E_THREAD FalloutNV.exe
03010140 ! CRASHSAV E_FAIL_0 FalloutNV.exe
Making it happen in game was fairly easy. From a new game saved just outside of Doc Mitchell's house, I'd run to Prospector's Saloon, entered fine. Ran back to and inside Doc Mitchell's, also fine. Then back out and into Prospector's Saloon again. Crash every time.
With 3D Vision (and fix) disabled, no crashing or exceptions at all. This is using the first person version, by the way, and no attempt to run ENBoost concurrently (setting proxy library didn't work for me).
I tried it with the older 2013 fix too, and that crashed me on entering Doc Mitchell's, so even worse.
Here's hoping I've provided enough information to nail it down.
EDIT: Profile information below is a bit outdated, I'm running on a single 1080Ti instead of 2 980Tis now.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
Wow. Seems I've found the solution myself.
After disabling 3D (sobbing uncontrollably all the while), I decided I might as well use ENBoost, which I previously wasn't using because when I tried to call the 3D Fix as a proxy library, it would crash MO2 on startup. So, initially had issues with the proper settings of ENBoost by itself, but after playing around with the settings enough, I got it working well and stable.
Then I thought, you know, the last time I tried to run 3D through enblocal.ini as a proxy, it didn't work... but my settings are different now. Let's try it! And holy cow, it worked. And apparently, the extra memory provided by ENBoost is enough to keep it from crashing in the same situation that I mentioned in my last post.
And with some optimized settings for NVSR, I now have what IMO is the holy grail: 3D Vision AND ENBoost running on Windows 10 with no noticeable stuttering or load hitching! A lot of people have had issues getting just FNV to run on Windows 10 *at all* without serious stuttering, so I'm pretty delighted here.
Sorry if anyone spent time looking at my issue. It looks like the crashing I was having as of the last post were mainly a result of running out of memory.
After disabling 3D (sobbing uncontrollably all the while), I decided I might as well use ENBoost, which I previously wasn't using because when I tried to call the 3D Fix as a proxy library, it would crash MO2 on startup. So, initially had issues with the proper settings of ENBoost by itself, but after playing around with the settings enough, I got it working well and stable.
Then I thought, you know, the last time I tried to run 3D through enblocal.ini as a proxy, it didn't work... but my settings are different now. Let's try it! And holy cow, it worked. And apparently, the extra memory provided by ENBoost is enough to keep it from crashing in the same situation that I mentioned in my last post.
And with some optimized settings for NVSR, I now have what IMO is the holy grail: 3D Vision AND ENBoost running on Windows 10 with no noticeable stuttering or load hitching! A lot of people have had issues getting just FNV to run on Windows 10 *at all* without serious stuttering, so I'm pretty delighted here.
Sorry if anyone spent time looking at my issue. It looks like the crashing I was having as of the last post were mainly a result of running out of memory.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
Awesome work Flint :)
@Qwinn
I ran into this thread awhile back on Reddit, no idea if it would help at all with this problem, but I figured that it might be worth mentioning
https://www.reddit.com/r/Windows10/comments/7a0763/standby_memory_issue_causing_stutters_on_creators/?sort=new
Win7 64bit Pro
CPU: 4790K 4.8 GHZ
GPU: Aurus 1080 TI 2.08 GHZ - 100% Watercooled !
Monitor: Asus PG278QR
And lots of ram and HD's ;)
Shader-CRC's are the same but Texture-CRC's are different.
And I really have not much time at the moment. This fix progress had been frozen for the last two weeks, but maybe this weekend I can finish it for a release. :)
Desktop-PC
i7 870 @ 3.8GHz + MSI GTX1070 Gaming X + 16GB RAM + Win10 64Bit Home + AW2310+3D-Vision
2 Wildcards though - Fallout NV or perhaps New California ?? But NC wont be out in the next 121 days...Hmmm..
Win7 64bit Pro
CPU: 4790K 4.8 GHZ
GPU: Aurus 1080 TI 2.08 GHZ - 100% Watercooled !
Monitor: Asus PG278QR
And lots of ram and HD's ;)
Found this game for 5€ (Ultimate Edition uncut for Steam), so I try to adopt my FO3 fix. Seems to work, but I still have to find the correct texture CRC's.
New California seems to be a big mod for FoNV, so chances are high, that it works with my fix too. If they left the graphics-engine untouched *fingers crossed* .
Desktop-PC
i7 870 @ 3.8GHz + MSI GTX1070 Gaming X + 16GB RAM + Win10 64Bit Home + AW2310+3D-Vision
Win7 64bit Pro
CPU: 4790K 4.8 GHZ
GPU: Aurus 1080 TI 2.08 GHZ - 100% Watercooled !
Monitor: Asus PG278QR
And lots of ram and HD's ;)
I proudly present the water-fix for Fallout New Vegas:
http://helixmod.blogspot.com/2017/08/fallout-3.html
http://helixmod.blogspot.com/2018/06/fallout-new-vegas.html
-fixed another water shader (underwater)
-convergence preset for Terminal-View
Desktop-PC
i7 870 @ 3.8GHz + MSI GTX1070 Gaming X + 16GB RAM + Win10 64Bit Home + AW2310+3D-Vision
THANKS Flint, much appreciated :)
Win7 64bit Pro
CPU: 4790K 4.8 GHZ
GPU: Aurus 1080 TI 2.08 GHZ - 100% Watercooled !
Monitor: Asus PG278QR
And lots of ram and HD's ;)
Here's what I get in the nvac.log generated by the New Vegas Anti Crash mod. As you can see, multiple exceptions by the d3d9.dll, all at the timestamp of the crash:
03005737 _ NewVegasAntiCrash FalloutNV.exe
03005737 _ 036D0000 07050000 nvac.dll
03005737 _ 0D700000 05010040 nvse_1_4.dll
03005737 _ 778A0000 0A0042EE ntdll.dll
03005741 ; DEFAULT: Unknown file type on file 0
03005745 ; DEFAULT: Unknown file type on file 0
03010139 h 6F591DF9 8B088B51 d3d9.dll
03010139 ^ 00E68DD2 00000156 FalloutNV.exe
03010139 h 6F591DFB 8B510850 d3d9.dll
03010139 ^ 00E68DD2 00000156 FalloutNV.exe
03010139 n 00000000 6F591E01
03010139 r 6F591E01 00000000 d3d9.dll
03010139 ^ 00E68DD2 00000158 FalloutNV.exe
03010139 n 00000000 14CC4520
03010139 r 778E22D3 00000104 ntdll.dll
03010139 ^ 00E68DD2 0000004F FalloutNV.exe
03010139 n 00000000 00000000
03010139 r 00E68DD2 00000009 FalloutNV.exe
03010139 h 778E2144 807BFF05 ntdll.dll
03010139 ^ 00ECD2FF 00000012 FalloutNV.exe
03010139 h 7792EC4E 0FB64706 ntdll.dll
03010139 ^ 00ECD2FF 00000012 FalloutNV.exe
03010139 h 778E2151 F647073F ntdll.dll
03010139 ^ 00ECD2FF 00000012 FalloutNV.exe
03010139 h 00E68E48 8B178B82 FalloutNV.exe
03010139 h 00E68E4A 8B82B000 FalloutNV.exe
03010139 n 00000000 00E68E55
03010139 r 00E68E55 00000000 FalloutNV.exe
03010139 h 00E68E5F 894F0C89 FalloutNV.exe
03010139 h 00E68E62 89571084 FalloutNV.exe
03010139 h 00E68E6B 8B480856 FalloutNV.exe
03010139 n 00000000 00E68E71
03010139 r 00E68E71 00000000 FalloutNV.exe
03010140 q 00E68C2E C0000409 FalloutNV.exe
03010140 _ CRASHSAV E_THREAD FalloutNV.exe
03010140 ! CRASHSAV E_FAIL_0 FalloutNV.exe
Making it happen in game was fairly easy. From a new game saved just outside of Doc Mitchell's house, I'd run to Prospector's Saloon, entered fine. Ran back to and inside Doc Mitchell's, also fine. Then back out and into Prospector's Saloon again. Crash every time.
With 3D Vision (and fix) disabled, no crashing or exceptions at all. This is using the first person version, by the way, and no attempt to run ENBoost concurrently (setting proxy library didn't work for me).
I tried it with the older 2013 fix too, and that crashed me on entering Doc Mitchell's, so even worse.
Here's hoping I've provided enough information to nail it down.
EDIT: Profile information below is a bit outdated, I'm running on a single 1080Ti instead of 2 980Tis now.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
After disabling 3D (sobbing uncontrollably all the while), I decided I might as well use ENBoost, which I previously wasn't using because when I tried to call the 3D Fix as a proxy library, it would crash MO2 on startup. So, initially had issues with the proper settings of ENBoost by itself, but after playing around with the settings enough, I got it working well and stable.
Then I thought, you know, the last time I tried to run 3D through enblocal.ini as a proxy, it didn't work... but my settings are different now. Let's try it! And holy cow, it worked. And apparently, the extra memory provided by ENBoost is enough to keep it from crashing in the same situation that I mentioned in my last post.
And with some optimized settings for NVSR, I now have what IMO is the holy grail: 3D Vision AND ENBoost running on Windows 10 with no noticeable stuttering or load hitching! A lot of people have had issues getting just FNV to run on Windows 10 *at all* without serious stuttering, so I'm pretty delighted here.
Sorry if anyone spent time looking at my issue. It looks like the crashing I was having as of the last post were mainly a result of running out of memory.
CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586
Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory
@Qwinn
I ran into this thread awhile back on Reddit, no idea if it would help at all with this problem, but I figured that it might be worth mentioning
https://www.reddit.com/r/Windows10/comments/7a0763/standby_memory_issue_causing_stutters_on_creators/?sort=new