Search the Community
Showing results for tags 'persistent'.
Lots of thanks (and cookies) to the following people: @White Owl, @MK3424, @xXIndestructibleEVAXx - for giving the mod a name. @BahamutoD, angavrilov, SilverFox, darklight - for helping me getting started with KSP modding and answering lots of dumb questions. @MK3424, @Unknown Venom - for helping me test my mod and becoming friends @Heretic391 - for creating a video featuring my mod @whale_2 - for contributing and maintaining the mod Virindi-AC - for fixing lots of bugs dkavolis - for cleaning up the code Please leave comments on your experience! Donate If you like this mod and you want to show your support, you can safely donate via Paypal and make me a happy developer. Description Momentum and Rotation in KSP are quite unrealistic and don't meet the needs of most players. So I have created this mod, with many features to make this aspect of the game better! PersistentRotation by heretic391 Beginners guide on GitHub wiki Feature Trailer on YouTube [deprecated] Feature List - Persistence of Momentum through timewarping and restarts. - Momentum Autopilot, keeping your vessel at fixed RPM. - Non-physical spin simulation when vessel is warping or unloaded. - Reference Rotation in both realtime and timewarp, 100% persistent.* - Slight spin for every Asteroid per default. - Simple & intuitive GUI supporting both Stock and Blizzy's Toolbar. License: GNU General Public License v3 Download Download PersistentRotation via CKAN and keep it up to date! or download it directly: PersistentRotation on SpaceDock GitHub Releases Manual Installation To install, just extract the .zip file and put the contents of the included GameData folder into your KSP/GameData folder. Warning: Do not copy old cfg files over to a newer version of PersistentRotation! It is not backwards compatible and doing so could result in errors! GitHub GitHub Repository Changelog: 1.8.6 - Updated for KSP 1.8 - Minor corrections Older Versions: Known issues & requests: See GitHub Issue Tracker
Hello my fellow Kerbals, I wanted to create this thread to test the waters and get an idea of the amount of people who would be interested in taking part in a persistent shared space program. For years me and my two brothers (all early to mid-20s with various career paths from engineering to accounting) have conducted joint space programs together in the standard KSP manner of coming up with mission ideas and passing around the share file. We have traditionally made our space program a USSR themed Soviet era type space operation for kicks. I thought it may be fun to make this more formal and open it up to the community. If you are interested keep reading I have come up with some ideas on how to keep this organized as well as the general game guidelines. 1. Space program divisions and Chain of Command 2. File settings and rules * File Settings: -The file would be vanilla KSP no mods to keep sharing simple -File would be backed up when shared, the backup would only, be used if someone was to intentionally spam the file i.e. destroy all our space stations, launch a bunch of rockets without approval etc.. * Game Settings & Rules: -Biggest rule- DON’T KILL JEB I love that crazy little guy. -The game would be set to hard (no quick saves revert flights perm death etc..) again don’t kill Jeb -Game will be set to sandbox mode (don’t worry operations Division 2) will keep you busy -To keep things “realistic” all Kerbals would have a 5 year contract, example being if Jeb goes to a space station on year one a retrieval craft needs to pick him up on year 5. A tracking sheet (see section 3) would be kept for all Kerbals on mission and the HR director would be responsible for communicating with operations to ensure all Kerbals are being relived -Be Honest, its ok to crash, leave a Kerbal in space etc.. It keeps things interesting. Division 4 (Investigations) will conduct a formal investigation but you will not be kicked off the team. Repercussions will consist of anything from temporary license suspension to license downgrade. -When in possession of the file only conduct approved missions, if possible record the operation of the mission. -Only Use Approved Space craft’s see section 3 for further details -All approved missions will be added to the mission tracker (see section 3) Control specialists will be able to request a mission with the Mission Control head. If they are found adequate they will be assigned and given the file along with the file checkout/in sheet see section 3 for further details 3. Approval Forms and documentation -ugh paperwork, I know this sounds boring, but I have designed a system of approval forms and documentation in order to keep the file updated and organized. See below for the required forms by division. Forms will be in word docs and retained and passed along with the file. Division 1 Mission Control- -File checkout/in sheet- Every time a mission specialist is given the file they will be issued a file check in/out sheet where they will record the mission they completed (or failed to complete) as well as Kerbals used/ spacecraft used and start and finish time of the mission (Kerbal UT time). These forms will allow us to actively track the file and its progress so we are not just playing hot potato with the file. -Licenses – Control specialists once they have passed initial mission flight tests will be given a license to conduct missions to their degree of skill. Division 2 Operations- -Mission Request form- can be submitted by the community will detail the objectives and purpose of the mission, operations analysts will read these and submit them to the operations head for approval. If approved it will be added to the open mission log to be completed at the discretion of the mission control head. Division 3 Engineering- -Spacecraft Approval form – Can be submitted by the community or engineers will include the capabilities i.e. delta V, TWR etc.. purpose, and also a checklist to ensure it has all the basic necessary components to function engineers will be allowed to approve Crafts from the community, the Engineering Head will oversee the engineers and also have ultimate approval. Division 4 Investigations – -KID report (Kerbal Investigation report) - KID will provide a report on the results of all investigations conducted. Division 5 HR and Admin – -Kerbal Tracker- will track all Kerbals currently on mission in order to keep track of when their designated contract is up. If a Kerbal is due for relief a mission request will be sent to operations for their recovery. -Mission Tracker- obviously KSP tracks all active missions but this will list and track missions that have been approved but are still open. This will be open to the Control specialists so they request passion of the file -File Tracker- Will utilize the file check in/out sheets to track who has the file and progress made. **Request this request that Blah Blah I know this sounds dumb but it will keep the file organized so we can have some fun! Section 4: conclusion: All positions are currently open YAY! And I am looking for some motivated people who would like to get this kicked off. I have more ideas but I wanted to keep this as an overview to see in anyone is interested. Comment below or message me if you are interested. Additionally please note that due to forum policy rule (2.2.j this post is strictly for recruiting
Hello there! I've been working on my mod, PersistentRotation, for quite a long time. If you never heard of it make sure to check it out, to know what I am talking about. The mod is currently saving it's data into a custom made cfg file. Every time the game quicksaves or switches scenes, a new file is generated. While I have added code to clean up deprecated versions of the file, I still have the feeling that it isn't the optimal solution to store the data. A while ago, I have heard about saving mod data to the game's sfs files. This would of course be a a lot more effective way of storing data. Now, the problem is, my mod saves data per vessel and has no custom parts at all. Could someone explain me how to do this or send me the corrseponding piece of code? Thanks in advance.
Hello. I am have some strange result after trying to update the plugin Kerbanomics for 1.1. When I have the plugin present contracts get broken upon going into the editor and back out to the space center. Contracts will no longer be active and will have disappeared and must be accepted. This prevents any progress and completely breaks career mode. Here is the contract Scenario from my persistent.sfs file. Notice the repetition of some contract types. I believe this is what leads to contracts breaking. I have no idea how my plugin would cause this. Logs or any other info will be provided upon request. Thanks for any help in advance! Here is a link to a copy of my source and the dll I have been using, and the source below for quick viewing