PDA

View Full Version : arks Launcher ate it's self!



Kazablanco
Apr 23, 2016, 06:24 PM
So i went from jumping from version 3.0.7.1. to 3081 and always updating the tweaker when i finally got 6 tier graphics to work with option on it and i run through maxing everyone video option then log in play for couple hrs and then when i need to log out which was in full screen i just exit game and when i did, the tweaker had corrupted its files on my desktop and where ever else it was before with missing icon. Just recently a team mate of mine was having trouble said the launcher tried to delete its self why? and how do i fix that? without uninstalling everything and reinstalling to cover up the real issue? the only thing left is the pso2 game itself. plz help

Just an update on my silly situation that maybe global...I decided to redownload the tweaker launcher when i did i run quick test for messing files when it found messing files i well post here and u till me what today next? Program started...


Loading sidebar page...
Program opened successfully! Version 3.0.8.1 [OK!]
Checking for updates, please wait a moment...
You have the latest version of the program: 3.0.8.1
Downloading GN Field...
Checking for PSO2 Updates... Done!
Checking for updates to patches...
Current EN Patch version is: patch_2016_04_19
Current Large Files version is: 4/20/2016
Current Story Patch version is: Not Installed
Beginning plugin update...
Downloading/Installing updates...
PSO2Proxy usage detected! Auto-enabling PSO2Proxy plugin...
Plugins updated successfully. [OK!]
All done - System ready!
Checking for necessary files... Done!
Checking for folders... Done!
Done testing! If you got any errors here, please carry out the recommended steps.
Downloading Patch file #1... Done!
Downloading Patch file #2... Done!
Downloading Patch file #3... Done!
Downloading Patch file #4... Done!
Restoring PC Opening... [OK!]
Restoring NVidia Logo... [OK!]
Restoring SEGA Logo... [OK!]
Restoring Vita Opening... [OK!]
Checking files...
ffbff2ac5b7a7948961212cefd4d402c is missing.
Downloaded and installed ffbff2ac5b7a7948961212cefd4d402c. [OK!]
All done! [OK!]

aleckeene2
Apr 24, 2016, 03:50 PM
If you mean that when you start the game PSO2 Tweaker gets deleted everytime, that's happening to me too. Anyone know why this is happening? Is SEGA on to us? How to bypass it?

Anduril
Apr 24, 2016, 04:13 PM
The Tweaker isn't deleting itself, it is just renaming itself to avoid NP1013. It is supposed to change itself back after you close the game but it seems that it doesn't happen for everyone, thus breaking any shortcuts; go to wherever you have the Tweaker downloaded, and just manually change the name back to "PSO2Tweaker.exe".

aleckeene2
Apr 24, 2016, 05:01 PM
What did it rename itself to? And if that's the case, why can't I connect anymore since the last update?

EDIT: All good. It was saying something about the proxy when I tried to log in. All the ships were gray and said "unknown" or something. I renamed PSO2 Tweaker back to ".exe" and reconfigured the proxy, logged in an it was all good. Not sure exactly what went wrong but Kazablanco, you should try this. Thanks for the tip Anduril.

Kazablanco
Apr 24, 2016, 06:45 PM
Kool, not a bad idea, mine after renaming the tweaker still does it. I think I found the behavior of the situation and literally a behavior linked to the GN Field, it maybe renaming the tweaker every time u launch it but it does 1 of 2 things. Idk if the GN Field is built in by Sega or arks layer but it takes the known launcher and hides it doesn't delete just hides it in the GN Field db after u execute it once :D and maybe renaming helps. If i want to find my tweaker again after i close out i just launch GN Field 1st like a firewall then launch Pso2 2nd and play as before with no 1013 errors.
It adds an extra step to the launching which is a times annoying. I thought the update for 3.0.8.1 was to stop the launcher from crashing or sending to background which i had np with up until now. Not relocate the process services to prevent from crashing. so i believe this is an update issue with coders lol

There maybe a temp fix but the issue still remains...