|
|
|
|
|
by Gaessaki
3356 days ago
|
|
The bank had the HoloLens for a few months before I had started, but they never did much with it. Basically, they had a budget to expend on R&D and that's one of the tools they felt could be useful (and also probably to market the department to their higher-ups). Me having experience with Unity, the Kinect (the precursor technology to the HoloLens) and just barely with the HoloLens (had a chance to try it before it was publicly available while I was at Microsoft) made me an ideal candidate for the bank to hire and engage in AR projects with it. I can do whatever I want with it. I was surprised to find out after I joined that the regulations are really not that bad, less even than when I was at Microsoft. I think it really depends on the department and the function. The HR department for example is a lot more stringent (though believe it or not, they also explored VR with our team). They have a pretty good set of tutorials on the HoloLens site, though they're kind of monotone and over polished for my taste. I think the key thing is to know Unity, which I've mainly done through doing and exploring their API or youtube videos. MVA is a pretty good resource, though I haven't needed to use it. |
|
I'll be doing a summer research project and senior capstone project with it (although I have yet to try it on, I saw a few other people demo it though), and I know enough about Unity to be dangerous. I was expecting more barrier to entry on it, thanks for the information!