The Director Change Couldn't Save Solo: A Star Wars Story

<img src="https://https://ift.tt/2kzU55o" /><p><p style="text-align: left;">Ron Howard did an admirable job getting <a href="https://ift.tt/2G8ZSHw A Star Wars Story</em></strong></a> across the finish line amidst its troubled production, but the last-minute director change wasn't enough to completely save the project. When Lucasfilm first officially announced the spinoff, Phil Lord &amp; Chris Miller were set to call the shots, riding high off the success of <a href="https://ift.tt/2wEULj3 LEGO Movie</em></a> and <a href="https://ift.tt/2sibVy2 Jump Street</em></a>. In one of the most bizarre developments in recent memory, the two were fired four months into production due to creative differences. Howard came on board just a couple days later, and he was asked to do much more than round out the last few weeks of filming. He oversaw extensive reshoots that encompassed <a href="https://ift.tt/2H1ybkf much as 80 percent of the movie</a>.</p></p><p><p style="text-align: left;">It goes without saying that <em>Solo</em> (probably more so than any other <em>Star Wars</em> film besides the original) was hell to complete, but was it ultimately worth all the trouble it went through? The answer to that question is more complex than one might think. From a certain point of view, Howard benefitted the spinoff - but that doesn't tell the entire story.</p></p> <strong>Click to continue reading <a href="https://ift.tt/2si55bP Director Change Couldn't Save Solo: A Star Wars Story</a></strong><br /><br /> <p>The post <a rel="nofollow" href="https://ift.tt/2si55bP Director Change Couldn't Save Solo: A Star Wars Story</a> appeared first on <a rel="nofollow" href="https://ift.tt/2KVjJNT>

from ScreenRant - Feed https://ift.tt/2H15STh
via IFTTT