Originally posted by neryreginato
View Post
Announcement
Collapse
Forum Rules
- No flaming or derogatory remarks, directly or through insinuation.
- No discussion, sharing or referencing illegal software such as hacks, keygen, cracks and pirated software.
- No offensive contents, including but not limited to, racism, gore or pornography.
- No excessive spam/meme, i.e. copious one liners in a short period of time, typing with all caps or posting meme responses (text/image).
- No trolling, including but not limited to, flame incitation, user provocation or false information distribution.
- No link spamming or signature advertisements for content not specific to Dota 2.
- No Dota 2 key requests, sell, trade etc.
- You may not create multiple accounts for any purpose, including ban evasion, unless expressly permitted by a moderator.
- Please search before posting. One thread per issue. Do not create another thread if there is an existing one already.
- Before posting anything, make sure you check out all sticky threads (e.g., this). Do not create new threads about closed ones.
- It is extremely important that you post in correct forum section.
- Balance discussion only in Misc.
- All art related (such as hero model) feedbacks go to Art Feedback Forum.
- All matchmaking feedback should go here: Matchmaking Feedback
- All report/low priority issues should go here: Commend/Report/Ban Feedback
- No specific workshop item feedback. These should go to workshop page of that item.
- When posting in non-bugs section (such as this), use [Bugs], [Discussion] or [Suggestion] prefix in your thread name.
- Before posting any bug, test it in latest DotA map or Latest DotA Test Map and make sure it is actually a bug.
You can also find references in PlayDota Guides and PlayDota Mechanics. - Follow Bug Reporting Guide when reporting bugs.
In case you object some action by a moderator, please contact him directly through PM and explain your concerns politely. If you are still unable to resolve the issue, contact an administrator. Do not drag these issues in public.
All rules are meant to augment common sense, please use them when not conflicted with aforementioned policies.
See more
See less
Patch Anticipation Station
Collapse
X
-
Originally posted by katsaroulhsAlso, I am laughing so hard because you people actually expected smth better from Valve. Some of you have been here for years. Some of us have been here from the beta, watching this mess of a game getting developed. And you STILL are surprised when you are fed shit. [...]
-
Originally posted by <>< View PostBtw Phoenix, DoctorGester is also creating a custom game where he uses Phoenix as "The Sun"
https://gfycat.com/TastyFeminineHorseshoebat
Comment
-
Originally posted by Phoenix. View PostNicee, thats rly cool. My Phoenix will have some new an cool abilities too, despite the Armaggedon Ability of 1 use.
Also Lycan https://gfycat.com/FarflungSplendidDuiker
The gamemode is actually UI-wise one of the most polished / advanced out there. It has it's own special pick screen even, i believe these screenshots are taken of it.
It's still WIP, quite obviously.
Comment
-
Roshpit Champion is also quite polished UI wise (except for the hero selection).
Mh.. I remember the early custom games in WC3 before TFT. Was fun and it only got better. But there were a lot of engine limitation which Dota 2 now does not have. However there are still a lot of issues which have to be sorted out first.James "2GD" Harding's career as a Dota 2 host on Valve events
* 25.02.16 - † 26.02.16
Spoiler:
Comment
-
Since everyone keeps complaining about performance issues in dota 2 , i'm going to boot up my super shitty old laptop i haven't used since Reborn got out, and see how well it fares in dota 2. I already fear how long it'll take up to install all windows 10 upadtes..
Edit: It's an Asus X73T series, AMD A6 and Radeon dual graphics - HD 6520g + 7670M 1GB laptop. 8 gigs of ram at least. This thing used to overheat after 15 minutes in source 1 dota 2.Last edited by <><; 12-30-2015, 09:37 AM.
Comment
-
I'm tired of these ability spam/max attack speed/holdout/tower defense game modes...ψ RAISE YOUR PITCHFORKS ψ
Valve's TO DO LIST (I see you guys keep forgetting so I made one for you):
- Viper remodel - Slardar remodel - Pit Lord - Manila Compendium - New UI - 6.88 (a real patch this time)
Comment
-
Originally posted by <>< View PostSince everyone keeps complaining about performance issues in dota 2 , i'm going to boot up my super shitty old laptop i haven't used since Reborn got out, and see how well it fares in dota 2. I already fear how long it'll take up to install all windows 10 upadtes..
Edit: It's an Asus X73T series, AMD A6 and Radeon dual graphics - HD 6520g + 7670M 1GB laptop. 8 gigs of ram at least. This thing used to overheat after 15 minutes in source 1 dota 2.
People will complain anyway.Originally posted by katsaroulhsAlso, I am laughing so hard because you people actually expected smth better from Valve. Some of you have been here for years. Some of us have been here from the beta, watching this mess of a game getting developed. And you STILL are surprised when you are fed shit. [...]
Comment
-
I actually forgot to say that the Lycan gfy i linked earlier was simply spamming the first skill with -wtf on, it actually only sends one pair of wolves. In case you were referring to that with "ability spam".
Comment
-
Ok i tested, all graphical settings off / to the lowest, game render quality to 70% and i had a solid 60 fps. We're talking about a machine using the AMD drivers from 2013. It shouldn't probably even run Source 2 dota2. No performance issues whatsoever, the only problem was that loading to a game took forever. And i've heard stories about people having i5-4770K and GTX 960, lowest settings @ 20 fps. Wtf.
Comment
-
Also, some people might be interested in reading through this. http://store.steampowered.com/news/19852/
We'd like to follow up with more information regarding Steam's troubled Christmas.
What happened
On December 25th, a configuration error resulted in some users seeing Steam Store pages generated for other users. Between 11:50 PST and 13:20 PST store page requests for about 34k users, which contained sensitive personal information, may have been returned and seen by other users.
The content of these requests varied by page, but some pages included a Steam user’s billing address, the last four digits of their Steam Guard phone number, their purchase history, the last two digits of their credit card number, and/or their email address. These cached requests did not include full credit card numbers, user passwords, or enough data to allow logging in as or completing a transaction as another user.
If you did not browse a Steam Store page with your personal information (such as your account page or a checkout page) in this time frame, that information could not have been shown to another user.
Valve is currently working with our web caching partner to identify users whose information was served to other users, and will be contacting those affected once they have been identified. As no unauthorized actions were allowed on accounts beyond the viewing of cached page information, no additional action is required by users.
How it happened
Early Christmas morning (Pacific Standard Time), the Steam Store was the target of a DoS attack which prevented the serving of store pages to users. Attacks against the Steam Store, and Steam in general, are a regular occurrence that Valve handles both directly and with the help of partner companies, and typically do not impact Steam users. During the Christmas attack, traffic to the Steam store increased 2000% over the average traffic during the Steam Sale.
In response to this specific attack, caching rules managed by a Steam web caching partner were deployed in order to both minimize the impact on Steam Store servers and continue to route legitimate user traffic. During the second wave of this attack, a second caching configuration was deployed that incorrectly cached web traffic for authenticated users. This configuration error resulted in some users seeing Steam Store responses which were generated for other users. Incorrect Store responses varied from users seeing the front page of the Store displayed in the wrong language, to seeing the account page of another user.
Once this error was identified, the Steam Store was shut down and a new caching configuration was deployed. The Steam Store remained down until we had reviewed all caching configurations, and we received confirmation that the latest configurations had been deployed to all partner servers and that all cached data on edge servers had been purged.
We will continue to work with our web caching partner to identify affected users and to improve the process used to set caching rules going forward. We apologize to everyone whose personal information was exposed by this error, and for interruption of Steam Store service.
Comment
Comment