Jump to content

Crispy81

Members
  • Posts

    25
  • Joined

  • Last visited

Everything posted by Crispy81

  1. Already reported here: https://forums.obsidian.net/topic/104841-bug-guardian-of-ukaizo-fight-not-occurring/ Terrible, almost show-stopping bug. I think you can just proceed without dealing with the Guardian, but who wants to do that? Please fix this, Obsidian.
  2. I've got the exact same bug. BoW installed. This is a terrible bug. Embarrassing, even. This should be the crescendo to the story and it spoils the entire experience. Shame on you, Obsidian. You really, really need to fix this immediately.
  3. The sound effect when Eder lights up his pipe is the same as when he equips the helm Okura's Kettle, and not the correct "striking flint" noise that it should be. This wasn't happening in prior versions. Please address, thanks. Edit: This appears to be intermittent in nature. I'm not sure what triggers the bug or not.
  4. I've seen the same thing. It's irritating. The other thing I can't stand is that the game doesn't respect my level of zoom. I'd prefer it if it remained the same from scene to scene and location to location, unless for "dramatic" purposes in a cut-scene.
  5. All I can think of is to try reaching out to the guy who came up with this fix. He last posted in the original thread (https://steamcommunity.com/app/560130/discussions/0/2572002906843374108/) yesterday (August 1). By the way, this still works for the newest version of the game, 2.0. Hope you can get it working for yourself.
  6. I still have a permanent (but non-active?) buff on Eder from the Grave Calling saber. It actually lists it as X2. Irritating.
  7. Sorry for not updating. You guys must be pretty confused. I have confirmed that custom_dxgi.ini is absolutely NOT required to get this working. Inexplicably, it was included in op's download previously, but you're both correct that it's no longer in there. Regardless, like I said, that file is completely unnecessary in order to affect the fix. What is not known, obviously, is why it's still not working for you. I don't know, but I suspect you've either got the files in the wrong area (they need to go into your PoE 2 game folder, e.g., C:\Program Files (x86)\Steam\SteamApps\common\Pillars of Eternity II) or that the download was corrupted, or there's some other factor involved. You are using the Steam version of this game and not the GOG version, right? Even stranger, op has closed the original thread this appeared in, apparently convinced that his fix was NOT responsible for the vast performance improvements it made in PoE 2, blaming, rather, some other 3rd-party software present on his computer! It's baffling, but I can tell you this: it's the only thing that made any different in mine, it was immediate, it was apparent, and unmistakable. Most of us can claim this, but I truly do run an extremely well-maintained PC which is kept up-to-date with everything, all the time. So I have no idea what he's talking about now and, frankly, it's a bit disturbing. Anyway, I hope this somehow helps you guys.
  8. Extract the entire archive there. You'll know it's working when you launch the game, because you'll see a banner across the top of the screen.
  9. Neketaka is a different story. When it's clear weather, it runs buttery smooth. But when the rain and mist effect shows up in Neketaka, even with the .dll fix, framerates slow down and there is some "choppiness". It's much better than before, but not as good as I'd like to see.
  10. Wanted to report that in Neketaka when it's raining with all the mist everywhere even this amazing fix doesn't help much. FPS on my system (see above) still dips into the 50s in that situation. It's still a lot smoother than without the .dll patch, but it still makes me want to see more improvements made. And yes, I could easily turn off the weather effects in options, but that's just a work-around.
  11. I do and it's fully enabled and not in and of itself causing any micro stuttering. See, however, this thread: https://forums.obsidian.net/topic/103723-so-uh-i-fixed-one-of-the-games-performance-problems-with-whom-do-i-speak/ This fix will probably help you out a whole lot.
  12. Holy monkey spit, did this make a dramatic improvement! My specs: 6850K @ 4.5GHz 32GB DDR4-3333 1080Ti 1440p w/ G-Sync SSD I was already achieving 80+ fps in most areas, even in Neketaka, but it was always choppy. This .dll fix makes things buttery-smooth. Much thanks. Obsidian, TAKE NOTE. Edit: To clarify, I used the exact same settings as OP, including the SwapChain settings.
  13. I am not running windows. I use a Mac. I may be confused here, but if you say you've got the PC version of PoE 2, how is it you're not running Windows? That was the purpose of my first question, whether you're running Windows from Boot Camp or not. If you're actually running the Mac version of PoE 2, then we're back to my original advice: since you're trying to run this on the bare minimum specs for Mac, that's probably why it's not running right. Remember that running the PC version of this game on its bare minimum requirements is causing all sorts of problems ranging from... well, let's just say they're similar to your problems. One last question: you also claimed that you've got a "NEW IMAC, NEW NEW NEW", but your own specs screenshot indicates the unit was made in 2013. Uh, that's not new...
  14. If you're running Windows, do you have it configured to boot on its own using something similar to Boot Camp or Parallels, or are you somehow running this in an emulated mode like with "GeForce Now"? If it's the latter, it doesn't surprise me at all that there are compatibility issues.
  15. I can tell you as a former SLI user (2 x 970) that with my new 1080Ti, and the newest patch, things seem better but not yet by any means ideal. I run in 1440p and the framerate in Neketaka still sometimes dips into the high 60s, mainly hovering around 75-80. I still suspect that if the option to force the rendering to OpenGL were reinstated, things would be even smoother. SLI will likely never be fully supported by this or any other Unity title.
  16. I was just about to report this myself. It's incredible how many bugs Obsidian introduces in their attempts to fix bugs. Whoever is in charge of QA should be shown the door.
  17. Please fix the Pearlescent Rhomboid Helstone. Upon loading a save game, unless you either toggle the show/hide button for headware OR un/re-equip this item, it's doesn't rotate around the character's head. It's frozen mid-air. This is one of those minor yet annoying immersion things. Thanks.
  18. I tried to report this to you guys here but all you replied with is hurrrr dxdiag and output.txt. All you have to do to reproduce this ANNOYING glitch is to enter some scene where's there a beach or "ocean water" (not any sailing screen and not indoor water afaik), then PAUSE the game, then scroll a little. Notice how the water "warbles"? It's like it's moving even when the game is paused. This was introduced in your latest patch, once you added more graphics effects options, such as controlling FXAA. Incidentally, if you go into options, toggle FXAA, then scroll some more, the problem disappears. However, as soon as you transition to another scene with the same kind of water, it's back again. The only thing I can't confirm is whether this occurs on Pascal or not, since I'm running Maxwell. That's a 900-series GPU. I've tried GeForce 397.93 as well as 398.11. Makes no difference. Please just load up a save near some water on a system running a 960, 970, or 980 and pause the game. Scroll a little. WARBLY WATER.
  19. Decided to try out the beta patch and one of the first things I noticed is that if you're in a location such as the docks at Neketaka that shows ocean waves, when you scroll the screen you'll notice an odd "warbling" graphical effect which looks very unnatural. It only occurs when you're scrolling, not if the camera is still. Going into the graphics options and either changing the AA level to any other value OR toggling the FXAA option on/off alleviates the problem for that area, but as soon as you transition to any other area the problem will... resurface (no pun intended). Currently running GeForce driver 397.93. I may experiment with other driver versions. Very irritating, please look into this.
  20. The problem with the wildly fluctuating framerate is, of course, with Unity as already pointed out. As we've all seen, it's worst when you're near certain objects that emit a light source -- specifically ones that can generate multiple shadows. In PoE 1, the worst offenders were these same types of areas. One in particular that I used as a framerate benchmark was the central firepit in The Gref's Rest in Stalwart Village. It was a consistently accurate location to point out the worst of what that version of Unity's main performance problem was. Critically, the only thing I ever found that significantly improved the problem was to force the game to render in OpenGL with the -force-opengl argument in PoE 1's launch options in Steam. I also experimented with -force-vulkan which also helped. Unfortunately, these two options simply don't work in PoE 2. Unity 5.2/5.3 certainly supports them, but Obsidian seems to have removed Vulkan and OpenGL support in their modified version. I think if that option were (re)integrated, it could help a lot.
×
×
  • Create New...