Waiting for The Hobbit 3 info? Well, it doesn't exist yet

Aug 01 // Nick Valdez    @Valdezology

With all of the drama surrounding Peter Jackson's newly confirmed Hobbit trilogy, it does not help matters when there's bad news about the production of the three films. When we assumed that Jackson and Warner Bros. had everything worked out, it turns out that there is no allocated budget or completed script for the final film. 

According to a source at THR, there "was such a short window of time to make this decision, if anybody had said no, it would have been two movies.” Assuming this is correct, Warner Bros. opted to put faith in Jackson to make an acceptable third film without knowing how much it will cost them in the long run, or if it's even plausible. The script for the third film is still in development, so that means Jackson would have to pull a feat of Lucasian proportion in order to fit its production within the other two films in this trilogy. 

So because Warner Bros. wanted to make a third film with a non-existent premise, we're probably getting one really good film, one okay one, and one that shouldn't exist. Sorry folks. But there's some good news though. You see the header image above? That's how the 3D glasses for The Hobbit will look. 


[THR, via Collider]  


Nick Valdez // News Editor
 Follow Blog + disclosure Valdezology Tips
Nick Valdez likes chick flicks, dick flicks, kid flicks, and skin flicks. Someone also let him be News Editor here.  full profile | More staff profiles

Get more Flixist:   We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out

Get comment replies by email.     settings

Unsavory comments? Please report harassment, spam, and hate speech to our comment moderators

Can't see comments? Anti-virus apps like Avast or some browser extensions can cause this. Easy fix: Add   [*].disqus.com   to your security software's whitelist.



Back to Top