![]() I'll try sending him something, but I feel like I would've gotten a message back by now from my first attempt. I've tried all the above, and it doesn't seem like I'm alone either, so if anyone has a better solution or work around, I think that Boris's going to have the answer. Processor at around 3.0GHz Graphics card with 1GB or 2GB VRAM 6GB RAM Recommended Specs (+- 50-60 FPS) Processor around 4. That, and would be forced to start a new game. I guess there is Tale of Two Wastelands, but I'd rather not go through the hassle of setting it up just to get and ENB to (maybe) work. Given the fact that Fallout 3's run out of its appeal in recent times, I'm not sure if anyone's willing to make a fix for this issue anytime soon. ![]() Other than that, my Fallout 3 IS playable, I just can't run an ENB alongside it with the d3d9.dll, which is kind of a pisser with all the time that I had spent getting my Midrhastic ENB preferences tweaked and settled. I would have rolled back to a previous version of Windows to avoid being in this state, but my computer had a fatal error a while back, and had to do all sorts of junk to get it to work again, so it wasn't able to record a system restore point during all that misfortune. If that's what I think it is, then the only way I think it can be fixed is if someone gets a hold of Boris at enbdev to update the binaries to coexist with what ever Windows 10 changed. I couldn't tell you exactly how it did so specifically, but I know that it doesn't play nice with the latest ENB binaries. For a time, my ENB was running flawlessly unitl a Windows 10 update came along and washed it away.
0 Comments
Leave a Reply. |