liquidhype

Members
  • Content count

    621
  • Joined

  • Last visited

Community Reputation

342 Excellent

4 Followers

About liquidhype

  • Rank
    Professional Cat Tickler

Profile Information

  • Location Space

Recent Profile Visitors

3744 profile views
  1. Not to be rude or anything, but Blender and Unity are the least of your problems if you can't even manage to create a UV-map for something as simple as a cylinder and a cube, which by the way, are the simplest primitive meshes one can uv-unwrap. Instead of focusing on the more "complex" aspects of modding such as using Blender and Unity, I suggest you spend some time looking up tutorials on the basics of Wings3D, Blender and Unity, as there are plenty of wonderful tutorials (both in written and video form) out there for you to learn from. Creating a uv-map is really not difficult, you just need to watch and/or read a couple of "how-to's" and you'll get the hang of it in no time.
  2. The Galactic Core skybox is absolutely stunning!
  3. Of course, but only slightly. How much it affects node burns depends on the AccelereationSpeed and DeceleraionSpeed values you set for the engines. Note that this is not an issue in real life when using restartable engines which requires up to a couple of seconds to achieve full throttle, or solid kicker stages with varible thrustprofiles, so it should not be a huge issue in KSP. There is a reason why most spacecraft perform course-correction maneuvers.
  4. For anyone wanting to use this, I recommend messing around with "engineAccelerationSpeed" and "engineDecelerationSpeed" values. Obviously the lower the number the more time it takes for the engine to spool up/down and vice versa. 1.65 for AccelerationSpeed and 1.90 for DecelerationSpeed might not give you exactly what you want. Realisticly some engines would have a much, much lower number than 1.65 for AccelereationSpeed. Real-world examples for low to semi-low AccelerationSpeed would be RD-107A/108A, RS-68A, RS-25, RD-170/171 etc.
  5. No mod needed, the stock game can already do this. You can add these 3 lines to the "ModuleEnginesFX" module; - useEngineResponseTime = True // True or false - engineAccelerationSpeed = 1.65 // How fast the engine accelerates once ignited - engineDecelerationSpeed = 1.90 // How fast the decelerates once throttle is cut
  6. I quickly made a model that somewhat resembles the one you are working on just to show you how to sharpen up the edges. As you can see, the first model (left) is just the basic mesh, no modifiers with 48 faces around (24 works fine too). The middle model has "Smooth shading" applied to it with 3 horizontal edge loops, and the one to the right has an "Edge Split" modifier applied to it. If the Edge Split modifier does not sharpen up the model as you'd like, I suggest either marking seams as "sharp" or selecting faces like I've done in the image and press Y to split them off from the rest.
  7. Yea I already sort of did that a while ago. Never got around to releasing it as a mod due to it being of very little use and kind of boring. As is, I have only configured the parts for RSS and Real Fuels, never got around to balancing it for stock. If there are people interested in having it released as a mod, I guess I can find someone to release and maintain it, as I have no intention of doing so. Anyways, here is a quick render of the thing.
  8. I think by "stockalike" they meant the art-style of the engines/parts, not how they are configured. I am not against having them balanced for both stock and RSS/RO. I just prefer having the engines look like they are supposed to, instead of that terrible stock art-style
  9. The title of the mod is RealEnginesPack, emphasis on the REAL. For the love of all the space gods, do not make these stockalike.
  10. Seriously, all you need to do it double click the config file. It is literally that simple. Here is an example using one of the stock engines.
  11. Well you are definitely doing something wrong still. Another screenshot of you GameData directory would help pinpoint exactly what you are doing wrong.
  12. I did give you a good answer. I told you exactly how to install the mod. You just seem to have an extremely hard time understanding how to install a mod. And so I'll explain it once more. Open the .zip file Double-click the GameData folder within the .zip file Drag and drop the "Launchers Pack" folder into your GameData directory. If you want to install the recommended mods (Firespitter, Texture Replacer) as well, the method of installing them are exactly the same. It really does not get any simpler than this.
  13. Guys, guys guys. It's not that hard. This mod installs the same as any other. Drag and drop the "Launchers Pack" folder into your GameData directory, that's it. It is literally all you need to do. If you want switchable textures, install firespitter (again, drag and drop "Firespitter" folder into GameData). If you want reflections on some of the parts, like the engines, install Texture Replacer (again, drag and drop the "Texture Replacer" folder into GameData).
  14. As I said, you don't need to do anything other than just adding another single transform to the model before you export it. Just export the launchpad like any other part like you normally would, except add one more transform to the model and call it whatever you want. Like in my example, I added a transform called "lc40transform". That's all you need to do. As long as there is an extra transform available, anyone who wants to make your launchpad model into a launch site (or static) using Kerbal Konstructs can do so with a simple .cfg file.
  15. All you need to do differently is to add an empty GameObject where you want the rocket to spawn. You can call the transform whatever you want. Don't need to do anything special. As long as the transform is there, anyone who wants to make a launchsite out of the .mu file can do so.