• Content count

  • Joined

  • Last visited

Community Reputation

1,434 Excellent

About Nils277

  • Rank
    Sr. Base and Rover Engineer

Profile Information

  • Location Searching for Spice on Duna

Recent Profile Visitors

8,861 profile views
  1. @Shadowmage Thank you for keeping TU up to date with KSP 1.4.1 I don't really know if this is intentional or not but i have experienced a problem updating to the latest version: Lets take the following code: //Adding the PBR shader to the normal parts @PART[Lynx_*]:NEEDS[TexturesUnlimited] { MODULE { name = KSPTextureSwitch sectionName = Appearance currentTextureSet = KerbetrotterLtd_Base textureSet = KerbetrotterLtd_Base } } //Default texture setup KSP_TEXTURE_SET:NEEDS[TexturesUnlimited] { name = KerbetrotterLtd_Base title = Standard recolorable = false //Plastics MATERIAL { shader = SSTU/PBR/StockMetallicBumped inheritTexture = _MainTex inheritTexture = _BumpMap inheritTexture = _Emissive mesh = Base PROPERTY { name = _Metal float = 0.0 } } } The problem is that there multiple meshes named "Base" in the same part but some use a different texture. In the old systems all mehes keep the texture they have by default. With the new update and the addition of the inheritance they do not. It seems that only the texture from the first found mesh is inherited and then used for all other meshes with the same name. Is this intentional and i have to use different materials?
  2. @Rafael acevedo lol...yeah that was a rather big derp from me...
  3. Addon Localization Home

    Kerbal Planetary Base System is now also translated into german: Kerbal Planetary Base System - [Russian] [Spanish] [Chinese][German] Kerbal Planetary Base System now needs translations into Italian , French , Brazilian Portuguese and Japanese Feline Utility Rovers now needs translations into Italian , French and Japanese
  4. Currently both versions use the old syntax. Will update once TU for 1.4.1 is released.
  5. Just pushed a hotfix to version 1.1.1 and 1.2.1 to fix a loading error of the platform ramp! This migth cause some trouble with CKAN until it runs its next update cycle!
  6. Hmm ok. A craft file or even better the "persistent.sfs" file from your save would help figuring out the issues. What kind of probe core do you use to control the rover(quadrocopter)? I'm not that versed with the "new" communication system but i have the suspicion that maybe the probe core has a limited functionality when controlled via the network. But a can't say for sure, the craft or the better the save with the communication setup will help figuring this out
  7. @JPLRepo Thanks, that was the reason. I though that a crash from running out of memory would have been visible in the crash logs. I tested it on two computers the version on one of them only vanilla KSP + Expansion but also crashed as regular as the one with mods ...seems that Making History alone needs enough ram to trigger the out of memory crash.
  8. Some more news on the update for 1.4.1. All bugs that have been reported (missing texture in IVA-Overlay for airlock, weird behaviour of landing gear and error loading the water drill) have been resolved Last thing to do is finish the german translation (add last missing texts and create KSPedia entries).
  9. Update to 1.1.0 and 1.2.0 ~It's so shiny!~ Changelog: Download: Download version 1.1.1 for KSP 1.3.X and version 1.2.1 for KSP 1.4.X
  10. I'm not really sure what you mean by controlling the craft through a relay in Eves orbit. Are you using some kind of mod to indirectly control the rover? Or are you still seeing the rover as in normal flight progression but the control signal comes through the stock communication network?
  11. In the last 23 hours (where i played ksp ground 4 hours) KSP crashed 20+ times, without any pattern. It crashed when loading a savefile, starting a mission from Making History, launching a vehicle, opening kspedia, recovering a vehicle, adding a part in the editor, reloading assets from the debug console or even when making a screenshot for another bug report. The crash itself is weird. Most of the time i only get a sound from Windows and 'poof' the KSP window is gone. Only once appeared a window saying that KSP crashed. Does this only happen to me? I'm wondering, because i haven't seen anything about it here or in the bug tracker. The output.log created each crash just stopps as if nothing had happened without reporting an error. If this happens to others too, i will create a bug in the tracker with the crash reports.
  12. Small update info for 1.4.1. It seems that i don't have to fix all IVAs, only the rear airlock. All parts will have weird specular lighting when the IVA overlay is enabled but this also happens to the stock parts so i assume its an issue that squad has to solve. I created a bug in the tracker for that. Edit: Well...i had 7 8 crashes of KSP in just 2 hours. Might still take some time to update if this frustrates me too much...
  13. That sound cool! Of course you have the permission If you need a texture source (gimp xcf) or a model source (.blend) let me know.