The launch of Star Wars Jedi: Survivor was, as we told you at the time, an absolute fiasco. Once again we have found a game that has reached the market when its state of development was far from being, no longer ideal, not even adequate, by the minimum, to go on sale. Developers and publishers have decided that you don’t have to do a job well and then get paid for it, and have turned pre-purchasing future releases into something of a gamble, only at best you get what you get for what you have paid, no more.
It is also true, however, that the tolerance of some players seems to be giving scope to this way of proceeding by developers and distributors. It is enough to take a quick look at the reviews that Star Wars Jedi: Survivor accumulates to see the enormous number of them that criticize the terrible optimization but, despite this, recommend it. In early April, following the disastrous launch of The Last of Us Part 1 for PC, we asked you what you thought about these failed launches and, of course, we thought alike. However, a quick look at the opinions on Steam will surprise you.
We have also gotten used to the fact that, after the failed launch, come the apologies and the promises, and it is true that we have already seen cases in the past in which redemption has been possible. The clearest and closest example is Cyberpunk 2077, but we can also remember other previous cases, such as the (now) fantastic No Man’s Sky. The problem is, of course, the way in which the confidence of the players who demand a minimum has ended up falling to historic lows.
One of the most common promises is, of course, that the problems will be solved with future updates. However, and especially during the first weeks, these do not usually solve the most serious problems. And such is the case, as we can read in Wccftech, Star Wars Jedi: Survivor patch 4 doesn’t seem to fix performance issues, at least on consoles. And it is that, if we review the complete notes of this update, we can see that the most interesting thing is not in what it solves, but in what follows in the list of pending tasks.
Recall that the launch of Star Wars Jedi: Survivor it was postponed from its initial date, March 15, until April 28, in theory to solve technical problems. Now, just over a week after its release, a small part of the problems have already been solved, and we must trust that the solution to the rest is on the way. So, if this is your capacity to work, why didn’t you choose to delay it for two months, or three, so that the game would arrive in better condition? We don’t know the answer, of course, but we can imagine it, right?
