NolanSyKinsley

For some reason transferring to a planet with a lower orbit doesn't really work. Put yourself in a solar orbit, then lower that orbit so it is a circular orbit that is closer to the sun then duna, then hit the transfer to duna button.

it is a command line tool, I do not use wine to run it, I use mono and it works like a charm. Install mono, found here, then open a terminal in the directory withe the .csv files, then just enter "mono ./ISA_MapGen.exe" Then again reading back I see you are on a mac. He may be referencing Linux wine, and I am referencing linux mono, but the mac mono should work just as well. There are some difference between the mac and linux wine so some things that work in wine under mac may not in linux and vice versa. With wine even being on different systems can mess things up.

What is your definition of max res? I run at 5x and get a GB+ in about 36 hours. I have seen trade off for every warp speed. To me 5x seems to get the best coverage, 50x seems faster but it leaves a ton of gaps so it takes more passes to complete the data set for the given resolution and for some odd reason 1x and 10x gets horrid resolution/coverage. I think maybe the best way to get the most data would be to crowd source, I.E. get data sets from many people and combining them. Although I have found once the files get much larger than 1.75 GB the become rather unmanageable. Even opening them with a text editor is a pain, but using command line programs work fine, but lack progress indicators. Appending one data set to another then removing duplicate lines may give decent results, but will require transferring large files.

I believe you can swap out the models contained in the ISA_MapSat folder for one you like and change the lines under "// --- asset parameters ---" in the part.cfg to point to the new mesh. Or you may be able to copy a part folder, rename the folder and the part name in the part.cfg to a new name and in the part.cfg change the "module =" line to "module = ISA_MapSat" Prefferably use a decorative part, I.E. one that served no purpose before. Both of these are just slightly educated guesses, but one or the other should work, I would start with the latter.

Have you tried placing the radar dish in the first(as in last to deploy) stage? (Just a shot in the dark)

Well after letting it run overnight again I got it to this: http://dl.dropbox.com/u/18919542/KSP/Mun_Topo_ISA_3200x1600_0-3337.6m_scale.png and the CSV is about 764 mb What is quickgrid? I will google it **edit** Hmm, I found quickgrid, but it does not want to accept my data. **EDIT2** I found a previous post on how to get the data into Quickgrid, will take a bit though with this much data.

Like greyscale? or natural terrain? For greyscale use "ISA_MapGen.exe grey" for the natural terrain use "ISA_MapGen.exe natural" I believe "ISA_Mapgen.exe grey" makes this: http://dl.dropbox.com/u/18919542/KSP/Mun_greyscale_ISA_3200x1600_0-3337.6m_scale.png "ISA_MapGen.exe natural" makes this: http://dl.dropbox.com/u/18919542/KSP/Mun_natural_ISA_3200x1600_0-3337.6m.png "ISA_MapGen.exe" with no arguments makes this: http://dl.dropbox.com/u/18919542/KSP/Mun_Topo_ISA_3200x1600_0-3337.6m_scale.png note all of these images I made with the "3200" flag to increase their resolution. I am currently attempting to make the highest resolution maps possible. I have had the MapSat running around the mun at 5x speed and 20km orbit for over 16 hours now to produce those images.

I was taking a look at it and I got it to display the Kerbonaut in the lower right hand part of the screen, and it has the EVA/IVA buttons(but the IVA internal view is the Mk1Cockpit). Sadly the Kerbonaut cannot exit as the pod "has no hatch". I got it to display him by adding these lines to the part.cfg // --- internal setup --- CrewCapacity = 1 INTERNAL { name = mk1CockpitInternal } I was going to do a dirty fix of adding an invisible ladder to the front of the TARDIS' fuel tank, and a "hatch" to the pod at the sign that says "Police Box" so you could climb up he front an enter the pod. Sadly I am running linux an unity will not run under wine as of yet. The instructions for adding a hatch and ladder can be found here: http://kspwiki.nexisonline.net/wiki/Adding_Airlocks_and_Ladders_to_Parts Another thing I noticed about the tardis, and I do not know if this happens to other ships or not. In the debug menu the no crash damage and unbreakable joints have no effect.

http://kspwiki.nexisonline.net/wiki/Adding_Airlocks_and_Ladders_to_Parts

Ahh, I see, the level files do not pertain to a single planetoid, they hold information on all of them.

I have 2 questions. A. How do you look inside the level files. And B, which planetoid does that file refer to?

If you do that does it continue to build the map while you are on another flight? if so that would be awesome! *edit* I tested it and nope, you have to be on that flight. I wonder if deploying multiple arrays will speed up mapping a planet.... I have a few questions though. If I collect raw data do I have to do it all in one go? Or can I come back later to collect more? Also can I run the mapgen while the game is currently making the map file? or do I have to wait for it to end to prevent file corruption? If I make the raw map file is there a way I can import that back into the game so I don't have to re-map the planetoid again? Oh, and good news for Linux/Mac users, I do not know if this has been stated before, but you can run the mapgen just fine with mono.

As far as the SSTV picture goes yes, he said it is the first and only clue at this time for this easter egg. I just think that yes, it is the only clue, but a clue still leads somewhere, just not somewhere with another step waiting.

That is what I said, there is nothing there yet, I was speculating on FUTURE possibilities. Yes, he said the SSTV signal is the only step at the moment, a step still leads somewhere. I also said that the SSTV was the only clue, and that a clue still leads somehwere but there are no more clues as of yet. My speculation was in no way a "revolutionary new unheard of tin foil hat theory" it was a response to a question that was posted to me. IMHO it is a quite logical assumption that I have made. I did not say it was in the game yet, I was thinking about what it may be in the future. My reasoning behind this is simple, they are not going to make it easy to continue from this point. We have already had to decode a SSTV picture to know to go to the south pole, where there is a pyramid(which is depicted in the picture). People would naturally land at the south pole without this picture. By having the requirement of 4 kerbins there it would take 2 deliberate trips to that point to unlock the next link, so someone just landing there would not skip the first step. An entity detector is much simpler to implement the orbital mechanics(I don't know C++ but I do know java and I could have it done in less then 10 minutes, orbital mechanics would take me years), so it is by no means a far stretch of the mind to consider this being implemented in the future. This thread is about easter eggs, not just the one easter egg currently being discussed. Please be civil, if the SSTV easter egg picture and its possible future meaning interests people and that is what they wish to discuss, then that is what they are going to discuss. After all, it is an easter egg, and this is an easter egg thread.

I have had the issue with it landing on duna. It mostly happens when the angle of attack is too steep. I have used it successfully to land on duna a few times by taking a more parabolic trajectory, or taking control about 5-10k up and slowing it down a bunch manually, then letting it take control again. The main issue I have with mechjeb is its use of RCS. I need it to use RCS on larger ships so it is at the desired angle when it needs to start the burn. But when I use it, it fires the RCS until right before it reaches the angle it needs to be, then my ship wildly over shoots the angle, by up to 90 degrees, then fires the RCS continuously until it is almost at the desired angle and over shoots again, over and over again. When it fires the RCS it needs to fire it again the same amount of time in the opposite direction to come to a stop at the desired angle. It can be a bit tricky to implement in the code, but not too hard. Just note the starting angle and the desired angle, fire the thrusters towards the desired angle until half way, then reverse the thrust for the second half. That should bring it to a nice stop at the desired angle, while reaching the desired angle quickly, and save a ton of RCS fuel. This may be an over simplification because you are orbiting and the angles change as you move, but the concept is there. I would love to see this implemented in mechjeb. I may take a look at the code, I do not know C++, but I do know some java and I learn rather quickly.

What picture? The one from decoding the sound?

Nah, I believe the 4 figures to be kerbols, i think you will need to get 4 guys there, as that means 2 trips. But for the time being, it is nothing special. Then again, this could all be the devs messing with us and they are laughing their butts off at us and our rabid speculations >.<

Where the sound first originated is more of a mound, at the south pole it is a more pyramid like structure. And yes I do know that he said some things were graphical bugs, but a pyramid? that is not graphical in nature, that is a model. I would call it a bug if it were exactly at the south pole, but it is off by a little bit, and has shading around it. That and the picture has a line coming from a planet pointing at a pyramid/mound and that mound has a line pointing to the south pole, seams rather clear and free of speculation to me that the pyramid/mound at the south pole is supposed to be there. That and when he said that, no pictures or statements about it had been made, just a picture of another anomaly near by from orbit. Whether it actually leads to anything more at this time, or has anything special there other then the pyramid itself is another story entirely. He said the sound was the only clue at this time. The clue still leads to something, but there are no more clues in the game to go elsewhere after that yet.

[ATTACH=CONFIG]33609[/ATTACH][ATTACH=CONFIG]33610[/ATTACH][ATTACH=CONFIG]33611[/ATTACH][ATTACH=CONFIG]33612[/ATTACH][ATTACH=CONFIG]33613[/ATTACH] Pictures of the "pyramid" close to the south pole of Duna, and the ridges leading away from it.

I managed to decode the second part, it is actually just a repeat of the first. I also when to the location of the noise and let it decode the repeating sound for 20 minutes, it is all the same picture, just repeating. Something of interest though! I saw the arrow at the bottom of the image pointed to the south pole, so I landed there, and there was a pyramid like mound! and a line of ridges leading away from the pole starting with this pyramid like structure...

In the end, I think it is going to be something like a map for the escape trajectory needed to get to another solar system, or just saying "when these planets line up, they point at another system"

nah, playing it backwards just garbles the info, looking up SSTV signal kinda explains why. You won't get anything useful out of reversing the signal, just garbled bits of the original.

I don't think that will work, there is a start signal for the decoder to know the beginning of the picture, but I will give it a shot. I did low pass and high pass filters and it cleaned up this image a little, but just barely.

I hope that .18 will have a few things. First is camera shaking while in IVA depending on g load/stress on the craft. Sound barrier. More clickable buttons/visual panels in IVA (like orbit) I think we should be able to complete a full interplanetary mision in IVA (that would be pimp and will most likely be foreseeable in the future, if not in .18). An option to see your orbital line in regular view. Did anyone say ejector seats? yea, ejector seats and parachutes for space plane pilots/cockpits!! Larger launchpad. Much Much Much longer/wider runway, probably doubled at least. Maybe just adjustable =P Or at least get rid of that little hill just past the end of the runway. Long gripe about the SAS/ASAS follows: I would really like to see major changes in the way SAS/ASAS works, to be more like real life. When you have reaction wheels controlling the attitude of a ship, you can override it in a single direction by just telling the system to let go of that reaction wheel. It takes I think 3 or 4 reaction wheels to keep control in all directions, but saying you have to turn of all of them just to change one of the directions is strange. Computer control systems should be there to help us constantly, not all or nothing. Like the F-117 Nighthawk, if it did not have a computer assisted flight system, no pilot in the world could keep it in the air(although it does not use reaction wheels). I understand this may make the game "too easy" but maybe they could make a power system that regenerates, so you can only make a limited correction in a set period of time, or it is significantly heavier because of the "computer" or hydraulic system required, or just have it take a crapton of research in career mode. When flying a spaceplane in kerbal's atmosphere the SAS locks onto a celestial point, so the farther I fly, the more it pitches up, it needs to lock onto an angle relative to the current horizon and keep the angle. Oh, and PLEASE tone down the ASAS. The control surfaces are either 100% or 0% with it. It needs to be a little more, well, gentle. Maybe even let the ASAS individually throttle each engine for more control(I know that would take some major coding)

I have been doing some decoding if the image as well. The last one that was posted was not only decoded, but ran through an image editor. Some detail may have been lost. I am convinced that at the end of the red line there is an arrow, as well as the line going down from the mountain and to the right, it has an arrow at the end of it as well. I am also curious about the 6 yellow dots on the right of the red line.