So by your logic the internet should be removed. We already had unlimited file size limit through the use of a edited file or custom MPQ's and/or local files/folders. They've done nothing so far besides make WC3 worst last year, hopefully that isn't the case this year.
Since the file size limit seems to be a big deal then what are they doing for the maps over 128MB? They're still playable on B.net/multiplayer however that isn't thanks to Blizzard. We have only lost feature's, maybe hashtables were a nice addition however we already had whatever those offered and they're even slower then what we already had. They didn't give us anything that could be even considered equal or close replacement to what they stole/patched away. So many varieties of possibility were there yet many didn't know how too achieve them back then, now there is quite a lot unlocked for the public.
Thursday already and still no news... 1stQ 2017? Running out of time, m8.
What about the people who, unlike you, don't WANT to play B.net with those extra files/edits because they've always been afraid Blizzard will ban them for it? Why the hell haven't you considered what this means for THOSE people?
Seriously, it looks like you're just looking for any reason to complain at this point.
Patience is a virtue!
What about the people who, unlike you, don't WANT to play B.net with those extra files/edits because they've always been afraid Blizzard will ban them for it? Why the hell haven't you considered what this means for THOSE people?
Seriously, it looks like you're just looking for any reason to complain at this point.
Patience is a virtue!
I have considered them in my maps, instead of seeing invisible models they'll see regular WC3 ones. If they want to play under the limit then they'll still be able to play however will be lacking a few feature's such as better graphics as well music/sounds. Not a single problem for people who don't want to have a better gameplay experience, they can still play properly if the mapmaker knows what they're doing. Those people might eventually have to quit WC3 anyways due to nobody to play with if Blizzard takes out bots however so far those people haven't got anything new technically and have lost some feature's to eventually play with already.
No, I am looking for any opening I get to help Blizzard make less mistakes.
I'd prefer not to quote myself so I will toss you a link instead for direction. Warcraft 3 1.28 Pre-patch PSAYou didn't even begin to answer my question.
It's fine to have opinions. It's fine to strut them about. Many of us may not like your pessimism, but we don't have to. What we can and should expect is a modicum of respect & a baseline of research; I categorically denounce this statement as scurrilous libel. Even a cursory look at his giant freaking signature banner would reveal that not only is @Kam a mapper... He's an active mapper with a finished product that he is continually updating even in recent months! How many of us can say that? Not me... Can you?... Sure you can call Kam community leader or whatever, but in fact he isn't mapper. He doesnt know what mapmakers need. ...
well, I mostly meant "coder". he's using GUI therefore he's not even nearly understand what does mapper (coder) really needs, those who push wc3 forward with amazing creations. No, I was talking about YouTD this time. Dota's code is simple and awful at many places, yet there's diamonds. Which had hard way getting good just because wc3 is fucking outdated. If devs do not love mapmakers, well, that's how games dies normally anywayHe's an active mapper with a finished product that he is continually updating even in recent months! How many of us can say that? Not me... Can you?
Well then. A literal example of "moving the goal-posts", and a short-sighted one at that. Geez.well, I mostly meant "coder". he's using GUI therefore he's not even nearly understand what does mapper (coder) really needs, those who push wc3 forward with amazing creations. No, I was talking about YouTD this time. Dota's code is simple and awful at many places, yet there's diamonds. Which had hard way getting good just because wc3 is fucking outdated. If devs do not love mapmakers, well, that's how games dies normally anyway
I'm not sure I follow your rambling train of thought here.aha, I see. Tell me how many maps EpicWar has, and how many of titles you actually know or plays weekly. Just to see what different "mapper" from "coder". Mapper can think of good concept but will never implement it due to how hard is to code. Coder wise versa. You can surely pleasure those "turtle rock copy-paste" mapmakers. But I doubt you'll ever play those. Until you see the difference there's no point to talk about it with you.
And im in the line, for a year already. Im patient guy
Tons of font bugs, can't change brightness, can't open options in the main menu. Nice, Blizzard!
WC3 never had the ability to change brightness... Cannot lose something it never had!can't change brightness
Use regedit to delete all WC3 settings while WC3 is closed. WC3 will rebuild those registry keys next time it is run. It seems invalid ones cause the options menu to crash.can't open options in the main menu
Can't change gamma (which directly translates to how bright things are on the screen, but thanks for being on guard for meaningless mistakes).WC3 never had the ability to change brightness... Cannot lose something it never had!
How about I don't tinker with my operating system's sensitive components just because Blizzard Entertainment can't patch their own games properly? And it didn't work anyways.Use regedit to delete all WC3 settings while WC3 is closed. WC3 will rebuild those registry keys next time it is run. It seems invalid ones cause the options menu to crash.
WC3 never had the ability to change brightness... Cannot lose something it never had!
Gamma does not change how bright things are. It changes the lighting response in a non linear way... Black is still the same black and white the same white no matter the value of gamma, unlike brightness which changes those.Can't change gamma (which directly translates to how bright things are on the screen, but thanks for being on guard for meaningless mistakes).
You are tinkering with a program's data and not the operating system's. If it still crashes try reinstalling WC3. If it still crashes then, possibly your graphic driver is exposing a mode that WC3 cannot handle displaying in the options?How about I don't tinker with my operating system's sensitive components just because Blizzard Entertainment can't patch their own games properly? And it didn't work anyways.
Check again, no brightness. Only gamma which has nothing to do with brightness or contrast.There is that option.Please go check Warcraft 3 settings again.
Thanks for admitting my point.Yes it can make an image look brighter
Now you are contradicting yourself?Gamma does not change how bright things are.
It doesn't crash. The menu scrolls upwards into infinity, never to come back.If it still crashes try reinstalling WC3
No I am not.Now you are contradicting yourself?
So could potentially negating (making a negative) an image if the components of an image are on average less than half maximum intensity. Still does not make it a "brightness" setting as brightness adjustment is neither gamma or negation.An image is a thing, thus if gamma correction can make an image brighter, it can make 'things' brighter.
Options work fine for me. Probably also worked fine on their test rig.I'm not interested in wasting time fixing what Blizzard fucked up by myself just because they can't run a patch in a testing environment first to see what will it break. I just felt the need to express how little regard I have for these twits here. I'd rather prefer getting my money back at this point.
How convenient, ignoring the whole point of me talking about brightness as it is understood in common sense and you incorrectly assuming that I'm talking about brightness as it is understood in color theory.No I am not.
So could potentially negating (making a negative) an image if the components of an image are on average less than half maximum intensity. Still does not make it a "brightness" setting as brightness adjustment is neither gamma or negation.
Options work fine for me. Probably also worked fine on their test rig.
Run Warcraft 3 with -nativefullscr OR change it in your AMD Catalyst/NVidia Control Panel/Intel HD Graphics Control Panel, whatever solution you use.Hello all, i'm french and i'm sorry if i don't speak english very well.
I play warcraft III Frozen Throne with the new patch 1.28 and i have very big problem : my screen during the game is extremely dark and i can't change the gamma control in the panel setting.
This problem make me crazy !
What can i do ? please help me or i die !
Also, I quoted two of your contradicting statements one after another. You can't just say "No, I'm not" in response to that.
So according to DSG, it can make things look brighter, but cannot change how bright things 'are'. Now, whether there's more than a semantical difference between "looking" and "being" brighter... Ah dannae. : )Gamma does not change how bright things are. It changes the lighting response in a non linear way... Black is still the same black and while the same white no matter the value of gamma, unlike brightness which changes those.
Yes it can make an image look brighter, but that is a side effect of gamma altering the average intensity of component values.
Run Warcraft 3 with -nativefullscr OR change it in your AMD Catalyst/NVidia Control Panel/Intel HD Graphics Control Panel, whatever solution you use.
Edit: Also I guess you could change your monitor brightness if those other two seem too difficult.
Add the -nativefullscr flag to the command line of a shortcut.Thank you for your answer Jondrean but i don't know how i can run Warcraft 3 with native full screen. Can you explain me ?
Weren't if we followed Dr Super Good's logic, were if we followed mine. He responded to me, so the context arose from my post. The context where "brightness" is how bright, in the common sense, the image displayed on the screen is, not where it's a property like in the color theory. I'm no expert on color theory or semantics, but I am pretty sure that in that context what he wrote was, if not contradicting itself, just irrelevant to that context.I generally agree with your points, and definitely agree with your presentation. However, if we're going into semantics & such, I must point out that the "two contradicting statements" you quoted weren't quite contradictory, read in context.
Add the -nativefullscr flag to the command line of a shortcut.
EG: Target: "C:\Program Files (x86)\Warcraft III\Frozen Throne.exe" -nativefullscr
When run from that shortcut the game will be in exclusive fullscreen mode.
Report it as a bug that mouse is not being locked to the display in a multi-display environment. In the mean time you can turn off one of the displays while playing WC3 and enable it afterwards (bad workaround but still a workaround).How i can resolve this problem ?
Are you sure it's happening during the game? Mouse clamping should be in effect while in-game and not when in menus.Edit : Ok it work, but i am in dual screen and during the game, my mouse can go to the second screen (and return to the windows when i click in the desk on the second screen)
How i can resolve this problem ?
Give it about 10 minutes. It will hang at 0 percent for a while but should eventually advance. It requires moving all maps from your install folder to a user folder which might take some time, especially if installed on a separate partition from where user profiles are stored.Any tips please?
Give it about 10 minutes. It will hang at 0 percent for a while but should eventually advance. It requires moving all maps from your install folder to a user folder which might take some time, especially if installed on a separate partition from where user profiles are stored.
If not then reinstall the game.
It is, you have to uncheck the checkbox below the solution drop-down-menu, this allows to choose solutions which are not 4:3.Ah.. Thank you. And how can I fix screen resolution ? Is it still possible to have 1920x1080 or not ?
You disable fixed aspect ratio. Mind you it will result in highly distorted visuals as only the text scales properly with everything else being stretched from 4:3 to 16:9. For this reason it is recommended to play with fixed aspect ratio, so icons are square and units do not seem fat.Ah.. Thank you. And how can I fix screen resolution ? Is it still possible to have 1920x1080 or not ?
Sure. Besides the 'bad stupid' part, did you ever consider that may be one of the reasons why they needed the new patch system in this update? So they can be able to test patches before they release it, among other things.Bad blizzard stupid developers can't test patch before release?
I'm not protecting anyone. I'm just answering your question.You are one of the bad blizzard stupid developers? Otherwise, why would you want to protect them?
You want something like PTR, or?Bad blizzard stupid developers can't test patch before release?
No? I literally just gave an answer to your question and that's it. I never said to stop hating Blizzard, anything to protect Blizzard, or anything of the likes. I honestly don't care about if you like them or not.You protecting blizzard developers. Every patch added new problems and resolve only part of previous problems.
The entire graphic system is poorly optimized by todays standards as it was written for D3D8/OpenGL fixed function pipelines. It is not something they can fix without raising the minimum system requirements.Blizzard developers publicly promised to solve the problem with big CPU usage (low FPS), they did it?
They promised to fix FPS in 127c or 128a.
For example hpbars not optimized and uses a lot of CPU, even on invulnerable(without hp bar) units.