It is currently Oct 19th, '19, 01:48

Launcher.sh

Post a reply

:
In an effort to prevent automatic submissions, we require that you enter both of the words displayed into the text field underneath.
 
BBCode is ON
[img] is ON
[flash] is OFF
[url] is ON
Smilies are ON
:arrow: :question: :exclamation: :idea: :mrgreen: :angel: :clapping: :confused: :crazy: :cool: :eh: :winking: :embarrassed: :sick: :geek: :ubergeek: :laughing: :lolno: :mad: :evil: :twisted: :neutral: :problem: :rolleyes: :sad: :crying: :shh: :silenced: :shifty: :smile: :razz: :veryhappy: :wtf: :shocked: :surprised: :thinking: :thumbup: :thumbdown: :waving:
 
   

Expand view Topic review: Launcher.sh

Re: Launcher.sh

Post by Konomi » Nov 2nd, '14, 02:52

Temp wrote:The problem now is that it doesn't seem to run Gw2.exe , because when the launcher runs, nothing happens.


Hey Temp,

Sorry for the late reply, I didn't really understand that posts need to be approved so I never seen yours for ages, annoying. Could you please send over your Log Files directory and do another debug run we talked about in previous posts and I'll try to get to the to bottom of what is causing this.

Re: Launcher.sh

Post by Anna » Oct 29th, '14, 00:25

Sorry, we have been quite busy with other things for some time now. Could you please check the latest version that we released several months ago and let us know if the problem still exists?

Again, apologies for taking so long to get back to you.

Re: Launcher.sh

Post by Temp » Jul 2nd, '14, 19:48

If I blank out wine_prefix="WineRoot" , the launcher spews out

Launcher.sh: Common main variables initilised
Launcher.sh: Help function set
Launcher.sh: Message function set
Launcher.sh: User variables defaulted
Launcher.sh: Conf file sourced
Launcher.sh: Helper binaries located
Launcher.sh: Wine path configured
Launcher.sh: Warning no Wine Prefix defined falling back to system
Launcher.sh: Wine debugging disabled
Launcher.sh: Wine registry winemenubuilder disabled
Launcher.sh: Wine registry CSMT enabled
Launcher.sh: Wine registry StrictDrawOrdering disabled
Launcher.sh: Wine registry UseXRandR enabled
Launcher.sh: Wine registry UseXVidMode enabled
Launcher.sh: Script pid saved to lock file: 9597
Launcher.sh: Program file present
Launcher.sh: No multiple instances found
Launcher.sh: Wine debugging already disabled
Launcher.sh: Nvidia threaded optimisations on
Launcher.sh: Logging enabled
Launcher.sh: Running Gw2.exe
Launcher.sh: Converting ScreenShots done

The problem now is that it doesn't seem to run Gw2.exe , because when the launcher runs, nothing happens.

Re: Launcher.sh

Post by Konomi » Jul 2nd, '14, 01:07

Okay I've exaimed Temp's debug log and realised I've goofed in a few areas. One my explanaton of what the "wine_prefix" does in Launcher.conf is incorrect. It currently is:

Launcher.conf
# This is where the WinePrefix is stored leave default if you
# do not know what you are doing or set to blank to generate
# one in your home directory
wine_prefix="WineRoot"


This is actually incorrect it should read like this:

Launcher.conf
# This is where the WinePrefix is stored leave default if you
# do not know what you are doing or set to blank to use the
# system's wine prefix instead
wine_prefix="WineRoot"


I want to make it clear you should not blank the WineRoot string for that variable otherwise you will use the system WINEPREFIX which is in your home directory, if you want to do that it is fine though!

I've done a point patch to account for a blank wine_prefix and use the system wine now, if you wanted the game self containted to the directory it comes in put the WineRoot part back.

WineGW2-Launcher-v1.9.1-2014.06.02.tar.gz

Once I know this one works for the people having trouble I'll do another small release for the tools.

Re: Launcher.sh

Post by Konomi » Jul 1st, '14, 04:50

Temp wrote:Yes, I still get the same error even with the latest release.


Damn I thought I fixed that, I'll look into it more sorry.

EDIT: Okay things are getting complicated, I just did a clean install of the projects latest version and encountered no error. I'm going to need debug logs.

If anyone has this error do the following:

1. Open up your terminal and navigate to the directory you have Launcher.sh in
2. Run the following:

Code: Select all
bash -x ./Launcher.sh &> Launcher.debug
ls -R . &> Structure.debug


3. Send me the resulting files Launcher.debug and Structure.debug, you can use the forum IM or pop into IRC and PM me some links. Your logs will be only seen by me or team members and will be discarded after the bug is fixed for anyone concerned about privacy.

Re: Launcher.sh

Post by Temp » Jun 30th, '14, 23:28

Yes, I still get the same error even with the latest release.

Re: Launcher.sh

Post by Konomi » Jun 28th, '14, 12:29

Temp wrote:Hi,

Did you find a solution to this problem? I get the same error "Launcher.sh couldn't create a wine prefix" and it can't seem to be solved by running winecfg.


Have you tried the most recent release?

Re: Launcher.sh

Post by Temp » Jun 26th, '14, 16:56

Hi,

Did you find a solution to this problem? I get the same error "Launcher.sh couldn't create a wine prefix" and it can't seem to be solved by running winecfg.

Re: Launcher.sh

Post by Konomi » May 4th, '14, 09:56

Logan wrote:Hi, the launcher script complains that it can't create a wineprefix.

Going to the launcher folder > wine > bin then running winecfg from there will create the wineprefix. After that the launcher runs fine.
.
Can the launcher do this automatically?


Hi, what verison of the launcher are you using? This sounds like a bug I might've already fixed if you're using an older version. The current version of the tools is v1.3-2014.03.31 and the launcher version (look inside the comments) should be 1.7. If you're on this version and still getting it please run the launcher like this:

Code: Select all
bash -x ./Launcher.sh >> "$HOME/Launcher.sh.log"


Then send me the log file in your home directory. Please PM it as a message to me though as it will contain your user name and other possibly machine specific information.

Re: Launcher.sh

Post by Anna » May 3rd, '14, 21:43

Logan wrote:Hi, the launcher script complains that it can't create a wineprefix.

Going to the launcher folder > wine > bin then running winecfg from there will create the wineprefix. After that the launcher runs fine.
.
Can the launcher do this automatically?

Konomi will get back to you on this sometime tomorrow.

Top

cron