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. If you like what you see, and would like to support development you can make a donation. One-time Donation through PayPal Mod(s) that Expand or Supplement TrekDrive: @Shammyofwar Is updating the Old SciFi Shipyards mod by implementing TrekDrive modules on that mod's USS Voyager and USS Stargazer, among others. The TrekDrive plugin will be bundled with their mod upon release. 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.

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. If you like what you see, and would like to support development you can make a donation. One-time Donation through PayPal 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 recently said I was going to update/remake because I have already some of the parts updated for my personal use. I have obtained permission from TheShadow1138 to use his code from So thought I'd drop an update and some pictures. Gallery here . I have a fully functional USS Stargazer, USS Voyager, Borg Cube, Doomsday Machine, TARDIS, and Flying Saucer that all use impulse engines and warp drives from TrekDrive. There are still bugs and tweaks to be made before I can publicly release the Beta and it may take me some time because I am limited on time to test and fix. Just wanted to let you all know it's a WIP. If anyone wants to help PM me.

Im just kinda curious on how to get the warp drive from martincitopants "Kerbal Scuffed Program 3" would be very helpful if there was a download for 1.12.3

From my own experience, I know that Interstellar Extended can be quite complicated to figure out, so I made this post to minimise the fuss. In the KSP @FreeThinker's Interstellar Extended mod, there is a number of very cool futuristic parts, and sometimes it can get quite hard to find out how to best use those parts. One of the best examples of such a feature is the Acullbierre drive (a.k.a the Warp Drive) As most parts in IE and in KSP in general, the Acullbierre drive requires a few more parts to function. To fully understand how a warp drive functions, we are going to use an example ship I’ve built. It’s parts fall into these main categories: -Means of control (Duh) - Reactor (mega joules generator) - Secondary power source (mega joules are considered a different resource, so it is best that there is at least a solar panel on the ship) -Acullbierre Drive -Radiators (an absolute MUST for almost any system in IE) Secondary Propulsion system (When exiting warp, you will be going at the exact speed you left at, so you will want to make some adjustments so that you don’t fall into or escape the planet you’re going after) With most parts being pretty self explanatory, there are two features I need to address: The drive and the reactor. Reactors are parts that generate electricity. Some do more than others but they may also require more resources or last less long. Make sure to read the description of them to make sure your ship has the required resources. As well as that, many reactors have different configurations, meaning that some can utilize different configurations of resources. These are different for every reactor, so make sure you choose the one that suits you best. (Most reactors can be fitted with an extra “thermal” reactor. Those utilize the excess heat your reactor/Acullbierre drive produce and repurpose it as electricity. They can go great with reactors as they increase the power output greatly) Acullbierre drive comes in three different shapes: small, large and compact. These differ in the amount of mass they can transport, so make sure you have the correct one (they can also stack BTW) When everything is set up and the reactors are working, go to the drive menu (via right click) to start the drive. CAUTION: this act will generate a lot of excess heat, so be sure you either have enough radiators or your actions are quick!!! When the reactor is charged (the exotic matter bar is full) select your destination on map screen, point there and turn the warp drive on! Tip: one of the readings on the drive menu is the current warp speed. You can increase and decrease that with the appropriate buttons on the menu. Make sure you you slow down quickly enough though!

Basically, it's the Portal Gun from Portal. In Portal, the device exists in the form of a futuristic-looking gun that works by shooting a pair of portals onto surfaces coated in moon rocks (and the moon itself) to instantaneously transport information and matter across space. Only two portals can exist at a time (save for co-op multiplayer, which will be ignored) and work both ways. In KSP, the portal device would exist as a large-ish part that could transport ships and their cargo (passengers, resources, momentum(?), across space to a duplicate of itself. To do this, both parts would require a large amount of electric charge, ore, and a way to refine it into fuel as well as a strong (green) connection to each other through CommNet (The two portals have to be able to communicate with each other and both have green signals. The signals can bounce as many times as needed but the route must stay green the entire way through). This would work only on bodies without an atmosphere, and in space. In order to function in-atmosphere, the portal part would need an airlock. Said airlock would be a deployable space made of "hardlight" or some form of tarp (textures would be interchangable for people who don't like scifi. Then again, why would they be using a portal mod if they don't like scifi. Whatever.). A ship would need to fit inside the airlock, which would need an increasingly large amount of electric charge to hold open (because it's hardlight) the bigger it gets. But what if you want to go somewhere else but you already have two portals set up? Easy, just switch the target location on the portal "here" portal to the desired "there" portal (all portals function as both "here" and "there" portals at the same time). Why does it exist? It's a colonization mod that I just thought would be a cool thing. Unfortunatley, I have next to no skill and would probably grow bored of maintaining the mod quite quickly, if it ever became a thing in the first place. That's where you guys come in. Anyone and everyone can make this mod, I'm simply bringing up the topic. Well, that's everything I have to say. Bye!

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

So I'm playing on ksp 1.2 with kerbalism and interstellar and some other mods I'll post them later but,I'm trying to make a warp ship to blalo in kss which can carry 1000 tons. I hope that some of you guys can help me out and also learn from others. -Thanks Devan

So, i'm fiddling with USI kolonization tools and found myself thinking of colonizing new stars. proceeded to download 1.2.2 compatible star mods. However, the journey cost and time is too damn high! So, i first downloaded Interstellar extended, to see it's many massive radiators, receivers and other things i propably wont use. I was interested in the Warp Drive. I also have Roverdude's warp drive mod. Still, i'd love to see more warp drive mods, as i plan on making big colonising crafts to conquer those new systems. Queue next issue: kerbal transport. As much as i love designing big ships, i realised that transporting kerbals to my ever-growing colonies is not an option all of the time. Money and logistics of such operations can be too much. So, if anyone could point me towards a mod that would allow my kerbal to multiply in numbers in their bases, (preferably compatible with CTT's "colonization" node in 1.2.2) i'd be greatful. o7

Hello, this time I thought a idea for a mod of advanced hypothetical methodes of propulsion, but I can not make this. This is the clasification and short description of each one: Esencial for the mod: - Diametric drive: a type of propulsion that would make use of regulated non-conservative gravitational field with non-zero curl, ie, a similar thing like "gravitational field with two poles", obtaining a zero energy acceleration. - Disjunction drive: similar to diametric drive, but would make use of permanent non-conservative gravitational field with non-zero curl, controlling the acceleration by de distance of "gravitational poles". - Pitch and bias: unlike diametric and disyunction drive, this method would not make use of regulated non-conservative gravitational field with non-zero curl, but would change the gravitational constant back and forth. - Differential sail: a engine that would generating negative pressure/energy (casimir effect) forth of this, and positive pressure back. - Warp/Alcubierre drive: a type of propulsion that would move the space arround the starship instead the starship. Other, not needed and very difficult to make: - Worm hole: two distant points of space interconected, ie, a thing like portal with spheric shape. Note: the non-conservative gravitational field with non-zero curl is hypothetically possible with negative masses (and hypothetical particles) together normal masses, this is, a negative mass would repelled by positive mass (and positive also), but would have negative inertia, and this mean atraction instead repulse, originating a lineal move of possitive and negative masses. New materials: - Negative energy/pressure: a density of vacuum required to make work the warp drive, differential sail, worm hole, etc. New parts: - Negative energy generator: a part that produces electricity to generate negative energy deinsity (only work when there is a receptor, ie, a exotic engine with negative energy storage space). - Diametric drive reactor: a part that works like engine, requires store negative energy to accelerate, more negative energy, more acceleration, until 10m/s^2 (variable per total mass of ship); and destroy negative energy to not accelerate (when destroy negative energy, consume electricity); is slow to change these actions. - Disjunction drive reactor: a part that works like engine, not requires store negative energy, only consume electricity to separate or bring near the two reaction masses; when separate the reaction masses, not accelerate; when bring near the reaction masses, accelerate until 20m/s (variable per total mass of ship); is very fast to change these actions. - Gravity constant reactor (Pitch and Bias): a part that works like engine, not requires store negative energy, but consumes a lots of electricity when change the acceleration, accelerate until 50m/s^2. - Warp drive reactor: a part that works like engine, consume and destroy negative energy when is active, but consumes more electricty than the produced for the generation of negative energy; her work althrought change directly the velocity instead the acceleration, and when not work brake to original velocity. The acceleration by previous methods cancel the G forces. - Differential sail engine: a engine that only consume negative energy, accelerating like another normal engine, with G forces and low power. Idea based in: http://ntrs.nasa.gov/?N=0&Ntk=All&Ntt=breakthrough%20propulsion%20physics&Ntx=mode%20matchallpartial&Nm=123|Collection|NASA%20STI||17|Collection|NACA||125|Collection|NIX