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.
Anyway, the 360 degree option is just another render option and not a complicated subsystem. It can be used for creating 360 degree backgrounds for example, which has been requested a long-time ago.
pmaina
Dear RL,
This suggestion is NOT a duplicate of 405. Issue #405 is requesting for VR.
In contrast, this issue, 453, says if RL absolutely has to do VR no matter what, can they consider having a special version of iClone that has VR and another regular version without VR? So that when VR fad dies off, as it will, they are not left with massive lines of unused code and code dependencies that only increase the cost of support & maintenance!
Best regards.