Unity 3D UI Position Instability (shaky UI)

I recently experienced an issue where I noticed that many of my UI elements would be shaking (unstable position) while the camera is in motion.

The setup I had was that described by Unity at one of their Unite conferences for performance (ie. logically nesting canvases under one canvas as much as possible). The canvas had pixel perfect turned off explicitly and the plane distance was 1, which was lower than the default 100 when you add the canvas using the create menu. The root canvas was set to a render mode of “Screen Space – Camera”.

After a few methods of troubleshooting I finally realized that this was caused by the plane distance being set to a low value while using a render mode of “Screen Space – Camera”; if I returned the plane distance value back to the default 100 there is no problem! Ensure that this is the option that suites your needs the best as “Screen Space – Overlay” might be a better choice in many cases. If you do need to use “Screen Space – Camera” in your situation then you would want to try out some values on different screen resolutions and platforms to ascertain that your users will not experience this behavior.

There is an “Screen Space – Overlay” option for root canvases which would be a better option in most scenarios. It does have some impact on FPS but it eliminate this “shaking” UI problem as well as any potential issue related to the UI not being visible due to obstruction by a closer mesh.

NGINX fails to ask for PEM password on start


  • Ubuntu 16
  • nginx version: nginx/1.10.0 (Ubuntu)

Amongst the common commands you will find online to start Nginx are:

Using a service
sudo systemctl restart nginx

Call the binary directly (assuming it located in /etc/init.d/) with start/stop/restart
/etc/init.d/nginx start

Even if you specify the configuration file using the -c option, it always throws an error.

However, it appears (for me) that neither of these options prompt a user for their PEM password if they have configured SSL or TLS certificates.

After a lot of digging you will find that calling the script directly without (start/stop/restart) prompts the user for the PEM password.


Glassfish Error – java.lang.ClassCastException: org.glassfish.grizzly.config.ContextRootInfo cannot be cast to org.apache.catalina.Context

This error appeared for me because I set a default web module previously to a different enterprise application archive (ear) project while trying to run a new one in the development environment.

The solution for me was to empty the Default Web Module field shown below and restart the server. After you do that you can deploy your application successfully.

Glassfish Configuration