nanoDLP

I am not sure if { is valid character inside "G1 Z10.8300 F{200/5 P1", it could be the source of error.

Chrome caches much more aggressively. Could you let me know how ln -sf fails on your environment?

OK, I got your point, it is not difficult to add but I believe it will be a feature rarely being used by anyone else.
Why you would not use external script to handle modifications?

You are right it is caching problem. during printing we force update images but not when printer is idle. Forcing to much update could put pressure on rpi. I have tweaked nanodlp a little bit to see if it helps or not.
When you put printer in mode to keep all photos. It use ln -sf command to create link from newly saved file to shot.jpg. So datestamp on shot.jpg should changes if not run command manually to see what is the issue.

The problem is RPi's slow processor, it does not have enough processing power to slice STL files in realtime. So we need to start slicing files before start of print.
But what you can already could do is to slice the file in 10micron for example (smallest possible layer to cure with your resin) and use SkipLayer keyword in gcode box to increase layer's height by skipping layers dynamically.

You mean it does not display it when the printer is idle?

Thank you for the sample file.
Unfortunately lots of STL files has issues. So it is not possible to ignore them. Will investigate issues with the uploaded model.

We can try it, will put it into road map.

1. True
2. True
3. Agree
4. Depends on projector, it usually should keep settings. So if you change it through buttons or computer serial connection, should be enough.

Please, download latest version see if it makes any difference.

1749 is fine.

Try wired connection.