Pets lagging behind will be addressed in the next hotfix patch.
Did you still have this option set throughout everything we did above? If so could ya give it a go without it now? Which Windows version are you on?
Edit: Got bored and have been searching around on your problem and it seems that laptops with 940M/Optimus type stuff can be problematic across various games, displaying symptoms extremely similar to what you are experiencing. I did come across something promising (cross your fingers).
If you could please go to the Intel site try to locate the correct intel graphic driver for the integrated graphics in the laptop. You may be able to just use their automatic update tool at the link to update any and all intel drivers on the system. Update it and reboot, then give GD another go.
If that doesn’t work you could use DDU to completely uninstall your Nvidia drivers and then reinstall. Download DDU, then go to Nvidia and download the correct drivers for your 940M. With that bit of prep out of the way go ahead and run DDU. Select the Safe Mode option. It will reboot into Safe Mode. Once in it should automatically popup with some options. Make sure that the Graphics Driver dropdown is set to Nvidia and then press the Clean and Restart button. It will (fairly quickly) purge the system completely of any traces of the Nvidia installation and then reboot back to a normal desktop. Go to the Nvidia drivers I had you pre-download and reinstall the drivers and reboot the system. You will probably want to recreate a new GD game profile and ensure it is set for the Nvidia GPU again.
Hopefully, something here helps.
Just curious, was the renderer (or anything in that general area) purposefully temporarily rolled back to the pre-1.0.2.0 version so that people having problems with it could get on with playing the expansion for now?
That’s fine if so, I just wouldn’t mind knowing if it was the case. Would be good to be able to put a reason to the fps loss issues some of us are having after 1.0.2.0 made things a fair bit smoother.
Well, for what it’s worth, I have a desktop system with a Radeon R9 290 running in 1920x1200 and an Intel i7-4790K, and now with the DirectX 9 renderer I can crank all video settings to max (even AA to 8x, although I suspect Ambient Occlusion not doing anything with D3D9) and get stable 60 FPS (with about 70%-80% GPU usage according to MSI Afterburner) unless I’m really surrounded by lots of enemies.
On the other hand, when using the DirectX 11 renderer just the starting spot in Devil’s Crossing drops to a jerky 40 FPS at the same settings with 100% GPU utilization (and the fan noise that goes along with it… :(). Reducing AA to 2x and settings everything to medium makes things playable, but since it makes the game look worse I’ll stick to the DirectX 9 render for now.
Unless the DirectX 11 renderer does a lot of things fundamentally different and/or better, I really would suggest making the renderer a menu option (main menu only, with a restart if neccessary) and defaulting to DirectX 9 since it makes that big a performance difference with little visual impact.
Hey, is it just me or did this patch add a whole heap of new armor textures? I didn’t see it in the patch notes XD I’m not crazy right?
No, you’re not crazy. They’ve been given an update too. 
Im confused, would have you prefered it just crashed when it hit a spot where the resource files were not available in your langauge, because from my understanding that was what was happening…
Sent from my SAMSUNG-SM-G935A using Tapatalk
GOG user here (without galaxy).
Some of the previous posts said that they get the GOG patch, but I’m still not seeing it available for download. I waited the whole weekend to get the update for the dx11 renderer.
Is it possible that:
- the patch is on GOG galaxy but not for separate download yet or
- some regional GOG servers got the distribution but not others (I’m in Asia)
The game at the 1.0.2.0 state is unplayable for me atm.
Was there an undocumented reduction to experience gain from normal grinding in this hotfix? The patch notes don’t say anything.
I have noticed nothing like this. In fact, I ended up at Log at the exact same level as I almost always do (48-49). I remember this because I always have to grind 1-2 more levels before I kill Log so I get the Legendary item.
As such I’m pretty confident that no chances have been made to leveling; at least not up until level 50.
GOG user from Europe, no Galaxy: I don’t see the patch, either. GOG took their time to make new patches available on their website in the past, too.
I just installed Galaxy now to have a look and 1.0.2.1 is available for 2 days already, it says in the launcher.
What I did now was that I installed Galaxy, imported the existing 1.0.2.0 game folder into the launcher which den patched it to 1.0.2.1 and after that I uninstalled Galaxy again. Game version in main menu is 1.0.2.1 now.
No idea though, if this a recommandable work around. But it seems the game files from their website and those downloaded when using galaxy are the same.
Ranged skeleton agro range fix is awesome. Thanks!
That is amazing. Wow, thanks for getting this fixed so fast.
Unless you want Log to drop a Legendary, the quest completion always gives 1. On my 7 toons ranging from 47 to 50.
Fun fact : killed Log with necro @ level 50, got legendary shoulders. 1st legendary to “legit” drop for necro was the same shoulders 
Thanks for pointing this out! My edits to the patch notes were scrubbed by the notorious notepad. Rhis’s post has been updated to reflect the updates to the torso armors!
And they are fantastic looking.
I got to hunt down a whole bunch of lower level gear now, thanks Allminoxy.
Any idea when 1.0.2.1 will reach GOG ?
It’s out, downloaded is this morning via Galaxy. Weird, doesn’t show up in my library as being updated from 1.0.2.0 though. Just checked the game itself and shows as version 1.0.2.1.
fort ikon indeed got a hit… with the patch I am forced to rotate camera and point it towards the riftgate just to get the 60’s 
game breaking problem, but i am pretty sure they will fix this one;)
Nice fixes, especially for translations functionality