Cerberus Garde
Thema drucken
28.11.2012 02:02
|
It is the 31st Century and mankind is once again at war. |
|
Antworten
|
Zum Thema Netcode und Bugfixing bin ich durch Zufall auf diesen Post hier gestossen: Posted 01 December 2012 - 10:27 AM To some extent people that produce content can fix bugs. For instance, a graphical bug can be fixed by the graphical team, a feature problem (weapon balance etc) can be fixed by the people who implemented them in the first place. That's kind of how we've got to this stage in the first place. However: People from the graphical team cannot solve netcode bugs. Switching emphasis only works within departments. Some bugs at present may be beyond the capability of the current team to solve - particularly netcode optimisation. It's probably not a coincidence that they're attempting to hire a lead network programmer at this stage. Most bugs, however, don't fall into this category. The bugs we're seeing now are by and large not the same ones we saw in closed beta. The bugs we used to have include having absolutely no rendering of textures whatsoever (you pilot based on red triangles and minimap only, because you can't see anything else), while new bugs in recent patches include an absurdly high crash-to-desktop rate that was never an issue prior to the introduction of some new content, and disappearance of the HUD upon shutdown. Introduction of new content creates new bugs, if they were to fix all bugs for one phase, the new set of content they introduce after that will restart the whole process again. Most games never truly finish quashing all bugs entirely, but main gamebreaking ones will all be destroyed prior to Release. The more content a game has, the more bugs it will thus have. Massive games like Skyrim have accompanying massive amounts of bugs, whereas small games like Minesweeper can have none by release. The new content has to be released on some semblance of a schedule or the game will never make it to release. Some games are stuck in the phase of bugfixing forever - 'development hell': the most recent example of this is Final Fantasy XIII Versus, but it never even made it to beta. When combined with #3 it makes sense to fix bugs while also releasing content, then only switch full emphasis to bug quashing just before release in order to release the product in the shortest development time possible. This is a Beta, and the B there stands for Bugs. Admittedly it's a relatively special Beta, since normally progress from even Open Beta is never carried into Release - but adequate communication has been made that spending money at this stage is a purchase-at-your-own-risk thing. We only see the product, we can't see the process going on behind the scenes. A lot of optimisation and bug fixes are invisible to the general end user. Thus they're better positioned to decide on what to fix and what to implement on what schedule than we are. We are better positioned to see what the bugs are, and to report them to them development team for fixing. Deciding on the priorities for them is not our job. That's about it. I'm closing the thread because this isn't the kind of thing that would really help the game at this point due to #6. This is NOT to say that fixing bugs are a minor issue, or their approach at present is necessarily the best one with respect to every single bug. If you come up with ideas on how to fix some of the bugs, please do post, it's entirely possible you can think of stuff the current dev team cannot. When you see bugs - please do post: that's more or less the main purpose of this subforum in the first place. [Patch feedback: talk about the latest patch and any new issues it caused. General discussion: talk about the game in its overall state, and bugs that have persisted for some time. Suggestions: ideas on new content.] Also, because it's horrendously vague. If you don't want to see a new feature currently in development (for instance, 3rd person [!!!]), feedback on that, accompanied by reasons, are welcome - but 'all new content' is a little bit over the top. Tl;dr, closing because this isn't really going to help things much.
I'm confused... or wait - maybe I'm not..
GoNutsforGlory |
|
|
Kannst du es bitte grob übersetzen? ^^  Solaris Light Tournament Champion - Leifur Eirikson |
|
|
Ah... toll... ^^ Solaris Light Tournament Champion - Leifur Eirikson |
|
|
Ähhh - na ja, nicht ganz.
I'm confused... or wait - maybe I'm not..
GoNutsforGlory |
|
|
Neuigkeiten beim Netcode-Roadmap. Another quick update on where we stand with the netcode roadmap. As outlined last time the first phase for the netcode was work to cleanup and solidify the basic movement code for Mechs. This work is complete and is already being phased into production, all initial work related to the movement code should be in by the end of January. Internally work has already started on the next, harder, yet much anticipated phase which is to implement correct ‘State Re-winding’ for those not familiar with the term State Re-winding means that when you shoot at a Mech rather than check the shot against the Mechs current hit box location we rewind the Mechs state to the time in the past when the shot was fired and check the shot against the hit box position at that time. We anticipate having this running in internal testing in a few weeks’ time, and then obviously it will be dependent on testing the time beyond that to get it onto production. We know that for some of you the lag shield issue can’t be resolved soon enough especially with the new Spider Mech hitting production today. We share your desire to see this issue resolved and wanted to re-assure the community that it remains one of our highest priorities and we’re excited to get this work wrapped up and available to the community. Quelle: MW:Omercs Forum Wird wohl noch 'ne Weile dauern, bis das alles so läuft, wie es soll. Angegebene Zeiten: Movement-Code ist komplett und soll Ende Januar "drin sein". Hitbox-Code: einige Wochen... Nix zum Lagshield und zur Kollisionsabfrage. Aber vielleicht ist die Kollisionsabfrage ja auch im Movement-Code mit drin... Wer weiss das schon?
I'm confused... or wait - maybe I'm not..
GoNutsforGlory |
|
