holy sh*t, i can never take anything you say seriously again.
merit and rationale are the only things ever give any weight to conjecture.
not that i imagine you care, because anyone that disagrees with a giant inflated ego like that will automatically be wrong in your mind.
New options that donât remotely address or improve the inherent engine problem. As for acknowledgement, Iâve seen Julie report that she was reporting to the devs the information provided by the very smart fellows in my thread - but when have you seen any acknowledgement they were working the kind of engine overhaul necessary to actually remedy the problem?
Iâd be very interested if you can provide a link to this. Iâd definitely back down on this issue - even apologize, with something like that in front of me.
As for âWhatever I sayâ, well, what I say isnât important. You only need to do a search on the subject - IMC not being at the office on weekends, and how this coincided with the worst episodes of commanderloadfail on Klaipeda, only being resolved when the work week arrived on South Korea. Be upset with reality - you donât need to even consider me.
@tzxazrael
You didnât get the joke. I said I didnât need to depend on merit and rationale to give weight to my words because my statements were no longer conjecture. They are observations that are both present and documented history, as evidenced by, well - Iâd tell you guys to search the forums, but you still arenât doing that, or you wouldnât be coming at me over what most informed members of this community consider common knowledge.
Need I point out that the engine problem has existed since closed beta?
Thatâs because CommandLoadFail has to deal with the number of people doing the instances at any given time. This is pretty much general knowledge at this point. I donât know how even you havenât read this somewhere. The peak times are always going to be the worst for this. That would be , you guessed it, the weekends. This is also the reason why Klaipeda has it worse than the other servers; it is by far the most populated server. It isnât because the staff is gone on weekends; itâs because there are more players on during the weekends.
They havenât flat out stated they are overhauling the enginge, but Hak Kyu Kim himself acknowledged the problem and said they are working on it ârecentlyâ.
Read it? I was arguing that same point myself! If they had staff present on the weekends - somebody at the till, as it were - they would have taken the server down for emergency maintenance and brought it back up with increased capacity. Instead that happened on, hey, you guessed it - South Koreaâs monday.
It isnât like this was the only problem that went ignored over an entire weekend, anyway.
And, Iâm not about to accept hearsay on these forums, so I insist you provide a link to this acknowledgment. Again.
This is the thread. I donât know how to externally link to an exact post of a thread.
I gave them a negative review on Steam because they deserve it. I donât give merit based on âpotentialâ or âeffortâ. This is my time and money, for that i demand results, as it should be.
When and if they reach a point that is satisfactory, reviews will change. Until then, new players should be well aware of what theyâre getting into, not what might be or could be.
Thank you. Iâm not sure how to interpret that post by kim. It doesnât match up to the very solid findings from the player base in a way I canât help but find ominous.
TLDR; Disabling all player models but 10 or 5 does almost nothing for most users in congested areas, the game isnât even processing graphics at that point - something is choking the engine and it isnât # of models or textures rendered. Testing indicates it might actually be the engine throttling FPS based on inefficient single-core processing of TCP packets related to player positioning and movement.
Nothing kim suggested in his âat leastâ will fix the problem at hand, or even address it. But he didnât say thatâs all they were doing, either.
the engine was created for Granado Espada, originally launched 10 years ago.
i would think that whatever optimization we could expect âsoonâ has already happened.
there might be more âeventuallyâ, but other things probably take priority right now, especially if CommanderLoadFail has come backâŚ