Stargazer
-
Posts
547 -
Joined
-
Quote:Maybe some find it a decent way to let the devs know that they don't like it when bugs, glitches and errors make it through the betas?Originally Posted by Canine
Leaping around crying DOOM because Issue 17 isn't perfect and completely bug free isn't necessarily the most productive way of bringing bugs, glitches and errors to the attention of the developers.
Complaining won't help remove the current issues, but maybe, just maybe, the devs could keep it in mind the *next time* an issue is to be released.
Bad experiences stand out, and it seems to me that quite a few people have had bad experienced with i17 thus far. There are going to be more.
Even if bugs/glitches/errors aren't game-breaking (and it seems that they actually are for some people), they detract from the general impression of a new issue (people do talk to each other, and negative comments travel fast). It is my belief that in many cases, taking time to eliminate some key issues *before* an issue is released will result in a much better reaction to that issue when it is released.
It should however be noted that in this case they were pretty much locked into releasing i17 this week a long time ago, so it's not exactly like they could decide last week to push the release forward a week or two. -
Quote:Using a lot of memory is not a sufficient condition for qualifying as a memory leak. Adding new features can increase memory usage. That's not a memory leak. Sometimes you can see memory usage increase over time *without* there being a memory leak (e.g. caching). It only becomes a memory leak if the program fails to release the memory once it is done using it. This can result in ever growing memory usage when memory keeps being allocated and fails to be deallocated (again, keep in mind that not all increases in memory usage is due to memory leaks).Originally Posted by venombeyond82
As I said, before today, It has never happened, and I've been playing City Of Heroes since launch. It has ONLY Been happening since yesterday. And I've done what you've said last night. It was going up to about a GIG of memory, in any of the major zones. In Missions it would go down to about 800 Megs or so, In Pocket D, it would topple around 950 megs. And still have some issues. However Memory Leaks is a long known issue in City of Heroes, if you've ever looked around at other parts of the forums.
Its just now effect higher end PC's, including mine, my Roommates and several of my friends who have what you might consider Monster PC's. The fact that its having these issues ONLY after I17 was released, and not before, proves it is the Issue, or patch that has begun causing it. If this was an on going issue, it would have happened before now, many times.
Yes, the game has had a history of memory leaks, but even more common are the false claims of memory leaks. People often seem to believe that anything that results in increased memory usage is a memory leak. That is false.
It is very possible that there is a memory leak in play here, but I don't see anything in what you're saying that would show this. In fact, you mention that the memory usage drops when you enter a mission.
You mention that this only started happening with i17, but that too is not necessarily due to memory leaks. You say that you're using some Ultra Mode features, and some of them come with increased memory usage. When using these features, increased memory usage is *expected*.
In addition to that, many Ultra Mode features can have a significant performance impact, and that too seems like a possible explanation for some of the symptoms you describe.
Again, it's very possible that i17 comes with its very own memory leaks, and if it does, they should be found and plugged. However, just saying "It uses more memory - there's a memory leak" doesn't help (more often than not, it's wrong). Now, if you could determine that it actually fails to deallocate memory, and maybe even tell under what circumstances this happens, now *that* would be helpful.
It might also help if you say what CPU/GPU/RAM you have, and what graphics settings you're using.
Have you checked if lowering your graphics settings helps at all? -
From the Known Issues thread:
Quote:Originally Posted by Avatea
- The command "/chan_timeout <channel name> <duration>" is not working currently.
-
From the Known Issues:
Quote:Originally Posted by Avatea
- The command "/chan_timeout <channel name> <duration>" is not working currently.
-
Oh!
The Epics that unlock at 20 are not the Epic Power Pools, it's the Epic *ATs*, Kheldians and Soldiers of Arachnos. You should now be able to choose them when making a new character. -
Another experiment could be to start a dual build, and level that past 20.
-
Quote:Wasn't item maxìmization added in *Open* Beta?Originally Posted by Djeannie
No you can't. We requested this feature in closed beta. Many bugs made it to live it seems.
-
Congratulations!
And if you don't know what to do with the extra money, you could always give me half.
What?
-
If you were not properly logged out the last time, this can happen. The server still hasn't registered that you're no longer there, so in effect you're still logged in. It does time out eventually though.
So, if for instance the fresh restart was after a crash or disconnect, this is a normal behavior. -
Hopefully it (and the other bugs) will be sorted out soon.
It'd be a very useful command to have. -
Quote:Unknown.Originally Posted by Call Me Awesome
Doesn't it start counting the inactive time from when you set it? In which case setting it to 120 days means it won't kick anyone for 4 months from now?
As far as I know, that theory is pure speculation with nothing backing it up.
It's quite possible that it works that way, but I have seen nothing that would indicate it.
And, it does not do that on Test (at least not within the limits that it's been said to have. I obviously haven't been able to test it with 100+ days.). -
Quote:Interesting...Originally Posted by Mephisto_Kur
I have never hidden any of my toons in any way. Bit I know about that bug and tried the old fix. No luck. This one is different.
You said that it happens to "some" characters. Does this mean that it doesn't happen to all your characters?
Can you think of anything that differentiates the affected characters from the non-affected ones? Hero/Villain? Server? Favorite movies? -
Quote:You prevented any 3rd party programs/services from being started at computer startup.Originally Posted by British Battler
WOOT!!!! this worked for me...I just have no idea what I have done to my computer...if anyone could explain that would be nice
That's not really a good long-term solution since sometimes this includes programs that should be running*.
It works as a temporary measure though, and if you're so inclined you could always try to re-enable some of them one at the time, and try to determine which specific program/service causes the problem.
*Very often it also includes a lot of programs that probably shouldn't be running ("crapware" and similar things), so it can be a good idea to prune the list of autostart items. However, it's not always easy to know which items to remove, and which to keep. -
Hi,
I have a villain-side Gladiator's Armor: +3% Defense recipe that I would like to sell (I'd been planning on using it in a respec build, but now I've decided to hold off on respecing that character for a while).
I'd like to get at least 3 Billion, and I'm willing to accept Villain Inf, Hero Inf, or a combination of both.
I'll leave the item up for bid for a couple of days, but I'm willing to close it down early if I get a bid that's high enough.
The recipe is currently on Guardian, but with the new email system we should be able to work something out regardless of server.
Please send me a PM if you're interested. -
Quote:Isn't that the 75 month Vet Reward?Originally Posted by Sailboat
Maybe it looks good on a set of synchronized, tiled 36-inch monitors or something, and they assumed we'd all upgraded for Ultra Mode.
-
Quote:I completely agree that the situation sucks.Originally Posted by British Battler
Hi Stargazer, I can see where your coming from, but there is one nagging question at the back of my brain....
WHY!!!!
This game was working fine before i17 now it's broken. Many of us have offered to help. I have been at my comp most of the day, my post count has gone up something rediculous, just waiting in case I can help in any way. I know the tech guys can even take over my computer remotely if I give them permission to see exactly what happens in game if they want.
No email, no replies in any threads, no information about whats going on, that's what the problem is.
I am not about to go stomping around my computer disabeling this that and the other aimlessly till we find out whats happening.
However, *if* turning off other programs could help (and it's far from certain that it would), then
1) It could help the devs narrow down what is causing the issue
2) It would be a *temporary* way to be able to play the game until the issue has been fixed.
I do understand that testing something like this is not feasible for everyone, but for those who are comfortable with doing such things, it could at least be worth a try.
(it also wouldn't surprise me if people have already tried, and haven't found anything that helps) -
Quote:Well, that depends on what they asked you to run. For instance there's a CoH-specific diagnostic tool that gives information that is different from what dxdiag gives. If, on the other hand, they asked you to run another dxdiag, well, then that'd obviously be the same information.Originally Posted by Riverdancer
Well Battler, I got a response back - they wanted me to dl a file that runs a scan on my system and does a printout of what I have, etc. Funny thing is, in my original email, I included a copy of a dxdiag. Is this not the same information?
It seems clear that 3rd party programs/services (like the ATI hotkey poller) can cause this issue. Has anyone tried to see if closing other 3rd party programs/services can also help get rid of the problem?
It might be worth trying to turn off pretty much any other programs running at the time, including browsers, media players, IM clients, antivirus programs, automatic updaters, quick launchers ... (pretty much anything that puts itself in your system tray) and see if that makes any difference.
If nothing else, it could help ruling out some potential causes. -
Quote:There's an ancient bug with the hide settings that basically means that the Hide-from-tells setting is semi-persistent.Originally Posted by Mephisto_Kur
Private Tells on some toons (confirmed by several others) respond with "AUTO REPLY [chat hidden]" to anyone that sends a tell to that toon while that toon is not hiding in any way.
If you are logged in on a character A that is hidden to tells, and then switch over to a character B that is not, then character B will also be hidden to tells. If you type /hide it will still show character B as not being hidden to tells, but it will actually be hidden. To get out of this situation, hide character B from tells, and then unhide it again.
It's rather annoying. -
Quote:linky thingOriginally Posted by Djeannie
Doesn't fix the Enhancement Management window where all your slotted powers can be looked at.
-
Quote:That would seem to be the case, yes. At least on Test. I don't know if the issue also extends to the Live servers.Originally Posted by Quinch
So wait, let me see if I got this right...
There's a command that automatically drops people from a global channel if they haven't logged in in the past X days?
But it doesn't work? -
After having done some fairly significant testing on this command, this is what the command seems to do (at least on Test).
/chan_timeout
Set the channel's time out duration
Syntax: chan_timeout <CHANNEL NAME> <TIME IN DAYS>
Effect: Does nothing.
Actually, that's not entirely correct. If <channel name> does not exist, or if you are not an Op in <channel name>, it tells you that "You are not allowed to perform this action.".
However, if the channel does exist, and if you are an Op in it, it seems to do.... nothing. At least it doesn't seem to function as advertised.
I've tried using it "in advance" (seeing if setting the timeout to 7 at t=0 boots players that remain offline until t=7) and "retroactively" (seeing if setting the timeout to 7 at t=0 immediately boots players that have been offline since t=-7).
I've tried on Ops and non-Ops.
I've tried in Public and Private channels.
(and all combinations of the above)
Nothing.
"In advance" is harder to test for larger timeout durations, but "retroactively" nothing seems to happen up to at least 25 days.
This is all on Test. I don't know if there's an issue with the command that is specific to Test, or if this behavior also extends to the Live servers.
It would be very interesting to see if the command does anything on Live, but personally I'm reluctant to test it on an existing channel until I have more information, and it might not be very easy to find someone that would be willing to join an entirely new channel and then stay offline for 7 days on the Live servers.
If anyone else does test the command on Live, I'd be very interested in hearing the results.
Oh. As far as I know, the idea that it would only count from the time the command was implemented is pure speculation, and was first offered as a possible explanation for why my tests hadn't resulted in anyone being kicked from a channel (failing to take into account that the idea wouldn't explain why my tests hadn't resulted in anyone being kicked from a channel ).
It's very possible that it'll actually work that way, but to my knowledge we have no indication that it actually does.
While I don't know how (or if) the command actually works, this is how I *hope* that the command is *intended* to work:
I hope that when the timeout is set, any player that has not been online for the selected timeout duration is immediately booted from the channel. Once it is set, anyone that reaches a total offline time corresponding to the timeout duration will also be booted.
The alternate possibility, that only people who remain offline for a period corresponding to the timeout duration *after* the timeout is set will be booted, would be a disappointment, and would make the command a fraction as useful as it could have been. -
Quote:No, it will not.Originally Posted by Derangedpolygot
But will any of this work for the respec screen? I can't properly pull off one with the numbers unreadable.
There is however an even uglier workaround that can work for temporary things such as a respec.
The Windows Magnifier.
(usually found under Programs/Accessories/Ease of Access, or something like that)
This dedicates an area (by default at the top of your screen, but you can drag it around) to show a magnified copy of whatever your mouse is hovering over.
You could use it when running CoH in fullscreen (but it might involve dragging the magnifier window around), but it's probably easier to manage if you're running in windowed mode.
It's not pretty, but at least it can help you get through a respec. -
As a temporary measure (I'm assuming this will be adjusted eventually), you can try the following:
typing
/windowscale auction 1.3
will increase the size of the auction window, and with it the text size for the enhancement/recipe numbers shown there.
Typing /windowscale auction 1 will put it back to default again (unless you've changed your global windowscale in the options, in which case you can just change the value there again).
Unfortunately it doesn't seem like you can go past 1.3 (it actually starts somewhere before that, but 1.3 is easier to remember than 1.27).
You can do the same for your enhancement tray with
/windowscale enhancements 1.3
(the enhancement tray has to be undocked)
It's a fairly ugly workaround, but at least it should make the numbers easier to read. -
It's been a fantastic 6 years.
CoH was my first MMO, and it completely sucked me in (hey, I'm still here after 6 years). It's a very nice game, but what truly makes it great is the people playing it. Regardless of how good the game is, I very much doubt that I would have been here this long without the Guardian community, and the very good friends I've made within it.
So, thanks to the incredible people of Guardian for making this place an online home for the past 6 years!
See you for the 10th?
-
On Test at least, the timeout command doesn't actually appear to work (at least not as advertised), though I'm not sure if this is because of an issue specific to Test, or if it'll also extend to the Live servers.
I doubt that using it would be "harmful" (it just doesn't boot people, or at least didn't appear to on Test), but it might not be a bad idea to hold off on using it until it's been confirmed that it works. After all, if it doesn't work, there's not much point in having it active anyway (and we should find out soon enough if it does work).