Laguna

Members
  • Content count

    285
  • Joined

  • Last visited

Community Reputation

246 Excellent

About Laguna

  • Rank
    Sr. Spacecraft Engineer

Profile Information

  • Location Beta Hydri
  1. @NecroBones, I hate to sound like a pest, but those gray stripes you have around the top and bottom of the FTP decouplers are causing a problem for me. They're ugly and present a visual disconnect, so I hid the top stripe of the interstage I made by offsetting it up into the bottom of the stage, but then the decoupler doesn't separate cleanly--it sticks for a moment (how long depends on the separation force) then falls crookedly, i.e. standard clipping problem. Just another of those things I never thought about, as I used to use the MRS decouplers much of the time. Not sure which would be easier to do, either making the textures run completely from top to bottom or removing the colliders from the stripe areas, but it would be a huge help if you could adjust them.
  2. @NecroBones, Just to show you what I had in mind with the FTP decouplers, here's what I'm currently working on: Yes, I know you have one in RSB, but what's the fun in that? I'm doing manual part welding with CCC tank models, some stock models....and some other parts of yours, with some changes by me.
  3. Wow, thanks a million, @NecroBones!
  4. @NecroBones, I have a favor to ask, could you add (or modify) a decoupler (just one size) that is truly hollow (i.e. no colliders) on the inside to match the visual appearnce, much like the Mk1 Structural Fuselage? I have use for such a thing as an interstage (with appropriate scale changes), and with the mesh-switching capability I could make all sorts of matching interstages. As you may have guessed, I found out the hard way that the FTP decouplers are not actually hollow.
  5. Yep, that was bound to happen with Roverdude making the parts, they're going to resemble the original stock parts (and his own MKS parts) rather than the Porkjet parts, let alone something from FASA, Blue Dog Design or Raidernick.
  6. The only things that would get me hyped would be: > No more memory leaks and stuttering and other bugs and an SAS that works again. > Graphics overhaul > Rocket part overhaul > Career mode overhaul If you're a non-English speaker, ok, good news for you. For me, it's a big yawn, sorry.
  7. @NecroBones, Yup, that's exactly what happens, one dome looks and switches like normal, the other is Z-fighting. I'll go ask in the IFS thread too.
  8. Ok, I'm experimenting with manual part welding to make custom spacecraft out of existing parts, and I thought I'd weld a Mk1 parachute into a descnt pod I'm making out of a nosecone from MRS. All I've done is include the part MODEL and all the chute modules from the Mk1 .cfg. Well, the chute can be operated like normal, it shows up on the staging stack, the deploy parameters can be adjusted, and it does deploy when staged. The problem is that it doesn't work like normal. When semi-deployed, the pod and chute turned to near horizontal and actually started climbing. The F12 aero overlay showed a strong body-lift line from the pod. After a while the pod started descending again, but when the chute fully deployed, it turned to a 45-degree angle, with the overlay showing equal-length drag and body lift lines 90 degrees apart. The pod never got into the usual vertical retrograde-pointing position. Putting a regular separate Mk1 chute on top of the pod works just fine, so there's something about welding one into a pod that's screwing things up, and I don't know what it could be.
  9. @NecroBones, I'm trying to make a part using two of the FTP dome tank models manually welded togther, but only one of them gets the texture mesh and switching capability (using IFS). Is there a way for the texture meshes to be applied to both of the part models, either individually or collectively? Simply including a second mesh-switching module doesn't work, just duplicates the variant buttons.
  10. @Sigma88, Ok, don't laugh , but this is a question about SD 0.4.3 with Kopernicus 0.6.2 in KSP 1.0.5 (don't ask either ( ). I noticed a bunch of exceptions showing up in the Alt-F2 debug console. Suspecting it might have had something to do with Kopernicus, I removed all other mods, but then no exceptions showed up. Adding in SD made the exceptions appear. This was even without my Kopernicus or SD change .cfg files being loaded, just the mods themselves. SD does appear to be working fine, the changes did work when I load them, but I am alarmed by the exceptions. Are they harmless? Screenshot of the debug console: KSP Log is here. Output Log is here.
  11. @NecroBones, Ah, thank you, so that's what that section does! Never really looked that far. So I just need to copy the ones I don't want into the part where FTP is present and appearance switching is turned on?
  12. Yep, Kopernicus is installed correctly, as all my other changes (moving stuff around, adding stuff via cloning stock moons, changing orbits) show up as expected. I saw the "FOR[]" line in the older post, was a bit confused about it. Does it go in the main "@Kopernicus:AFTER[Kopernicus]" line at the top? And what name do I use? I did Hyperedit a probe to Laythe at a 100K orbit. At first I thought I saw more land, as there was a blur of brown below the probe. Increasing the otbit to 400K though made things look like the normal stock appearance. I also tried to use Kittopia, but got lost in it, couldn't find where to adjust VertexHeightOffset in the 5 million () PQS setttings.
  13. @The White Guardian, A Google seach brought up this post of yours, as I'm trying to lower the sea level of Laythe, the goal being to make more land visible--that is, if such a thing is even possible. I used your example, but there was no visible change to Layhe, whether the offset value was 100, 1000 or even 5,000. Here's the entry in my Koperncus .cfg:
  14. @NecroBones, Is there a way to have only specific meshes from Fuel Tanks Plus show up as options, or even use just one texture, e.g. the Black and Soyuz ones or just the Saturn one? I'm making some custom parts using the stock fuel tanks models, and I'd like to to have only certain FTP textures be used for them. Simply deleting the unwanted ones from the "objects = " and "objectDisplayNames =" lines in the MM patch files I've made didn't work, the mesh is broken, with the Z-fighting result of what appears to be all the textures trying to be displayed at once. Restoring the lines to the orginals, with all the mesh options, made things work again.
  15. Claw's bug-fixing-by-mod is what got him hired for the 1.1 and 1.2 development. He knew his stuff. And many of hix fixes and extras are now stock in 1.2 Of course, he's seemed to have disappeared post-1.2 release, so who knows if he'll ever continue this mod. Or even just do a 1.2 version as a last service to the community.