Steps to reproduce:

1. Start a new career save that does not have maneuver nodes enabled
2. Open the 3d orbital map
3. Observe the orbital map does not render because maneuver nodes are not present.

The map in the landing module should be replaced with the new Ground Track. If possible, the altitude estimation chart should be included in the module as well.

Zepto.js is significantly smaller than prototype, which would reduce the page weight and (hopefully) improve performance.

As Houston grows, I'd like it to have better support for quickly releasing versions. This will help us expand the app and will hopefully help improve the install process for Houston.

The following tools should have "standalone" stations so mission control teams can customize their workspace:

• 3D Map
• Ground Track
• Camera Feed Gallery (post tcannonfodder/Telemachus#3)
• Staging Analysis

I'm not sure how to do it (otherwise I would!), but this feels like it really should be added to ckan!

https://github.com/KSP-CKAN/CKAN

math.js is one of our largest dependencies and we only use it for 1 function (math.add, which is matrix addition). A method can be written in math_polyfill.js that can do the same thing, reducing page weight.

Below is a mockup of the mission wall module, which would be projected on a larger monitor in mission control

Right now Houston loads all the app's assets for every page load. As the app grows, this increases page bloat and weight unnecessarily. The assets are also not compressed. Both of these create problems for users running Houston remotely: their limited network connection is bogged down sending "junk" requests and bloated data.

I prefer Jammit style asset compression, it's straightforward and does the job without getting in the way. However, I haven't had much luck finding a jammit-style asset packager that works well with Nanoc.

The SCIENCE module needs improved, and it should be renamed to SYSOPS to indicate that it's broader scope. While it largely includes basic science & sensor data, the module can control custom actions and will include a live feed of cameras attached to the vessel in a future version of Telemachus (tcannonfodder/Telemachus#3)

A rough mockup of the SYSOPS station

The parts appear fine in the latest release of KSP but no UI elements appear. (Including the toolbar icon)
The server for the telemetry mod does not start but this could simply be because it's required to be turned on in the UI.

The Atmosphere meter on the Boost/ECOM page will fall much faster than it does in game. It seems that as the atmosphere meter in game is half way, the atmosphere meter on Houston is all the way down to nothing.

Images below are taken at the exact same time in a KSP launch.

http://imgur.com/a/S80kh

The rake task to build the site is a good start, but it should be enhanced slightly to generate a complete houston directory that can be installed from Telemachus

A design and UX audit of the station screen is necessary, given the enhancements in the latest version of Houston. We may need to make additional stations, split work amongst them, or even move specific components (like the maneuver node editor) into separate station.

Self-explanatory. Not sure what it's supposed to look like, but it should look like something 😜

Hi,
Upon loading index.html, the only data that is displayed is MET and UT. When I open up the web console I am seeing several" downloadable font: download failed" messages, and finally at the end after about 2 seconds after page load, the message "NetworkError: A network error occurred." I've attached a screenshot if that helps.

Cheers,
Tim

If Houston is unable to collect data, a "loss of signal" error should be shown somewhere on the title bar. This will let users know that they are not getting live data from the vessel.

If the connection is restored, the LOS notice should disappear

This is a major overhaul to Houston's backend (maybe 1.5/2.0?), but could have a number of performance and usability improvements:

• Page weight could be reduced, since browsers aren't caching the AJAX responses, needlessly filling up the page cache
• A version of Houston could be hosted on a centralized website, rather than relying on the Telemachus server to pass all that data along (currently CORS prevents this)
• Potentially better performance?

It's worth looking into and seeing what the effect is and how feasible it is

While it's not critical for 1.0, the build chain should also create a CSS asset package, with prefixes automatically handled by the build chain.

Below is a mockup of the new docking module

I did have one question about the Orbital Map. I initially tried this with a pre-existing probe that is currently in a tight orbit around Gilly and this is the resulting Orbital Map. I understand that the cube represents the craft, but is the size in relation to Gilly (essentially a large asteroid) the intended behavior? If so, I suspect that the cube size is appropriate relative to larger bodies such as Kerbin or the Mun, but you may want to reduce the dimensions of the craft-cube if it is possible.

Sketch's SVG export for the station thumbnails was broken, so right now the thumbnails are rendered as PNGs. This increases page weight, so we should try using SVGs again.

Below is a rough mockup of the Navigation module. The mockup may be missing some fields in the orbital info table

Right now Houston works on Webkit browsers. If someone wants to fix Houston to work on Firefox and Microsoft Edge, I'd love to merge that PR in!

This should make it easier to coordinate precise docking procedures. See https://github.com/stemkoski/stemkoski.github.com/blob/master/Three.js/Viewports-Quad.html

demo: http://stemkoski.github.io/Three.js/Viewports-Quad.html

The current navigation might not make sense with the inclusion of new stations and multiple possible stations per role. It might make sense to design a new navigation UI to make it easier to switch stations.

An overlay grid might make sense, since relevant stations can be grouped by role (and it might be possible to open all relevant stations for a role with a single click).

It's been a while since an update, and I've been having trouble getting Houston to work with the newer version of KSP.

Any other ground control mods I should check out?