Jump to content

AG5BPilot

Members
  • Posts

    156
  • Joined

  • Last visited

Everything posted by AG5BPilot

  1. Another problem now: Downloading "https://github.com/Galileo88/Galileos-Planet-Pack/releases/download/1.6.1.1/Galileos-Planet-Pack-1.6.1.1.zip" Oh no! It looks like you're trying to install a mod which is already installed, or which conflicts with another mod which is already installed. As a safety feature, the CKAN will *never* overwrite or alter a file that it did not install itself. If you wish to install GPP 1:1.6.1.1 via the CKAN, then please manually uninstall the mod which owns: GameData/GPP/Cache/Agrippina.bin and try again. Your GameData has been returned to its original state. Error! That was from the GUI. This is from the cli version: ckan upgrade GPP Upgrading modules... Unhandled Exception: CKAN.FileExistsKraken: Trying to write C:/KSP/KSP 1.3.1 GPP 1.5.3/GameData/GPP/Cache/Agrippina.bin but it already exists. at CKAN.ModuleInstaller.CopyZipEntry(ZipFile zipfile, ZipEntry entry, String fullPath, Boolean makeDirs) at CKAN.ModuleInstaller.InstallModule(CkanModule module, String zip_filename) at CKAN.ModuleInstaller.Install(CkanModule module, String filename) at CKAN.ModuleInstaller.AddRemove(IEnumerable`1 add, IEnumerable`1 remove, Boolean enforceConsistency) at CKAN.ModuleInstaller.Upgrade(IEnumerable`1 modules, IDownloader netAsyncDownloader, Boolean enforceConsistency) at CKAN.CmdLine.Upgrade.RunCommand(KSP ksp, Object raw_options) at CKAN.CmdLine.MainClass.RunSimpleAction(Options cmdline, CommonOptions options, String[] args, IUser user, KSPManager manager) at CKAN.CmdLine.MainClass.Execute(KSPManager manager, CommonOptions opts, String[] args)
  2. I'm still having the same problem. Is "a few" more or less than 8? Sorry if I seem impatient; I'm not. I'm concerned it's not going to resolve itself and needs some sort of intervention.
  3. I posted about it in the CKAN thread also. I'm having trouble installing this latest version with CKAN... ckan upgrade --all Upgrading modules... Downloading "https://github.com/Galileo88/Galileos-Planet-Pack/releases/download/1.6.1.1/Galileos-Planet-Pack-1.6.1.1.zip" 12.7 MB/sec - downloading - 92.2 KB left - 99% Unhandled Exception: CKAN.InvalidModuleFileKraken: C:\Users\Mike\AppData\Local\Temp\tmpB82D.tmp has SHA1 EF179B24AF5C10E000C6AD10D35 11DF8919BB594, should be 95BB6B4ECDCAC1B7F0A62E352AE0B5787720893D at CKAN.NetModuleCache.Store(CkanModule module, String path, String description, Boolean move) at CKAN.NetAsyncModulesDownloader.ModuleDownloadsComplete(NetModuleCache cache, Uri[] urls, String[] filenames, Exception[] error s) at CKAN.NetAsyncModulesDownloader.<>c__DisplayClass8_0.<DownloadModules>b__3(Uri[] _uris, String[] paths, Exception[] errors) at CKAN.NetAsyncDownloader.triggerCompleted(Uri[] file_urls, String[] file_paths, Exception[] errors) at CKAN.NetAsyncDownloader.FileDownloadComplete(Int32 index, Exception error) at System.Net.WebClient.OnDownloadFileCompleted(AsyncCompletedEventArgs e) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boole an preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean prese rveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() ckan version v1.24.0+195ed164d95f
  4. This had been working for a couple of days, now there's a problem: ckan upgrade --all Upgrading modules... Downloading "https://github.com/Galileo88/Galileos-Planet-Pack/releases/download/1.6.1.1/Galileos-Planet-Pack-1.6.1.1.zip" 12.7 MB/sec - downloading - 92.2 KB left - 99% Unhandled Exception: CKAN.InvalidModuleFileKraken: C:\Users\Mike\AppData\Local\Temp\tmpB82D.tmp has SHA1 EF179B24AF5C10E000C6AD10D35 11DF8919BB594, should be 95BB6B4ECDCAC1B7F0A62E352AE0B5787720893D at CKAN.NetModuleCache.Store(CkanModule module, String path, String description, Boolean move) at CKAN.NetAsyncModulesDownloader.ModuleDownloadsComplete(NetModuleCache cache, Uri[] urls, String[] filenames, Exception[] error s) at CKAN.NetAsyncModulesDownloader.<>c__DisplayClass8_0.<DownloadModules>b__3(Uri[] _uris, String[] paths, Exception[] errors) at CKAN.NetAsyncDownloader.triggerCompleted(Uri[] file_urls, String[] file_paths, Exception[] errors) at CKAN.NetAsyncDownloader.FileDownloadComplete(Int32 index, Exception error) at System.Net.WebClient.OnDownloadFileCompleted(AsyncCompletedEventArgs e) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boole an preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean prese rveSyncCtx) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() This is with the latest version of CKAN: ckan version v1.24.0+195ed164d95f
  5. Yup, yup, just wanted to give you a data point to work with. The one obvious thing I didn't check while playing was whether objects already landed on a planet survived the transition to a new Kopernicus version.
  6. I jumped right in the pool when it showed up on CKAN, knowing it was a risk. I encountered no problems, other than the flickering orbit lines coming back because the fadeout code which fixed that was removed. Pick your poison -- flickering orbit lines, or orbit lines that fade out too soon. Other than that everything I did seemed to be okay. No problems with my saved game.
  7. To be fair... Github announced this change back in July, I think, and they even did a one hour "brown out" earlier this month where they turned off TLS 1.1 to try to get the attention of people who hadn't already read the appropriate notices. As a publisher of information, it's very difficult to make sure you reach all the people who need to have the information, and as a consumer of information, it's very hard to stay on top of everything when there's so much out there. It's nobody's fault. Everyone is trying to do their best. And, yes, a superb job was done by everyone for diagnosing and fixing CKAN in less than a day.
  8. If I had to guess, the herd of cats is an indicator that MM is unable to connect with Github to check if there's a new version available. That, in turn, could be because Github deprecated TLS 1 today. (That broke CKAN today.) It could be just a coincidence that the cats appeared when Github deprecated the protocol, but it seems like a likely culprit.
  9. Updated GPP, the textures, and Kopernicus via CKAN. Everything worked perfectly, as far as I can tell, and memory usage is way, way down. Excellent work!
  10. In my experience, 8 GB simply isn't enough. Should you decide to try making lower resolution textures, I wish you luck. But if it's at all possible, I would strongly recommend upgrading to 16 GB.
  11. I personally don't mind if the visuals change, and download bandwidth isn't a consideration. As far as I'm concerned, go for it!
  12. Yes, quite recognizable. That's clearly the T-65B X-Wing from the original trilogy. But if, by chance, you were referring to the planets, did you mean you've updated the textures and we should download them now, or did you mean that you're considering replacing the textures in the next release? Would the texture replacements have any effect on save games? EDIT: On second thought, I take that back. It looks more like the the T-65B than the T-85, but the laser cannons don't look right. Maybe it's not so recognizable after all.
  13. What I do, and what I suspect many people do, is keep the Steam installation not only stock, but also never played. It's just where Steam delivers the game. I then copy KSP from the steam folder to someplace else, and modify it and play it there. I usually have three or 4 copies of KSP with different sets of mods, but I never play in the real Steam directory.
  14. Very nice, however, there's already a website that will do this. It comes preloaded with the stock planets, but it does allow you to add your own planets. It's actually designed for RemoteTech, but it works perfectly well for any satellites. It also includes orbital eclipse periods and calculates battery requirements as well as EC production requirements. In addition to giving you the orbital parameters for launching a satellite constellation from a single carrier spacecraft (useful for everywhere *except* Gael), it also gives you the timing for launching satellites individually, which is how one would usually do it around Gael. https://ryohpops.github.io/kspRemoteTechPlanner/#/planner EDIT: I suggest that when you select "dive orbit", you show the resonant orbit's periapsis rather than its apoapsis. Also, showing the atmosphere height and the SOI may be useful, especially if the resonant orbit goes near either one.
  15. Upgrading to GPP 1.5.88 did, indeed, solve the problem for me. Thank you!
  16. I'm still running the previous version of GPP (1.5.3) and I'm seeing the same problem -- everything is in shadow. Spacecraft in orbit never show any lighting from Ciro -- there's uniform lighting all around the spacecraft. Solar panels ARE working correctly, however. I'm not 100% sure when this started. Various mods get updated, and one of those updates (no idea which, unfortunately), caused this problem. (Several weeks passed when I wasn't playing but was updating the mods, which is why I'm not sure where the cause lies.)
  17. There's three mods I use that can help with funding, Extraplanetary Launchpads, Strategia and Stage Recovery. Yes, you can use Extraplanetary Launchpads as a business to build off world and then recover, but it's just as useful simply for building spaceships without having to pay anything for them. (Although see below; if you're making a profit on launches this isn't an advantage.) Stage Recovery lets you recover most of the cost of your boosters, or more stages if you're creative enough. It can significantly reduce costs. Strategia is a very interesting replacement for the administration building and gives you a whole new set of strategies to choose from. If this is your priority, you can choose strategies that are very profitable. One strategy will reduce launch costs by up to 75% -- and another rewards you for getting large payloads to orbit. It's possible to make a profit on each launch, especially when combined with Stage Recovery.
  18. Unless something has changed and my spreadsheet is out of date (always a possibility of course), the scanners and planets where you'll have trouble are: Lilli: SOI is too low for the DMOS multi-spectral scanner or the soil moisture scanner (50 km). Otho and Nero: With a 600 km and 560 km atmospheres, the only instruments that work are the stock resource scanner (max: 1000 km) and SAR (max 800 km). Everything else in stock or DMOS has a maximum height of 500 km or less. Gauss: The atmosphere is higher than then 300 km maximum height of the DMOS multi-spectral scanner. I vaguely remember that a while ago (several years) the stock scanners were modified to work on particularly large or small planets by adjusting their range limits, but I may be remembering that incorrectly. If the stock biome scanner works at Otho, that would be why. I haven't tried scanning the stars, but based on their wiki entries everything except the DMOS soil moisture scanner should work at Grannus and nothing should work with Ciro.
  19. You'll need radiators there too. Off the top of my head, I don't remember whether Icarus or Thalia was hotter. Icarus is very close to the star, while Thalia's heat source is internal (it's radioactive). Both require attention to cooling systems, and on both Kerbals can only survive on the surface for a limited time. Also, unless it's changed in the latest GPP release, there's almost no ore on Thalia. You can mine Karbonite, but ore is very rare there. Eta is a perfectly fine place to set up a base, however.
  20. Not for Eta -- at least not for the environment. If you're running equipment that produces heat, you'll need radiators for that, same as anywhere. Otherwise you'll have no problem with heat. Thalia is deadly hot. You'll definitely need radiators on the surface, and even in low orbit.
  21. That pusher canard design is actually very popular kit planes, most of which are derived from Burt Rutan's VariEze. There was also the twin turboprop Beech Starship. https://en.wikipedia.org/wiki/Beechcraft_Starship If your KSP version is built correctly, it can't stall in a normal fashion because the canard will stall before the main wing, which will lower the angle of attack and prevents the main wing from stalling. Here's a four place design I'm fond of: http://www.velocityaircraft.com/ Many of my KSP aircraft are also canards, although I never build an inverted gull wing. It looks great.
  22. Assuming you still want the awesome goodness of RealChute, head over to their forum thread. There's an MM patch config file that will restore the parachutes to the the VAB (but in the Utility tab since the parachute tab is missing.)
  23. Are you using RealChute? And what do you mean by "the parachutes don't load"? If you're using RealChute and your problem is that chutes no longer show up in the VAB, that's a known problem with the current version of RealChute. There's several work-arounds for this problem and you can find more information in the RealChute forum thread. If that's not your problem, I'd go the opposite route: start with an unmodded KSP and add mods one at a time, starting with any mods that might affect parachutes (such as RealChute).
×
×
  • Create New...