Jump to content

Agarwel

Members
  • Posts

    75
  • Joined

  • Last visited

Posts posted by Agarwel

  1. 22 hours ago, Tyko said:

    At some point in the future Squad is going to be releasing an update and there'll be an internal discussion

    "Should we announce the launch date ahead of time? All the players bug us incessantly about launch dates".

    Followed by "ummm...maybe not, you know what happened last time we gave out a launch date"

    You know, maybe they should not announce the update release date, and just fix the game in reasonable time instead?

    To compare, when No Mans Sky or Kingdom Come were released, there were also many bugs and complains. But these companies (in case of NMS also very small indie studio) released more updates per week, than KSP EE had in year. And you could feel the game improving under your hands. They didnt need to announce the release dates of these updates. They just released them.

    That is the way to do it. Most of the people are not annoyed because there is a delay. But because it is taking so long (actually over 2,5years since initial release) wiht basically no communication during this time.

  2. 1 hour ago, KosmoNot79 said:

    So the hate that Squad is getting is directed to the wrong person/group? I'm just curious.

    That is the question. Blitworks should be responsible for porting the game (making sure it runs on the consoles, changing the tutorials to reflect gamepad controls, makings sure trophies are working correctly on the platform and taking care of the certification process). I dont believe the "porting job" should include fixing the source product.

    And considering the KSP has been ported by two different companies (at least one of them really experienced) and both of them were released broken, it makes you think that the troubles may be caused by the code they are asked to port.

    You know - if someone pays you to move the furniture to a new house, and they have a broken fringe, you are not responsible that the fringe will be still broken after you move it to new locaiton.

  3. 4 hours ago, T1mo98 said:

    If you had any idea how development works you'd know that these things happen and cannot always be accounted for beforehand. 

    This can happen. But honestly - three times is not normal, do you agree? The KSP was released in such state, that it got pulled of from the store (at least you could not buy it in some regions). It was so broken, they decided to do new port from scratch so fixing took 1,5 year. (this is not normal - when did this happen before?). Then then one version was also full of gamebreaking bugs so we waited months for two updates (normal studios supprot their games much faster). And now we have another upate, that is so broken, they had to cancel the release.

    If this happens during development, how many games are released like this?

  4. So after 8 months of development since last update, the current version is in unplayable state (at least so bad, it can not be released to the public). Well, lets hope that some quick patch will fix all of that :-(

    Well, I really hoped that this next pathc will just polish the game. Not break it even more :-/

  5. Well. Who is actually surprised?

    9 hours ago, sicko kerman said:

    Either way does anyone know because I have only played KSP for 6 month and been in the forums for less than a month does anyone know how long the delays usually are? A couple weeks a week a couple days idk

    Unfortunatelly in case of console KSP, the "soon" usually ment months or even ever whole year. So who knows this time. :-(

  6. On 3/6/2019 at 3:15 AM, The_Cat_In_Space said:

    And they're referring to the major update coming out, I believe you're referring to KSP console being replaced by Enhanced Edition, not about the update

    I belive that he is reffering mainly to the time frame, that "after 18 months" has been presented "soon".

    And if I rememeber correctly they mentioned new patch with "soon" info in October? 5 month ago. So if they promisse something soon again, what should we expect? Weeks? Months? Years?

    It really reminds me beggining of the movie Snatch: "It was three minutes, five minutes ago!"

  7. On 2/2/2019 at 12:27 AM, Invenisso said:

    There will be update "fairly soon". See:

     

     

    Unfortunatelally the "soon" can mean "more than one year in the future" on the Console KSP. We are promissed to get working version soon for more than 2,5 years.

    The new promised update scares me. It should bring new features? I expect additional new bugs too? I would prefer for them to finish the version we have, iron out the bugs and let us just enjoy it. If this update is buggy and we will wait another year for another update, than what is the point?

  8. If you consider the game support (after 2,5years sice original release date we are still waiting for the version without gamebreaking bugs), I would not expect the future content to be added.

    Supposedly they are still working on the update (but there is no info except that we will have a info "soon"). So I expect somewhen in the future we will get one last final patch and then the game will be abandonned :-(

  9. 31 minutes ago, Leopard said:

    Ture, but that doesn't mean a common code base isn't possible, you use conditional compiling to produce the different versions, means fixing a bug on one platform should sort them on the others - unless its in a platform specific bit.

    That is true in theory. But look at the release pains of this game. Two different companies ported the game to the consoles. And both resulted in broken game (both times in very similar way).

    What does it tell me just by common sense? Kerbal code is written in a way, that just porting a updating gui breaks lot of stuff that normally should not be broken. So it required lots of updates a patches and workarounds that are not implemented in the original PC code. As a result I can imagine the console port code is now very different from the PC code. And because it is done by different companies, I dont believe it is possible to merge it into one code. And release both versions together.

    So I can imagine 1.4 is planned. But it will take some time to implement into already existing console version.

  10. I jsut encountered small bug. I had contract to expand spacestation. Once I docked new module, the objective "ensure it has antena, docking port and can geenrate power" was not marked as completed.

    Fortunatelly if I went back to space center and then loaded the station back via tracking station, it was marked as completed. So realoding the ship was needed.

  11. So about that control lock issue - Im now 100% sure it is bug. And not me missunderstanding some flight controls. Because it happened to me even in the space center main screen now. I could control the game by the cursor. But as soon as I pressed L3, the cursor should dissapear and I should be able to use stick to browse the icons on the left side of the screens (one of them should be highlighed). And this did not happened. None of the icons was highligheted. I could not browse them.

    Switching back to the cursor I could load up any building and continue playing.

    And again - this happened to me after I was checking the notification queue.

  12. 3 hours ago, Arch3rAc3 said:

    There's also the in game tutorials, pretty handful.

    True. But Scott Manleys begginer tutorials are much deeper (seriously approx 10 hours of interesting stuff) and they dont just cover what to do, but also why to do it and what would happen if you do it another way. After his videos the game is much easier to understand by "common sense".

    When you are beggining I really suggest to watch at least first fours his videos. Then all the ingame tutorials. And then go for career.

  13. 29 minutes ago, Tex_NL said:

    WRONG!!! You're a perfect 180 degrees off. In orbit mode on the navball at launch the prograde marker faces EAST!

    You are right. And I was double wrong (making me actualy right in the end :-P) I totaly messed up, that you want to start to the east (I know the direction on the navball, but totally got these messed up.) To using propagade on the orbit navbal gets the desired result in the end. But my original question was completelly wrong :-D

×
×
  • Create New...