Some information about the Soyuz spacecraft. :)
http://www.astronautix.com/fam/soyuz.htm

With an inclination that's not around 90° you have two launch windows when the orbit passes the location of the KSP site.

For example when looking at a flat map of Kerbin, the orbit would look like a sine curve, rather than a straight line if it was 90°.

With an inclination of 52° you need to launch to a heading of 52° when the orbit is crossing KSP.

On the other launch window, when the planet has rotated. IIRC the orbit should be 90° (<Wrong! look in edit below) + 52° = 142°
Not entirely sure of this one though. A bit tired after having trouble falling asleep at night for a week. :dead::-?

That way you should save quite a lot of fuel since plane changes require a lot of fuel. :)

Edit:
Oops. At 45° inclination the opposite direction is +90° but after 45+ you have to take away 2° from 90° for every degree of inclination added.

46, the opposite is 46 + 88
47, the opposite is 47 + 86

---------------
52 - 45 = 7[°]
7 x 2 = 14[°]
90 - 14 = 76[°]

52, the opposite is 52 + 76 = 128°


So on the second launch window the heading should be 128°.

That should be more correct, I hope. :p

The Krussian Module is the Kosmos TKS if you're interested in it Lion:

https://dl.dropbox.com/u/43321825/TKS.png

http://forum.kerbalspaceprogram.com/...-Design-Bureau

Cool, thx, I´ll try that out! But 52° inclination can´t be HDG 52°, or am I wrong here? on first launch 52° inclination (set via MJ) was HDG 32° or something like that...

Anyways, the Newton module was successfully connected a few minutes ago:
https://lh5.googleusercontent.com/-M...2520Newton.jpg
Delivery...


https://lh4.googleusercontent.com/-c...520Modules.jpg
After connecting it with the KSS...

Next step would be the additional crew module "Meduna", but some RCS reserves could be more important, so I will send them first I guess. Problem is... my FPS are getting eaten again. I guess it never was the KOSMOS that caused the trouble, it seems KSP can´t handle stations/multiple ships very well at the moment... meh. :-?

What orbit is your KSS at?

Also, what mods are you using?


I spy KW and Mechanical Mouse(why not just use KW's shrouds?) and it looks like you're also using ExPI Space stations. I'm not sure where that huge satellite dish comes from, but I see it all over the place.

If I'm not mistaken, it looks like the one from the Remotetech mod.

Lack of sleep good not for brain. :doh:

Seems I mixed launch azimuth with inclination... My bad. :oops:


Now I've made a mess of things... :dead:

Spike,
at the moment, the KSS is at 80x100 with an inclination of 52°.

Mods I use:

• [0.18.1] KW RocketryOverhauled*
• ISA MapSat 3.3.4
• Kosmos TKS Pack [0.18]*
• RemoteTech 0.4.0.1*
• Anatid Robotics / MuMech – MechJeb – Autopilot – v1.9.5
• Mini/Mega Sepratrons [0.18] – Robau’s Warehouse*
• Crew Tank Command Pod [0.18] – Robau’s Warehouse*
• Cupola Space Station Module
• SN Service Module*
• ExPI Space Stations 0.4*

*Modified by myself for convenience and/or realism and/or efficiency

Edit: Lionclaw, go to bed man! :D

80 periapsis with 100 apoapsis?

Also ISA causes lag for some people. Remote Tech may be causing it too.

Yep, 80 peri, 100 apo.
The other way around would make every astrologist mad I think :haha:

I had ISA in mind but now, my main suspect here is remote control - what would be a disaster since I cant play without it. After connecting the 4th module my FPS descended to 2-7 (yes, TWO to SEVEN!). It was that wore because while using ASAS or MJ to stabilize the ship, it fired the RCS thrusters non stop like crazy. when I dont fire the thrusters, I have 14-20... still terrible.

Its unplayable. Additionally, MechJeb, besides being xtremely experimental in the actual stage, seem to cause lag too.

You could try pushing your KSS up to 120KM, might get better performance.

One thing I have learned when designing a rocket is to double check the stages because the program does not always pick the smartest staging sequence.This is really common when making tweaks to a design.

Now a question I have D/Led the KOSMOS files and they contain MuMechLib.dlls and ZKreuzung.dlls MechJeb also uses a MuMechLib.dll so what do I do in this case over write the file or keep both files?

Yep, that is my plan, moving it to 125x125km for testing. I actually expect it to run smoother then... God I hope! Or my program is toast...:nope:

Thx for the tip though! :)

I guess that my question got missed so I will ask again more clearly.

When I add in more than one mod and they happen to have the exact same file what do I do?

For example the Kosmos mods have a plugin file named MuMechLib.dll MechJeb also has a plugin with the exact same name.According to the D/L page the Kosmos mods require that you also have Mechjeb how do I do this if they both share a plugin file with the same name?

Change the names of the files or keep both files or what?Or maybe you stack them with the required one on top..confused:hmmm: I cant seem to find a clear answer anywhere.


EDIT: Never mind each Kosmos pack comes with the .dll for MechJeb and electrical energy but they each came with rather useless read mes I figured it out by hovering the .dlls.
Nice that they included the needed files if only they'd have explained this.Actually they do have tow rad mes one basic one that tells you little and then a second one that tells of the included .dlls it just is not right in your face.

Even before the pic loaded, I saw what you did there.

I've been working with my father on stream lining his home office. Learned the other day that used to do that, write everything down in a notebook. Then he decided to move them all to an unencrypted excel file. I about beat him with a stapler.