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.
 

Help to install Teste Server without using the TQ shared folder
Author
Previous Topic Next Topic
Castelo Selva
OS GUERRAS
Brave United
#1 - 2015-04-18 13:30:27 UTC  |  Edited by: Castelo Selva
Yes, I would like to install a fresh copy of Singularity, but without using my current Tranquillity shared cache location.

I do not want to gamble with the working TQ shared folder, I want to copy it to another HD and install Sisi in that other HD. Is that possible?

If yes, could someone give me a step by step guide? I am not a computer person, but I would like to try the new skins before the official launch.

Thank you.

Best post ever!
Mister Ripley
Ministry of War
Amarr Empire
#2 - 2015-04-19 02:00:49 UTC  |  Edited by: Mister Ripley
Since the shared cache location is stored in a RegKey, I don't think there is a simple way to work around it. You could change the cache location every time you launch either TQ or SISI, but that's not really convenient..

Just use the same cache. It works without problems and you will also have most things already downloaded when next release for TQ is available.
Torgeir Hekard
I MYSELF AND ME
#3 - 2015-04-19 06:56:11 UTC  |  Edited by: Torgeir Hekard
Shared cache location is taken from a registry key in HKCU.

So your options are:

1. Launch each client through any kind of script file that would change the registry key and then run the launcher. This way, it is not entirely clear how SiSi and TQ clients running in parallel would interact.
2. Install SiSi client as a separate user thus giving it it's own HKCU hive.
3. Sandbox SiSi client thus virtualizing registry for it.
4. Install linux, run eve via wine and have separate wineprefixes for SiSi and TQ clients Bear

PS: another possibly working idea. Use an environment variable in the cache location path. Then, as with (1), launch each client via it's own script, but instead of overwriting registry, it would setup the right environment for the corresponding client.
Rivr Luzade
Coreli Corporation
Pandemic Legion
#4 - 2015-04-19 12:21:09 UTC  |  Edited by: Rivr Luzade
Fun story:

I just created a Sisi shortcut of the eve.exe (added /server:87.237.38.50 to the shortcut) in my previously TQ only folder as I am forced to do that after the shared cache stuff, it launched the Sisi launcher and downloaded Sisi files into my TQ installation. Now I launch the normal TQ launcher and it tells me that I run a pre-release version of the game and that this might cause problems. If I click "Cancel" nothing happens (as per notification). If I click "Ok", however, the TQ launcher patches every time after I had previously opened the Sisi launcher in the TQ installation folder and it downloads files. The reverse is also the case: after every use of the TQ launcher, the Sisi launcher needs to patch something again. And then the TQ launcher needs to patch again...

Having said this, DOD is a disaster in my opinion. I can't really convince myself to care about the advantages for the devs as I do not benefit from their advantages. It also looks to me as if this is yet another unfinished piece of software thrown out for the sake of it. It would at the very least have needed the option or (easy to use, as I do not want to mess with my registry) ways to use several installations and not just one folder. After the above, calling DOD and shared cache folders with TQ and Sisi in one folder is neither working flawlessly nor does it work conveniently nor is it remotely as easy to use as the old system with 2 separate installations that do not influence each other.

Another thing is that I cannot even launch the Sisi launcher as long as I have the TQ launcher open so I can't even connect to Sisi while TQ is running. Added to that is that I cannot patch Sisi while TQ is running so I can't play on TQ and prepare patch Sisi at the same time. I have to close all TQ things to launch anything Sisi. This was better with the old system as well. So, I hope the devs have some really heavyweight benefits apart form the dubious stuff mentioned in the blogs, because for me, the new system is an unacceptable mess compared to the straightforward system from before.

UI Improvement Collective

My ridicule, heavy criticism and general pale outlook about your or CCP's ideas is nothing but an encouragement to prove me wrong. Give it a try.
Torgeir Hekard
I MYSELF AND ME
#5 - 2015-04-19 12:30:12 UTC
Rivr Luzade wrote:

I just created a Sisi shortcut of the eve.exe (added /server:87.237.38.50 to the shortcut) in my previously TQ only folder as I am forced to do that after the shared cache stuff, it launched the Sisi launcher and downloaded Sisi files into my TQ installation.

This is so unimagineably, horrendously and hillariously wrong I have a hard time believing the statement.

No, you are not. You are forced to have a shared resource cache folder. Which is called Shared Cache for some totally mysterious and incomprehensible reason. You are not forced to pile all the clients into one folder. You should have a folder with a TQ client and a separate folder with a SiSi client, and without some additional non-trivial steps they will be 2 separate and totally working clients that share a single non-conflicting resource cache.
Rivr Luzade
Coreli Corporation
Pandemic Legion
#6 - 2015-04-19 13:06:34 UTC  |  Edited by: Rivr Luzade
And would you care to explain how I keep my TQ launcher from pointing to the folder I specified in the Sisi launcher? Even If I set-up a separate folder, the launchers always only point to one cache location. I fail to see how this changes anything I wrote above. What I want back is 2 completely independent locations. What I want back is the fact that when I open the TQ launcher, it only cares about the TQ folder and when I open the Sisi launcher shortcut in the Sisi folder, it only cares about the Sisi folder. That is, to my understanding, not the case. I have had a separate TQ and a separate Sisi folder. But the launchers from both folders can only point to 1 location.

UI Improvement Collective

My ridicule, heavy criticism and general pale outlook about your or CCP's ideas is nothing but an encouragement to prove me wrong. Give it a try.
Torgeir Hekard
I MYSELF AND ME
#7 - 2015-04-19 14:05:05 UTC
Uggghhh...

The client now has 2 parts.

1. The client itself. That is, the launcher and the game binaries and whatever.
2. The client resource files.

The (1) is independent. It can be anywhere. You can copy the launcher to any folder you wish, run it with /server:singularity, and it will update the launcher in that folder and the client in that folder to the singularity version. You just have to make sure you run the correct launcher.

The (2) is shared between all the clients run by the current user (in theory it can be made separate for each client through the steps mentioned above. Or made shared between all users by choosing the same path for every user). It's a database. Most likely each resource of a certain version has some kind of an UID, so if a resource is first downloaded by the singularity client and later makes it into the release version unchanged, it retains it's UID and does not have to be downloaded again for the TQ version.

The resource database is not a set of files used by a particular version of a client and only by that version. It's a database that contains the files needed by that particular version and possibly some other files required by some other version, so sharing this database with some other client does not remove any files used by your current working client. It just adds the missing files for the new client. Not to mention it has nothing to do with the client or launcher binaries itself.
Rivr Luzade
Coreli Corporation
Pandemic Legion
#8 - 2015-04-20 09:07:45 UTC  |  Edited by: Rivr Luzade
Well, even with 2 separate folders for the client stuff, I still get the notification every time I start my TQ launcher that I play with a pre-release version of the game and that this could cause problems. Quite irritating to be fair. Not to mention that I had to setup all my clients yet again because I moved the client files into a separate TQ folder...

UI Improvement Collective

My ridicule, heavy criticism and general pale outlook about your or CCP's ideas is nothing but an encouragement to prove me wrong. Give it a try.
Sgt Ocker
What Corp is it
#9 - 2015-04-26 23:23:51 UTC
Failed to download update for EVE Online Launcher
This is what i get from a sisi launcher that had until the introduction of shared caches, worked flawlessly. I can't import saved patches to it, well it does actually import but Creating EVE_Online_865927-877899_win.patch 6.0% is as far as it gets.

My shared cache is in my old DOD folder as I was playing with it prior to it going live and just left it there. TQ although as laggy as hell at least works, SISI has stopped patching.
I was planning on moving my TQ client to an SSD and have the cache on another drive but seeing it has issues reading from 2 folders on the same drive I am not game to try it.

The worst thing is, there is an update due for release in a little over 24 hours and the mess from the last one has not been sorted.

I too get the message regarding a pre-release launcher when loading TQ. (I don't think they know how to fix it)

My opinions are mine.

  If you don't like them or disagree with me that's OK.- - - - - - Just don't bother Hating - I don't care

It really is getting harder and harder to justify $23 a month for each sub.
Caleb Seremshur
Bloodhorn
Patchwork Freelancers
#10 - 2015-06-09 14:22:25 UTC
Torgeir Hekard wrote:
Rivr Luzade wrote:

I just created a Sisi shortcut of the eve.exe (added /server:87.237.38.50 to the shortcut) in my previously TQ only folder as I am forced to do that after the shared cache stuff, it launched the Sisi launcher and downloaded Sisi files into my TQ installation.

This is so unimagineably, horrendously and hillariously wrong I have a hard time believing the statement.

No, you are not. You are forced to have a shared resource cache folder. Which is called Shared Cache for some totally mysterious and incomprehensible reason. You are not forced to pile all the clients into one folder. You should have a folder with a TQ client and a separate folder with a SiSi client, and without some additional non-trivial steps they will be 2 separate and totally working clients that share a single non-conflicting resource cache.


NNNNNECRO POWERS

Does this mean I can delete some parts of my SISI installation? Since it's now functionally redundant? I'm trying to shave off surplus files on my HDD to speed it up when defragging with file prioritization in effect.
Primary This Rifter
Mutual Fund of the Something
#11 - 2015-06-10 09:48:23 UTC
Caleb Seremshur wrote:
Torgeir Hekard wrote:
Rivr Luzade wrote:

I just created a Sisi shortcut of the eve.exe (added /server:87.237.38.50 to the shortcut) in my previously TQ only folder as I am forced to do that after the shared cache stuff, it launched the Sisi launcher and downloaded Sisi files into my TQ installation.

This is so unimagineably, horrendously and hillariously wrong I have a hard time believing the statement.

No, you are not. You are forced to have a shared resource cache folder. Which is called Shared Cache for some totally mysterious and incomprehensible reason. You are not forced to pile all the clients into one folder. You should have a folder with a TQ client and a separate folder with a SiSi client, and without some additional non-trivial steps they will be 2 separate and totally working clients that share a single non-conflicting resource cache.


NNNNNECRO POWERS

Does this mean I can delete some parts of my SISI installation? Since it's now functionally redundant? I'm trying to shave off surplus files on my HDD to speed it up when defragging with file prioritization in effect.

You can run a rescache purge from both the TQ and the Sisi folders.

The easiest way to do this is to go to the main installation folders for TQ and Sisi and create a shortcut to rescache.exe, then right click on it and open Properties, go to the Shortcut tab, and add the word "purge" at the end of the target path. It should look like this: http://i.imgur.com/1OoqrHo.jpg

If you do this for both TQ and Sisi, you'll wipe any files that either server doesn't use. Then the next time you play on either server, the client will download any missing resource files only when you need them. Unless you tell the launcher to download all the resource files, and then restart it.
Sir Constantin
#12 - 2015-06-10 15:15:51 UTC
Awesome tip!
My SharedCache folder was around 25GB, not it's back to 12.5GB
Primary This Rifter
Mutual Fund of the Something
#13 - 2015-06-11 03:04:36 UTC
Of course keep in mind it will grow again as you play, and especially after major updates.