These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Test Server Feedback

 
  • Topic is locked indefinitely.
 

Is it ok to point the TQ and Sisi clients at the same ResourceCache?

First post
Author
Previous Topic Next Topic
Prozn Zanjoahir
Escalated.
OnlyFleets.
#1 - 2015-04-07 07:49:57 UTC
Both my launchers currently point to the same directory, which is great as it frees up valuable SSD space. However I'm concerned about corrupting my TQ install with Sisi data. Will this be a problem?

Thanks
CCP Habakuk
C C P
C C P Alliance
#2 - 2015-04-07 13:26:13 UTC
This is working as intended and it should not cause any problems. All clients should use the same resource cache (and it is quite tricky to configure it differently).

CCP Habakuk | EVE Quality Assurance | Team Five 0 | (Team Gridlock)

Bug reporting | Mass Testing
wollschoof
Free-Space-Ranger
#3 - 2015-04-07 13:55:27 UTC
hi

I fixed this problem for me this way
http://imgur.com/0XELVL8


sisi\launcher\launcher.exe /forcelauncher /server:87.237.38.50

my TQ Launcher uses an Different shared cache folder then my SiSi Launcher
Hakaari Inkuran
State War Academy
Caldari State
#4 - 2015-04-07 14:38:19 UTC
CCP Habakuk wrote:
This is working as intended and it should not cause any problems. All clients should use the same resource cache (and it is quite tricky to configure it differently).

I assumed this was the case when intalling sisi two weeksago but you guys might want to pin this info somewhere? Maybe in the wiki
CCP Habakuk
C C P
C C P Alliance
#5 - 2015-04-07 15:17:37 UTC
Hakaari Inkuran wrote:
CCP Habakuk wrote:
This is working as intended and it should not cause any problems. All clients should use the same resource cache (and it is quite tricky to configure it differently).

I assumed this was the case when intalling sisi two weeksago but you guys might want to pin this info somewhere? Maybe in the wiki

Yeah, good idea. I'll add a comment to the wiki.

CCP Habakuk | EVE Quality Assurance | Team Five 0 | (Team Gridlock)

Bug reporting | Mass Testing