Jump to content


  • Posts

  • Joined

  • Last visited


3,550 Excellent

Contact Methods

Profile Information

  • About me
    Junior Rocket Scientist
  • Location

Recent Profile Visitors

19,077 profile views
  1. Correct, there is no special HeatShifter config required. The only thing that must be added is the line "maxTempAngleOffset = 0" inside the Atmosphere node of the planet's config. My spreadsheet already adds this, so as long as you copy and paste from my spreadsheet to your config, you should be good. In fact, the offset angle can be anything you want it to be. A value of zero means that the hottest time of day occurs at noon (or at the subsolar point for a tidally locked planet). An offset angle of 45 degrees means the hottest time of day occurs midway between noon and sunset. (An offset of 45° is hardcoded into stock KSP.)
  2. @Cruesoe, to fix this you have to use the variable Dm instead of D in your DisplayDate config (also Dmth instead of Dth). D is the day of the year while Dm is the day of the month. I'm also planning to release JNSQ v0.10 at some point in the not too distant future. When that happens the intialRotation and offsetTime changes will be incorporated into JNSQ. You'll therefore need to delete this from JNSQRealDate when v0.10 drops.
  3. Did you install GEP_Rescale? GEP is built to a different scale than JNSQ, so it's designed to work with JNSQ only if you resize it using the optional mod GEP_Rescale, which comes packaged with GEP. In addition to resizing GEP, GEP_Rescale also fixes some things that JNSQ breaks, including the scatterer atmospheres.
  4. The current JNSQ version was never designed to work with other planet packs. However, GEP does include an optional addon that is suppose to make it compatible with JNSQ. The responsibility for making to two work together is on GEP, not JNSQ. If something doesn't work it should be reported there. That being said, I've never observed any issue with scatterer atmospheres when GEP and JNSQ have been installed together. Not sure what the problem is. There has been no effort to make GPP work with JNSQ, so there is no support available for that.
  5. I'm just waiting to see how Gordon gets off Nara. Curious to see if his hydrogen-breathing engines factor into the equation.
  6. Yes, but I don't remember what caused it. I'm thinking it might have been a scatterer related issue, but I'm not sure about that. I recommend that you start uninstalling mods and try to figure out what's causing it that way.
  7. There's no firm target date for an update, but I hoping it will be sometime in the next couple weeks.
  8. At this point I'm planning to remove Kronometer from JNSQ and instead list it as a recommended mod. The user will have to download and install Kronometer separately.
  9. There are no Parallax configs written for GPP, so there's no point having it installed. Would be best to uninstall it. We hope to make GPP Parallax compatible as some point in the future, but there's no schedule for making that happen.
  10. Most of the changes have already been pushed to GitHub. But to be honest, I really don't know what it all includes. I'm going to have to look over 19 months worth of commits to figure out what's been done and get it all into a changelog. Along the way I might discover it's not release ready and requires more changes.
  11. There won't be anything silent about it. It will be a pretty significant upgrade with 1-1/2 years worth of changes that have never been released. It's about time we get JNSQ up to date. There will be an announcement about it here with a lengthy changelog. If there is anything about it that has the potential to break existing saves, we'll issue warnings. (It probably won't be version as the updates are more significant than that minor version number change suggests.)
  12. I'm considering doing that. That's correct, it's the ribbons for the celestial bodies added by JNSQ. The Final Frontier mod includes the ribbons for the stock bodies.
  13. It should work in either, but since you're installing it separately, it probably makes more sense just to put it directly in GameData. We're likely going to delete it from JNSQ in the future, so a separate install is probably going to be the way forward.
  14. I don't really pay much attention to pitch vs. altitude. My rule of thumb is to hold the "time to apoapsis" at about 50 seconds. If it starts to fall below 50 s, pitch up a little bit, and if it starts to climb above 50 s, pitch down a little. And if it starts to run away to where I can't control it with pitch alone, throttle back. Only during the final moments of ascent does the time to apoapsis start to rise well above 50 s.
  • Create New...