Why couldn't Darth Vader detect Obi-Wan Kenobi and Yoda while they were in hiding?


https://qph.fs.quoracdn.net/main-qimg-1cef5bf406035d458b820b7b1e2feeab

https://qph.fs.quoracdn.net/main-qimg-e631782ba8080c15efe5ac0fb65754c4

reply

In the case of Yoda, might have something to do with Dagobah itself, which had "massive life readings", according to Luke, when he crash landed there. Maybe one small jedi master could hide there undetected.

reply

Vader would never go to Tatooine. It's full of sand and he doesn't like sand. It's coarse and rough and irritating and it gets everywhere.

reply

It’s where little Anakin grew up. There are a lot of things in the Star Wars series that you are better off not thinking about. On the top of the list is: we are going to hide the kid from Darth Vader with his uncle and aunt right where Darth Vader was raised.
Anakin never popped in to see if they had any idea where his son might be?

reply

To be fair, at the end of Revenge of the Sith, Palpatine said Padme was dead, which would likely lead to Vader thinking the kid was dead too. Remember, he did 't even realize Padme gave birth to twins until Return of the Jedi. Sometime between A New Hope and Empire Strikes Back, he learned his son was alive and that it was Luke (now, that one is a mystery).

It also doesn't help that he considered Anakin Skywalker to be dead and that the "name no longer had any meaning to [him]". It's unlikely he would go off looking for the Son of Skywalker, even if he knew he was alive. It wasn't until he met Luke that he had any notion of trying to reach out to him. And even then, he almost let Palpatine kill him.

reply

You know the movies a lot better than I do. I’m a casual fan and don’t remember all those details.

reply

I've been watching the OT since longer than I've known how to read. There are still a lot of things that don't add up, but I can see how Vader might not immediately start looking for a kid that he probably believes is dead anyway.

reply

Sometime between A New Hope and Empire Strikes Back, he learned his son was alive and that it was Luke (now, that one is a mystery).

Not true. He learns Luke is his son half way through ESB, there's a scene literally showing us this:-
https://youtu.be/3xpJhtfF9pk?t=0m53s

reply

That scene is from the special edition. Vader originally had a different conversation and the Emperor was played by a different person (an old woman with a man dubbing her, in fact).

reply

Don't take this the wrong way but most people only have access to the Special Edition since Lucas refused to release the original versions in good format (the DVD releases are in fullscreen) so most only watch the special edition.

reply

Wow - that's very interesting, thanks!

I knew about the old woman original version and putting Ian McDiarmid in there was a revision. However, I never appreciated that the dialogue had been slightly altered as well in that scene:-
https://youtu.be/rKtciRCVpFE

That change of dialogue is actually more important than the SE actor meddling because it does remove that reveal being explicitly made there and then by the Emperor. Vader takes it all onboard very lightly in this version so yeah there is the implication he was already aware, although that not being stated between the pair of them is a bit odd...

reply

After watching that original version, it's still about the same minus the "Are you sure?" line. The original version still had Darth Vader declaring, "I am your father!" to Luke so, yeah. For audiences in 1980 it was to hide the reveal that Darth Vader was actually Luke's father Anakin but he still found out from the emperor that Luke is his son in that scene. Also just to clarify the original Special Edition Trilogy from the late 90s had those exact same scenes. It's only when released on DVD they made the change with the emperor in Empire Strikes Back and also added in Hayden Christianson into Return of the Jedi. I'd personally prefer to just have the original Special Edition that kept those scenes intact and unedited.

reply

https://www.youtube.com/watch?v=rKtciRCVpFE&ab_channel=mielr

Eh, I never got that impression from this scene.

reply

I think you misunderstood what I meant. The scene makes it seem that what Obi Wan said in the previous movie about Anakin being killed by Darth Vader was true and that Darth Vader is wanting to turn Anakin's son to the darkside or kill him if he refuses. But, originally in 1980 people didn't know about the later scene where Darth Vader declares to Luke he's his father. So therefore, he knew Luke is his son in that scene with the Emperor. It was just intentional misleading the audience to hide the twist of Vader being Luke's father Anakin. So yeah. Vader finds out Luke is his son halfway through the film as that other poster said.

reply

Ah, okay. I misunderstood.

reply

It's a compilation of the little things: Luke knows Obi-Wan. He has Force abilities. He shows up with the R2 and 3PO, who were last seen over Tattooine. His name is Skywalker (is the name so common that a lot of other people have it? Why don't we hear about them?). Those little clues add up. They're probably what caused Palpatine to figure it out. Vader believed Padme's baby to have died with her, so he wasn't expecting Luke to be his son, but how does he not wonder if they're related in some way?

reply

Well he actually had a home on that Volcano planet, where his arms and legs were hacked off and his dick was burned away by the lava. He didn't let hating a place stop him, but I assume Tattooine was too insignificant for him to bother with.

So there are two explanations for his original question: Either Yoda and Obi-Wan could block his senses if they wanted to, or they had to be fairly close for that sense to kick in. Probably the latter, considering "ANH".

reply

Yes, the serious reply would be that the scene in the hanger of the Death Star with the Millennium Falcon implies that there has to be a proximity for Vader to sense Obi-Wan's presence. And that sensing his presence across the galaxy was not a thing.

reply

Force Skype hadn't been invented yet.

reply

In fact why couldn't he sense every move the rebels were making?

reply

If we accept the explanation that a person has to be nearby for Vader to sense them... well Vader didn't know where the Rebels were.

reply

He was pretty quickly sure where the rebels were in The Empire Strikes Back after they received the probe message from Hoth...

reply

Well, he had actual data to go on that time. He didn't need to rely on the Force, which failed to locate either Rebel base for him. And he'd tried, and so had Palpatine, I'm sure of that.

reply

Even Palpatine couldn't sense Yoda until he was in his office in Episode III maybe Yoda's species are unique. As for Obi-wan really doubt Vader even thought of going near Tatooine he hates the place.

reply

Shhhhh!

reply

I said this in a similar thread in the New Hope boards, but basically ... Vader's Force "clairvoyance" is evidently crap. He couldn't find the Death Star plans; he couldn't find find the Rebels; he didn't know Leia was his daughter despite spending all that time with her in ANH, and possibly time before that for government stuff...

Anakin never seemed to care about those aspects of the Force in the Prequels tbf

reply

Plot hole

reply