New Launcher

On June 30th eve is making it so you have to use their new launcher. I have yet to figure out how to make the new launcher update IsBoxer. All it says is unable to connect to server, until I use the old launcher to get the updates.

[lax]

Known issues with the new EVE Launcher were resolved with Inner Space build 6130, which has been live for some time now. If you have not updated Inner Space in a while, close and restart it to let it patch up.

If you are still having trouble, it might help to see "Diagnostics for game crashes" from ISBoxer's Help menu. http://isboxer.com/wiki/Diagnostics

Otherwise, as is detailed in several other recent posts in this EVE section, launching via exefile.exe still works. As far as anyone knows, they are disabling the old launcher, but not disabling the ability to bypass the launcher.

I had the same problem today here is the diagnostic report


http://pastebin.com/4T4pSNKB


Please help lol

[MiRai]

Your ISBoxer is several months out of date. You should update it via the Help > About menu and try again.

[bob]

Did Inner Space actually update? Check to see if the current build is 6030. You can hover the mouse over the Inner Space icon in the system tray, and if the tooltop says 1.15 (build 6030), then you are current.

If not, you may have disabled it.
You can get current, by right clicking on the Inner Space icon, selecting Patcher, and make sure the "Always patch at startup" option is selected. Then right click the icon again, select Exit, and then reload Inner Space. It should patch if you current build was less than 6130.

Also, this application compatibility setting probably wont help if you are using this loader executable to load the launcher. Note, it is completely unnecessary to use this executable, it may be a leftover from something else, if you are not using it, there is no need to start.

Code:

Application Compatibility flags under HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers:
0 C:\Program Files (x86)\CCP\EVE\eve.exe: $~ IgnoreFreeLibrary<Wpc.dll> WIN7RTM

You will need to edit the registry and remove this to get rid of it.

I just updated it again and now it says I'm using 1.15 6131 so tomorrow I will try to launch again and let you know if it works... Fingers crossed!!

Also I'm really not sure how to get to the registry to delete that code... sorry.

I have tried running the new launcher, it looks like its updating, but when I try to run ISBoxer it still says
"Unable to connect to tranquility servers.eveonline.com on port 26000" then when I ran it using Default instead of no patch mode, it brought up the old launch window to update. I have the latest version or at least that's what everything is telling me, I'm lost.

[lax]

I have tried running the new launcher, it looks like its updating, but when I try to run ISBoxer

But ... you can run the new launcher with ISBoxer

it still says
"Unable to connect to tranquility servers.eveonline.com on port 26000"

The EVE client you have ISBoxer launching, that does this, is out of date.

The signs in this thread point to you have ISBoxer launching exefile.exe at the old location, e.g. "EVE\bin\exefile.exe". You need to have ISBoxer launch it at the new location instead, which is now "EVE\SharedCache\tq\bin\exefile.exe". The old location is known to give the message you are describing (as the client in that folder is no longer kept up to date).

To adjust it , you can either edit your existing Game Profile that you have ISBoxer launching -- http://isboxer.com/wiki/Game_Profile -- or use Add Game from the Inner Space menu to add it anew, and then change each of your Characters in ISBoxer Toolkit to use the new Game and Game Profile. If you edit your existing Game Profile(s), you can very likely just change the "Main executable path" so instead of ending in "EVE\bin" it ends in "EVE\SharedCache\tq\bin"

Sticky this ^^ worked great!

The advice to launch a normal Eve window
Open Task Manager
Right click on Exefile.exe
Open File Location
Was INVALUABLE! Because I had a C:\eve\sharedcache\ with nothing in it.
Mine was in Program Data (that's where ccp put mine apparently)