Nicodemus

all i can think of is make sure compiz is off and maybe try older drivers. i've hear that the ATI drivers lately have problems with CoH. i hear 11.3 are good, but be mindful of your X server version as well if you downgrade.

i'm afraid that's all i can offer. sorry. =/

-project CoH isn;t needed with cohlaunch.pl. the script already includes it by default.

i'm afraid i'm not experiencing any rubberbanding. =/ maybe someone else can better assist you?

what drivers are you using?

good idea Kosmos.

i also have two launchers, one to update and run the script, and one that just launches the game.

Happy Double XP weekend! =)

my hope is the issue will be fixed when he updates the script to shut down after launch. if you have any particular concerns you'd like to bring to his attention, feel free to post on wineHQ. the more the merrier, so he knows it's not just bart and i pestering him. =)

*edit* also, i loved working on this with all of you. =) if you're ever looking to team, feel free to look me up. =) @nico144 on Virtue.

is everyone enjoying the game? i know i am. =) played a good deal yesterday. i also archived my bottle now, so in case something goes wrong i can pick up right from this update. =D much easier.

i noticed that i can't play the game for long after using the perl launcher. it slows my whole computer down tremendously after about 40 minutes, and i need to kill it for things to get better. i think it's because of all the output from CoH into the terminal, but Mark disagrees. all i know is, if i run the game without cohlaunch.pl running persistently in the background, everything is fine for hours.

in either case, Mark will be making an update to the launcher so that it closes after launching the game.

i've updated the first post to make it more relevant and consolidate the new information.

good stuff, W4E! i've officially updated the CrossOver Games page for CoH also, letting everyone know about this workaround.

glad to be back in Paragon! =D

great info, thanks guys!

ack, W4E, don't edit that stuff out, that was good info. =)

*edit* i confirm that i can now see the servers. =) i can successfully install, patch up and play the game using the cohlaunch.pl perl script with the following command:

./cohlaunch.pl -live -renderthread 0 -auth 64.25.36.4

=D looks like we're back in business! thanks to everyone for all their help and sticktoitiveness! =)

special thanks to Tex for helping us out and putting up with us. =D

yay!

thanks for the heads up, Tex! =D

can anyone with windows hook me up? =)

it did, but then it immediately updated to 2060.201108050059.1 for me.

still no joy. UNNAMED server remains.

W4E, awesome news that your new live install patched up and worked! =D sounds like you're good to go! here's hoping my results will be as positive. =)

it may or may not be relevant, but note that the script patcher dropped a .0 off of the end of the version.ini version number. i had to readd it in order to match the server version #.

in either case, i still only saw the unnamed server.

just fyi.

*edit* going to try a redownload with the new, fully working version of the patcher. couldn't hurt at this point. *shrug*

Mark, the author, has put up a new version which seems to fix the patching issue.

let me know if it works for you guys.

mine seems to patch ok, but when i try to run cityofheroes.exe -project coh -renderthread 0, all i see is one Unnamed server. =/ this may be because i use CrossOver and not straight wine, so the launcher won't actually launch for me (though it will patch.)

well, it does unrar the patch archive, because it places the new directory with the archive contents into the .patches folder. but it isn't applying the patches. this is odd, since it claims to fail the decompression. i guess it cannot complete the process for some reason, which would then trigger the next step which should be to call xdelta.

mark, the author, can't look at it right now, but if anyone else has the skills and wants to give it a go, by all means. =)

this is where we stand so far. =)

will do. thanks Kos! don't worry about rushing anything, the game isn't going anywhere. =)

ok, thank you for replying Tex.

good to know, thanks guys! ok, so that's probably not it then...

regarding the extraction error, i need to check the version of Unrar in the repos when i get home. maybe that has something to do with it?

that's exactly where we're at, Cx. =) now we're all on the same page of being unable to update. =P =D hopefully Mark (the coder) or someone can shed some light on this issue soon.

ah, right! why didn't i think of that? i ran it with ./ out of habit, didn't even think about it. listen to Kosmos, Cx. =)

Cx, is it in your CoH directory? it has to be run from there.

that's about all i can think of, if you've met the dependencies.

i actually couldn't use it to launch my game, perhaps because i use CrossOver and not straight WINE.

i did get it to reinstall the game by placing it in an empty directory, but it failed to successfully update it after that. i'll keep messing with it when i get home.

the thread with the creator is here at winehq for CoH: http://appdb.winehq.org/objectManage...rsion&iId=2980

i also get the "Unable to decompress patch CityOfHeroes.etc.etc.ncpatch" error.

i'll probably keep trying until my sub runs out, but it's getting a bit frustrating when i could just play other games instead of paying to be hassled. lots of my motivation is pure principle at this point, more than a desire to play. (ok that last part is only sort of true. Freedom does look AWESOME. )

hehe, thanks wildcat! i sure was ready to give up, but my account hadn't expired yet, so since i could still post, i still tried. :P

i'm trying the perl script patcher right now to reinstall. i'll report back.

*edit* ok, i was able to reinstall with the perl script, though it put it in a weird folder. and it seems like i can run it through CrossOver with -project coh -renderthread 0.

so far so good, this perl script has been the most promising for me yet. i'll have to try actually logging in tonight, as the servers are currently down.

have a good day, all!

cool, thanks je.

and just to keep our options open, it looks like there's also a perl script that someone put together to patch and launch the game. it's here: http://www.carnildo.com/cohlaunch/index.html

*EDIT 8/24/11*

a solution to the NC Soft Launcher problem for City of Heroes has been provided by Mark on the WineHQ page for City of Heroes. it seems we've abandoned the effort to get a universal NCSoft launcher at this time.

this is a PERL script he wrote. the original page is located here and it will list the dependencies needed.

this script will update an existing install. it will also download a new version of the client if placed into an empty folder. i could not get it to work correctly with a fresh install from DVD (Architect Edition) due to a lack of a version.ini file. i recommend downloading a new client with the PERL patcher instead of trying a fresh install from CD/DVD.

complete directions for it are on the webpage provided above. make sure to place the script inside your City of Heroes install folder (ie. where you want the game to be) and run it from there. for example, mine is located here: /home/<USERNAME>/.cxgames/CityofHeroes/drive_c/Program_Files/City_of_Heroes

*CrossOver Games Specific Section*
i have made a minor adjustment to the script so that it will launch using CXG. in order for this work you must first:

1) open your Manage Bottles window in CXG.
2) highlight the City of Heroes bottle that you've made.
3) click on the Advanced tab.
4) Check the box that says "Use This Bottle as the Default for the Command Line"

that should sort it out. you can grab my CXG specific version of the patcher here. all i did was change the wine call at the end of the script to the cxgames specific method of a command line call.

NOTE: the script assumes you installed CXG with the generic .bin installer. if you used a .deb or .rpm installer, you will need to first locate the directory where the CXG program was installed, and then edit the call at the bottom of the perl script to call the correct directory.

for example, user Vauluur tells us this: