The design of the X-wing is such that a lot of the components are actually on top.Tavish McFini wrote:I really don't see how, if a laser cannon gets damaged the astromech is able to get it operational again just by tweaking something right behind the cockpit
If you pause the video at 0.48 seconds, you see R2 fixing a stablizer and you can see how exposed the components are. Note also that in a battle, its entirely possible that a shot is glancing enough to burn away part of the X-wing's panel and fry some wires, but not do much else - in which case the fix would be simple, youd simply connect the wires.
TIE's are very different in that you dont really have much capacity to fix them on the run. Partially its the nature of the design - extreme efficiency - as opposed to what the NR did, which was have fighters that could be fixed with anything and fixed fairly easily. The option of diagnosis and problem solving is much better and something R2 and even R5 units dont seem to do much. One thing i would mention though is that the port should have the capacity to eject the droids into space.jacenwesiri wrote:Realistically, inflight repairs would be limited, as the droid wouldn't really be able to reach much of the fighter itself, and even then, primarily external portions of it. What it could do is run diagnostics, and perhaps come up with workable solutions to keep the systems operating as damage is sustained. At a position like that, it's possible it could reach the drive system or perhaps the power supply, but I doubt much more than that. Still, the possibility of reaching the engines wouldn't necessarily mean the engines are laid out in such a way that the R8 unit could actually be the most effective with doing such things.
You can speak to it, or it can actually put messages on the screens in the fighter in text. Generally you want droidspeak though, because you dont want to learn about your droids feelings, you want things like range to target. Over the comms system - its pretty simple, the droid is plugged into the fighter - easy enough to plug it into the systems.jacenwesiri wrote:Anyways, as far as the wails and such, my understanding is that with the rebel fighters and such, they actually had the droid communicating with the pilot over the comms system, though how they do it is another thing altogether. So really, perhaps mounting it internally would allow some increased protection for the droid and an easier way of communicating back and forth between the droid and the pilot.
There are none. But, we do have cameras!jacenwesiri wrote:As for rear facing windows,
It is well established that pilots in fighters with astromechs, must do navigation training. They all hate it. Its tricky, its boring, and if you dont do it right your quite possibly dead. To quote Niles Crane, its 'difficult, yet boring'. Without an astromech, you still need to feed information into a navicomputer, and you need time. At the end of a battle, where pilots are fatigued, this can lead to avoidable catastrophies. We don't hear about it so much because the NR had astromechs and the Empire of course had ISDs with good systems and a large crew. Navicomputers will retain information such as star charts, gravity wells etc, but quite often you need to put a lot of info in yourself.jacenwesiri wrote: Now, on to the navicomputer. I think that a navicomputer does more than handle hyperspace jump calculations, and even if it just did, over relying upon the astromech would mean that the pilot would have to know how to do manual navigation, and so by leaving a basic form, you are in essence leaving a bare minimum functionality behind in case the astromech is lost. I think that on some level, the rebels did something like that too, where you can see in Empire Strikes Back, that Luke was doing navigation with going to Dagobah, rather than telling R2-D2 to take him to Dagobah. This would probably be something along those lines, though by necessity kept to a minimum so as to not take up too much mass or power.
My thinking that the next part of a navicomputer is that it would handle some navigation functions, though that could be included with the avionics. This would be functionality like keeping track of where things are in system, and one's position within the system to prevent getting lost or off course. For a fighter pilot, I'm thinking it would be useful to be able to track positions of a lot of things, and either this or the enhanced avionics package would do this better
Why have one? simple really - as a backup in case the droid goes down, and as well because its simple and cheap to integrate into your fighter. Its just a harder way to go about things.
I seriously doubt they take much mass or power though - this is partially because theres a lot of power in a fighter, and the main draws - engines, weapons and shields wont all be in use at the same time when you use the navicomputer.
Just my two cents!