Latest version is v2.86.2. It appears to be working. AOPP appears to be compatible still as well. However, I have no been able to get ReShade to work – It will prompt what packages to install, but at no point do I get the option to configure it.
I’m grateful to just have it playable, of course.
Some more helpful information – I always played in windowed mode, and it seems this way you’re able to run many instances without ever worrying about this alt-tab crash problem. I don’t know if it’s due to version improvements with dgvoodoo or windowed mode, but there you have it.
I do have crash issues when trying to log out while running Mali’s toolkit. I just try not to use Mali’s unless I am rolling and running RK missions.
ah the reshade problem could be quite simple, I think i know the issue. so you need install reshade in main folder the C:funcom by default then rerun the setup on Users/AppDate/Roaming/AOPP anarchy online exe also doing AOPP second. you have to duplicate it for both installs, to get it run properly if that make sense, it seem issue AOPP has with dgvoodoo2 seem to be quirk of AOPP.
if doesn’t work you can try run reshade on main install second instead AOPP second, but having it both locations fixed the issue for me when first installing.
So it not that it crashes on ALT tab it that if stay tabbed out for more say 30 minutes when tab back in crashes, it appears to be weird interaction with window focus. as I can see game momentarily come back to life then crash in split second. If play windowed mode you will bypass most of that anyways. Though with latest DGVoodoo2 2.86.2 this appears to be a rare occurrence, it was inconsistent originally now it happens less. As mentioned in guide if really want dualbox (All I got) I will run voodoo2/reshade/aopp clinet and 1 Vanilla (the clinets not in focus) solves all issues.
Now I have seen the Mali toolkits issue on borderless fullscreen too not sure what cause but doing manuall mali rather then standalone seemed fix it.
For DPS meter i use AO damage which doesn’t seem have crash issues (my preffered style of meter) You need learn key/click shortcuts to get all details and post logs but it good once you know.
I am happy to dicuss ingame or via discord. you can usuals find me on besaid(insert word) or buster (insert word) Busterkeeper or Besaidshot as examples.
Do let me know if reshade advice above works please?
updated the guide to include some windows 10/11 optimzations that can help zone crashes and don’t require adding anything or modding your AO install. I have added near bottom of the guide.
Just update to share some more testing I do using DX11 vs dx12. I bad at grammar so used AI to rewrite it see below:
Why dgVoodoo2 DX12 Is More Unstable for Multiboxing (Explained Through CPU Core Usage)
There’s been a lot of discussion about DX12 being unstable for multiboxing, and I’ve seen many people mention crashes, freezes, or clients randomly closing. I wanted to understand the actual reason behind this behavior — so I spent some time testing and profiling CPU usage across multiple setups.
After testing across multiple systems (8-core and 16-core CPUs), I’m confident I can explain what’s happening.
DX11 vs DX12 CPU Usage Behavior (with dgVoodoo2)
dgVoodoo2 DX11
Typically uses 1–2 cores/threads
Occasionally spills to a 3rd core
Even when running 6 clients, the CPU overlap stays fairly manageable
Result: More stable, but lower maximum performance / FPS
dgVoodoo2 DX12
Actively spreads load across 3–4 cores/threads
Sometimes spills into 5–6 cores, depending on system load
When running multiple clients, cores become heavily overlapped
Result: Higher performance, but much less stable during multiboxing
Why This Causes Instability
When you run six DX12 clients on an 8-core or even 16-core CPU, the CPU scheduler has to keep reassigning threads across overlapping cores. This leads to:
Resource contention
Cache thrashing
Task scheduling conflicts
This is where we start seeing:
Client instability
Sluggish input response
Random freezes or crashes
To be clear:
This assumes all other variables are already controlled (Windows redistributables installed, Nvidia control panel tuning, Game Mode enabled, etc.).
Focus Behavior Note
dgVoodoo2 DX12 also tends to behave worse when a window is not in focus. Borderless mode reduces this somewhat, but does not prevent the CPU conflict issue described above.
Verification Testing
I used Process Lasso to artificially limit how many CPU cores each client could access.
Client Mode
Cores Per Client
Stability
Performance
DX12 (unrestricted)
3–6 cores
Unstable
High FPS
DX12 (manually limited to 2 cores)
2 cores
Stable
Much lower FPS
DX11 (default behavior)
1–2 cores
Stable
Lower FPS
This confirmed that the instability comes directly from DX12 scaling across too many cores.
Recommended Setup for Multiboxing
If you want to use DX12 for the performance boost:
Run ONE dgVoodoo2 DX12 client (your main, actively controlled window)
Run the remaining clients as vanilla DX9/DX11 (unmodded)
Set all of them to borderless windowed mode
This lets you:
Get the higher FPS and smoother input on your main client
Avoid the CPU overlap instability on the background clients