Look who I found in the comment section of a 2017 generalkidd video
Just watched a GeneralKidd halo video for the first time in a decade. How are his videos still so badly edited and terrible on the spot commentary. Like the mythbusting stuff is cool but what the fuck man.
https://www.halowaypoint.com/en-us/news/mcc-development-update-3
Blue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).
Quote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.
Quote from: Boomdeyadah on April 18, 2018, 06:22:33 PMQuote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.Honestly I feel bad for the individual artists and programmers and animators there, who I'm sure do genuinely want to build the best game they can and are probably the ones who actually see all the shit flung about the newer entries online, especially the ones who probably signed up to work at 343 back in 2008-2011 when the series was at its most popular. Just a shame that unless you're one of the leads, you pretty much get no say in anything and just have to do the work you're given.
Quote from: BaconShelf on April 18, 2018, 07:13:01 PMQuote from: Boomdeyadah on April 18, 2018, 06:22:33 PMQuote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.Honestly I feel bad for the individual artists and programmers and animators there, who I'm sure do genuinely want to build the best game they can and are probably the ones who actually see all the shit flung about the newer entries online, especially the ones who probably signed up to work at 343 back in 2008-2011 when the series was at its most popular. Just a shame that unless you're one of the leads, you pretty much get no say in anything and just have to do the work you're given.What kills me is that the actual concept at 343i are genuinely great but by the time it ends up actualy in the games it's been corrupted into shit like Seeker. I'd really like to know what is going on behind the scenes that this happens.
Quote from: Chaos Metal Dragon on April 18, 2018, 08:41:24 PMQuote from: BaconShelf on April 18, 2018, 07:13:01 PMQuote from: Boomdeyadah on April 18, 2018, 06:22:33 PMQuote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.Honestly I feel bad for the individual artists and programmers and animators there, who I'm sure do genuinely want to build the best game they can and are probably the ones who actually see all the shit flung about the newer entries online, especially the ones who probably signed up to work at 343 back in 2008-2011 when the series was at its most popular. Just a shame that unless you're one of the leads, you pretty much get no say in anything and just have to do the work you're given.What kills me is that the actual concept at 343i are genuinely great but by the time it ends up actualy in the games it's been corrupted into shit like Seeker. I'd really like to know what is going on behind the scenes that this happens.I think people are just afraid to speak up. Imagine roasting your lead artist after he worked 30 hours to make the Seeker helmet. It can be intimidating.
Quote from: FatherlyNick on April 19, 2018, 02:28:51 AMQuote from: Chaos Metal Dragon on April 18, 2018, 08:41:24 PMQuote from: BaconShelf on April 18, 2018, 07:13:01 PMQuote from: Boomdeyadah on April 18, 2018, 06:22:33 PMQuote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.Honestly I feel bad for the individual artists and programmers and animators there, who I'm sure do genuinely want to build the best game they can and are probably the ones who actually see all the shit flung about the newer entries online, especially the ones who probably signed up to work at 343 back in 2008-2011 when the series was at its most popular. Just a shame that unless you're one of the leads, you pretty much get no say in anything and just have to do the work you're given.What kills me is that the actual concept at 343i are genuinely great but by the time it ends up actualy in the games it's been corrupted into shit like Seeker. I'd really like to know what is going on behind the scenes that this happens.I think people are just afraid to speak up. Imagine roasting your lead artist after he worked 30 hours to make the Seeker helmet. It can be intimidating.That's not how it works. Most of the arnour is contracted to third party studios, not done in-house.
Quote from: BaconShelf on April 19, 2018, 03:23:26 AMQuote from: FatherlyNick on April 19, 2018, 02:28:51 AMQuote from: Chaos Metal Dragon on April 18, 2018, 08:41:24 PMQuote from: BaconShelf on April 18, 2018, 07:13:01 PMQuote from: Boomdeyadah on April 18, 2018, 06:22:33 PMQuote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.Honestly I feel bad for the individual artists and programmers and animators there, who I'm sure do genuinely want to build the best game they can and are probably the ones who actually see all the shit flung about the newer entries online, especially the ones who probably signed up to work at 343 back in 2008-2011 when the series was at its most popular. Just a shame that unless you're one of the leads, you pretty much get no say in anything and just have to do the work you're given.What kills me is that the actual concept at 343i are genuinely great but by the time it ends up actualy in the games it's been corrupted into shit like Seeker. I'd really like to know what is going on behind the scenes that this happens.I think people are just afraid to speak up. Imagine roasting your lead artist after he worked 30 hours to make the Seeker helmet. It can be intimidating.That's not how it works. Most of the arnour is contracted to third party studios, not done in-house.Oh, they need to stop that or at least review them in early stages.
Quote from: FatherlyNick on April 19, 2018, 03:37:04 AMQuote from: BaconShelf on April 19, 2018, 03:23:26 AMQuote from: FatherlyNick on April 19, 2018, 02:28:51 AMQuote from: Chaos Metal Dragon on April 18, 2018, 08:41:24 PMQuote from: BaconShelf on April 18, 2018, 07:13:01 PMQuote from: Boomdeyadah on April 18, 2018, 06:22:33 PMQuote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.Honestly I feel bad for the individual artists and programmers and animators there, who I'm sure do genuinely want to build the best game they can and are probably the ones who actually see all the shit flung about the newer entries online, especially the ones who probably signed up to work at 343 back in 2008-2011 when the series was at its most popular. Just a shame that unless you're one of the leads, you pretty much get no say in anything and just have to do the work you're given.What kills me is that the actual concept at 343i are genuinely great but by the time it ends up actualy in the games it's been corrupted into shit like Seeker. I'd really like to know what is going on behind the scenes that this happens.I think people are just afraid to speak up. Imagine roasting your lead artist after he worked 30 hours to make the Seeker helmet. It can be intimidating.That's not how it works. Most of the arnour is contracted to third party studios, not done in-house.Oh, they need to stop that or at least review them in early stages.They do it because hiring an additional large amount of character artists is unfeasible.
Quote from: BaconShelf on April 19, 2018, 06:47:22 AMQuote from: FatherlyNick on April 19, 2018, 03:37:04 AMQuote from: BaconShelf on April 19, 2018, 03:23:26 AMQuote from: FatherlyNick on April 19, 2018, 02:28:51 AMQuote from: Chaos Metal Dragon on April 18, 2018, 08:41:24 PMQuote from: BaconShelf on April 18, 2018, 07:13:01 PMQuote from: Boomdeyadah on April 18, 2018, 06:22:33 PMQuote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.Honestly I feel bad for the individual artists and programmers and animators there, who I'm sure do genuinely want to build the best game they can and are probably the ones who actually see all the shit flung about the newer entries online, especially the ones who probably signed up to work at 343 back in 2008-2011 when the series was at its most popular. Just a shame that unless you're one of the leads, you pretty much get no say in anything and just have to do the work you're given.What kills me is that the actual concept at 343i are genuinely great but by the time it ends up actualy in the games it's been corrupted into shit like Seeker. I'd really like to know what is going on behind the scenes that this happens.I think people are just afraid to speak up. Imagine roasting your lead artist after he worked 30 hours to make the Seeker helmet. It can be intimidating.That's not how it works. Most of the arnour is contracted to third party studios, not done in-house.Oh, they need to stop that or at least review them in early stages.They do it because hiring an additional large amount of character artists is unfeasible.Considering how 70%+ of the armor in H5 is shit, they can probably do it all internally.Quality > quantity.
Quote from: FatherlyNick on April 19, 2018, 07:31:38 AMQuote from: BaconShelf on April 19, 2018, 06:47:22 AMQuote from: FatherlyNick on April 19, 2018, 03:37:04 AMQuote from: BaconShelf on April 19, 2018, 03:23:26 AMQuote from: FatherlyNick on April 19, 2018, 02:28:51 AMQuote from: Chaos Metal Dragon on April 18, 2018, 08:41:24 PMQuote from: BaconShelf on April 18, 2018, 07:13:01 PMQuote from: Boomdeyadah on April 18, 2018, 06:22:33 PMQuote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.Honestly I feel bad for the individual artists and programmers and animators there, who I'm sure do genuinely want to build the best game they can and are probably the ones who actually see all the shit flung about the newer entries online, especially the ones who probably signed up to work at 343 back in 2008-2011 when the series was at its most popular. Just a shame that unless you're one of the leads, you pretty much get no say in anything and just have to do the work you're given.What kills me is that the actual concept at 343i are genuinely great but by the time it ends up actualy in the games it's been corrupted into shit like Seeker. I'd really like to know what is going on behind the scenes that this happens.I think people are just afraid to speak up. Imagine roasting your lead artist after he worked 30 hours to make the Seeker helmet. It can be intimidating.That's not how it works. Most of the arnour is contracted to third party studios, not done in-house.Oh, they need to stop that or at least review them in early stages.They do it because hiring an additional large amount of character artists is unfeasible.Considering how 70%+ of the armor in H5 is shit, they can probably do it all internally.Quality > quantity.So I'm guessing you have no idea what an art pipeline looks like or how art works in games dev
Quote from: BaconShelf on April 19, 2018, 08:41:37 AMQuote from: FatherlyNick on April 19, 2018, 07:31:38 AMQuote from: BaconShelf on April 19, 2018, 06:47:22 AMQuote from: FatherlyNick on April 19, 2018, 03:37:04 AMQuote from: BaconShelf on April 19, 2018, 03:23:26 AMQuote from: FatherlyNick on April 19, 2018, 02:28:51 AMQuote from: Chaos Metal Dragon on April 18, 2018, 08:41:24 PMQuote from: BaconShelf on April 18, 2018, 07:13:01 PMQuote from: Boomdeyadah on April 18, 2018, 06:22:33 PMQuote from: Spartan on April 18, 2018, 02:08:42 AMhttps://www.halowaypoint.com/en-us/news/mcc-development-update-3QuoteBlue Screen – Sean has done some work to bring back to the Halo 2 network transition screen (the bluescreen that pops up saying “Connecting to game…” and when there’s a wait for a player to join or when a host migration occurs). Turns out that original code was ‘commented out’ during MCC development which resulted in H2 network games just having black screens or just a scoreboard which isn’t informative for players (nor historically correct!).Wow I forgot that was a thing in Halo 2. Got so used to the black screen in MCC I guess. Looks like some people at 343 really do want to fix this abomination of a game when they go after the little things like this.Honestly I feel bad for the individual artists and programmers and animators there, who I'm sure do genuinely want to build the best game they can and are probably the ones who actually see all the shit flung about the newer entries online, especially the ones who probably signed up to work at 343 back in 2008-2011 when the series was at its most popular. Just a shame that unless you're one of the leads, you pretty much get no say in anything and just have to do the work you're given.What kills me is that the actual concept at 343i are genuinely great but by the time it ends up actualy in the games it's been corrupted into shit like Seeker. I'd really like to know what is going on behind the scenes that this happens.I think people are just afraid to speak up. Imagine roasting your lead artist after he worked 30 hours to make the Seeker helmet. It can be intimidating.That's not how it works. Most of the arnour is contracted to third party studios, not done in-house.Oh, they need to stop that or at least review them in early stages.They do it because hiring an additional large amount of character artists is unfeasible.Considering how 70%+ of the armor in H5 is shit, they can probably do it all internally.Quality > quantity.So I'm guessing you have no idea what an art pipeline looks like or how art works in games devThey have the tools and assets. 70% of armor is shit. Is 343i capable of producing 30% of H5s armor internally? They will reuse the assets for protagonists in H6. Art isn't exactly in high demand in later dev stages, just polish? So can they not make 15 / 20 good armors?
Thanks for the clarification. The asset re-use I mentioned is mainly Blue team and Osiris. I don't think they will change their look much. MC's suit was the template for him in H5. I also doubt 343 just asked a bunch of contractors to make armor without giving them some sketches or at least reviewing the third-party sketches and choosing the ones they liked best. But then again - 343 did release MCC in the state that it was in, so perhaps they don't do any monitoring / reviews and just push any old shit onto the release build?Unlikely that they will write a new engine for Halo 6, maybe just some extra beef for X1X? Loot boxes were definitely a big part in diluting the quality, forcing a quota on the art team but why rush things when you can just push content out post-release? Instead they gave us 30+ armors, but only 2 playlists and no forge.
you guys hear about the Halo Online update that's coming out today?YouTube
Microsoft just give us Halo 3 PC already.
Quote from: Boomdeyadah on April 22, 2018, 01:30:09 AMMicrosoft just give us Halo 3 PC already.Microsoft says NO: https://www.halowaypoint.com/en-us/news/eldewrito-community-content
Quote from: FatherlyNick on April 25, 2018, 03:36:01 AMQuote from: Boomdeyadah on April 22, 2018, 01:30:09 AMMicrosoft just give us Halo 3 PC already.Microsoft says NO: https://www.halowaypoint.com/en-us/news/eldewrito-community-contentI mean, they're acting pretty reasonable. They even say in the post that they've learnt there's a massive group of people who want a classic halo for PC and they want to work in the future to see what they can do with that. Hell, the general impression I've been given is that 343 is cool with the project and they're onpy doing this because they/ microsoft have to - it does breach the terms of use microsoft have had for years.Anyone who didn't expect this is a retard tbh