1. Deze website gebruikt cookies. Door deze website verder te gebruiken, gaat u akkoord met ons gebruik van cookies. Leer Meer.

[Multi] Star Wars Squadrons

Discussie in 'Games' gestart door AgentSmith, 15 jun 2020.

  1. AgentSmith

    AgentSmith GT iD: AgentSmithNL PSN iD: AgentSmithNL

    Berichten:
    2.316
    Leuk Bevonden:
    331


    Vanaf 2 oktober verkrijgbaar.
    Vermoed wel dat de PS4 versie VR ondersteunt.
     
  2. NLegendkiller

    NLegendkiller Active Member

    Berichten:
    1.745
    Leuk Bevonden:
    513
    "Het spel wordt uitgebracht op 2 oktober 2020 voor PlayStation 4, Xbox One, PC via Origin, Steam en Epic Games Store, en kan worden gespeeld via Virtual Reality (VR) op PlayStation 4 en PC met ondersteuning voor crossplay."
     
  3. Servantes

    Servantes Live: Servantes NL PSN: Servantes-NL

    Berichten:
    7.080
    Leuk Bevonden:
    2.375
     
    AgentSmith vindt dit leuk.
  4. Servantes

    Servantes Live: Servantes NL PSN: Servantes-NL

    Berichten:
    7.080
    Leuk Bevonden:
    2.375
  5. Servantes

    Servantes Live: Servantes NL PSN: Servantes-NL

    Berichten:
    7.080
    Leuk Bevonden:
    2.375
    Squadron 42 & Roadmap Update

    Hi everyone,

    When we realized that our old Roadmap didn’t represent our development progress very well, we started exploring options for how to build something more informational that fit how we develop games. Our original message about this was in one of March’s Roadmap Roundups, and we followed up with hints about this in our Squadron 42-focused Calling All Devs on March 13.

    The recent SQ42 video update, which is a brand-new show we were debuting called “The Briefing Room,” was a lower-effort video that we embarked on with the goal of sharing more information with you but in a scrappy and fast manner, so as to minimize the disruption to the dev team and yet still give you new information. We planned for this to be a semi-regular show, with its cadence depending on how well the content was received and how disruptive (or not) this first episode would be to our dev team. This first episode was meant to focus specifically on (spoiler alert) updates on our conversation interrupt tech and level design in SQ42. What we discovered after the whole piece was finished and getting ready for publish was that our approach resulted in an underwhelming show. Not only did the episode have major audio issues due to WFH recording, but it lacked visuals to support the talking, and we truly prefer to show rather than tell. Ultimately, we decided that it wasn’t good enough to show, even for a “scrappy” video that was not meant to be a marketing sizzle trailer. However, before that “stop ship” message could permeate our entire marketing org, we had moved forward with a public publish date.

    Originally, we thought we could simply splice in fresh b-roll, but as we spent the next few days reviewing the show, we saw the need to update our visuals to better reflect what we were discussing, and that led us to the realization that we still didn’t have the right footage, at our quality bar, to tell the story we wanted to tell. So, we ended up deciding to re-shoot the entire episode with our usual quality standards.

    We’ve certainly communicated the delays and the reasons for it, and have even had Brian Chambers relay the news initially, with our CMs repeating that message when the topic cropped up multiple times. We’ve had to do that a couple of times over the past weeks. And unfortunately, the plain truth was always the same: The initial video didn’t meet our standards and we are redoing it. We didn’t get into such details as sick personnel nor did we explicitly spell out that the video footage couldn’t leapfrog actual dev work in our priority list. After all, we don’t like to make excuses.

    The SQ42 video is still coming (probably in the next few weeks), along with an assortment of other updates, including an overhaul to our Public Roadmap.
    The new Roadmap is something we hinted at in March but because that is still very much in development, we can’t share as much about it as I would like. Believe me when I say I’m personally very eager to release it to you. We took the time to explore options for how we could better represent our progress, and I believe we are getting close to landing in a pretty great spot.In the immediate future, we plan to deliver the following communications:
    1. Give an explanation of the goals of our new Roadmap and what to expect from it
    2. Show a rough mockup of the proposed new Roadmap
    3. Share a work in progress version of the Roadmap for at least one of our core teams
    And then finally transition to this new Roadmap
    We’ll approach them in the order above, and we’ll likely need a few weeks between steps, so I don’t want to create the impression that this is happening overnight. But we should be announcing step 1 pretty soon if my meeting on Thursday about this is as good as I think it will be.
     

Deel Deze Pagina