Yinepuhotep
-
Posts
13 -
Joined
-
Not much to add to what everyone else has already posted, so I'll just say thanks. Thanks for everything. Here's hoping whoever you land with realizes how incredibly lucky they are to have you.
-
Quote:Ah-ha! I knew there was something of the Dark Side involved! Just for that, no chocolate for you!Originally Posted by DarkGob
It was my idea. I'm sorry.
-
Quote:Oh, I'm not pointing fingers. As I said in my post, I was cranky because the update deleted my options, and if I weren't religious about saving a copy of options.txt every time I make any change, no matter how small, I would have had to completely redo my settings.Originally Posted by Aneko
Relax. I also use 1600x900 and it worked fine for me. There's no reason to start pointing fingers.
-
...to set up today's (10/11/11) patch so that it frakked the preference file? According to the patch notes, all it did was fix a potential game crash issue, but when I logged in after applying the patch, I got a message that said that 1600x900 is not supported in full screen mode (note, my desktop is 1920x1080), so the game is reverting to 800x600. This makes absolutely no sense, since I had my preferences set to run the game at 1600x900 (a mode which is, according to the graphics options, supported by the game). So now I get to load up the options, reset the game to run at 1600x900, and then rearrange all the UI elements that got repositioned by the game's arbitrary decision to reset its display size, before I can get down to actually playing the game. Had I known that the patch was going to reset my preferences (which reminds me - any chance of including graphics settings in the options.txt file in some future update?), I probably wouldn't be quite so cranky, but as it is, I'm rather cranky because I not only had to fix my graphics, I had to load my options.txt file to restore the rest of my options. Thank goodness I'm religious about updating it every time I make any changes to my settings!
-
What confuses my wife and I is that she doesn't have NEARLY the trouble I am, even though we're both sharing the same computer (stats listed up-thread), I actually have my graphic settings reduced farther than she does, and she uses Zoom in order to be able to see the screen clearly enough to play.
-
Quote:It did. It reduced my lag to the point where I can actually cross a room without crashing. Not so much help during combat or zone events. I'm almost at the point of relegating this machine to RP only, and waiting to do anything that would bring me XP until I can get back on my desktop PC.Originally Posted by Blackleviathan
What I found helpful so far from the forums is tuning off a geometry buffer in advanced graphics quality settings you enable them and then you can tweak different aspects of graphics like world or character settings individually. It helps a lot with lag and stuff
-
2:00 PM EST - no change in error. CoH has finished downloading and installing the GAME update, but the CIDER update is crashing every time. And the LAUNCHER update is still the same ***** mess it's been since the day the launcher was released to the Mac public.
-
Quote:Nice idea, but unfortunately, we always run the NC Launcher directly. Wish it would work.Originally Posted by Gargadon
Im not sure if this will fix it for anyone else. But usually I launch the game by running the City application from spotlight and then that runs the NC Launcher. I ran the NC Launcher directly this time and then it worked. Hope this helps.
-
Quote:(Since I use the same computer as Sliewyn) Unfortunately, this seems to be related to the "Unable to connect to launcher.ncsoft.com" error that we've been receiving since manually downloading and installing the Mac launcher when it was finally released live. I say that because if you try to update by simply clicking the "Yes" button when it asks if you want to update, it briefly flashes the "Unable to connect to launcher.ncsoft.com" message before closing itself. This has been an ongoing error since the day NCSoft released the Mac version of the launcher.Originally Posted by CuppaManga
I can't say for sure since I haven't seen it, but usually an NSURLErrorDomain error would imply the target server (patch server) was reassigned and the DNS information hasn't trickled down yet. Give it a few hours and see if it works.
-
Quote:If we start seeing Cole demonstrate an interest in art, I'll start sweating.Originally Posted by Nericus
As I read this I began thinking that Cole and Grand Admiral Thrawn have a bit in common.
-
Assertion Failure (Have had six in less than twelve hours, usually while on a mission map or in a base - including 2 since my last full power-down and rest reboot)
Have also had:
3 crashes during loading screens (no idea what causes those, as I got no message, just a CTD)
1 PIGG corruption message (Make that 2 pigg corruptions. The newest one was Worldmisc.pigg)
1 game frozen so badly I had to reboot the computer to exit the game
2 Mapserver disconnects
And this is all within the last twelve hours.
Macbook Pro 3.1 17"
2.4GHz Intel Core 2 Duo
2GB 667MHz DDR2 SDRAM
GeForce 8600M GT
256 MB Video RAM
Snow Leopard 10.6.8
Update: Am currently running a full file check, so far the validator claims 0 bad files, but will try again after doing the file check and see if it's fixed the crashes.
New Update: Ran full file check, validator claimed 0 bad files, problem not resolved. But, since tomorrow is the VIP launch, hopefully the updated version will be in better shape. Assuming, of course, that the launcher ever connects to the correct address to self-update, and/or Cuppa's manual update instructions work. -
Five years, and still no answers. So much for "good communication", eh?
-
Does anyone have any idea what changes have been made in the bind feature? I've come back after a fairly long hiatus, and discovered that none of my old binds work any more. Either the game complains when I load my bind file, or when I attempt to use the bind, the game complains that it doesn't recognize the command. As an example, two of my most heavily-used binds are:
f "powexec_name Sprint$$powexec_name Fly$$powexec_name Hover"
lshift+f "powexec_name Fly$$powexec_name Hover$$powexec_name Sprint"
The game complains that it doesn't recognize the command, and gives the entire line within the quotes as a single command, as if the old $$ convention for separating commands in a queue doesn't exist any more.