• Content Count

  • Joined

  • Last visited

Community Reputation

3,779 Excellent

About ProtoJeb21

  • Rank
    TESS Citizen Scientist

Contact Methods

  • Skype Array
  • Twitter Array

Profile Information

  • Location Array
  • Interests Array

Recent Profile Visitors

74,275 profile views
  1. @R-T-B The planet pack I'm developing ran into an error with 1.10-1. I got a message once the game loaded that "Kopernicus was not able to load the custom planetary system due to an exception in the loading process". Here are all of the recommended log files: I love how Kopernicus now automatically creates a zip file with a copy of the KSP log file, the planet log files, and ModuleManager.ConfigCache. This is going to make bug reporting far easier. NOTE: all 8 of the terrestrial planets currently lack a color and normal map, and are currently only using a flat height map. This is just the first test to make sure they load in properly. A proper height map will be given to each later on, and I will build the color and normal maps via KittopiaTech (assuming it will work).
  2. As I should've anticipated from the name of the patch, Kopernicus 1.9.1-9 does not work in KSP 1.10.1 (although the Nyan Cat loading screen does). And I had just spent the last hour or so prepping the configs for a system of nine planets I'm working on.
  3. My main method of creating planet textures — well, the main method from when I was actually making Kopernicus planet packs — was to customize a planet in SE, export its height map, and use that as a base to create a better height map using a variety of PQS mods (vertexsimplexheight, vertexsimplexheightabsolute, vertexheightnoise, vonoroicraters) and a color map via vertexheightcolor. The reason for an SE height map as a base is because it can include some smaller details and ideal continent/ocean shapes that are difficult to replicate with PQSMods. For example, often I want only a few areas of some mountains, but PQSMods will generate mountains and hills all over the surface and not in specific areas. Custom SE height maps give me the specific terrain details, and PQSMods help refine it. I only mentioned using pure SE textures as a last resort option. They might look cool from a distance, but most surface details scale terribly from SE to KSP (hence why I try to refine the height maps I get and make sure they’re the maximum resolution possible). And trust me, I know plenty well how poorly SE textures are received in the Kopernicus community.
  4. So, just for clarification, since I've been absent from the Kopernicus community for ages: Has the time warp altitude limit feature been removed now that there are no longer altitude limits for the stock bodies (except for the minimum time warp altitude)? Is KittopiaTech permanently not working? Will there ever be a feature to generate and update textures/height maps like it? Have PQSMods remained the same since 2018/19? I'm under the assumption that the latest patch(es) work for KSP 1.10.1, but since I'm hoping to develop a new planet pack in the coming weeks (I'm almost finished calculating the physical, orbital, and atmospheric parameters of all objects I currently plan to add), I'm mainly concerned about whether or not Kittopia can ever be used. I suck with custom terrestrial planet textures, and I can't even fall back on Space Engine textures for two reasons: I'd need to spend $60 on SE Pro for the texture export feature, and the latest update broke the game for me and now 99% of all objects won't load due to an issue with shaders.
  5. Today I rode out my second tropical storm of the year so far, Isaias. I live in CT and don’t often get tropical cyclones, but the 2020 Atlantic hurricane season has seen record levels of activity prior to August 1st, and many of these storms have impacted land. TS Fay formed off of the VA coast and tracked into the tri-state area in mid July. It weakened rapidly after making landfall in NJ and only brought mild rain and moderately gusty winds. Isaias turned out to be a far more significant storm. Heavy rainfall started in the late morning, with winds maxing out from 1-4pm. I couldn’t measure them directly but I wouldn’t be surprised if gusts were confirmed to have consistently hit 50-60 mph. I lost power for about 10-15 minutes, and then it was on and off for an hour or so. Unlike Fay, there was moderate wind damage, with a couple of large branches falling in my neighborhood and debris from trees being scattered everywhere. At least 40% of my town lost power. No fatalities in the state, as far as I know. It’s cleared up now but some occasional gusty winds are still present. Somehow, my crippled tomato plant survived. A thunderstorm caused the stems to crack in early July, and it survived both Fay and Isaias without taking additional damage. I was sure that half of it was going to get torn off. Now I’m just hoping we don’t get yet another tropical cyclone this year in the Northeast, but since it’s 2020 and this season is expected to continue being extremely active, we probably are going to get something else eventually.
  6. Some positive news from the United States. After the massive spike in new cases per day starting in early-mid June, it’s started to level off over the last two weeks, with a mean of ~65k cases/day. Yes, that’s really high, but the increasing trend appears to have stopped. It took a nosedive to only 47k new cases yesterday, the lowest daily total in weeks. The Big Four of this second wave — Arizona, California, Florida, and Texas — have either leveled off or have shown a slight decrease in new cases per day, signaling that their exponential COVID growth has ended. The Northeast states have remained stable throughout all of this (Connecticut has kept a daily positivity rate of 0.5-1.2% since June), and some other states are showing signs of slowing down; these include Oregon, Idaho, Arkansas, Ohio, Alabama, and more.
  7. We’ve got some trouble on the horizon for the May 27th launch date: several models try to quickly spin up a weak tropical cyclone around Florida between Wednesday and Friday, and the European model is forecasting a lot of rain for Florida duding that time frame. The Euro, GFS, and CMC are also on the fence about maybe another tropical cyclone forming more in the open Atlantic at the end of May/start of June, which I heard could impact booster recovery, depending on if the launch is delayed.
  8. India and Bangladesh were thankfully spared from the Cat 4+ landfall some models were showing (mid-level shear disrupted the storm during an eyewall replacement cycle and prevented it from ever recovering), but the biggest issue was not the maximum wind speeds, but rather the storm surge. Amphan had a very large wind field prior to landfall, which had expanded due to the EWRC, and this area is always extremely vulnerable to surge because of the V-shape of the BOB and how low-lying it is. You don’t need an ultra-powerful storm for destructive surge; just look at Ike (Cat 2 landfall) and Sandy (Cat 1, technically post-tropical at landfall). I don’t know how things have folded out near Amphan’s landfall, but it’s not going to be good regardless.
  9. The directly imaged exoplanet Fomalhaut b, later formally named Dagon, was just determined to be the debris cloud from a pair of large icy objects colliding within Fomalhaut’s debris disk: I guess you can say...Dagon is gon.
  10. Humans: hey look, a bright comet is coming! Finally something to make 2020 good! Comet Atlas:
  11. Atlas is starting to develop a tail and looking less like a fuzzy blob: It’s around V=8.2 right now. If I’m correct, that’s one of the brightest comets we’ve had since PANSTARRS.
  12. Day 19 of Coronavacation: Distance learning started yesterday, and I’ve been dumped with tons of Calculus work that I barely have any idea how to do. This seal now supports my dwindling sanity. 


  13. Comet ATLAS may have been brightening faster than expected, but that isn’t a guarantee that it’ll become the next great comet:
  14. After ISON, we all have a good reason to be skeptical about the next bright comet. The media ran with the “comet of the century” stuff for almost a year before perihelion, and look what happened. Predicting comets something like ten months out won’t end well.
  15. The rather newly discovered Comet ATLAS has been brightening faster than initially expected, and now it’s believed it could reach naked eye brightness by the end of May, possibly reaching or even exceeding the brightness of Venus. What’s more exciting is that this could FINALLY be a bright comet visible in the Northern Hemisphere, best observed in latitudes 40-60 N. There’s always a chance it could be a bust like ISON, but since we’re only two months away and not 10+, I think ATLAS has a better shot of living up to the (pretty new) hype. Here’s one of the articles published in the last few days about ATLAS’s peak and how to observe it: UPATED 4/7/20: Atlas has died of corona