OrbitalManeuvers

Hiya ... I'm hoping to get educated about launch clamps and their effects on dV calcs in the VAB. I'm on MLP build 2.1.2, KSP 1.10.1. My Saturn 1B has a TWR of 1.48 without the milkstool and mobile launchpad attached, and a TWR of 1.04 when the (mostly completed) launch stand is attached. Is this due to the mass of the launch clamps being factored into the dV calcs? Both KSP and KER report this huge jump when attaching the stand. Moving the launch clamp stage to be first makes the dV calcs correct again. It can't stay there of course, but at least there's a workaround to check the numbers. So these are my observations. Is this expected behavior?

Just for reference, in 1.10.1 a freshly constructed 401 configuration with no payload shows: stage 1) 1.19/4665m/s, stage 2) 0.47(vac)/5994m/s, with a Isor in 10C1 mode.

This is a development repository, so there's really no guaranteed compatibility with anything. That said, the devs have said the next release will be for 1.11.

In all likelihood you will have nothing but frustrations unless you follow the installation instructions very carefully. They're listed on the first page of the mod, and they include the info you're asking about, which makes me think you're not looking at the written instructions. In any event, this is the Eve thread and isn't really the right place for this. Look in the spoilers on the first page under How To Install.

I'm 99% sure that if you're using GU you should not have the BoulderCo configs installed at all. GU has configs for Eve and Scatterer. Galaxies Unbound is not compatible with: - Other visual mods (AVP, SVT, ...) This almost certainly includes the BoulderCo configs.

I'll keep a list of any more differences I see. The first was the EVA report which I see you've already addressed (I was away for a hot minute). I'll do some more side-by-side testing between xscience and sciencealert soon though.

Sad trombone. The silent majority does not appreciate the vocal minority ruining these waters. Please people, keep in mind that mod authors are not big software corporations that run on shareholder-driven schedules to meet financial goals. Mod authors are just folks who've spent an ungodly amount of time learning a ton of niche skills because they want to make something cool in KSP and share it with other people. That is the extent of your "rights" as a mod user -- to be grateful that someone just gave you something for free. The vast majority of mod authors (I used a crap ton of mods) are genuinely appreciative of feedback at the right time and in the right way.

Quick note to put on the shelf: If/when the time comes for that, ScienceAlert is better behaved under 1.11 so you may already have some solutions that xScience will need, e.g. EVA Report not showing up.

There's another case where stages are missing, this one is even simpler, but also less clear. The screenshot below shows that an SRM from Probes Plus registers correctly with KSP but not KER at all. However, this one is more iffy because some of the other Probes Plus SRMs do not show any value for KSP either. Since PP is an older mod I'm only mentioning this because of the one case where stock gets it but KER doesn't. Also in all likelihood this isn't related to the previous discussions, but since I don't know how KER works, I'm just throwin out data points.

@OnlyLightMatters I can reproduce this. Here are the steps that repro for me (p.s. why are we building rockets in the SPH?). I have yet to determine which of these steps are truly necessary. Grab the SEQ9 as the first part Put a cubic strut on the front, put another on the back. There is no symmetry here because it's the wrong direction, so I placed two individually. Re-root to the front cubic strut Attach the fuel tank and capsule to the front Attach the terrier to the back. edit: Just wanted to also mention that I've seen this behavior many, many times. I've been using KER for years and I have always been able to confuse it into not showing entire stages. For example, it's not hard to repro when you're building the Lunar Orbiter mission from BDB. The probe is built first, sort of "upside down" and needs to be flipped over when put into the fairing. If you build this and then re-root to the Agena's core, you can get these symptoms, too.

Must be old news if you're talking about KSP versions where it actually works. I have it and have never run in windowed mode.

There are only a few there that I don't have or recognize. Not sure if this will help at all but here's mine.

This doesn't happen to me in 1.10.1, as somewhat expected. I've used that part lots of times. You might have some luck if you post your mod list. There's a convenient list inside the ksp.log file if you search for "folders and files"

I'm pretty sure the craft files were built with a later version of KSP, but the wiki has all those instructions, too. If you need help with builds you can always ask here, and lots of us still have 1.8.1 installs, too (mine is for KSRSS)

As an old fart who has done that for upwards of 20 years now, I can relate very well to the challenges of coding all day and then trying to do "fun" stuff that also involves coding. Sure, it's different, but it's also the same part of your exhausted brain that you're trying to use, and it can get very tiresome very quickly. Everyone is different and deals with this differently, but please do keep an eye on your own well-being. KSP is awesome, and I'm (stupidly?) starting to dip my toe in the modding pool, too ... but there's a lot of life/mental health balancing you gotta do to avoid burnout.

another nit -- I believe AVP + SVE is asking for problems with visuals.

Are you on the latest builds, like from github? I had similar errors on a 1.8.1 install which were fixed by updating to the latest BDB (I had an older dev build installed there). The version of B9 bundled in the github download also works on 1.8.1 for me. This install is stuck in the dark ages due to KSRSS, but all the latest BDB stuff works there for me, and the same files work through 1.10.1 as well.

The file that you unzipped that resulted in the directory with "-master" in the name? delete both that file and that directory. The correct files are all linked on the first post of the thread, and here's the one you want for the textures: https://github.com/KerbalFrench/KSRSSVE-Textures/releases/

Genuinely curious ... do you like to know all of this ahead of time? I ask because I'm still kind of yearning for an experience where everything about a solar system has to be discovered by in-game mechanics, like nothing shows in the tracking station until you know X about it, you have to use telescopes, etc. I think there are a couple mods that aim at tackling this (on my ksp to-do list) but I was curious if the complete opposite fits into a particular play style maybe? Or maybe you're just sandboxing and want everything laid out? Curious what you use this much detail for in game.

This works for me on 1.8/1.11. Any time stock fairings won't close for me it's because I haven't made the straight parts high enough before tapering. Try making sure snap is on? Last idea: post a picture of the sat without any fairings and maybe someone will spot something.

Is this the right thread where I say thank you for the 1.11 update? Playing KSP without KER for a couple weeks was just not as enjoyable. THANK YOU!

While I'm not in the interstellar market, I've been curious so I installed this last night, created a lander and cheated to some orbits and did some landings. Am very happy I did, as I got to see some really gorgeous work! These probably don't do it justice as I didn't really tune anything ...

To echo the previous answer: heck no. I've been using the same JNSQ release in 1.9, 1.10, and 1.11. The "thing" you'll need to keep in mind if you move past 1.8 is the Kopernicus version - which is pretty trivial, since RTB's builds are built with the target KSP version number plainly visible.

So you're on KSP 1.8.1 for KSRSS, correct? Are you using the latest BDB stuff, or do you have an older frozen version? Thanks!

Oh, cool. Just to be specific, that one is HideEmptyTechTreeNodes by Orthethac ... idk if there are others.