Master-Blade

[ QUOTE ]
I have too much time...

[/ QUOTE ] I think we both have a history of being able to say that. lol

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
Are you sure you're not just talking about the hide/show UI button?

[/ QUOTE ] That's exactly what disable2d is. lol

[/ QUOTE ]

Right, but it's not called disable2d in the options/keymapping menu, which may be where some of the confusion is coming in. It's called disable UI.

[/ QUOTE ] It doesn't matter. Selecting that option in the keybind menu binds ++disable2d to the key of your choice.

In short YES, that's exactly what we are talking about... whether or not that option was set by default at some point or not.

[/ QUOTE ]

Which, IIRC, was besides the point. Except I forgot why the hell are we talking about disable2d anyways? What the hell was this thread even about?

[/ QUOTE ] Yes, it is beside the point.. but on that note:

I was just using a character I created in September 2008. (I know when it was because I created him based on the PPD Hardsuit PAX code.) As it turns out, he still has the bind! "numpad ." is indeed still in the keymapping options for "Disable UI".

I certainly never put it there myself, so it must have been the default bind around that time... but the VEATs I created just a couple months before that, do NOT have that keybind set. Seems strange to me... but like you said, regardless if it was default before, it's not now.. and that's all that matters.

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
Are you sure you're not just talking about the hide/show UI button?

[/ QUOTE ] That's exactly what disable2d is. lol

[/ QUOTE ]

Right, but it's not called disable2d in the options/keymapping menu, which may be where some of the confusion is coming in. It's called disable UI.

[/ QUOTE ] It doesn't matter. Selecting that option in the keybind menu binds ++disable2d to the key of your choice.

In short YES, that's exactly what we are talking about... whether or not that option was set by default at some point or not.

[ QUOTE ]
Well, even though simply chaining 'e slap' and 'e smack' doesn't work, throwing in 'e none' gets you pretty close!

I was figuring there must still be some way, so I bound numpad7 to "e none$$e slap" and numpad8 to "e none$$e smack" and after a few seconds of practicing, I was able to somewhat chain the slap and smack emotes. A bit after Hasten fires I actually get a half-way decent chain going... probably with some practice I could get it to work at least as good as it used to.

[/ QUOTE ] ok, you get a legitimate bow for that one.. lol

[ QUOTE ]
BOW DOWN BEFORE ME!

[/ QUOTE ] Hey, I was still right, I just didn't convey it completely. lol

*Bows anyway.

[ QUOTE ]
[ QUOTE ]
The only exception is between powexec commands.. it activates the last power in the chain, and queues the second to last, making it look like it's being read right to left. Other commands are processed left to right anyway.

[/ QUOTE ]This is wrong. Powexecname still opperates left-to-right, the misconception comes in because powexecname doesn't immediately execute the power...

[/ QUOTE ] That's actually what I meant. My only fault was I didn't explain WHY it activates the last power in the chain. I was too busy trying to rationalize why the second to last power also get's queued, but that's because I was thinking ahead to the idea of using the "Powexec_Auto" command to queue the next to last power.

Also, using Toggles will activate more than one power at the end of the chain as well.

Thanks for clearing it up.

[ QUOTE ]
Are you sure you're not just talking about the hide/show UI button?

[/ QUOTE ] That's exactly what ++disable2d does, toggle the UI. lol

Just for fun, I added some AFK text above my head:
/macro POW "e smack$$e slap$$afk !! SMACK !!"

And yes, it's no longer letting us do it fast.. again.

You may have seen it "the other day", but that was probably before the recent issue/patch that "broke" it again.

Unfortunately.. I'll most likely be unavailable that night.

I wish you all luck.

And I wanted to try out my character changes too.. Well, maybe I'll get lucky and my family visitors will turn in early for the night by then. Tentative, ftw! lol

[ QUOTE ]
Meh.
I was disappointed to lose badges that I'd selected as titles

[/ QUOTE ] If you selected a badge as a title before i15 went live, you should still have the title (as long as you don't change it to something else).

I have several toons still sporting the "Architect LXXV" title, and a friend of mine still has "The Chosen One" selected.. even though those badges are no longer available.

I suspect the badges didn't really get deleted, but are instead just hidden in the background.

[ QUOTE ]
Welcome back!!!

Well first here is http://wiki.cohtitan.com/wiki/Main_Page it as ton of info for you.

The first thing I would do is roll a new toon and start over, because a lot of things have changed. Other then that just have fun

[/ QUOTE ] Fixed the link.

[ QUOTE ]
I was under the impression that binds executed from right to left. Has that changed?

[/ QUOTE ] As far as I can tell, it's always been left to right.

The only exception is between powexec commands.. it activates the last power in the chain, and queues the second to last, making it look like it's being read right to left. Other commands are processed left to right anyway.

Somebody had a good explanation as to why it does it that way, but I forgot what it was. lol

Now you see me...






...now you don't!

To add to what Texas said.. have your friend enable File Sharing on his CoH directory and then you can easily pull the files over your network a lot faster (you said he was connected to the same router).

[ QUOTE ]
My mouse is doing things by itself. It doesn't act up until I load the game up.

When I left click powers the mouse acts as if I'm trying to grab the powers. As if I still have the button clicked when I don't. It's not a mechanical problem as it's done the same thing with three different mice.

When trying to move the cursor it's like moving through molasses then sometimes the cursor will just move from wherever I have it to some random part on the screen. I thought perhaps some kind of virus, but I really have no clue.

I've also updated all the drivers for the mice, so yea....any ideas?

[/ QUOTE ] Well, about grabbing powers, you can prevent accidental dragging by binding the following:
/bind KEY optiontoggle disabledrag

That will allow you to enable/disable the icon dragging with a quick press of a button.

As for what is causing it to stick to begin with.. I'd guess wireless interference of some sort. Make sure you have new batteries, and move the receiver closer.

If it's not wireless, or that doesn't work... then I have no idea.

[ QUOTE ]
[ QUOTE ]
Couldn't make the full change, eh Bob?

[/ QUOTE ]


Yeah, and I have to try and keep you guessing on what it will be week after week until new boards.

[/ QUOTE ] It's Bob.

[ QUOTE ]
Back to my orginal question: How do i tell between driver crash and a graphics card crash?

[/ QUOTE ] You can tell the difference (usually) depending on the type of error message you get.

If you are not getting an error message, I don't know what to tell you... other than check for possible sources of errors...

If the whole system is stalling out like you say.. I'd guess it's possibly hardware.. but it's not necessarily the graphics card. It could be the motherboard, powersupply, or anything else ceasing up or causing a problem... but that doesn't mean a bad driver or program isn't causing a problem either.

I'd do what he suggested.. check the temperature and see if it's heat related.. It's a good start anyway.

"+down" doesn't necessarily make the bound key "look" for pressing and releasing as two separate actions...

What happens is the execution of "+down" is a movement which continues as the key is being pressed. As soon as you release, it stops executing, and continues to the next command in the bind. You could also use "+up", "+forward", "+back", "+left", or "+right", but like you said.. "+down" is the least bothersome as most people are already near the ground when they want use binds like this. Running off would be annoying. lol

Also, you forgot powexecname soul extraction.

My guess is...
/bind a "+down$$target_custom_next defeated mypet$$follow$$powecexname Soul Extraction"
...should set the target upon key-press, then follow and queue the power on key-release... then the power will execute when you are close enough.

Let us know how it goes.

[ QUOTE ]
Hey Luna just a quick question,

Are we going to be doing all the TF's now that the Monday night thing has alot of interest? By all of them I mean the Moonfire TF etc.

Not sure if you did them last time around because I kinda joined the madness late

[/ QUOTE ] Yes, we did all the TFs and Trials on our journey to 50... and our Monday night Event has been popular since the beginning. Besides Positron (our first run), we've had 2, and sometimes 3 teams every week steady.

Yes, we'll be running them all again, starting with Positron like last time.

[ QUOTE ]
If this is still on, I'm definitely in.

Brab, 50 Thugs/Pain MM

I've got experience running MoSTF on a Grav/Emp, so I can handle the no deaths .

[/ QUOTE ] We started about an hour before you posted.

The final mission ended with all the Heroes being pulled at once, and we had 2 deaths this time... but we still kicked their behinds! I decided to upgrade my range to about 240ft (from 190), and I have a slight strategy-change I want to try.. so I'm hoping things go a little different next time. Also, I recommend everybody stocking up on some good inspirations for the next run as well.

We decided to do Barracuda now... we'll see how it goes.

[ QUOTE ]
Hey Fox you don't what you are getting yourself into brother. Prepare for a 25 min ITF with TT

You know your name sounds familiar. Were you ever on Justice with the Phoenix Phoenix Prime SG?

[/ QUOTE ] Hey now, Teal Tabby hasn't been on an ITF in quite some time, plus it's the rest of the team being able to keep up that allows for the sub30 runs. I certainly can't do it by myself. lol

I can make no guarantees.

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
Disable2D is not bound to any key by default (check the default binds!), which is why I've manually bound it to DECIMAL on several of my characters (I use it whenever I'm recording something in the game, like the new costume change emotes or the drone bug).

[/ QUOTE ] I'm pretty sure it used to be at some point. I remember manually removing it a long time ago because I'd accidentally hit it all the time.

I could be wrong, but it appears Zombie also remembers it that way.

[/ QUOTE ]That must have been at least pre-issue 6.

[/ QUOTE ] I started the game slightly after i7 went live.

Either way, you are right. It's definitely not the default now, which can easily be confirmed by anybody by removing keybinds.txt from the CoH folder and creating a new character.

[/ QUOTE ]Odd, it's not on my character from i6...

[/ QUOTE ] I don't know how to explain that. I distinctly remember looking for it and finding it in the last section of the keybind options menu and not knowing how to directly remove it.. so I replaced it with W, then rebound W to forward, which removed the bind.

I don't think I have any characters I can check, as I have since made my own default keybind files that I'm sure I loaded on each character at least once by now.

Also.. we could be misremembering.. it wouldn't be the first time. lol

[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
Disable2D is not bound to any key by default (check the default binds!), which is why I've manually bound it to DECIMAL on several of my characters (I use it whenever I'm recording something in the game, like the new costume change emotes or the drone bug).

[/ QUOTE ] I'm pretty sure it used to be at some point. I remember manually removing it a long time ago because I'd accidentally hit it all the time.

I could be wrong, but it appears Zombie also remembers it that way.

[/ QUOTE ]That must have been at least pre-issue 6.

[/ QUOTE ] I started the game slightly after i7 went live.

Either way, you are right. It's definitely not the default now, which can easily be confirmed by anybody by removing keybinds.txt from the CoH folder and creating a new character.

[ QUOTE ]
Disable2D is not bound to any key by default (check the default binds!), which is why I've manually bound it to DECIMAL on several of my characters (I use it whenever I'm recording something in the game, like the new costume change emotes or the drone bug).

[/ QUOTE ] I'm pretty sure it used to be at some point. I remember manually removing it a long time ago because I'd accidentally hit it all the time.

I could be wrong, but it appears Zombie also remembers it that way.

[ QUOTE ]
Except for the "++" in front makes it so that it's as if the "button" is being pressed continuously, so enter would bring up the chat screen, and then it would go away immediately since it's constantly disabling the UI.

[/ QUOTE ] There is no "button" being pressed continuously.. imaginary or not, and pressing Enter wouldn't make the chat visible anyway, not even for an instant.

++ simply toggles the value of disable2d (from 0 to 1), making the 2d interface always invisible. Pressing Enter wont "bring up" the chat screen, because 2d drawing is still disabled.. It's still there, but it isn't drawn on the screen.

Pressing Enter still puts the invisible cursor in the invisible chat box, and allow you to type commands. (If you have sound enabled, you can even hear the characters being typed.) Obviously since you cannot see yourself typing, you'd have to really know what you are doing to enable 2d drawing again.

Issuing a command that sets disable2d to 0 will make the interface viewable again, and it will stay that way until another command is issued to the contrary. (Yes Zombie, even using the period bind brings the display back up. The previous state of the variable does not override a new command to toggle the variable from 1 back to 0.)

By the way, besides having a little programming background, I've done it before on purpose to test it for a previous thread, so I know it'll work exactly as I say I does. As a backup, I had bound a key to set disable2d to 0, just in case, but it wasn't even needed. I even tried it again just now, and it still works just fine (except as I said.. current chat bugs mean you may have to make several attempts before getting the correct text to send in the chat).