Search the Community

Introducing... (Source code is included in the download) License: Code and Configs are licensed under the GPL v3 license. Author: TheShaddow1138 Tester(s): @Puggonaut Here's a spacedock by @StinkyAce that @Puggonaut has been featuring in his videos: https://spacedock.info/mod/1815/USS Nimitz and Drydock A scaleFactor of 0.6 makes the best fit for the NX. A compatibility config is included that creates a copy of the drydock and modifies the included resources to include the resources needed by the NX. StinkyAce's mod must be installed for this config to work. Dependencies: (bundled with the Spacedock download) ModuleManager 4.1.4 B9PartSwitch Community Resource Pack Waterfall Small Trailer for TrekDrive made by Puggonaut This fantastic video was made by @Puggonaut, and you should definitely give it a watch. Change Log: v1.0.3b - Log Spam Hotfix * Updated TrekDrive.dll to remove spamming the debug log with the number of warp coils that are charged. v1.0.3a - Warp Drive Hotfix * Updated TrekDrive.dll * Updated the CheckStatus function to check if the minimum number of nacelles have been charged instead of all nacelles on the ship. Fixes an issue where embarked warp-capable shuttles prevents the mothership from going to warp. * Updated the warp coil code so that coils that are not charged will not try to drain themselves and prevent the ship from going to warp if the minimum number of nacelles are in fact charged. v1.0.3 - The Galileo Seven * Added Type F Shuttlecraft (all parts have two texture variants) * Main Hull (crew capacity of 7) * Impulse Engine * Warp Core * Type F Warp Nacelles (Port & Starboard) * Added warpEffectParent.mu (an empty transform model) This model is in "TrekDrive/Generic" along with usage instructions * Added a WaterfallFX template for the TrekDrive warp stars effect to make it easier for others to add the effect to non-TrekDrive parts. * Added Mirror Universe texture variants and registry/name variants for the Type F Shuttlecraft. * Updated all parts with the SW_ModuleWarpGenertor module to have a warpEffectParent transform to standardize the transform to which the warp stars effect is parented. (Doesn't affect anything, all effects are intact and the same as before.) * Updated all parts with RCS thrusters to use LqdDeuterium, removing MonoPropellant entirely from the parts. To maintain propellant consumption rates all RCS thrusters' ISP were increased by a factor of 25. * Updated surface attach node on NX-class warp nacelles allowing for sane surface attachment. * Updated TrekDrive.dll to apply forward and reverse impulse thrust per-part instead of to the vessel as a whole (thrust vectoring still works). v.1.0.2 - The Original Reborn * Added Constitution-class Starship (all parts have two texture variants) * Bridge Module (crew capacity of 6) * Saucer (crew capacity of 30) * Impulse Engines (includes a docking port) * Engineering Hull (crew capacity of 20) * Navigational Deflector * Nacelle Pylons (two variants: flared and straight) * Warp Nacelles (Port and Starboard) * Starship Registry Variants (present on Saucer, Engineering Hull, and Nacelles [port & starboard] * USS Bonhomme Richard (NCC-1731) * USS Cassie (NCC-1711) * USS Constellation (NCC-1017) * USS Constitution (NCC-1021) * USS Defiant (NCC-1764) * USS Eagle (NCC-956) * USS Emden (NCC-1856) * USS Endeavour (NCC-1895) * USS Enterprise (NCC-1701) - The Default * USS Essex (NCC-1709) * USS Excalibur (NCC-1664) * USS Exeter (NCC-1672) * USS Hood (NCC-1703) * USS Hornet (NCC-1708) * USS Intrepid (NCC-1631) * USS Kearsarge (NCC-1733) * USS Lexington (NCC-1709) * USS Porthos (NCC-1712) * USS Potemkin (NCC-1657) * USS Ticonderoga (NCC-1714) * USS Yamato (NCC-1716) * USS Yorktown (NCC-1717) * Added two (2) new registries for the NX-class and NX-class * Cassie (NX-11) * S.S. Cassie (NX-11) * Porthos (NX-12) * S.S. Porthos (NX-12) * Added Mirror Universe Kerbban Empire Content in "Extras" (content is encapsulated and may be easily removed by deleting either the "Extras" folder, or the "MirrorUniverse" folder inside "Extras") * Kerbban Empire Texture Variants to the following parts * NX-class Saucer * NX-class Engineering Section Refit * NX-class Warp Nacelle Refit (Warp 7 Nacelles) Port and Starboard * Enterprise-era Shuttlepod fuselage * Constitution-class Saucer * Constitution-class Engineering Section * Constitution-class Warp Nacelles Port and Starboard * Kerbban Empire Registry variants for all currently available registry variants on the NX-class and Constitution-class ships * Flag of the Kerbban Empire * Added Textures Unlimited patch - authored by Puggonaut with "excludeMesh" statements provided by TheShadow1138 so that registries appear correctly with this config. v1.0.1 - Thrust Vectoring * Updated plugin to add thrust vectoring to impulse engines. Thrust vectoring is toggleable in the PAW and by Action Group * Added a new parameter to impulse engine CFGs, "maxVectorAngle" a value in degrees to control the amount of vectoring. Default value is 15º. v1.0 - Initial Full Release * Includes: * Phoenix Warpship * Phoenix Warpship launcher * Enterprise-era Shuttlepod (can be docked in the aft bays of the NX) * NX-class starship (has two aft shuttle bays for the shuttlepod) * Added A User's Manual * Added NX-class Bridge IVA and Props * Updated warp stars configs so that they are visible in the Bridge IVA * Updated the plugin to add an ambient rumble sound for the warp core. The sound is customizable by simply editing the CFGs with SW_ModuleWarpCore to give the path to your desired sound. * Added ENT-era Shuttlepod IVA (Stock and MAS versions) * Updated Shuttlepod Impulse engines to have a hover altitude of 1000m * Added ModuleLiftingBody to the Shuttlepod fuselage improving flight characteristics * Balanced the RCS and COM of the Shuttlepod removing most if not all unwanted movement during docking or other maneuvers. * Updated SW_ModuleImpulseEngine to apply Takeoff/Landing forces to every part to provide even acceleration to the entire vessel almost entirely removing the need for RCS or SAS to keep the vessel level during takeoff/landing in atmosphere. Below are the previous WIP Change Logs: v0.99.1w - Spacedock * Added a ModuleManager patch for StinkyAce's Spacedock, available at this link: https://spacedock.info/mod/1815/USS Nimitz and Drydock The patch scales the dock down to 0.6, a near perfect fit for the NX-class, and instead of modifying the drydock that comes with StinkyAce's mod, it creates a new part with the aforementioned scale, an impulse engine (no part, just the module), and produces the resources used by TrekDrive ships. This will be a good refueling station for the NX. * Updated the plugin * Fixed an NRE spam in the impulse engine code while in the editor * Added the ability to select a "forward" or "reverse" mode for the impulse engines. Toggleable in the PAW, and can be set as an action group. * Cleaned up the Waterfall patch by splitting the warp effects into their own patch. * Tweaked the texture tiling on the NX warp effects (both the Warp 5 and Warp 7 versions). v0.99w - NX-class Release * B9PartSwitch is now a hard dependency. (Included in download) * Updated the TrekDrive.dll * Warp speed formula changed to allow faster interstellar travel * OnLoad function updated to not automatically set the warp drive to "Not Ready" if it was in a "Ready" state at the last save. This allows the player to immediately engage the drive after the vessel loads, if the drive is in a Ready state upon loading. * Added NX-class Starship Parts * Bridge module (Crew capacity of 6) * Saucer section (Crew capacity of 20) * Engineering section * Nacelle Pylons (B9PartSwitch variants) * Upper variant (2 upper pylons) * Lower variant (2 lower pylons) * Four variant (2 upper & 2 lower pylons) * Warp Nacelles (Port & Stbd) * Main Impulse Engines (Port & Stbd) * Secondary Impulse Engines (Port & Stbd) * Navigational Deflector (2 variants) - Serves as a transmitter * NX-01 Oval "Mark I" Deflector * NX-02 Rectangular "Mark II" Deflector * Added NX-class Refit Starship Parts * Engineering Section Refit (Includes warp 7 warp core and warp drive, Crew capacity of 10) * Refit Warp Nacelles (Port & Stbd) * Added Custom Waterfall FX model and texture for streaking stars at warp effect. * Updated the warp stars effect on the Phoenix * Added six (6) craft files for the NX-class and NX-class Refit * NXClass_A: Standard NX-class starship (as seen in Star Trek: Enterprise) * NXClass_B: NX-class starship with two (2) ventrally (lower) mounted nacelles * NXClass_C: NX-class with four (4) nacelles * NXClass_Refit_A: Standard NX-class starship Refit * NXClass_Refit_B: NX-class Refit with two (2) ventrally (lower) mounted nacelles * NXClass_Refit_C: NX-class Refit with four (4) nacelles v0.9w - Shuttlepod & Impulse Engine Release * Updated the TrekDrive.dll * All TrekDrive buttons/toggles can now be set as Action Groups * SW_ModuleImpulseEngine Added - automatic takeoff and landing modes when sub-orbital, it will not automatically land from orbit. * SW_ModuleBussardCollector Added - When the collector is activated it will collect at a random rate for a random period of time before choosing another random rate and period of time. Collects LqdDeuterium and Antimatter with LqdDeuterium collecting at a higher rate. Collection will only occur at sub-light velocities. * Updated Waterfall version. * Updated Waterfall effect on the Phoenix Launcher Main Engine to correct a position issue. * Added a Waterfall effect to the Phoenix - visible when traveling at warp; the effect is based on the streaking stars warp effect from TNG - VOY and ENT. * Added Enterprise-era Shuttlepod * Shuttlepod main body - holds 5 kerbals with airlocks on both sides (No IVA) * Shuttlepod Impulse Engine v0.7.5w - OnLoad Hotfix: * Corrected an issue that prevented engaging the warp drive after switching to another vessel, after reloading the game, or any other loading action. Upon switching back to the warp ship, or loading the save, the warp drive will be automatically disengaged and set to "Not Ready" status. Simply clicking "Check Ready Status" and then engaging the warp drive will get you ready to go. Thanks to @Tanner Rawlings for finding this issue and bringing it to my attention. v0.7w - Phoenix IVA release: * Added Phoenix IVA (Stock and MOARdV's Avionics System) * The MAS version replaces some of the central props with MAS props, and replaces the Main Display with a functional MFD * MAS version of the IVA will only be available with MAS is installed. v0.6w - Phoenix Initial release: -------------------------------- * Updated Code: * Added nacelle glow animation capability, giving a visual indicator of coil charge. * Fixed coil charge logic to allow charging a partially discharged coil * Fixed a logic issue with the Warp Field Generator code. Now the "not enough charge" warning will only occur if the warp drive is active. * Moved to LqdDeuterium and Antimatter from Community Resource Pack * Added Phoenix Parts: * Phoenix Crew Cabin (no IVA currently, built-in RCS, no effects yet) * Phoenix SAS (contains Monopropellant and Electric Charge) * Phoenix Fuselage (contains LqdDeuterium and Antimatter) * Phoenix Nacelle (deployable warp nacelle) * Phoenix Warp Core/Warp Field Generator * Phoenix Main Thruster (matter-antimatter rocket engine) * Phoenix Vernier Thruster (matter-antimatter rocket engine) * Phoenix Fairing (to conceal the warp nacelles during launch) * Phoenix Interstage Decoupler * Phoenix Launcher First Stage * Phoenix Launcher Main Engine (Liquid Fuel Oxidizer engine) * Added Phoenix Warp Ship Test craft. * Added Community Resource Pack and Waterfall as hard dependencies (bundled) Inspired by RoverDude's Standalone Alcubierre Warp Drive, this warp drive aspires to operate in a Star Trek-like manner requiring at least two types of parts to operate: warp coils/nacelles and the heart of the drive, the warp core and warp field generator. I have seen in other threads here where people were trying to figure out how to require the use of warp nacelles to get that Star Trek feel to their KSP warp drives, and that's what I set out to do with this, my first plugin mod. Maybe a bit ambitious, but I think it turned out well. Now, on to the details. Technical Aspects: The plugin includes three Part Modules: SW_ModuleWarpCoil, SW_ModuleWarpCore, and SW_ModuleWarpGenerator. SW_ModuleWarpCoil: This module would typically be attached to a warp nacelle part, but could be added to any part for a design that perhaps doesn't use a nacelle, or similar structure. Requires: Warp plasma, which is generated by a warp core part using SW_ModuleWarpCore. Restrictions: Cannot be added to the same part as the SW_ModuleWarpGenerator. This is the restriction that requires at least two types of parts. Example Config: MODULE { name = SW_ModuleWarpCoil warpPlasmaConsumed = 5 // Amount of warp plasma consumed per second during charging and operation warpPlasmaNeeded = 250 // Amount of warp plasma needed to fully charge the warp coil cutoffThreshold = 2.000 // When the charge percentage drops below this percentage, the coil and drive cut off (1 - 100) coilEfficiency = 0.01 // Thermal efficiency of the coil (0 - 1) maxWarp = 2 // Maximum warp factor this coil can safely achieve } SW_ModuleWarpCore: A simple generator module that takes in deuterium (matter) and anti-deuterium (antimatter) to generate warp plasma and electric charge. (Could be replaced with a stock ModuleGenerator I suppose, but it's included all the same). Requires: Deuterium and Anti-Deuterium. Restrictions: None hardcoded. Example Config: MODULE { name = SW_ModuleWarpCore minAntimatter = 0.05 // Minimum amount of anti-deuterium required to operate minMatter = 0.05 // Minimum amount of deuterium required to operate warpPlasmaProdRate = 10 // Amount of warp plasma generated per second ecProdRate = 100 // Amount of electric charge generated per second } SW_ModuleWarpGenerator: The heart of the warp drive that actually moves the ship at warp speeds. Just like RoverDude's Standalone Alcubierre Warp Drive, the drive uses translation, not acceleration, to move the ship through space. Also, like RoverDude's drive, I used a slightly modified version of his gravity braking code (RoverDude's source code including the GravityBrakes() function) so that ships will slow down when they near gravitational bodies. Requires: At least one part implementing SW_ModuleWarpCoil that cannot be the same part implementing SW_ModuleWarpGenerator. This is what forces the requirement of multiple parts. Restrictions: All warp coils must be charged before the drive can be activated, and enough electric charge to run the drive is also necessary. If either of these is not true the drive cannot activate, or will automatically disengage. Example Config: MODULE { name = SW_ModuleWarpGenerator maxWarp = 2 // Maximum warp factor this drive can attain minNacelles = 2 // Minimum number of nacelles required by the drive to operate (must be at least 1) electricityReq = 50.000 // Amount of electric charge that is required per second of warp operation } NOTE: Some part on the vessel should have a container for warp plasma. In the included test parts the nacelles have their own warp plasma containers, but it can be on any part of the vessel. Warp Speed: The ship's warp velocity is computed using a simple cubic function, which was used for the original series and in Star Trek: Enterprise. So, velocity = (warp factor^3) * c In my initial testing, I find that Warp 2 is a good speed for traveling to the edge of the Kerbol System in a comfortable amount of time. I haven't tested higher warp factors, but will install appropriate mods on my end to further test travel times with increasing warp factors before final release. How to Use: I have kept the operation of the drive entirely within the Part Action Windows (PAW) of each part. Follow these steps to activate the drive. All of these actions can be set as Action Groups to somewhat simplify the process. Step 1: Activate the Warp Core by clicking the "Warp Core Status" toggle. Step 2: Charge the Warp Coil(s) by clicking "Charge Warp Coils" in the coil PAW Step 3: Once the coils are charged click "Check Ready Status" on the Warp Generator (combined with the Warp Core Test Article here). The drive will not enter the "Ready" status until all the coils are charged, and will not do so if there are any other active Warp Generators. Step 4: Once the "Ready Status" reads "Ready", click "Engage Warp Drive" on the Warp Generator. This will change from "Drive Inactive" to "Drive Engaged" Once the drive is engaged, any throttle input will move the ship at warp speeds. To return to non-warp operation, simply click the "Engage Warp Drive" toggle in the PAW to disengage the drive, or use an Action Group. Current warp factor is determined as a percentage of the drive's maximum warp rating, based on the amount of throttle: 50% throttle is half of the maximum warp, 100% throttle is maximum warp. E.g. for a drive with a maximum warp of 2, 50% throttle will be Warp 1, and 100% throttle will be Warp 2. The warp factor can also be selected using a slider in the PAW. The slider moves in 0.25 increments from Warp 0.25 to the maximum warp of the drive. The slider defaults to Warp 1. Increasing the slider scales the throttle so that your warp speed does not increase until you manually increase the throttle. The current warp factor is displayed in the Warp Generator's PAW Step 5: Once you have reached your target destination simply throttle to 0%, or use "x" to cut the throttle. There is an "Orbit Mode" option in the Warp Generator PAW that defaults to "Easy", this places the vessel in as close to a circular orbit as possible when the throttle hits 0 after having been non-zero. That is, it doesn't continually change the orbit while the drive is active, only if it had been moving the ship and then stopped. If the Orbit Mode is toggled to "Realistic", it will simply use the vessel's velocity vector to determine the current orbit, in the same manner as RoverDude's Alcubierre drive. Limitations: I tried to implement some limitations to make the drive less "cheaty". I took cues from Star Trek, particularly Star Trek: Enterprise, which dealt repeatedly with the limitations of the ship's warp drive. In the show, most problems occurred with the plasma injectors, but I though trying to code some kind of simulation of the injectors would be cumbersome and place unnecessary computational overhead. Other limitations that come to mind are the stability of the warp field, and the warp coil temperature. I opted for warp coil temperature to place a limitation on time at maximum warp. Warp Coil Temperature: While the drive is active, and moving at warp speeds, to emulate the warp plasma cycling through the coils I have implemented an exponential function that increases the temperature of the warp coil part. The smallest amount of heating occurs at low warp, while the maximum heating occurs at maximum warp. There is a built-in warp coil efficiency that can be used to aid in cooling. The value in the config file is between 0 and 1, and the upper limit is enforced in the code to prevent config editing to make the coils cool themselves at high warp. If a value greater than 1 is used in the config, the plugin randomly chooses an efficiency in the correct range. So, you may get a decently efficient coil, or a really inefficient one. This is also done per coil, so you could have one coil that is really efficient and one that is terrible, which could hamper your warp travel to keep one coil from overheating and exploding (the stock behavior). The maxWarp parameter of the warp coil also plays a role in temperature calculation. A ratio is taken of the active drive's maxWarp to the warp coil's maxWarp to further scale the exponential function. If the warp coil's maxWarp is equal to the drive's, there is not scaling, if it is less, there is more heating, if it is greater it is less. The reasoning is that if you have a warp coil rated for Warp 1, and try to push it to Warp 2, it would burn out much faster, but if it's the other way around, it would be able to handle the temperature better. Warp Coil Discharged: If the source of warp plasma runs out, or is shut off, the coils may completely discharge, if the user doesn't notice that warp plasma production has stopped. If the coils completely discharge (or their charge goes below the threshold set in their config) the drive will automatically disengage and either be automatically placed in a nearly circular orbit (Easy orbit mode), or be in a realistic orbit based on the vessel velocity vector. Running out of Electricity: If there is not enough electric charge to run the Warp Field Generator, the drive will automatically disengage and enter an orbit based on the selected orbit mode. Multiple Warp Generators?: If there are multiple parts on the vessel that implement SW_ModuleWarpGenerator, only one may be active at a time. If you try to activate a second warp generator when one is already active, it will not activate. If you disengage the active drive, you may then activate another. Screenshots Phoenix Warpship: NX-class: NX-Refit NX-class Bridge IVA Custom Registries There are ten (10) different names and registries in two variants each, so 20 textures in all giving you NX-01 through NX-10 and names with and without the "S.S." prefix. The registries are B9PartSwitch selectable on the saucer part and the refit engineering hull part. I have included instructions on how to make custom names/registries in the config file that sets up the variants under "TrekDrive/Parts/NXClass/Registries/Registries.cfg". The instructions are at the bottom of the file. There are also two (2) template images, one in PNG format and another in PSD. To use the PSD file you will need to have the font "Airborne", or one that looks close enough to it, if you want show-accuracy, or any font of your choosing will work.

Skunk Works Presents: STAR TREK SHUTTLES. Boldy going........ https://spacedock.info/mod/1811/Star Trek Shuttles

Introducing... (Source code is included in the download) License: Code and Configs are licensed under the GPL v3 license. Author: TheShaddow1138 Tester(s): @Puggonaut Here's a spacedock by @StinkyAce that @Puggonaut has been featuring in his videos: https://spacedock.info/mod/1815/USS Nimitz and Drydock A scaleFactor of 0.6 makes the best fit for the NX. Small Trailer for TrekDrive made by Puggonaut This fantastic video was made by @Puggonaut, and you should definitely give it a watch. Change Log: v0.99.1w - Spacedock * Added a ModuleManager patch for StinkyAce's Spacedock, available at this link: https://spacedock.info/mod/1815/USS Nimitz and Drydock The patch scales the dock down to 0.6, a near perfect fit for the NX-class, and instead of modifying the drydock that comes with StinkyAce's mod, it creates a new part with the aforementioned scale, an impulse engine (no part, just the module), and produces the resources used by TrekDrive ships. This will be a good refueling station for the NX. * Updated the plugin * Fixed an NRE spam in the impulse engine code while in the editor * Added the ability to select a "forward" or "reverse" mode for the impulse engines. Toggleable in the PAW, and can be set as an action group. * Cleaned up the Waterfall patch by splitting the warp effects into their own patch. * Tweaked the texture tiling on the NX warp effects (both the Warp 5 and Warp 7 versions). v0.99w - NX-class Release * B9PartSwitch is now a hard dependency. (Included in download) * Updated the TrekDrive.dll * Warp speed formula changed to allow faster interstellar travel * OnLoad function updated to not automatically set the warp drive to "Not Ready" if it was in a "Ready" state at the last save. This allows the player to immediately engage the drive after the vessel loads, if the drive is in a Ready state upon loading. * Added NX-class Starship Parts * Bridge module (Crew capacity of 6) * Saucer section (Crew capacity of 20) * Engineering section * Nacelle Pylons (B9PartSwitch variants) * Upper variant (2 upper pylons) * Lower variant (2 lower pylons) * Four variant (2 upper & 2 lower pylons) * Warp Nacelles (Port & Stbd) * Main Impulse Engines (Port & Stbd) * Secondary Impulse Engines (Port & Stbd) * Navigational Deflector (2 variants) - Serves as a transmitter * NX-01 Oval "Mark I" Deflector * NX-02 Rectangular "Mark II" Deflector * Added NX-class Refit Starship Parts * Engineering Section Refit (Includes warp 7 warp core and warp drive, Crew capacity of 10) * Refit Warp Nacelles (Port & Stbd) * Added Custom Waterfall FX model and texture for streaking stars at warp effect. * Updated the warp stars effect on the Phoenix * Added six (6) craft files for the NX-class and NX-class Refit * NXClass_A: Standard NX-class starship (as seen in Star Trek: Enterprise) * NXClass_B: NX-class starship with two (2) ventrally (lower) mounted nacelles * NXClass_C: NX-class with four (4) nacelles * NXClass_Refit_A: Standard NX-class starship Refit * NXClass_Refit_B: NX-class Refit with two (2) ventrally (lower) mounted nacelles * NXClass_Refit_C: NX-class Refit with four (4) nacelles v0.9w - Shuttlepod & Impulse Engine Release * Updated the TrekDrive.dll * All TrekDrive buttons/toggles can now be set as Action Groups * SW_ModuleImpulseEngine Added - automatic takeoff and landing modes when sub-orbital, it will not automatically land from orbit. * SW_ModuleBussardCollector Added - When the collector is activated it will collect at a random rate for a random period of time before choosing another random rate and period of time. Collects LqdDeuterium and Antimatter with LqdDeuterium collecting at a higher rate. Collection will only occur at sub-light velocities. * Updated Waterfall version. * Updated Waterfall effect on the Phoenix Launcher Main Engine to correct a position issue. * Added a Waterfall effect to the Phoenix - visible when traveling at warp; the effect is based on the streaking stars warp effect from TNG - VOY and ENT. * Added Enterprise-era Shuttlepod * Shuttlepod main body - holds 5 kerbals with airlocks on both sides (No IVA) * Shuttlepod Impulse Engine v0.7.5w - OnLoad Hotfix: * Corrected an issue that prevented engaging the warp drive after switching to another vessel, after reloading the game, or any other loading action. Upon switching back to the warp ship, or loading the save, the warp drive will be automatically disengaged and set to "Not Ready" status. Simply clicking "Check Ready Status" and then engaging the warp drive will get you ready to go. Thanks to @Tanner Rawlings for finding this issue and bringing it to my attention. v0.7w - Phoenix IVA release: * Added Phoenix IVA (Stock and MOARdV's Avionics System) * The MAS version replaces some of the central props with MAS props, and replaces the Main Display with a functional MFD * MAS version of the IVA will only be available with MAS is installed. v0.6w - Phoenix Initial release: -------------------------------- * Updated Code: * Added nacelle glow animation capability, giving a visual indicator of coil charge. * Fixed coil charge logic to allow charging a partially discharged coil * Fixed a logic issue with the Warp Field Generator code. Now the "not enough charge" warning will only occur if the warp drive is active. * Moved to LqdDeuterium and Antimatter from Community Resource Pack * Added Phoenix Parts: * Phoenix Crew Cabin (no IVA currently, built-in RCS, no effects yet) * Phoenix SAS (contains Monopropellant and Electric Charge) * Phoenix Fuselage (contains LqdDeuterium and Antimatter) * Phoenix Nacelle (deployable warp nacelle) * Phoenix Warp Core/Warp Field Generator * Phoenix Main Thruster (matter-antimatter rocket engine) * Phoenix Vernier Thruster (matter-antimatter rocket engine) * Phoenix Fairing (to conceal the warp nacelles during launch) * Phoenix Interstage Decoupler * Phoenix Launcher First Stage * Phoenix Launcher Main Engine (Liquid Fuel Oxidizer engine) * Added Phoenix Warp Ship Test craft. * Added Community Resource Pack and Waterfall as hard dependencies (bundled) Inspired by RoverDude's Standalone Alcubierre Warp Drive, this warp drive aspires to operate in a Star Trek-like manner requiring at least two types of parts to operate: warp coils/nacelles and the heart of the drive, the warp core and warp field generator. I have seen in other threads here where people were trying to figure out how to require the use of warp nacelles to get that Star Trek feel to their KSP warp drives, and that's what I set out to do with this, my first plugin mod. Maybe a bit ambitious, but I think it turned out well. Now, on to the details. Technical Aspects: The plugin includes three Part Modules: SW_ModuleWarpCoil, SW_ModuleWarpCore, and SW_ModuleWarpGenerator. SW_ModuleWarpCoil: This module would typically be attached to a warp nacelle part, but could be added to any part for a design that perhaps doesn't use a nacelle, or similar structure. Requires: Warp plasma, which is generated by a warp core part using SW_ModuleWarpCore. Restrictions: Cannot be added to the same part as the SW_ModuleWarpGenerator. This is the restriction that requires at least two types of parts. Example Config: MODULE { name = SW_ModuleWarpCoil minWarpPlasma = 400 // Not used warpPlasmaConsumed = 5 // Amount of warp plasma consumed per second during charging and operation warpPlasmaNeeded = 250 // Amount of warp plasma needed to fully charge the warp coil cutoffThreshold = 2.000 // When the charge percentage drops below this percentage, the coil and drive cut off (1 - 100) coilEfficiency = 0.01 // Thermal efficiency of the coil (0 - 1) maxWarp = 2 // Maximum warp factor this coil can safely achieve } SW_ModuleWarpCore: A simple generator module that takes in deuterium (matter) and anti-deuterium (antimatter) to generate warp plasma and electric charge. (Could be replaced with a stock ModuleGenerator I suppose, but it's included all the same). Requires: Deuterium and Anti-Deuterium. Restrictions: None hardcoded. Example Config: MODULE { name = SW_ModuleWarpCore minAntimatter = 0.05 // Minimum amount of anti-deuterium required to operate minMatter = 0.05 // Minimum amount of deuterium required to operate warpPlasmaProdRate = 10 // Amount of warp plasma generated per second ecProdRate = 100 // Amount of electric charge generated per second } SW_ModuleWarpGenerator: The heart of the warp drive that actually moves the ship at warp speeds. Just like RoverDude's Standalone Alcubierre Warp Drive, the drive uses translation, not acceleration, to move the ship through space. Also, like RoverDude's drive, I used a slightly modified version of his gravity braking code (RoverDude's source code including the GravityBrakes() function) so that ships will slow down when they near gravitational bodies. Requires: At least one part implementing SW_ModuleWarpCoil that cannot be the same part implementing SW_ModuleWarpGenerator. This is what forces the requirement of multiple parts. Restrictions: All warp coils must be charged before the drive can be activated, and enough electric charge to run the drive is also necessary. If either of these is not true the drive cannot activate, or will automatically disengage. Example Config: MODULE { name = SW_ModuleWarpGenerator maxWarp = 2 // Maximum warp factor this drive can attain minNacelles = 2 // Minimum number of nacelles required by the drive to operate (must be at least 1) electricityReq = 50.000 // Amount of electric charge that is required per second of warp operation } NOTE: Some part on the vessel should have a container for warp plasma. In the included test parts the nacelles have their own warp plasma containers, but it can be on any part of the vessel. Warp Speed: The ship's warp velocity is computed using a simple cubic function, which was used for the original series and in Star Trek: Enterprise. So, velocity = (warp factor^3) * c In my initial testing, I find that Warp 2 is a good speed for traveling to the edge of the Kerbol System in a comfortable amount of time. I haven't tested higher warp factors, but will install appropriate mods on my end to further test travel times with increasing warp factors before final release. How to Use: I have kept the operation of the drive entirely within the Part Action Windows (PAW) of each part. Follow these steps to activate the drive. Step 1: Activate the Warp Core by clicking the "Warp Core Status" toggle Step 2: Charge the Warp Coil(s) by clicking "Charge Warp Coils" in the coil PAW Step 3: Once the coils are charged click "Check Ready Status" on the Warp Generator (combined with the Warp Core Test Article here). The drive will not enter the "Ready" status until all the coils are charged, and will not do so if there are any other active Warp Generators. Step 4: Once the "Ready Status" reads "Ready", click "Engage Warp Drive" on the Warp Generator. This will change from "Drive Inactive" to "Drive Engaged" Once the drive is engaged, any throttle input will move the ship at warp speeds. To return to non-warp operation, simply click the "Engage Warp Drive" toggle in the PAW to disengage the drive. Current warp factor is determined as a percentage of the drive's maximum warp rating, based on the amount of throttle: 50% throttle is half of the maximum warp, 100% throttle is maximum warp. E.g. for a drive with a maximum warp of 2, 50% throttle will be Warp 1, and 100% throttle will be Warp 2. The current warp factor is displayed in the Warp Generator's PAW Step 5: Once you have reached your target destination simply throttle to 0%, or use "x" to cut the throttle. There is an "Orbit Mode" option in the Warp Generator PAW that defaults to "Easy", this places the vessel in as close to a circular orbit as possible when the throttle hits 0 after having been non-zero. That is, it doesn't continually change the orbit while the drive is active, only if it had been moving the ship and then stopped. If the Orbit Mode is toggled to "Realistic", it will simply use the vessel's velocity vector to determine the current orbit, in the same manner as RoverDude's Alcubierre drive. Limitations: I tried to implement some limitations to make the drive less "cheaty". I took cues from Star Trek, particularly Star Trek: Enterprise, which dealt repeatedly with the limitations of the ship's warp drive. In the show, most problems occurred with the plasma injectors, but I though trying to code some kind of simulation of the injectors would be cumbersome and place unnecessary computational overhead. Other limitations that come to mind are the stability of the warp field, and the warp coil temperature. I opted for warp coil temperature to place a limitation on time at maximum warp. Warp Coil Temperature: While the drive is active, and moving at warp speeds, to emulate the warp plasma cycling through the coils I have implemented an exponential function that increases the temperature of the warp coil part. The smallest amount of heating occurs at low warp, while the maximum heating occurs at maximum warp. There is a built-in warp coil efficiency that can be used to aid in cooling. The value in the config file is between 0 and 1, and the upper limit is enforced in the code to prevent config editing to make the coils cool themselves at high warp. If a value greater than 1 is used in the config, the plugin randomly chooses an efficiency in the correct range. So, you may get a decently efficient coil, or a really inefficient one. This is also done per coil, so you could have one coil that is really efficient and one that is terrible, which could hamper your warp travel to keep one coil from overheating and exploding (the stock behavior). The maxWarp parameter of the warp coil also plays a role in temperature calculation. A ratio is taken of the active drive's maxWarp to the warp coil's maxWarp to further scale the exponential function. If the warp coil's maxWarp is equal to the drive's, there is not scaling, if it is less, there is more heating, if it is greater it is less. The reasoning is that if you have a warp coil rated for Warp 1, and try to push it to Warp 2, it would burn out much faster, but if it's the other way around, it would be able to handle the temperature better. Warp Coil Discharged: If the source of warp plasma runs out, or is shut off, the coils may completely discharge, if the user doesn't notice that warp plasma production has stopped. If the coils completely discharge (or their charge goes below the threshold set in their config) the drive will automatically disengage and either be automatically placed in a nearly circular orbit (Easy orbit mode), or be in a realistic orbit based on the vessel velocity vector. Running out of Electricity: If there is not enough electric charge to run the Warp Field Generator, the drive will automatically disengage and enter an orbit based on the selected orbit mode. Multiple Warp Generators?: If there are multiple parts on the vessel that implement SW_ModuleWarpGenerator, only one may be active at a time. If you try to activate a second warp generator when one is already active, it will not activate. If you disengage the active drive, you may then activate another. Current State: The Phoenix warp ship is now playable (complete with stock and MAS IVA). The launcher is included. The balance may not be the greatest, but it's playable. Community Resource Pack and Waterfall are now hard dependencies. Warp Coil charge animation is now implemented.

I was wondering if there were any mods that add Star Trek style transporters?

An idea to reconcile a perplexing fact-cluster from the Star Trek franchise in what I think is a new, hard-sci-fi-ish approach: Crews on board starships experience "gravity" (exactly equal to that of southern California), which is rarely explained, discussed, or explored in an interesting way Line of sight with away teams on the surface is never interrupted by the horizon, for comms, sensors, transporters, weapons, or anything else Starships' engines are extremely powerful and efficient, for both FTL and sub light speed travel, able to accelerate extremely quickly and rarely limited by fuel supply "Weightlessness" and "zero G" are not artifacts of being in space, but of being in free fall, i.e. experiencing no forces such as running the engines When other vessels are encountered, they never whiz past at 7–15 km/s, but instead gently cruise by at a leisurely pace What if the sheer power of Starfleet vessels' engines leads to the abandonment of true "orbits" as pertains to starships? When the captain says to enter "orbit" around a planet, the ensigns understand by established Starfleet convention that this means to enter the region of space where a low orbit would be, i.e., 100–2000km altitude They maneuver the starship into that rough altitudinal region, and instead of establishing a proper circular orbital velocity, they bring it to a faux-geocentric "stop" over designated a point of interest; with no further action, it would drop out of the sky, burn up, and crash, so... The ship is oriented so the "bottom" points towards the planet The engines are configured to thrust "upward" exactly equal to the force of the planet's gravity, effectively holding the ship in place over one spot The result for the crew would be just like standing on the top of a ~100–2000-km-tall tower; they'd feel the planet's gravity pulling them down, almost as strongly as at sea level, with no magic "artificial gravity" tech required. Benefits include having your Starfleet-branded iPad not float away and the ability to sip Romulan ale from a glass without spilling it. The energy budget to do this, even for several consecutive days, should be relatively trivial next to that expended in the typical space battle or race to rescue the ambassador or deliver the self-sealing stem bolts. And if all space navies adopt this practice, then enemy ships have a reason to have low relative velocities. Obvious caveats and objections: "Gravity" in deep space remains unexplained The ships are never shown accelerating "upwards", only "forwards" I realize this is not what the canon says, and it doesn't cover everything, but for hard sci fi fans, it may be a serviceable excuse for turning your brain off during some episodes.

Coming soon from skunk works... USS Kerbin departs Alexandria Station.

So, I just finished watching the first episode of the new Star Trek series, Picard. I thought it was quite good - I was half expecting a lens-flare riddled explosion-fest like Discovery, but they seem to have mostly avoided that, perhaps because Patrick Stewart is on the team. I'd like to hear the first impressions of everyone else. Discuss away! (moderators, I haven't seen another thread like this but if one exists please do merge this into it )

STARDATE: Y4-D303-4H25M The third Dres Fleet has arrived and are now captured in Dres' sphere of influence. So far, our Dres colonization fleet - whether they're orbiting the planet or already landed - consist of: The U.S.S. Defiant (and it's crew). Though it has plenty of liquid fuel left for the return pod, it has run out of fuel for itself and very low on monopropellant. That can be fixed. 2 permanent self-sustaining bases Dresden Base is within 10 kilometers of the designated landing spot (Rosly's Whim) for incoming landers, chosen for its rich ore deposits Colorado Base is in orbit. I have ordered it to wait until the Dres Canyon is in daylight to land it. 1 ore-scanning satellite in polar orbit 1 Interplanetary Escape Pod The next crew will come in another one, but I already have one stationed in Dres orbit in case of emergencies 2 mini-buses DRES MINI-BUS 001 already within range of Rosly's Whim and Dresden Base DRES MINI-BUS 002 in orbit, as I have not yet decided where to put it 1 large fuel truck in spotting range of Rosly's Whim. 1 surface relay, planted on the opposite side of the planet from Rosly's Whim 1 three-man surface lander, equipped with science. 2 one-man surface landers. Though they have more Delta-V than the three-man lander, they still need refueling after each use - not to mention I can only take one person at a time in them. 1 Ore converter module. I shall dock it with the U.S.S. Defiant so that the station can produce its own fuel. 1 Ore Delivery probe. It shall land in Rosly's Whim and collect ore to bring back to the upgraded Defiant for conversion. I made sure it had PLENTY of Delta-V ready so that it won't need to refuel itself once it reaches the Defiant. * screenshot of our progress. My crew has been itching to get down to Dres' surface and explore, and I assure them they will get their chance. But first, I need to: Dock the ore converter with the Defiant. Land the delivery probe at Rosly's whim to collect ore and take it up. Take the three-man lander (myself, one engineer, one scientist) down to the surface after the ore collector's clear of Rosly's Whim I don't want any incidents involving two vehicles in the same spot. Return to the Defiant with a surface sample and scientific data for processing. Either inform Mission Control that's it's more efficient to send three people at a time or one. Mission Control tells me that there's a fourth fleet coming to Dres in about one Kerbal year, and it involves a self-refueling ore delivery module and the Defiant's replacement crew. From what I hear, this crew will start living permanently in Dresden Base while finding other potential landing sites. Personally, I hope Mission Control finally figures out how to build an SSTO to send here; that way, we can explore Dres as we would Kerbin on a plane without the hassle of using a legged lander. I also requested Dres gets an ultimate relay antenna stationed there, as we had an incident where we almost lost our first mini-bus due to a signal loss. To anyone who reads this entry, let it be known that we're paving the way to plant Kerbalkind's feet on other planets - starting with Dres.

WarpCoreUnit1 A Star Trek Trek inspired warp core for Kerbal Space Program. Dependencies: Alcubierre Warp Drive (Stand-alone) By RoverDude. https://github.com/BobPalmer/WarpDrive/releases At my request, SpannerMonkey created this model for me based on a warpcore model I found on blendswap, and derived a config for it following the configs for Alcubierre Warp Drive (Stand-alone) By RoverDude. which is a dependency for this mod. He has given me permission to modify it as I see fit, and release it. I have heavily modified the config to: 1) The reactor uses Dilithium Crystal (of course) to create LqdDeuterium which the Warp engine runs on. 2) Provide it's own power (850 ec/s) and power storage (1000 ElectricCharge) 3) Provide a way to replenish the Dilithium Crystal from processing ore at a rate of 1 Dilithium Crystal per every 10 ore, every 10 sec. This warp core is a little cheaty compared to the other warp drives out there, mainly because of it's size... and yes, I know... no warp nacelles. I was fed up building warp capable ships and having to use enormous (but very awesome!) warp drives, I wanted something I could fit inside a large cargo bay, and well, here it is! *This Warp Core is a fully self contained warp drive, reactor and ore processor. In order to make use of the reactor and ore processing, first you must "Deploy the Converter" wait for it to be ready (it takes a little while), start the reactor, Initialize the Dilithium Chamber, and if you are converting ore into Dilithium Crystal, Start Crystal Extraction. The ore processing requires exactly 99% of the reactors power output, leaving you with a very small output of 8.5 ec/s to maintain minimal ship functions. Do not attempt to run the ore processor and the engine at the same time unless you have a rather large secondary power source. In order to create a "Warp Bubble", you must be a minimum of 90km above the surface... then buckle up and engage! Change log: This work is licensed under the Creative Commons Attribution-NonCommercial 4.0 International License. Download links: Github SpaceDock Dropbox

Well here it is.... The Uss Nimitz and Several variant DryDocks https://spacedock.info/mod/1815/USS Nimitz and Drydock?ga=%3CGame+3102+%27Kerbal+Space+Program%27%3E

According to me, this is the entire Mirror Mirror ethics or lack of it is more better than regular universe. For whole life i was honest aspie boy but maybe it's better to be like Lorca Mirror Maybe i try to be pilot, lie on medical, than lie all my career

The Strike Fighter from Star Trek https://spacedock.info/mod/1741/Federation Strike Fighter

The Runabout is ready for delivery. https://spacedock.info/mod/1740/Danube Class Runabout?ga=%3CGame+3102+%27Kerbal+Space+Program%27%3E Enjoy

Welcome to Raptor Aerospace Industries. My name is Raptor22, President and CEO of Raptor Industries. Please, enjoy your stay. Here at Raptor Industries, we are dedicated to bringing you reliable aircraft, spacecraft, and other aerospace systems that will serve you throughout multiple missions. From cargo planes to faster-than-light starships, we will ensure that our systems are versatile and affordable. We are not to be confused with Raptor Aerospace Concepts and Solutions. If you mistakenly came here, go here: View our products on KerbalX: Visit Raptor Industries! While in the past, Raptor Industries (or, as it once was called, Raptor Aviation and Aerospace Technologies) mainly created aircraft, in recent times the company has shifted to creating ships for interstellar travel. Our Star Fleet division (inspired by but not affiliated with CBS’s Star Trek) specializes in creating the finest star ships, star bases, and shuttlecraft for the United Kerbin Defense Force, along with other contractors. In addition, we still serve the KAF (Kerbal Air Force), and have many military systems, alongside the civilian market. Our defense systems are among the best on Kerbin. As such, victory is almost always assured. We often incorporate military technology into civilian projects to provide the best safety systems that you can hope for. All modded aircraft will be incorporated with aviation lights for safety. If you have even more concerns, we may grant special requests to outfit certain civilian aircraft with electronic warfare jamming systems, flares, and chaff, to provide the utmost defense against enemy attacks. We will always do our best to provide as much information as we can about our systems. We shall ensure that each vessel in our catalog has the following statistics listed clearly: All action groups Resource values (i.e. maximum fuel load, electrical charge, etc.) Maximum Proven Altitude (unburden, or without a payload or weapons) Maximum Proven Airspeed (criteria for determining such shall be determined later) Maximum number of passengers and crew Other statistics, such as maximum payload, range, and endurance, are hard to obtain, and may vary from user to user as a result of different handling of the systems. While some may be aiming to squeeze every last drop out of a system, others may simply be aiming to get there quickly, regardless of fuel usage. We do not dictate how our customers operate our systems, but we will provide suggestions in order to make sure all of our customers are satisfied. Stock Market Modded Market If you wish to become one of our corporate partners, we shall be sure to include information about your company (profile) here. Here is a list of our Corporate partners: WaffleTech Military Technologies, Lead by Joseph Kerman. Visit them here: We thank all of our corporate partners for their support If you have any suggestions or complaints, please contact us at [email protected] Please bear with the current lack of craft for the time being. I'm still making the first iteration of aircraft and designing their pages, so it will be a little empty for now. But please, stay tuned. I'll be uploading my craft very soon.

My wife gave me a very nice Christmas present this year that I just received today: a VIP pass for a photo and autograph with Nichelle Nichols! This was at Wizard World in Cleveland. She was very friendly and gracious, and, if she saw anything wrong with my somewhat-hastily-thrown-together TOS uniform, she didn't let on. I'm sure she's already seen every variation under the sun...

Does he was good or arogant idiot? He was my favorite character from Universum of Star Trek

If Star Trek was real who would opted to serve on steerfleet if United Federation of Planets distribute all necessary things to good life if: We've eliminated hunger, want, the need for possessions I guess most of Starfleet would be 50 % Aspies 50 % ADHD folks

Does anybody on the forum play Star Trek Online? I've got it on the xbox

USS Excelsior Link to album: https://imgur.com/a/B04i8 Download link: https://kerbalx.com/Azimech/77I--USS-Excelsior-v11

Hello all. Ever since the announcement that the math behind a warp drive is semi-plausible, And NASA's own (very optimistic) concept released, I've wanted to essentially reinvent the ship (or perhaps the concept of the series) In a more realistic fashion. The concepts in the show redone in a way that could be done now or in the near future. (Obviously the ability to create a space-warp is assumed) Perhaps without fundamentally changing the ship too much, but that's not set in stone. Wanting to incorporate things like a warp ring, a centrifuge for 'gravity' and semi long-term habitation A semi sustaining ship. likely incorporating a greenhouse. Mostly Self-sustaining and ISRU is assumed. Capacity to land on planets (Without fancy beaming). This would likely require one or multiple SSTO's attached. A primary drive capable of significant deltaV changes (likely using some form of nuclear rocket, or perhaps a EM drive variant. A large scientific capacity. This ship would likely be designed for a fraction of the Enterprise's crew in the show. Otherwise all these things would grow exponentially rather quickly. Now i realize there are concepts here that are not totally set in stone. Such as the warp drive and EM drive. I want to use this as a project to get myself back into 3D modeling and perhaps programming. Eventually I'd like to make a parts pack but that's not set in stone. Not yet at least. I'm curious as to peoples thoughts on this. While i have had a interest in science and science fiction and the universe as a whole my whole life most of my knowledge is limited to documentaries wiki and KSP. Go easy on me.

Waiting on Procedural Parts and Wings to catch up to KSP 1.2. I was encouraged to make additional and preferably older Trek ships. On my way to finding and settling on the Excelsior Class known for USS Enterprise B, I stumbled on this one. I figured it would be a breeze since this, the Nebula class, is very similar to the Galaxy Class. I also went ahead and did this because ships in this class tend to do patrol and courier missions, and sensor sweeps, and the tail-mount up top seems to generally hold the scanner parts! Deciding this a very worthy ship to be Kerbalized, and to serve in KerbNet I ensured that there is some cargo space. Since the tail-mount is different per ship in the Nebula Class, I made it to be swappable via senior Clamp-O-Tron for whatever other purpose or specifics you have. Specs and tips: Carries 49 kerbals but there's plenty room to add more crew cabins. (The part count is nearly 200 so there already isn't more of them.) Saucer section is Procedural Parts with 18m diameter and Kerbal Hacks: Procedural Parts Textures. Elliptical caps inside the nacelle fronts are Procedural Parts Extended. Neck is a stock Structural Pylon. Tail mount is B9 Procedural Wings Modified. Most other body parts include Mk2 Stockalike Extension. The visible Mk2 engines are Ion drives from the aforementioned mod, purely for aesthetics. The warp drive is GN Drive from Mobile Suit Gundam 00. It provides its own RCS translation power but not rotation power. It might not show up in Staging. Tweakscale. Nacelle lights are Surface Mounted Lights for Self illumination. Right-click a GN Drive and turn on Trans-AM to use warp/kraken/whatever speed. Do not use in atmosphere with this ship. The tail might burst or disorient the ship. This drains the engines and ends itself then. If you only have one drive (lose one by damage?), you may lose this option and a portion of your agility. The fuel is locked inside the Mk2 tails on the saucer to not get wasted by the RCS. On spawn at runway, press 3 and kill throttle. Then you can safely detach clamps. The real ship does not have visible impulse engines so there's no "T1" or "NF" stuff here. Action groups: Toggle Ion and Warp Drives. - Make positive gravioli. Toggle Antigravity. Downloads: KerbalX

Waiting on Procedural Parts and Wings to catch up to KSP 1.2. An incredibly faithful and highly functional replica for you to download and drive. Room for 49, excellent bridge view and it has room for a small 2.5m craft! If anyone asks, I'll post additional editions without the warp drive, without the lights, or just the hull. It just came to me and I recreated this awesome ship. Due to the nature of the GN Drive that makes it all work, only two of the pure drive can fully function in a given ship. It is self-powering and near-perpetual. There's the lesser GN Drive Tau part which has high demand for electric charge and has its realistic ups and downs, and any number can be safely installed but those are not important for this post. This also enables you to easily and comfortably land and take off at your favorite impossible planet. Full Gallery: http://imgur.com/a/9KicG Specs and tips: Carries 49 kerbals but there's plenty room to add more crew cabins. (The part count is nearly 190 so there already aren't more of them.) Saucer section is Procedural Parts with 18m diameter and Kerbal Hacks: Procedural Parts Textures. Neck is a stock Structural Pylon. Abort action group will activate its decoupler function and the saucer's engines. Unfortunately, since the root part is in the secondary hull, the neck remains with the saucer. Trying to change the root part and fix that has caused my game to crash every time. On separation the saucer's root part becomes the pylon or another awkward part. Most other body parts include Mk2 Stockalike Extension. The visible Mk2 engines are Ion drives from the aforementioned mod, purely for aesthetics. The warp drive is GN Drive from Mobile Suit Gundam 00. It provides its own RCS translation power but not rotation power. It might not show up in Staging. Tweakscale. Cosmetic D-NF edition requires Near Future: Electrical, Propulsion and conditionally, the Infinite Electricity cheat. D-T1 edition sacrifices all Near Future parts for less mod dependency. Contains eight stock RTGs in each major section for 12 EC/s total power generation. It's named T1 for the T1 Toroidal Aerospike engines. Nacelle lights are Surface Mounted Stockalike Lights. Right-click a GN Drive and turn on Trans-AM to use kraken speed. This drains the engines and ends itself then. If you only have one drive (lose one by damage?), you may lose this option and a portion of your agility. The fuel is locked inside the Mk2 tails on the saucer to not get wasted by the RCS. In D-T1, also check the flat white disk between the convex surfaces as to not waste the LFO in that. In D-NF, this disk is a structural element, not a tank. Considering Kerbals now pass out from excessive Gee in KSP 1.2, and this ship uses acceleration, its crew in this situation will be in for many great times. Action groups: Toggle Ion and GN Drives. Toggle Impulse drives. I advise you only use those (especially the LFO in the D-T1 edition) on saucer separation or you might waste the fuel. Toggle Antigravity. [Abort] Activate impulse drive and separate the ship. Launch sequence: Press X, 1, 3, Spacebar. Downloads: Moddier, cheatier "D-NF" edition (Now on KerbalX) Less moddy, less cheaty "D-T1" edition (Now on KerbalX)

"These are the Voyages of the Starship Enterprise. Its five-year mission: To explore strange new worlds; to seek out new life, and new civilizations, and to boldly go where no Little Green Man has gone before" As you may know, today is the 50th anniversary of the first airing of Star Trek. As a tribute, I made my very own, however slapped together, Starship Kenterprise! For warp, just use hyperedit! Live long and Prosper!

The Star Fleet Mini Collection Sector 7 Space Laboratories These craft have been very challenging for such small craft, each have their unique launcher and difficult but yet fun challenging ways of control. Please note, none have a nav ball that is reading correctly, some if not all have opposite controls much like a real aircraft, down is up and up is down. The launchers are not my best work but they can get you off to a really good orbit for space travel and the two space craft pack a punch, I don't know for sure but these could be the smallest Interplanetary craft built in KSP. I had know idea that these craft were going to travel the distance they are going. None have been in any orbit other than Kerbin and I am not sure if they can achieve any other Mun or Planet's orbit, mainly because of the difficulties with the navigation ball because of the way the craft was built. All require much patience. Photo Album The Mini Enterprise AC-1 Parts: 46 Mass: 1.704t Height: 1.8m Width: 2.1m Length: 4.0m The Mini Enterprise AC-2 Parts: 78 Mass: 2.774t Height: 14.8m Width: 2.9m Length: 2.3m The Mini Enterprise Parts: 176 Mass: 315.108t Height: 41.6m Width: 11.2m Length: 11.2m The Mini Enterprise I. C. E. Parts: 75 Mass: 39.060t Height: 20.4m Width: 4.0m Length: 5.9m Flight Operations The Mini Enterprise AC-1 launches in a very unique way, from a cart. Launch with full throttle and decouple at near 40 m/s tapping the W key and your off. The Mini Enterprise AC-2 launches in it's unique way by engaging the Juno Engines and waiting about 7 or so seconds for them to build thrust and then release and your in flight. The Mini Enterprise launches with full throttle & SAS, use RCS to stop the gravity turn, you might want to slow the engines down for better control during the gravity turn but no necessary. The Mini Enterprise I. C. E. launches the same way as The Mini Enterprise with full throttle & SAS, slow the engines down for better control during the gravity turn and enjoy the solar system.