>>57103854What to do next (specific improvement proposals)
・We will think of ways to reduce the workload. In cooperation with the terrain design, we will create size patterns and corresponding camera values in advance, and create a state where only the default settings are required.
->We can also hire more people.
->We can add functions. (Can we automate the scroll stop?)
->We can share the implementation. (Can some parts be shared with background graphics? Scroll stop, for example.)
Where was the problem?
Was the cost-effectiveness right?
An environment where we have to set up a large amount of dedicated data.
->We can create an environment where this can be improved.
Improvement proposal
->We can reduce the amount of settings on the system side.
Example: A function to automatically hide the camera if it sinks into an object.
・We will design and set up the system to avoid specifications that change the camera values as much as possible.
We will use the checklist of things to watch out for from the start of niji+ development, and check them at the appropriate times.
We will take videos during development and objectively check each specification and behavior. (Ikuta-kun said it actually looked good)
There is a big advantage in being able to check repeatedly and share with others without having to start the game every time.
・For large-scale changes, from the early stages, try to design and set up with the game camera and the promotional camera in mind.
・Those who don't get motion sickness should take the opinions of those who do into consideration.
-> It would be good to have an open quality check environment.
->From niji+ onwards, a person in charge will be appointed and a system will be created to conduct reviews.
