Amigo345

Guys from crate entertainment basically invented the system PoE uses. They introduced it in their first game - Titan Quest and then in their second game - Grim Dawn. They never called it multiclassing. They actually call it what it is - dual classing. http://www.grimdawn.com/guide/character/masteries.php

nope still dual class

You can call it whatever you like it is still dual classing.

Multiclass? This game allows dual class only.

Unfortunately POE2 is one of those games with this freezing issue. There are several other games out there and some users are suffering from this same problem. Developers tend to ignore it due to the fact that only a small number of users is experiencing this. There is also a blaming game going on between developers and Nvidia. Nvidia can tell you this is game related issue and develoepr must solve it. Developer can tell you this is something with your hardware or Nvidia drivers. My advice - make waves, report it to Nvidia here. https://surveys.nvidia.com/index.jsp?pi=6e7ea6bb4a02641fa8f07694a40f8ac6 Or you can send a message to Nvidia customer care.

Have you tried updating your GPU drivees like the patient above? It's usually the first thing support tells you when **** like this happen. It can work sometimes. You can use DDU to uninstall your old drivers.

So does it crash during character creation? Start a new game and check it out. Also after a crash check windows event viewer for any error messages. There could be an error message like this - display driver has stopped responding and has recovered. One known solution to game frezes is to downclock your GPU. If your GPU is overclocked, you can set it back to factory frequencies in Nvidia control panel. If it's not OCed, then this **** shouldn't be happening. You can still try to underclock it manually with MSI afterburner. Like 100 Mhz or something should do the trick.

Does the game crash on character creation screen for you? It's not a solution but you can try the following if you haven't already. Create Pillars profile in Nvidia control panel. Set these options there - vsync off, triple buffering - off, thread optimization - on. Launch the game and set these graphic options - vsync off, ambient occlusion - off.

They need to learn some lessons from this. I mean how could they not see ship combat will be bashed by everyone because of it being so bland and uningaging. Short, boring story, buggy game overall. I mean you release a game for PC with bugged mouse clicking? Cmon man. This game is not good and no wonder its sales are low.

I've just head the exact same issue. I selected wild orlan, no head option. I went back, switched to amua. Head option appeared but clicking on it didnt do anything. So I clicked on x to close character creation screen and got a crash.

Got a crash with an actual error message. It happened during a loading between a text based quest and combat. It was a R6025 pure virtual function call. Here's a description. https://support.microsoft.com/en-us/help/125749/description-of-the-r6025-run-time-error-in-visual-c Cause This error occurs when your application indirectly calls a pure virtual member function in a context where a call to the function is not valid. In most cases, the compiler detects this and reports the error when building the application. But depending on how your code is written, sometimes the problem is detected only at run-time. The error occurs when you indirectly call a pure virtual function within the context of a call to the constructor or destructor of an abstract base class. This is illustrated in the sample code below, along with some more description. Resolution Calling a pure virtual function is a programming error, so you need to find the call to the pure virtual function and rewrite the code so it is not called. One way to find a call to a pure virtual function is to replace the pure virtual function with an implementation that calls the Windows API function DebugBreak. When using the debugger, DebugBreak will cause a hard-coded breakpoint. When the code stops running at this breakpoint, you can view the callstack to see where the function was called. Another way to find a call to a pure virtual function is to set a breakpoint on the _purecall function that is found in PureVirt.c. Breaking on this function has the advantage of keeping the stack intact so that you can trace what is occurring.

If you have Win10 update 1803 try doing this - set poe2.exe to run as administrator and check disable full screen optimization.

I agree. It's unnecessary. I see it as a marketing trick first and foremost to attract more players and make that wow effect keeping up with DOS2. VO in DOS2 was like a BBC radio speaker reading fairy tale for kids.

As long as its along these lines Im all for it -Can I pet him? Im gonna pet him! - Its your hand!

Its possible. Some ppl may not be really excited about their ship to ship combat feature and the second game overall. Moreover they went with crowdfounding again after the first part.