Jump to content

AeroEngy

Members
  • Posts

    78
  • Joined

  • Last visited

Reputation

18 Good

Profile Information

  • About me
    Rocketry Enthusiast
  1. Thanks for the information. I'm sure I'll have more questions as I get back into this mod. I haven't played KSP for over a year so lots of new things to get back into. What??? No such thing as too much power! Actually I was messing around and put 2x antimatter reactors / thermal turbojets on a MK2 plane. It was ~10g at full throttle in atmospheric mode off the runway and I killed Jeb pretty quick. I had a hard time keeping the throttle low enough for it to be controllable ... might have been a tad of overkill. Thanks again.
  2. I wasn't to worried about waste heat in this test. I was just trying to get a feel for the performance level of the quantum vacuum mode. I just needed it to not shut down for < 1 minute. I was mainly curious if this very low thrust level is typical in quantum vac mode? Why max throttle power is only ~500MW when the reactor/generator combo can produce up to 3.9GW.... what is limiting the power output to the thruster?
  3. I have been away from this mod for a long time but thought I would give it a go in sandbox and test out some stuff. I seem to be having a problem with plasma thruster operating in quantum vacuum mode ... or am not understanding something. My test vehicle has a 1.25m antimatter reactor, charged particle gen, & a plasma thruster in quantum vac mode. Reactor Stats: Charged Power 586MW / 4.5GW (Why isn't it generating more?) Generator Stats: Current Power 507MW of 3.89GW Thrust: 0.8kN with max throttle power: 507MW (Is this all that the thruster can do? Is it limited in the power it can output?) I kind of assumed I would get more thrust out of it since the wiki states this: I am certainly not seeing the same performance as liquid fuel ... so whats going on exactly. Thanks for any information.
  4. Check out this guys website. It shows a decent amount of detail in his design, construction, and testing of an 8-stage coil gun.
  5. The reason they are there is mostly to give some padding in the timeline and to target an exact launch window. So they do a bunch of checks, preps, and fueling that might take a variable amount of time if someone is slow to do a step or some other complication pops-up. This is all done as part of the initial count and it is possible to fall behind due to random complications etc. Then they hit the planned hold time which can be extended or shortened. This allows them to catch back up if necessary and pick the count back up so that T-0 hits on the exact time they need to launch to hit their window ... or rendezvous with the ISS or whatever. So it is basically just some padding in the schedule. IT could be done without a planned hold put the launch procedure would just need to have a little bit of padding here and there instead of one longer hold/ time pad.
  6. I made this awhile ago for KSPI for people to get an idea of how to use warp without using tons of fuel to to match velocities. Basic steps are match velocity direction, then magnitude and then jump to target. 1) Warp close to Kerbol and wait for craft velocity to be parallel to your target. 2) Warp so you are falling directly toward Kerbol. Wait until your V is the same magnitude as target. If you target is an outer planet then reverse the warp point so you are flying directly away from Kerbol. 3) Warp to target body with your V matched in direction and magnitude.
  7. It could be the antimatter tanks. They require a bit of EC to keep containment and if you have no other source of power they could drain your batteries. It has been awhile since I sent mine up ... but I believe you can disable/turn off the tanks in the VAB. Then they won't start using EC until you re-enable them. I just left mine disabled until the were connected to my station which has a fusion power source.
  8. These are kerbals we're talking about ... they are always careful. Plus Jeb said it was fine to drop 2 big antimatter tanks from orbit what could go wrong?
  9. KAS definitely works with antimatter. It is what I use on the ground to fill up on the pad/runway. Here is how I did it:
  10. I had the same problem. Running fuel lines from the helium cryo tanks to the telescope fixed it for me. I had no decouplers or docking ports in between so it seemed like the helium just doesn't follow the same flow rules as everything else.
  11. Thanks for the info. I have that toolbox at work but not on my home version. However, there is a way to access TCPIP via Matlab's Java framework that I might try to see if I can implemenet. Here is a Mathwork's file exchange submission similiar to what I am talking about. There is probably some extra overhead this way but it might work. http://www.mathworks.com/matlabcentral/fileexchange/24524-tcpip-communications-in-matlab
  12. Does this use the Communications toolbox in Matlab to get the TCPIP data or does it uses something else like Java to access TCPIP? I didn't think you could do that in the vanilla version of Matlab. Any other Matlab version / toolbox requirements? I can't download it to take a look right now but this looks pretty interesting since I spend 90% of may day job in Matlab working on real rocket data.
  13. It could be done and controlled reasonably well ... with some compromises. I think the camera control would be a the hardest part. However, I don't really mess with the camera position that often once I get it where I like it. WASDQE = Left stick + L1, R1 throttle control = L2, R2 SAS+ RCS = X,B Staging = A menu = Start button Camera = Right Stick (Zooming might be an issue) external/IVA = Depress Right Stick time warp = D-Pad left/right action keys = Selection wheel on D-Pad down. HNIJKL = Use Y or menu to toggle translation control. Then left stick + R1, R2 normal/docking/map = D-Pad Up switch between celestial bodies/vessels = menu or alter keys when in map view(x,y bodies &a,b vessels)
  14. Here it is in diagram form. However, I usually match direction then speed. Where his explanation was speed then direction. 1) Warp close and wait for craft velocity to be parallel to your target. 2) Warp so you are falling directly toward Kerbol. Wait until your V is the same magnitude as target. If you target is an outer planet then reverse the warp point so you are flying directly away from Kerbol. 3) Warp to target with your V matched in direction and magnitude.
  15. I would love the ability to integrate Fractal's resource scanners with something like the old ISA MapSat or the newer SCANsat terrain mapping plugin. http://forum.kerbalspaceprogram.com/threads/55832-PLUGIN-PARTS-0-23-SCANsat-terrain-mapping You could send probe(s) to a body with Fractal's scanners, let them orbit in high inclination for awhile and then create an actual full surface map of each resource. It would be much more similar to how an actual space agency would do it.
×
×
  • Create New...