Tuesday, March 13, 2018

'Deadpool 2' Test Screenings Went Poorly? Not So Fast

It's time to put maximum effort into "Deadpool 2" rumor busting.

The Internet has been passing around rumors that initial test screenings did not go well, prompting reshoots to fix the problems. Some of the reports are coming from people who weren't there and haven't seen the movie, they just heard it tested "really poorly" and the producers were "stunned" with the audience's reaction. Without having been there, it's hard to be sure of what's true and false. It's true that the film is undergoing reshoots (as confirmed by Josh Brolin), but that's true of almost all major movies, and doesn't carry a negative connotation on its own.

So -- and maybe it's just wishful thinking -- we're leaning toward Collider's source report saying testing went well and the reshoots are focused on adding more of Domino (Zazie Beetz) and Cable (Josh Brolin).

Here's the story from Collider:

"We're hearing that the first Deadpool 2 test screening was in January, when the film tested around 90 or 91 out of 100. The studio then had another test screening after more editing had been completed, at which point the film tested in the high 90s. However, while both test screenings went well, our sources tell us that crowds in both screenings had the same 'complaint': They wanted to see more of both Zazie Beetz' character Domino and Josh Brolin's character Cable."

From that angle, the reshoots were a positive response to how much fans liked two new characters and wanted even more from them.

If you're Zazie Beetz or Josh Brolin, that has to feel good. (Zazie Beetz reportedly has a three picture deal with 20th Century Fox, so hopefully fans continue to love Domino.)

The "truth" about the movie's merits will be subjective, as it is for all movies, but we won't have to wait too long to see the final product. "Deadpool 2" opens in theaters May 18th.

Want more stuff like this? Like us on Facebook.




from Moviefone News RSS Feed - Moviefone.com http://ift.tt/2tNdRSo
via IFTTT

No comments:

Post a Comment