If you have a space fighter parked onboard a spaceship, standing near the fighter and looking through the cockpit glass will show you the view outside the ship, whatever is generating the view through the cockpit glass isn't taking into account obstacles like a ship being in the way.

   

It is not possible to access the sea chest while in a berth if the room the berth is in has cargo access.

Workaround: Declare a building your home and access your sea chest there.

When you are using the construction window, you have to select the construction materials you want to use. This can be overriden by using the up and down arrow keys while placing a building.

This is too easily done by mistake and confuses new players. I suggest removing this behavior, or at least removing it from default key binding or whatever.

Could instead mirror what the mouse-wheel does with the up/down arrow keys. Changing altitude of platforms and roads. Would make it easier to use without a mouse-wheel.

See title.

Logging camp is not limited in its number of manufacturing workshops like the mine and well. Logging camp actually seem to be using fields instead of workshops, which is weird.

There is also no default logging camp building blueprint, which seem to confuse some new players.

I'm noticing multiple colonies with 0 population, and 0 morale displayed in the city report.  They do however still run all processes, as though they have full population.

I notice this most often with moon bases.

The addition of platforms which you can build under the sea and on the sea floor would be really helpful. Given all the other platform and biodome types there's no reason they shouldn't exist. Or you could just allow existing aerial platform types to go into negative numbers, below MSL. 

They would be especially invaluable on gas giants, where you'd then be able to place airports with transporters within overlapping range at various heights within the deep sea. That would allow you transport from the core into orbit and vice versa by "island hopping" from one platform to the other.

When a process is in the "not ready" stage, it displays an estimated time to run.

This estimated time is currently multiplied by the number of workers working the process, which makes no sense because the actual run time always remains the same, irrespective of the number of workers. It should be changed to remain the same value as for one worker.

The Building Code guide and Usage Tips are something I find really useful in the designer.

More reference material in the main game would really help with planning your empire. All the info is there in the code and databases, so I would really like to have a window where you can look up the material requirements, tools, modifiers and base time to run any given process. Perhaps you can check and uncheck modifiers to see their effect. It would really help with setting up larger scale production chains and broker shipments, and I'd use it a lot. 

Ultimately I'd also like to see an "empirical" usage chart which you can set up at a concrete city: i.e. you tell a city to "prepare detailed usage report" and it will log a power, food and resource usage flow chart for every building/home/process in the city over a standard period so you can identify bottlenecks and understand shortages at the source. It shouldn't add to the general strain on cities since it the info will only be logged when you request it in advance.

1. Please add SSL. Almost every website these days forces HTTPS, and it's easier than ever to get an SSL certificate. What's more, many programs and websites will default to https when a user types a domain without any prefix, which causes confusion when people click their link and receive a 401 error. By all means, use a free certificate from Let's Encrypt. It's so easy to install using the Python program Certbot, which you can install using APT on Debian and Ubuntu. They even have an additional program to automatically configure Apache and Nginx to enable SSL and configure your websites to use your new certificate.
   
   
2. Upgrade PHP! Upon inspection, the version of PHP being used by the server is pretty out-dated. The longer this waits, the greater the chance some nefarious individual will get bored enough to launch an attack using one of the various vulnerabilities at their disposal.