Google Doc Version of this README: https://docs.google.com/document/d/1BfCOYtP85jEY19XnY2wmbgGzpKgPAhrvZc5Tv-cqNJs/edit?usp=sharing
- Set up the project
- Create project and add to Github repository
- Create README.md
- Import mesh and architecture assets
- Configure gimbal control prefab
- Add basic meshes for gimbal control
- Create script files
- Implement ‘shoddy’ first draft 7. Add translation and scaling 8. Add rotation without gimbal locking 9. Add mouse interactions 10. Add first draft code annotation
- Solve gimbal locking issues 11. Experiment with solutions 1. Check Youtube videos and Google Search for existing solutions 2. 4th axis rotation 3. Euler calculations 4. Converting world/local spaces 12. Ensure parent/child relationships are working 13. Test on pointed arrow mesh (for visibility of direction)
- Other technical issue solutions 14. Scaling of gimbal control (so they don’t overlap with mesh)
- Wrap up for delivery 15. Final Q/A pass 16. Second draft of code annotation 17. Test on an exported build (I think I will only be able to test on Windows for now) 18. Write build instructions document 19. Second draft of README.md
https://assetstore.unity.com/packages/tools/utilities/scriptableobject-architecture-131520
https://assetstore.unity.com/packages/tools/particles-effects/shapes-173167
https://www.youtube.com/watch?v=z3dDsz4f20A&ab_channel=SkittyAnimates
https://www.youtube.com/watch?v=kB7iE8Udq5g&ab_channel=WojciechSterna
30 minutes creating mock up document
1 hour of research
10 minutes of prompting ChatGPT
2 hours spent scripting based on GPT generated code
30 minutes wrapping up for delivery
- Set up the project
- Create project and add to Github repository
- Create README.md
- Import mesh and~~ architecture assets~~
- As it turns out I did not need to use the ScriptableObject architecture package as it would be overkill for this task
- Configure gimbal control prefab
- Add basic meshes for gimbal control
- Create script files
- Implement ‘shoddy’ first draft 7. Prompted ChatGPT for basic code 2. The code it generated was a solid outline, but didn’t actually solve the problem. I thought this was a fun experiment using ChatGPT to save me some time. 8. Add translation and scaling 9. Add rotation without gimbal locking 10. Add mouse interactions 11. Add first draft code annotation
Solve gimbal locking issues12. Using Unity’s RotateAround function there were no Gimbal Locking issuesOther technical issue solutions13.Scaling of gimbal control (so they don’t overlap with mesh)3. Skipped as I feel I am behind the schedule I wanted to be on. 4. Will likely go back later to fix these issues as I think it would be fun!- Wrap up for delivery 14. Final Q/A pass 15. Second draft of code annotation 16. Test on an exported build (tested on Windows) 17. Write build instructions 18. Second draft of README.md
- Gimbal control scaling fix
- Currently the gimbal controls will scale with the object
- Decoupling Gimbal Control from the specific object so that any object in the scene can be selected and manipulated
- Adding planar transformation
- Adding step controls using “Ctrl” key
- Adding multi-axis gray gimbal controls
- Adding camera controls
Existing build can be found in the zip archive at this Google Drive link:
https://drive.google.com/file/d/1x5rEWqyZxMfdC0gkF3OfmYF5G83PSRx-/view?usp=sharing
- Go to File > Build Settings (Ctrl + Shift + B) to open the Build Settings dialog
- Ensure base.scene is included in “Scenes in Build”, if not click “Add Open Scenes:
- Click the ‘Build’ button in the bottom right corner
- Select a new folder to export the build