Studio questions
Read the practical questions by topic. For a specific situation, include the relevant details in your enquiry.
Answers by topic
Can a commission begin with a blockout?
A blockout is a useful starting point when the player task and technical environment are clear. Describe what has been tested already and which spatial questions still need attention.
Share the tested version and explain what the blockout already answers. Keep unresolved spatial questions distinct from desired visual improvements.
Do you work from an existing world direction?
Share the approved direction and explain its role in the game. The brief should distinguish fixed requirements from areas open to exploration, including references and any asset-use restrictions.
Include the source and intended use of references. Approved direction and permission to incorporate a production asset are separate pieces of information.
What belongs in the first enquiry?
Include the game's perspective, mechanics, target platform, engine and intended location. Explain whether you need a map, design exploration, a blockout or a developed environment.
A first message can be concise. Agree an appropriate channel before providing restricted builds, credentials or a full archive of production assets.
How are deliverables defined?
The precise files, dependencies, documentation and integration responsibilities are agreed for the project. A service category on the website does not by itself define a complete production contract.
Keep the agreed outputs and any later changes together. That makes it easier to discuss a review without silently expanding the commission.
Can supplied assets be used?
Provide their origin, permitted use and technical details. Rights and dependency restrictions need checking before assets enter a delivery. References and usable production assets should be identified separately.
A supplied asset can carry technical as well as rights restrictions. Identify formats, dependencies and any permitted modification conditions before use.
How should feedback be organised?
Connect each observation to the player task, a review view or a technical constraint. Consolidate priorities where possible, and distinguish a structural issue from a preference about visual treatment.
Include the view or player situation where the issue occurs. That gives a spatial observation a context another reviewer can inspect and discuss.