Create a reference 'viewer' application as a basis to start exploring implementation. Specific choice of engine should be established for this project, keeping in mind the requirements of target platforms desired by line #2 requires easy porting to mobile platforms, while still supporting desktop VR platforms. While it may be desired to created specialized standards-compliant viewer applications for various platforms, at this stage let's keep focused on one target until we're more established.
What is the motivation for this suggestion?
Why is this important?
What are the use cases for this suggestion?
What should the outcome be if this suggestion is implemented?
Explain the suggestion with enough detail that someone familiar with the process and environment of the project can understand the suggestion and explain it to others.
It should include at least one end-to-end example of how the community will use it along with the specific details with outlying use cases.
If there is any new terminology, it should be defined here.
What are the advantages of the suggestion?
Explain the advantages of using this suggestion
What are the disadvantages of the suggestion?
Explain any disadvantages or trade-offs to using this suggestion
How will this be work within the O3DE project?
Explain how this suggestion will be work within the foundation or its groups.
Are there any alternatives to this suggestion?
Provide any other alternative ways that have been considered.
Explain what the impact might be of not implementing this suggestion.
If there are other similar suggestions previously used, list them and explain which parts may have solved some or all of this problem.
What is the strategy for adoption?
Explain how new and existing users will adopt this suggestion.
Point out any efforts needed if it requires coordination with multiple SIGs or other projects.
Explain how it would be taught to new and existing users.
Summary:
Create a reference 'viewer' application as a basis to start exploring implementation. Specific choice of engine should be established for this project, keeping in mind the requirements of target platforms desired by line #2 requires easy porting to mobile platforms, while still supporting desktop VR platforms. While it may be desired to created specialized standards-compliant viewer applications for various platforms, at this stage let's keep focused on one target until we're more established.
What is the motivation for this suggestion?
Why is this important? What are the use cases for this suggestion? What should the outcome be if this suggestion is implemented?
Suggestion design description:
https://lists.openmv.org/g/fig-virtualworldsim/viewrow?id=37932&rowid=3237877&lv=1&p=RowNum%2C%2C%2C50%2C1%2C0%2C3237877
Explain the suggestion with enough detail that someone familiar with the process and environment of the project can understand the suggestion and explain it to others.
It should include at least one end-to-end example of how the community will use it along with the specific details with outlying use cases.
If there is any new terminology, it should be defined here.
What are the advantages of the suggestion?
What are the disadvantages of the suggestion?
How will this be work within the O3DE project?
Are there any alternatives to this suggestion?
What is the strategy for adoption?