Jump to content

Pendragon1951

PC Member
  • Posts

    2,636
  • Joined

  • Last visited

Posts posted by Pendragon1951

  1. Just saw a clip from Steve on his twitter showing a warframe battling a Eidolon, now here is a question, someone tried to tell me that Eidolons and Sentients are one and the same, which seems odd to me since on the big reveal Steve called it a Eidolon?

  2. Here is a suggestion, which I hate to give out because once known the nerf hammer may not be far behind, which is much simpler. Just use a Rakata Cernos bow, not sure which syndicate it's from, it replenishes energy after so many kills. When I go into say a spy mission before I begin I pop a energy restore, once done I go invisible and just kill as I go and I can stay invisible the whole mission without using anymore energy restores.

  3. I will be the first one to admit that after four years of playing this is the most hyped and excited I have ever been about what's coming next in Warframe and I can't wait. Finally something that will actually feel like you are making a difference in the game. Imagine coming upon a small village that you have to defend against hordes of enemies like in the Magnificent Seven (The Original). The idea of what comes out only at night gives a creepy vibe to the game as well. To those worrying about if your machine can handle all this apparently Steve has stated that they are working to make sure even potato machines can run it. I also think that with this cross country traveling Archwing will finally come into its own. Imagine being high up in the air and using your sniper gun, which also will finally see some value as well. All in all i'm really looking forward to this and what they will do ith this new direction in the future moving forward.

  4. On 7/2/2017 at 3:40 PM, pnellesen said:

    I use Limbo to solo Spy and Rescue sorties. It sometimes takes  me 2 or 3 attempts, but still faster than pugging. And I only have myself to blame when I fail.

    I'm curious, aside that maybe Limbo is your favorite, why would you ever take Limbo, the enemy can always see you no matter if you void walk, and won't you still trip lasers? Not bad mouthing Limbo just curious why him for a spy mission?

  5. It might be time to re-examine your faith if a video game is able to give you pause, maybe have a talk with your Pastor, it may be something deeper that the game has triggered that is going on in your life. There is nothing wrong with external sources making you think deeper about your religion, I myself being a Catholic have always questioned certain things and to be honest I think I'm going to drive my Priest to drink. To conclude just enjoy the game for what it is a game and as I said maybe talk to your Pastor:)

  6. 1 minute ago, Tesseract7777 said:

    I understand why that sounds reasonable, but think of it this way: That "live test build" is still not the same build as the live build everyone uses. It's still going to have small differences, and you still have the chance of unforeseen issues cropping up when you port it from the live test server to the live main server. 

    I think it would be better if they just hadn't said "definitely today" in the first place. Then they wouldn't feel the pressure to keep their employees all night to get it out today, and people wouldn't feel like they are waiting past expectations. 

    I so agree with you on that, I guess I'm just spoiled by World of Warships they have a play test server where anyone can jump on and play the update for a week and give feedback then about a week or so later they deploy no muss no fuss:)

  7. 1 minute ago, Tesseract7777 said:

    The problem is that coding is a crapshoot. They test builds on the dev build first, but sometimes things still unexpectedly go wrong. About a billion little things can go wrong anytime you slightly change something involving code. They can be sure its fine on the dev build, and still end up with issues on the regular build. I remember taking coding classes in college and them driving me to drink at how frustrating it could be. For example, one tiny missing parenthesis buried in so many nested parenthesis that it can be very hard to find, can ruin everything. That's very basic and has nothing to do with what's going on here, but it's just a small example of how little things in code have such a huge effect. 

    I could never imagine being a professional programmer, I think I would go insane. Most programmers spend the majority of their time debugging. 

    once again I completely agree and once again I say they should have a public build like world of warships to test on this way they would actually deploy on the day they say.

  8. Just now, SamareRein said:

    Take the time you need to get it done right. Ignore the salty morons. Those of us with brains understand it takes time to fix errors when they pop up. They don't seem to understand it takes a lot of work and playing through the quest over and over to make sure things are fixed.

    Then maybe you could explain to me why this wasn't all done before deployment day instead of on deployment day?

  9. 2 minutes ago, Tesseract7777 said:

    I think some people are forgetting basic empathy 101 right now. Yes it's frustrating, and I understand people are waiting and very excited. But, regardless of how people feel DE's managment is at setting deadlines and meeting them, etc, the random average coder or animator at DE has no control over how good DE's management is at meeting deadlines.

    And right now lots of animators and coders and all those other jobs are working their butts off, overtime, to bring the update tonight if possible. If they have kids, their kiddo's will probably be in bed by the time they get home. And they won't have much time for their spouse, because they will probably almost immediately have to go to bed, exhausted, to have enough energy for work the next day. Because it's still the work week and the wheels at DE don't stop turning right after a big update is released. 

    I feel for them, and I would prefer if DE let their employees go home to their families for the night. We can wait until tomorrow. 

    We here waiting, we can play fun video games to entertain ourselves. 

    The random everyday employees at DE are doing tedious debugging for our sake. I know which group I feel more sorry for. 

    I completely emphasize with what your saying, but as the saying goes "fore warned is fore armed" all this testing and fixing of problems that come up should have been done and completed before making any kind of commitments and especially not on deployment day.. As I said before this is like giving a college marching band their music formation notes an hour before they go on.

  10. 3 minutes ago, [DE]Mumbles said:

    8:44PM:

    We're still here and still working on deploying tonight - we'll update this thread again in at least 2 hours. 

    I would personally like to know why all this was not taken care of before announcing a launch time?? It seems really impractical to me to test something on the suppose day of deployment and find out there are problems with the update, that is like giving a college marching band their music and formation notes an hour before going on to the field.

  11. 1 minute ago, Radagosh said:

    isn't that what they always do? It's become a ritual by now. Overhype the community - find bugs - fix bugs - find new bugs - fix new bugs - repeat step 2-4 - delay update for at least 12 hours

    In World of Warships they have a play test server and the community plays the update and gives feedback then about a week later or so it deploys, no hype no [de]lays

  12. 1 minute ago, SenorClipClop said:

    They said that's what they're trying to do. Places in London are closing down, it's after normal working hours. Peeps gotta stop breathing down devs' necks and let them do this nice thing for us that they don't even have to do today.

    but doesn't it make you wonder why you would test on the same day as deployment and not have done it and complete it before hand?

  13. 4 minutes ago, QU67 said:

    I think what they're saying is, "If you announced the update was gonna drop, shouldn't you have already had most of the major kinks worked out before you announced the date?" If that's the case, I agree. I get that Warframe survives off getting as much content out as quickly as possible, but for a major/semi-major update like this is I would've hoped tests for "quest progression" would've been finished before the day of release.

    This!

×
×
  • Create New...