I get the VAN 1067 error now ever since the latest Valorant update only when mudfish is open even if I am connected or not connected. If I close out of mudfish entirely this does not happen though so it has to be an issue with mudfish. I can dump logs and network information. Considering reinstalling mudfish drivers as well here. Just wondering if anyone has gotten this issue recently because mudfish was working for me previously.
Ummm… Might be that something (at game side) checks the process list and blocks the mudfish process?
Very weird that this issue is even happening without connecting the mudfish core meaning that only Mudfish UI process is running. Just curious, did you try to change the executable name of Mudfish Launcher to another and run it? For example,
- Open the explorer and move the installation directory of Mudfish.
- Find
mudrun.exeand change the name to ramdom one such asmudrun_tmp.exe. - Then run it as the administrator right.
I tested this on my side even though I don’t play Valorant much but I don’t get this issue.
I mainly play League of legends but I use custom game items with the actual game server ip only and it works and game server traffic is tunnelled through mudfish correctly.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.