Jump to content

Raptor42

Members
  • Posts

    112
  • Joined

  • Last visited

Reputation

83 Excellent

1 Follower

Profile Information

  • About me
    Worshiper of Kraken
  • Location
    Looking for some spicy MEMEZ

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Mine favourite old version would be 1.4 since it is the latest version that supported Gameslinx's Planet Pack, and I found out that you can use newer part mods, such as ReStock, on older versions with almost no problems.
  2. Hello, I was playing BH on 1.11 and stumbled upon a problem: when I had craft landed on Armstrong and tried to land with my other craft near it the landed craft either fell through the terrain completely or partially clipped into the terrain. I have the tesselation option in Parallax settings completely disabled. It always happened when entering the physics load range and upon entering it, the landed craft clipped into the terrain as mentioned above or was flung off into the "air". Any idea on what might be the cause of this issue? Or is it just KSP being KSP?
  3. Ok, issue solved, it was a problem with scatterer, updating to latest version of scatterer fixed it.
  4. I have had an issue where simply launching a vessel including a part (specifically stock Mk2 lander can, and NF Spacecraft Mk4-1 command pod) caused sunflares (from scatterer sunflares) to disappear. I have pretty good idea what might have caused this, but I am not sure HOW exactly. I have checked and it is definetly caused by those parts. One thing that those 2 parts have in common is the fact, that the part switch menu allows switching between different models of the part (i.e. rover and lander versions of the Mk2 lander can). I have now checked and it is, in fact, caused by the switching module of the part (in the Mk4-1 pod's case at least, verified by removing the module and the sunflares working properly after that). I am now wondering what has the switching part to do with sunflare disappearance... any suggestions welcome. PS: How do you duplicate parts to compensate for this switching problem, will copying the .cfg file and replacing the referenced model for it work just fine or do I have to do something more complicated?
  5. You can move KSP to external drive and it will work just fine, even without Steam. The mods you are using should not be affected by this move, since they are stored in GameData folder that is part of the KSP folder. One thing that might be a problem is updating the game, but mods may not function properly when uptating tha game to another version. So I would suggest keeping modded game in other folder than where steam puts it. If you would like to keep your progress, your saves are stored in Saves folder, that is stored inside the KSP folder as well, so when you update, you can just copy this folder to the new updated KSP folder.
  6. What you need to calculate is the orbital period for the transfer orbit, then you can do the rest. The calculation for your burn longtitude should be: Desired long. + 180 + how many deg. will Kerbin rotate when you get to Ap* for kerbin it is transfer time in minutes
  7. I suggest buying the KSP1, if you wait for sale on Steam, it will cost about 10-15€. KSP2 will probably cost 60€ Plus there is a ton of mods for KSP already, so you have plenty of options, if you like that sort of stuff.
  8. I have not done the entire calculation myself but here's something that might help you: 1. Suppose that your vessel is in circular orbit and can do the entire transfer burn at once. 2. Calculate the semi-major axis of your transfer orbit, that is -> [(your current altitude in km + 600* km) + geostaionary orbit altitude in km + 600* km] / 2 *Note: the 600 km is the radius of Kerbin 3. Using Kepler's third law calculate the orbital period of your transfer orbit (μ is the standard gravitational parameter (for Kerbin it is about 3.531× 103 km3/s2 ), a is the semi-major axis), then divide it by 2 (to get your time from Pe to Ap) 4. This is your time to Ap (in seconds), which means that when you reach Ap, the point you're trying to reach is now (that is, when you do your transfer burn) this amount of time "behind" compared to when it will be when you reach Ap. For example if you depart from about 300km orbit going to the geostationary orbit (2863 km-ish) the point that will be directly under you when you reach Ap is the same point you are perfoming your burn above -> this means that the time it takes you to from Pe to Ap is exactly the same as the time it takes Kerbin to rotate 180° 5. SOME NOTES: Kerbin rotates at the rate of 1° per minute, so you can take the time to Ap you calculated, divide it by 60 to get how many degrees will Kerbin rotate. You then want to have your desired point this many degrees behind where the Ap will be. 6. You really don't need to do this calculation when you do this manually, you can just create the maneuver node in-flight to see how much time to Ap it will take and just perform step 5. I hope it helps you in some way, good luck trying to translate this into kOS program, and also I hope that this explanation makes at least some sense. You really don't need the mass of your probe as it is almost none compared to Kerbin and also the planets are on rails, which means that your ship will NOT pull Kerbin at all.
  9. I am pretty sure that the latest version is the same for Mac and PC. I don't see why they should be different.
  10. MechJeb then remotely armed weapons that even the engineers didn't know were present on the mothership, aiming them at incoming lander
  11. Thanks for explaining this, and as far as the sound goes, I am not aware of any other sound files that are in the install folder .
  12. I have to say that the planets look great. I have been only to Lua during my new carrer mode and I found one interesting thing about the experiments you added (rocks sampling etc.): the game registers it as different experiment when you sample the object while flying and while staying on ground. There is also an interesting story about my journey to Lua: I have my lander in orbit, land in one of the craters, do experiments and so on, leave, dock with my main ship and then... I notice I forgot to plant a flag as part of the Strategia contract for Lua Exploration... sooo second landing it is, this time in highlands. I land, do the experiments and then leave. On my journey to orbit I encounetred the Lua terraformer for the first time, it looks fabulous, however it's kinda sad that scatters load only when you get quite close to them, especially in the case of the massive structures that you added. I hope I won't crash into them (oh yes, I will...at some point). When I got back to orbit I noticed.... yes..... exactly that..... I DIDN'T PLANT A FLAG...... AGAIN. Well then I guess I'll just take the science and plant a flag another time if I remember to do it. Also one last thing: I looked at the sounds you added with the modpack, I now feel so smart after listening to them. Edit: I just landed on the other side of Rhode, recovered my craft and in the recovery screen it says "Recovered - 132,9km from Lua Base Launchpad" and it gives me about 92% funds from recovery, do you have any idea what could be the cause for it, because one thing I know for sure, Lua definetly isn't only 132km away from Rhode.
  13. I hope that we'll have REAL landing gear that works instead of pogo sicks that smash your entire plane to pieces the moment you touch the ground.
  14. Usually when I start up the game, it eats about 6-7 GB of RAM on startup, so the story goes as follows: I started my game as usual, launched few rockets, normal stuff. Then I went away for like 20-30 minutes and I left my game paused in orbit. Then after I returned, I noticed that the RAM usage went down from the usual 6-7 GB to only about 3-4 GB (even when I unpaused). Does anyone know what could've caused this unusual behavior? I don't complain or anything, it just surprised me a bit.
  15. Today I "experimeted" with the game to see what I can do to it before it stops working. Here's what I found. 1. Always have clean/stable gamedata folder as a backup. 2. DON'T try putting old mods to newer versions of a game. 3. Surprisingly, part mods that are meant for newer versions usually work just fine when used in old versions 3.5. You can completly replace the parts folder with newer ones (for example parts folder from 1.4 can be replaced with parts folder from 1.8) Now I can finally play my Gameslinx's Planet Overhaul (version 1.4) game with ReStock and new parts installed.
×
×
  • Create New...