Nuke

you need about 13 jupiter masses to sustain deuterium fusion and 65 jupiter masses to sustain lithium fusion. this would still just be a brown dwarf. http://en.wikipedia.org/wiki/Brown_dwarf you would need about 78.6 jupiter masses to have an actual star. http://en.wikipedia.org/wiki/Red_dwarf

any aircraft sent to titan or anywhere else with an atmosphere would be a milestone in robotic missions. you need to learn to fly before you can learn to fly awesome.

the aricle wants to send a big mothership and a small quad copter. i say instead just send a large drone and omit the mothership enirely.

i wouldn't even have a mothership. id just build one large quad copter with the rtg and everything else you need. the mix of low gravity and and high pressure means that you really dont need much power to stay airborn. not to mention the atmosphere is cold enough to use superconductors in the motor coils for even more power savings. also you are going to have a lot of cooling on your rtg so its power output would be higher than usual. i would also do a winged varient to allow for soaring to save power while operating transmitters and other instruments, sort of like this: or here is a better design: this one gives you some serious speed. so you could get coverage that would be impossible with a rover or even a dedicated quad copter.

i bet them cows were scared. i guess they are there for the victory bbq.

hydrogen doesn't fuse so well. thats why stars have to be pretty big to ignite. if six teratons of comet fragment impacts cant initiate fusion on jupiter, tsar bomba would not be able to scratch it.

you probibly just had a case of unseated parts. the "wiggle it" technique usually works here.

i dont think so. in the future programs are going to grow even more complex than they are now, and its very hard to discribe a complex system with diagrams. case in point, hardware description languages. in the olden days when you wanted to design a cpu or other digital device, you did it with schematics of the logic gates, which are themselves very intuitive. but as digital design become more intricate, schematics were no longer sufficiently intuitive. languages such as vhdl and verilog came into existence to define that hardware with code. initially for simulation, then for use in devices such as clpds and fpgas. they are also used to design new architectures. designing a modern cpu would be very difficult with schematics. there are some niches where it works though. robotics is a good one, you got things like ladder logic and robotos. where the control over the system need not be very granular. also for educational purposes, like what the op wants. i remember programming my lego smart bricks was always fun (though these days i use nqc/nxc).

tell them they can play the free version of minecraft for the pi. then tell them they have to instal it themselves. they can learn them some linux.

i had a joke about a star trek breaking bad crossover, but it would violate forum rules.

damn, i thought this was about motorcycles so is there an error message or is it just dead?

they also hide screws under labels sometimes. if you cant find any then its either a snap together thing, or worse, they used ultrasonic welding. ive never encountered either in a mouse but it wouldn't surprise me. its like manufacturers dont want us to fix stuff anymore.

also this is relevant: http://www.artificial-gravity.com/sw/SpinCalc/

i dont think america could have attacked germany over the atlantic. the only way we were able to bring our bombers into germany was because we had england to base from. had that not been the case it would have been very hard for us to do bombing raids on germany. also without support from the british navy, it would have been all but impossible to pull off d-day, or even get warships (of any kind) anywhere near axis territory. i do admit that the germans would have better luck invading the usa, though i dont think it would be very successful. if the uboats needed to be used defensively they could have, the atlantic was swarming with them, bunched up near germany (and sans the british navy), they could have butchered any assault. i think that after securing europe, the nazis would try to distance themselves from the fighting with the usa directly, and would instead fill a support role and let japan take its pacific empire. nuclear weapons might bring the war to a diplomatic ending with the usa mostly intact, a german controlled europe and a japanese controlled asia. needless to say the subsequent cold war would be rather interesting. then again if german production survives mostly intact we might see jet aircraft and rockets playing a bigger role in the war, possibly giving germany the capability to launch air strikes across the atlantic (and possibly intercept nuclear armed aircraft as well). in that case, the usa would probibly be consumed by the nazis and japan. then both would begin annexing countries one after another until they have no one to fight but eachother.

if the nazis would have succeeded in a conquest of europe, uk and russia, they would have been unable to attack the usa directly across the atlantic because they didnt have much in terms of carriers or long range bombers. likewise the german uboats would have made a naval assault on germany impossible. they would instead have to support japan's war efforts (with production and soldiers) at first. with german support, the japanese would have been able to take territory in the pacific (and possibly the west coast) and hold it. this would buy them some time to progress their rocketry and jet aircraft programs to the point where an atlantic front would be possible. we would likely have nuclear weapons ready at that point to defend ourselves and possibly force a diplomatic solution. of course eventually germany would gain our nuclear secrets the way the russians did, and since they had a leg up on rocketry, america would be cratered.

no thats a myth as far as i can tell. i fill with hot water, not for any reason other than when i hold the tray with my right hand, the left hand turns the knob, and the hot knob is on the left side. i figure people in a similar predicament use all kinds of excuses to cover their blatant waste of energy (why heat water just to cool it down again).

they like to hide screws under those sticky pads that the mouse slides around on. though i have a couple high end mice that were designed im sure to be very hard to fix. like my logitech mx5000 (i think thats what it was, the label is all worn out and unreadable) laser mouse. it has 2 pcbs sandwiched together on headers soldered at both ends. this makes it impossible to access the solder pads where the switches are soldered (not to mention two of the screws that let you remove the pcb, i drilled those out from the other side). i built a makeshift jack out of parts i had laying around and put enough flex on the board to get my iron in there. i also changed the lithium cell for one that held a better charge. mouse works fine now. cheap mice are a lot easier to fix.

its easy: get old. i dont want anything you can afford to get me. i dont need to eat any more cake. dont remind me that im old. get off my lawn.

decals would be pretty cheap and can look realistic with normal mapping. it would be nice if they were persistent but i dont think that would be a good idea. you could probibly make them semi-persistent, for example they exist so long as the part that created it exists, and only a max of x amount per part. go over that and older track is deleted.

things evaporate better if they are a little warm.

ksp does have shaders.

for me they are, and often the middle mouse button is what gets sacrificed in the name of a functional mouse. unless you have spares.

middle button failures are rare. its usually the left one that dies first. my fix is to take the mouse apart and (assuming the switches are the same type) and swap middle for left with my soldering iron. this wont work for you though. but fairly recently somone dropped a box of old ball mice on my doorstop and they have been an invaluable source of parts (and rubberized metal balls that the cats like).

you said it cost $2000. i assume the other $1000 was parts. most of my builds are a few hundred below that. my i7 build cost a little under $800. i probibly put less than 4 hours work into design and build, and when i was building machines professionally back in 2002, i didnt get paid very much per hour. simple fact that you have much wider profit margins at the high end.

i dont think building a computer is a one grand job. ive built several and never got paid that much.