Observe

I am not quite sure what you are asking. Could you elaborate?

Yes, I noticed that and was intending to mention it. Thanks!

@ss8913Works like a charm! I'll be creating more flight paths and will let you know if I encounter any problems or have any suggestions. I recommend this script should be included in the opening post so it doesn't get buried in this thread. Thank you.

@ss8913It appears to work! The values seem correct. I'll run some tests and post my results within next day or so. This will be a great addition for Kramax Autopilot! Thanks.

@ss8913My mistake on the radius. It should be 6371 for Earth (RSS mod). Nevertheless, the latitude is still completely wrong. Here are my parameters and output: python kramax.py -p="Earth" -r="6371" --name="Auckland Intl" --description="Auckland International airport" --latitude="-36.995305687613502" --longitude="174.84381177178" --heading="88" --altitude="200" KramaxAutoPilotPlans { Earth { FlightPlan { planet = Earth name = Auckland Intl description = Auckland International airport WayPoints { WayPoint { Vertical = true lat = 0.70229352 lon = 174.80270837 alt = 12000 name = MAXKY } WayPoint { Vertical = true lat = 0.70315401 lon = 174.82324689 alt = 10000 name = HIKEY } WayPoint { Vertical = true lat = 0.70350616 lon = 174.83352649 alt = 6500 name = LOKEY } WayPoint { Vertical = true IAF = true lat = 0.70367464 lon = 174.83907989 alt = 1808 name = IAF } WayPoint { Vertical = true FAF = true lat = 0.70373318 lon = 174.84113710 alt = 1109 name = FAF } WayPoint { Vertical = true RW = true lat = 0.70380616 lon = 174.84381177 alt = 200 name = FLARE } WayPoint { Vertical = true Stop = true lat = 0.70381162 lon = 174.84401753 alt = 200 name = STOP } } } } } EDIT: I downloaded and installed Python version 2.7.15. Same results. Latitude wrong. Thanks.

@ss8913 Latitude calculation doesn't seem to be working. Here is my command: python kramax.py -p="Earth" -r="6371000" --name="NZ East" --description="my flight" --latitude="-37.684254347674603" --longitude="178.54679267814799" --heading="90" --altitude="507" Problem with latitude: Output gives "lat=0.014xx". Should be around -37.xx KramaxAutoPilotPlans { Earth { FlightPlan { planet = Earth name = NZ East description = my flight WayPoints { WayPoint { Vertical = true lat = 0.01482610 lon = 178.54679268 alt = 12000 name = MAXKY } WayPoint { Vertical = true lat = 0.01484180 lon = 178.54679268 alt = 10000 name = HIKEY } WayPoint { Vertical = true lat = 0.01484965 lon = 178.54679268 alt = 6500 name = LOKEY } WayPoint { Vertical = true IAF = true lat = 0.01485389 lon = 178.54679268 alt = 2115 name = IAF } WayPoint { Vertical = true FAF = true lat = 0.01485545 lon = 178.54679268 alt = 1416 name = FAF } WayPoint { Vertical = true RW = true lat = 0.01485750 lon = 178.54679268 alt = 507 name = FLARE } WayPoint { Vertical = true Stop = true lat = 0.01485765 lon = 178.54679268 alt = 507 name = STOP } } } } }

Never mind. You script is working once I figured out how to pass the parameters and fixed the missing parenthesis. I'll try feeding in some airports and report on how it works.

@ss8913I downloaded current version 3.7.0 and I read version 3 requires parenthesis for Print command. After adding parenthesis for all incidences of Print, your script seems to work. Now I need to figure out how to pass the required arguments. I'm working on that now. Could you post an example command-line with arguments. Thanks.

@ss8913 I tried your script, but am unable to get it to work. Running Windows, I installed Python. Your script runs, but kicks out syntax errors. Admittedly, I have zero knowledge of Python code. Errors include missing parenthesis for Print. Adding parenthesis moves on to a new error. I wonder if you could test on Windows and also if you could provide example command line with arguments. Thanks.

@ss8913 I think a script for generating flight plans would be an excellent idea and I encourage you to proceed with this. At one time, I created an excel spreadsheet to calculate the various points from lat/lon/alt input, but I didn't get it to a point where it was in a releasable form. I exclusively use the Real Solar System mod. Therefore, none of the available Kerbin airports are valid. I've made quite a few flight plans for real airports around the world, but I am constantly wanting to add new ones. Good luck!

Just for the record, in my experience, @linuxgurugamer is one of the most responsive and helpful modders in the KSP community. He frequently goes "above and beyond".

Others could probably help you better than I, but first check that you have the following folders within your GameData folder: EnvironmentalVisualEnhancements Kopernicus RealSolarSystem RSS-Textures RSSVE scatterer If so, we can check further for correct versions etc.

@BlackDragon Korean Which KSP version are you running?

Warp causes problems with this mod. For one, Kerbals lose their level experience - or at least the number of "Stars" gets reduced to zero. Another, after warp, all the Kerbals have "snow" in their profile image. Going to the Tracking station and back to the ship, corrects the profile image, but doesn't retrieve their experience status. I'm using KSP 1.3.0. I expect you already know about these issues, but I thought I should post them anyway. I'm uninstalling this mod, until these severe bugs are resolved. Love the mod. Can't wait for it to work properly. Thanks.

I assume you mod the game because you like doing so. Part of your enjoyment, is seeing others take pleasure in your work. It takes a community of modders and players for this to work. While you may be justifiably impatient, it is not good to treat players with disdain who are trying to weave their way through the labyrinth of getting mods to play well together. Remember, modders need players as much as players need them. It's a two-way street. I understand your frustration and also your reasoning for not updating Constellations so that it can run with 1.30. At the same time, please understand the frustration of players (like me) who love RSS/RSSVE and who would love to play with Constellations. The situation is particularly depressing, because a "lot" of people are in fact running RSS/RSSVE with no significant problems at all and it seems that Constellations could likewise run fine with a few config changes to bring into compatibility with whatever version of Kopernicus/Scatterer that RSS/RSSVE are using with success for 1.30. Considering you have made it very clear that you may not be updating this mod for 1.30 any time soon, do you have any general suggestions about what needs to be changed, so that individual players can have a go at it? I understand Kopernicus changed some of its naming conventions. I've made those and other changes that I am aware of, to your configs. As you can see from my pics, things are looking much better than before (no super bright neon planets). To me, Constellations is sufficiently playable for an enjoyable experience, even though you say it looks "messed up". If it is messed up, could you point out how so? Or, would you prefer everyone just shut up and leave you alone? If maintaining this mod is no longer enjoyable for you, then perhaps you should step away from it for your own peace of mind? No one could blame you if that is best for you. In my own case, I was once a fairly major modder with a different game, and I too walked away after several years, because of some of the issues you are facing. Thanks.

Please understand, I am in no way trying to be argumentative. To the contrary. I am not suggesting using with 1.3.1, but rather 1.3.0. The big question I have, is if RSS/RSSVE works with 1.3.0 (which it does and is known to to so), what is so different about Constellations that precludes it also from doing so? From what I can tell, the lighting is less "messed up" with changes to lighting. Certainly, it seems very playable unless I'm missing something else? Thanks.

Just so you know, as far as I can tell, everything is working fine with KSP 1.3. As mentioned previously by @logan2611 and also I noticed, initial install has sunlight intensity extremely "neon" bright. Even the dark sides of planets were...not dark. After adjusting intensity values, and properly merging the various scatterer files I have things looking normal. I also adjusted the lens flare intensities and positioning, because I personally don't like the huge "ghost" flares creating false suns and spreading out too far. Anyway, I am satisfied. Here are how things are looking after adjustments: SeaBase in Pacific ocean Proxima Centauri b Kepler-1229b Considering Constellations "out of the box" doesn't work properly on KSP 1.3 without adjustments, it seems like it might be worthwhile releasing a 1.3 version. Thanks for a great mod!

You are right. It was RSS that a patch was made. So many mods and so many versions! So yeah, if I can get Constellations working with Scatterer (as it is with RSS bodies), all will be running fine with KSP 1.30/RSS/RSSVE/Scatterer 0.0320b.

My BAD! I'm using KSP 1.30. Sorry! In any case, RSSVE does work with 1.30 (they made a patch as I recall). I'm hazarding a guess that many/most players who use mods, have not updated to 1.31. As such, it appears that Constellations works fine with 1.30; which the exception of too bright objects and scatterer not working on Constellation bodies only. Thanks.

Not as bright as before reducing those values! Here is a comparison shot of Proxima Centauri b using the original Constellations configs. All the other planets (including Earth etc) are likewise too bright as @logan2611 pointed out earlier. Scatterer works perfectly on the RSS/RSSVE planets. I'm not sure why it isn't working on Constellations bodies. Should be a minor config patch I expect.

Here is Proxima Centauri b using KSP 1.3 with the adjusted configs:

That's what I would have thought too - except from what I've seen, all the Constellations exoplanets look "normal". Admittedly, I've never used Constellations before and so I'm not acquainted with all the various planets. Is there a particular planet that you could point me to, so I can check it and post a screenshot of it to determine if it suffers as you suggest? Thanks.

That's easy enough to fix. I'm running KSP 1.3 with RSS. After installing Constellations, Earth was very bright (just like in your image) and so were most of the other stars and planets (both RSS and Constellations objects). What I have done, is go into the various config files in Constellations that specify Sun brightness. Look for these entries (values differ depending on star): Reduce those values by a factor of 100. For example, if the value is 0.09, change it to 0.009. After doing that to all the Constellations configs (19 of them in my case), everything looks they way it should (beautiful). Earth is back to normal brightness, as are all the other planets and stars. Cheers. Note: I did not use the Constellations visual files for RSSVE because I didn't want to mess with something that was already working perfectly in my install. However, I did use the provided visual CVO files. Those are needed for clouds on the Constellations planets.

Keep in mind, the problem I described may not be universal. A few others have also experienced it, but perhaps you won't. In any case, the "solution" is simple enough.

It's working fine with exception of the ground splitting into tiles if you go straight up into space and then straight down again. The way to avoid this, is to first visit the Tracking station and then go back to the ship before re-entry. This seems to be an RSS issue - not RSSVE, Scatterer or Kopernicus version related. I've run completely stock with only RSS and dependencies (no RSSVE or Scatterer) and the problem still persists.