Posted: 12 Sep 2013, 18:07

i have an AMD card, and the game works fine, the reply you guys give is that it does not work, but neither of you actually say if you did what i said.
Since your answers are half answers, there is no way for me to give you another suggestion, i have years of experience in dealing with the game's stability,
so i can probably give like 20 different ways to make the game crash less, but i cannot suggest anything if you guys don't say if you have done what i suggested.
it sounds to me like you don't want to solve the crashing problem, otherwise you would have let me know if you did what i said.
again, i have a AMD card with the latest drivers and Fallout has never run better then with the latest ENB.
first try the things i suggested, if it does not work, let me know and i have some new tips for you.

_________________
Intel I5 8600k, GTX 1080, 256GB Samsung EVO 970 M.2, 256GB Samsung EVO, 500GB Samsung EVO, 1,5TB WD Caviar Green, Realtek HD Audio, 16GB 15-17-17-36 3000MHZ System RAM, W7 Pro x64.

Posted: 12 Sep 2013, 19:03

I have tried both of those things with no luck. On my Nvidia card my games run surprisingly stable because I have done various tweaks to help.
I'm glad to hear that your game and ENB works with Fallout, I guess that means I was wrong and it is compatible with AMD.
@Boris: If extra software was running and conflicting with ENB, wouldn't it affect ENB on other games too? I have no idea how ENB is actually coded so in the mean time I'll retry disabling all the extra software.
Thanks for your help guys, I'm just frustrated at this and really busy with school work so I can't dedicate huge amounts of time to Fallout any more.

Posted: 12 Sep 2013, 19:17

I wrote in my previous post what is it, you may not agree, but for me it's fact. Any assumptions and conjectures not work when speaking about other software as they hooking in to game and enb very dirty way.

_________________
i5-4690k, 16Gb RAM, GTX 1060 6Gb, X-Fi Titanium, Win7 x128
I am INFP, not the brutal, godamnit.

Posted: 12 Sep 2013, 19:50

I really don't doubt that's what the problem is, but I can't for the life of me figure it out.
I started up in safe mod and got a bit further, instead of crashing immediately the screen turned green (before the menu loads up) then crashed.
In regular mode, I disabled literally every non-essential Windows process (from 100 processes to 30) and still the same results as before. Crashing right on startup, screen stays black.

Posted: 12 Sep 2013, 20:52

i can understand frustration, sometimes i get frustrated too, so there's no harm done.

No, every ENB is different, the code in it and where it reacts to is different, that's why the filesizes differ, cause there's new code added and old code revised sometimes.
If you don't know programming, then let me tell you that each program is different, each new ENB version is different, so you cannot compare Skyrim enb to Fallout enb.
It would be wise to not assume that you know what the problem must be if you do not know how it works.
this means that every ENB reacts differently to your game and card.
I bought Fallout New Vegas on a disc, but i had to install it with Steam, i never got Fallout NV running, ever !
I tried everything i could think of from Fallout 3 to make it run, it Always crashed on startup.
What i did to make it run was i downloaded a cracked version and after updating to the latest version on steam
i copied the FalloutNV.exe from the cracked version over my steam exe, and that was the only way to make it start.
try that and see if you can start it up.
You can also try to set the ?2GB flag on the exe with cff explorer, if you don't know how to do that.let me know.
same for a friend of mine, he could get it to run from steam, but at a given moment he had to reinstall and the steam version did not work anymore,
after that he tried everything you can think of, never got it running till he used the cracked version.
it can also help if you install the game outside of the program files directory, windows can mess up the file permissions.
if it does run without ENB and not with ENB i would try some different drivers.
you can also try to disable most features of the memory manager in enbseries.ini to see if you can get it to run.
then one by one enable stuff again and set memory sizes.
and don't use cc from ati, use radeonpro, it has more options.
don't use any overlay programs like fraps or other stuff.
disable AA and Water displacement.
i'm sure you know these things but it can't hurt to double check this stuff after a fresh install.
and last but not least, do a fresh ENB install, do not use old enbseries.ini files, copy back the settings and files later one by one if it starts.
if you do just replace the dll and put the new enbhost.exe in the directory things can go wrong badly.

_________________
Intel I5 8600k, GTX 1080, 256GB Samsung EVO 970 M.2, 256GB Samsung EVO, 500GB Samsung EVO, 1,5TB WD Caviar Green, Realtek HD Audio, 16GB 15-17-17-36 3000MHZ System RAM, W7 Pro x64.

Posted: 12 Sep 2013, 23:25

Awesome thanks for the suggestions. I have to write an essay right now, but as soon as I get a chance I'll try what you said and report back. Hopefully we can get this figured out.
Update: Ok... Tried everything here, no luck. I set everything in ENBseries regarding memory management to off, no extra software (I think, killed all extra tasks via taskmanager that I could), used older drivers (on 13.4 now, tried 13.1), checked that AA and Water displacement were off (they were), tried a clean ENB install, but I can't not use CCC. Every time I download AMD drivers CCC is automatically used to install them. I forgot to clarify earlier, the game works fine without ENB running.
I double checked and made sure that everything Fallout related is running as admin and in XP compatibility mode. Fo3.exe is already large address aware (I made it 3gb iirc).
I will get this to work, eventually.
If you don't mind, could I take a look at your ENBseries.ini? I tried forcing NVidia card (both settings) but that didn't work either.
Also, one last thought. Do you think it could be something to do with the Fallout.ini/rendererinfo.ini/falloutprefs.ini? I've looked through those and changed a couple of settings, and also replaced them with clean versions but that didn't work either.

Posted: 14 Sep 2013, 01:14

I can install only drivers with AMD's driver package with the installer.
Dont set it to XP comp mode when you have the more then 2 GB flag set, XP86 can't handle that, the emulator either.
Yeah i will include a zip with my ini files, both from the game and enb.
It could definitely be something in the ini files, but usually when it is something in the game's ini files
the game will not run without enb either, so i don't think that will help if it is working without enb.
try downloading the latest DX( from microsoft and install that, maybe some other files are outdated or missing.
you have the steam version ?
try to copy the latest skidrow exe over the FalloutNV.exe and make it larg adress aware again.
also make sure you have NVSE and the stutter remover installed.
the stutter remover also has some improvements to make sure the game crashes less.
https://www.dropbox.com/s/d8dog80yyn4i0p8/all%20ini%20files.rar

_________________
Intel I5 8600k, GTX 1080, 256GB Samsung EVO 970 M.2, 256GB Samsung EVO, 500GB Samsung EVO, 1,5TB WD Caviar Green, Realtek HD Audio, 16GB 15-17-17-36 3000MHZ System RAM, W7 Pro x64.

Posted: 14 Sep 2013, 12:48

I agree. None of anyones suggestion works, and people keep coming up with the same problems. If your not willing to fix the issue and just blame the user then fine, like the guy said you dont owe us anything. But its pretty clear whats going on. And should be said to anyone else with these issues your probably not going to get any help because of this.
But its not that big of a deal, ENB Series is not needed to play.

Posted: 14 Sep 2013, 16:24

So if you understand that he doesn't owe you anything, why are you complaining ?
play with a older version that works.
or try with the injector, since that seemed to work with chicknwatermelon.
In the end Boris always fixes problems if it becomes really clear that the fault lies within his ENB.
But since people usually give little information to work with for him, his only logical conclusion will be that the problem lies with you.
The only thing you say is that it doesn't work, how is he supposed to figure out from that what the problem must be ?
If you bring you PC to him maybe he can find out what the problem is, otherwise, it is impossible to fix, by guessing maybe ?

_________________
Intel I5 8600k, GTX 1080, 256GB Samsung EVO 970 M.2, 256GB Samsung EVO, 500GB Samsung EVO, 1,5TB WD Caviar Green, Realtek HD Audio, 16GB 15-17-17-36 3000MHZ System RAM, W7 Pro x64.

Posted: 14 Sep 2013, 17:10

Well I started fiddling with the ini files, changing some of my settings to the ones you use but still no luck. I disabled compatibility mode, that didn't work either.
I have already installed the lastest DX files, I reinstalled them but no dice.
I do have the steam version. My Fo3 and FNV both have script extenders and stutter remover already installed.
Thanks for all your help, I'm determined to make this work haha.
Oh and to clear things up, the injector did not work for me. The game would still freeze upon ENB being used in the game world.

Posted: 14 Nov 2015, 02:00

There is some major misinformation in your video regarding VSync. ENB's Vsync is currently the best form of Vsync available for Fallout 4. Why? Because FO4's stock Vsync introduces input lag if you are not at full FPS, even with mouse acceleration off. This was a bug with Skyrim as well that they eventually corrected, but it's back with Fallout 4. There's also a 30fps limit if you are running fullscreen mode, and this ALSO introduces input lag! Thus it's best to turn Fallout 4's Vsync off in FalloutPrefs (iPresentInterval) and just use this one.
It is also superior to Adaptive Vsync because Adaptive Vsync WILL have screen tearing.

Posted: 14 Nov 2015, 02:06

As a sidenote, ENB's frame limiter is also the only frame limiter anyone should be using. If you try to enforce an fps limit through your drivers, this will cause input lag as well.
So in summation, ENB's VSync and Frame Limiters are the only method I've seen to do both these things without any sort of input lag or screen tearing. Use em.

Posted: 14 Nov 2015, 02:16

Well, MSI Afterburner (RivaTuner) fps limiter is also working great, no any input lag.

Posted: 14 Nov 2015, 03:01

@Bonnie Lass
There is no misinformation in my video because all I claim is that I notice no difference with the vsync effect, I do not claim that it does nothing.
There is, however, misinformation in your comment:

Boris himself says that the in-game vsync needs to be enabled to see any benefit from ENB's vsync feature. From the mod page:

_________________
Fallout 4 ENB Video Series | Skyrim ENB Video Series | My YouTube Channel
Intel i7-4700HQ @ 2.4GHz | NVidia GTX780M 4GB | 24GB RAM

Posted: 14 Nov 2015, 03:02

I don't see how that can be possible. With the frame limiter off and iPresentInterval set to 0 in FalloutPrefs.ini, it caps Fallout 4 to 60 fps. If I turn off ForceVSync, it's no longer capped at 60fps and will start screen tearing. It is clearly working without the in-game vsync turned on, you can test for yourself.

Posted: 14 Nov 2015, 03:06

Where exactly are you reading that line? I don't see it anywhere on the enb site. It can't be the nexusmods page, because it says this there:
'ForceVSync - this is a bit different thing compared to game vsync, i won't
describe how it works, but for some game setting and users it could be very
useful, better than own game vsync.'

Posted: 14 Nov 2015, 03:13

Well I found where he says it, he says it in a comment to somebody on the nexusmods page.
Boris, can you please investigate this? Your Vsync appears to be working without having to have the default vsync on at all. I can reproduce it easily. I just boot the game up with ipresentinterval=0 and your fps limit off, and the fps skyrockets. As soon as I tick 'ForceVSync' in the ENB menu, it properly caps and there's no screen tearing whatsoever.

Posted: 14 Nov 2015, 03:22

Hi Bonnie,
I pulled that from one of Boris' comments on his Nexus mod page. I'm not trying to pick an argument here, I concede that I do not know the ENB vsync feature really works or how it is meant to work. I just replied to your initial comment to suggest that my video does not have any 'major misinformation' about vsync; I just speak honestly about my personal experience with the feature. In any case, there will be plenty of opportunity for more videos, and I am happy to make corrections and amendments to my comments as appropriate. So, if I learn to better understand ENB's vsync or I am able to identify some benefit on my own (or if someone else can demonstrate the benefit to me), then I will likely cover this in a future video.
Seriously though, no hard feelings. I am just an enb 'enthusiast' making videos, not a real 'expert'..

_________________
Fallout 4 ENB Video Series | Skyrim ENB Video Series | My YouTube Channel
Intel i7-4700HQ @ 2.4GHz | NVidia GTX780M 4GB | 24GB RAM

Posted: 14 Nov 2015, 03:24

I'm not trying to make an argument either, I'm just genuinely confused.
Doing some more testing, it does appear that Boris's ForceVSync feature actually corrects the bug that limits Fallout 4 to 30fps in fullscreen mode. So while it may still work when you turn it off, it appears like it's unnecessary to do so.

Posted: 14 Nov 2015, 03:39

Hmm, that's curious. For me, Fallout is not limited to 30 FPS in fullscreen mode , even without ENB. The built in vsync in Fallout 4 seems to be triple buffered, such that the framerate doesn't 'snap' to 30 or 60, but can fluctuate between those two.
Anyone else out there having a similar experience with this 30FPS cap in fullscreen?

_________________
Fallout 4 ENB Video Series | Skyrim ENB Video Series | My YouTube Channel
Intel i7-4700HQ @ 2.4GHz | NVidia GTX780M 4GB | 24GB RAM