Originally Posted by shellthor
I have been attempting to get danksole 1.2 and Godmode and 1 Hit Kill v5 to work for the past few days. I have followed the tutorials in the tutorial section using both the modded Sinject that automatically closes after injection and the Perx injector. I launch the injector as an admin, select location for Vindictus.exe, select the .dll's, and then attempt to inject. I get the message from danksole asking if I want to run in console or not so I assume that the dll is being injected properly, but no matter what I select, nothing else happens. The hackshield window does not start, and I have to go through task manager to close Vindictus.exe, which is only using 1920 KB memory compared to it's normally much higher footprint.
At first I just figured I was impatient and needed to wait longer, so I left to grab some food after one attempt and came back over an hour later and nothing had changed. Any suggestions as to what I am doing wrong would be appreciated.
At first I just figured I was impatient and needed to wait longer, so I left to grab some food after one attempt and came back over an hour later and nothing had changed. Any suggestions as to what I am doing wrong would be appreciated.
I personally haven't had this exact problem, but I'll give you some generic advice that may help.
Step 1:Try launching Vindictus normally, with no hacks installed.
Step 2:Assuming that's successful, try loading up PerX with a single .dll file.
Step 3:Then try load PerX with the other file, while keeping out the first one.
Step 4:From that point, assuming everything is still working, try loading both .dll files.
It's odd that Vindictus is giving you the low memory footprint, and not displaying hackshield splash/load screen at all. That's why I'm curious if it works even with no hacks loaded.
If Step 1 fails, it's likely your client is messed up or something on your system is now blocking Vindictus.exe from running.
If either Step 2 or 3 fail, but NOT both, it's the individual .dll file that you tried loading on the failure. Re-download it.
If BOTH Step 2 and 3 fail, then the problem likely lays with the injector.
If Step 2 and 3 work, but step 4 fails.... I have no clue. Possibly a mix-up by trying to inject 2 files at once?