Jathniel
G I A N T
EoN.
370
   |
Posted - 2013.05.24 13:44:00 -
[1] - Quote
Interesting post, but I take issue with some of the complaints.
FPS - This is a game engine/PS3 issue. They chose Unreal. The PS3 is doing it's best given the scale, with the intended engine. It's not fair to compare with BF3's Frostbite engine, for example, (totally different engine optimized for the PS3). Graphics are going to be ongoing, but don't expect things to get much better with the current engine. They would need to create a whole new engine to get the major graphics rework that you want that would produce improved FPS (another year of dev time).
Lag/Latency - Another variable. More dependent on so-called "internet weather". They're doing pretty good in this area considering the scale. This game does a LOT more on the server-side as opposed to the client-side vs. other games. Improvement here is GOING to take time.
New player experience - This I can agree with. Even if a new player were someone that stopped to read all the information pertaining to gear and skills, he will still end up in a bad way. With how Dust is currently balanced, what looks good on paper doesn't translate into the field. Furthermore, they have no definitive indicators of what weapon types they are using (hybrid, kinetic, energy, etc.). So the tutorial they DO have is limited, and the information they are provided with in tooltips, etc. is incomplete. It doesn't say what a weapon's range is, or the rate of decay, etc.
Matchmaking - I disagree with the matchmaking. Newbies play with us, to learn how to play, and to get recruited. Dust is squad-based, and they will learn this very early, or they will leave. I DO however wish, the MM would compensate for putting them up against 2 fully-stacked teams. SP difference, not too much of a problem. Organized TEAM difference? That's the MM issue.
Dev Communication - this has improved a lot as of a day or two ago. Patch notes are updated every night now. You sign in, hit R2, and bam. Issues addressed during maintenance are listed right there. Bravo to CCP for this one.
Game Modes - My understanding during the closed beta was that the "Instant Battle" thing is actually what we are trying to get away from. We don't want a random set of game modes that have no purpose. Faction Warfare is being developed so that every battle fought literally effects EVE, and matters. The Instant Battles were simply supposed to be "proofs of concept" for the full game, with a Combat Arena coming later to satisfy the player desire for things like CTF and Domination, etc. But the INTENTION is supposed to be totally player owned and controlled districts, where we decide what buildings and installations to place... naturally this will take time. I imagine the Combat Arena will have a betting system so people can earn isk.
More Maps - I agree with this. A new map every month would be wonderful. This would make maps where certain roles dominate, inevitable, and I agree with that. A map where snipers rule? Yes. A map where heavies rule? Yes. I want to see us spitting out more maps. Monthly is perfect.
KB/M vs. Gamepad - This has already been addressed. Mice have a new sensitivity cap to keep them more in line with gamepads, this reduces the effectiveness of multi-DPI mice.
AFK Camping - You really don't need to be concerned about what someone is doing if they go afk. Yes, them not helping you means the match is unbalanced. Public matches where this occurs is of no consequence to anything. Every game has AFKers in some way. As long as matches are open to the public this will exist. Mid firefight, someone can walk right off and abandon you, and go AFK. That's reality. Get over it. If SP farming is what you're complaining about, that's not going to break the game. Players voted that system in during the beta. That is likely here to stay. It's New Eden, in a public match, no one is nor should be obligated to help you fight.
Starter SP - Currently, yes. The starter SP doesn't go far enough to enable players to compete. But we should wait until the new skill tree is revealed before saying there should be a change here. |