ryohpops

@NeuroticGamer Sorry for the lack of documentation. I don't have enough free time at all. The single launch idea is far simpler than the multiple launch. It should be used when you are going to launch satellites one by one, which is an popular method on early-game network constructions. Satellite A is inserted directly into the target orbit. Satellite B is launched into a parking orbit. Target Satellite A and setup a rendezvous maneuver, which is also valid as a hohmann maneuver to the target orbit. Here is the "slide" values come in: move the maneuver forward or backword by one of the values which are representing the same span. Execute the maneuver and circularize at the target altitude. Satellite B now achieves the target orbit with 90-degrees (for 4 satellites) separation to Satellite A. Launch another satellite, target the last satellite and slide the maneuver to the same direction. You can also use the dV values to design your multi-satellite launcher which has enough dV to reach the target altitude. Launch it and achieve Ap of the altitude, then bring up Pe to the lower altitude on Multiple Launch View, consuming "dV to lower".

I'm sorry, there is not much time so I'm afraid I couldn't update this to get 1.2 CommNet supported. As you found out, you can still obtain basic parameters required for establishing your satellite network, using current state of this tool with adding some antennas yourself. Just make sure Range model type on Settings tab is set to Root, according to my understanding of CommNet. Currently I'm waiting for definite information about how CommNet works in 1.2 out of beta and how RemoteTech responds to the release.

I'm truly glad to hear that. Yes, as you found out, the development is still active but slow. I'm currently busy in my real life, and any coding of queued features in todos / issues haven't been started yet. I'm sorry for owner of those ideas. I will continuously check this thread and GitHub repo. Please feel free to post new ideas, issues and pull requests. Well, even if the development is completely halted, you can use the website for long term because whole data are hosted on GitHub. You don't have to worry about that too much.

Thank you for your comment. It has been added to the TODO list.

Oops, I thought I done so in my first implemention. Fixed it. - 1.6.6 : 2015/08/01 * Fix calculation of Multiple Antenna Multiplier again. (westamastaflash)

Thank you for the report. I've found a wrong calculation in my codes and already fixed it. - 1.6.5 : 2015/07/31 * Fix calculation of Multiple Antenna Multiplier. (westamastaflash)

Release 1.6.1 is available. - 1.6.1 : 2015/07/06 * Fix settings page. * Fix reset feature. - 1.6 : 2015/07/06 * Add Multiple Launch View. * Borderlines are drawn clearer. * Improved units used in Views. - 1.5.6 : 2015/06/05 * Fix calculation of night time. (Aerospace)

Thank you for the report, you are right. These bugs were caused by new display class. I should consider use of automated testing seriously. - 1.5.5 : 2015/05/08 * Fix display of Slide time.

Thanks for the report. I've just fixed that. - 1.5.4 : 2015/05/07 * Fix calculation of Delta-V.

Release 1.5.3 is available. * Views are now rendered by SVG (a vector graphics standard).

Sorry for my late response and thank you for your idea. I have been busy lately and the development becomes slower now, but the idea is already planned as the next View. Don't worry and please be patient

Release 1.5.2 is available. * Add data for Real Solar System. (dirtcrusher) * Views shrink on small window.

Release 1.5 is available. * Support multiple pair of antenna and quantity. * Fix autosave feature with local storage. Last input and user's bodies/antennas will be saved and restored automatically. (westamastaflash)

I could reproduce your problem with IE, thank you for your report. I looked into the code of ngCookies in angular project and now I'm wondering why Chrome does as I wish :-/ I will fix this problem in the next update with your detailed information, thanks!

The config is superior than my code. It means Chrome ignores developer's setting of cookie and any other browser storages and clear them on close. There are some other methods to keep data, but they will be deleted as I say, so allowing Chrome to have it's data permanently is the best solution.