Issue 453
Fork iClone into VR and Non-VR verions.
How many requests do we have on Feedback tracker for VR?
Lets face it, VR is DOA for iClone and will only result in bloatware, integration bugs + troublesome legacy code down the line when VR fad dies off as it inevitably will.
I would like to request pleace that RL forks iClone into two development paths. One for VR and the other for regular vanilla iClone. This will save the regular iClone user the trouble of:
1. Bloatware with unused features
2. Unnecessary downtime due to Bugs caused by the same unused features
3. Unnecessary complication in workflow or features
4. Limitations that will delay iClone maturity.
iClone is always 80% complete because of "shiny new toys" whereas the basic core aspects of it remain a key element of frustration for users.
Submitted bypmaina
May 26, 2016