1. 1. Open Arma 3 editor
   2. place a player on the map
   3. place Radio Alpha trigger on map ('Activation:' drop down and scroll to 'Radio Alpha')
   4. in that triggers 'On Act:' field type '0 = execVM "myScript.sqf";'
   5. save the mission (i.e. 'splendidCamTestMission')
   6. Alt tab out of Arma
   7. Open notepad or equivalent coding program
   8. type a script that will be active for a good deal of time(i.e. 'while {true} do { a = 10;};')
   9. save the script as 'myScript.sqf' in your mission file (i.e. C:/documents/Arma3/missions/splendidCamTestMission.altis)
2. Alt tab back into Arma 3
3. Click preview
4. Press 0-0-1 to activate the Radio Alpha trigger
5. Pause the game (escape)
6. Click on the 'camera' button below the console (below the big text box, second row of buttons)
7. mess around in splendid cam (not necessary)
8. press escape to exit splendid cam
9. if you are at time acceleration 0 then change it to another value (bottom bar in lower right corner)
10. Click either 'cancel' or 'ok' and observe the results as described in the description part of this bug report
11. Restart Arma3 (Either: Alt F4 or: control Alt Delete -> click task manager option -> click Arma 3 -> click end task button)
12. Open your mission back in the editor
13. Preview mission
14. open splendid cam without activating the trigger
15. Mess around in splendid cam (optional)
16. Exit splendid cam (clicking either 'cancel' or 'ok' will have their normal intended effect)

This isn't a huge issue, but using splendid cam's aerial and thermal capabilities vastly speeds up a mission makers ability to test missions and see that AI and other objects are in position and behaving accordingly without moving the player.

There are a number of other issues that I have seen reported with external scripts and functions causing bugs when splendid cam is in use. (I would site sources, but just look around the feedback tracker and you will find a few) It is possible that splendid cam works in a non scheduled environment while the external scripts run in a scheduled environment. When splendid cam opens the exit dialog box it could relegate splendid cams thread(s) to a lower priority than external scripts preventing it from getting any time on the processor. This would cause all your input to 'cancel' or 'proceed with exiting' to effectively fall on deaf ears as the data is collected, but the processor never gets a chance to process it. In other bugs it could be the opposite happening, where splendid cam gets too much priority, or other thread priority problems. This seems likely from my understanding of threading with scheduled and non scheduled code (internal scripts versus external scripts). (source: http://killzonekid.com/arma-scripting-tutorials-code-performance/)

The Steps to Reproduce section is written so that those with no coding experience can reproduce it. Experienced modders, coders and BI developers, hopefully you understand.