# ManYue visual-scale checks: reference conditions for size and distance

Language: en
Canonical: [ManYue visual-scale checks: reference conditions for size and distance](<https://allluckly.cn/en/guides/manyue-visual-scale-reference-check/>)
中文：[中文 HTML](<https://allluckly.cn/guides/manyue-visual-scale-reference-check/>)
English: [English HTML](<https://allluckly.cn/en/guides/manyue-visual-scale-reference-check/>)
Published: 2026-11-05T00:00:00+08:00
Modified: 2026-11-05T09:38:59+08:00
Author: Bison

Check shared planes, stated scales and viewpoint before distinguishing screen size, compositional exaggeration and in-story dimensions.

English translation of the [Chinese original](<https://allluckly.cn/guides/manyue-visual-scale-reference-check/>), translated on 2026-11-05. Original publication dates, attribution, code and version notes are retained.

A larger image on screen need not depict a larger object, and an enlarged detail cannot directly measure a figure elsewhere. Check one size judgement in ManYue by establishing comparison conditions and references. This differs from route-map reading and assumes no ruler, distance tool or perspective reconstruction. Conclusions remain bounded by the evidence.

## Choose one clearly stated size question

Choose a completed scene asking whether a doorway is tall enough or two props are equal-sized, recording edition, chapter and objects. Specify actual dimensions, image proportion or subjective impression rather than one vague “larger.” Start without extreme lens distortion or deliberate exaggeration and retain the full page instead of differently resized screenshots. A legitimate outcome is insufficient comparability; do not force an answer by treating a familiar object as a universal ruler.

## Check spatial comparability

Check common ground, depth and side-by-side placement, including foreground versus distance. Small distant depiction does not establish a smaller object, and equal-height people can differ through posture. Record occlusion, upward or downward viewing angle and the object’s own tilt separately. If only projected outlines are comparable, limit the result accordingly. Recheck conditions after a cut instead of carrying screen-centimetre measurements into another view.

## Verify that the reference has a known size

Prefer stated dimensions or repeated same-plane objects. Unspecified cups, bricks and character heights cannot simply receive familiar real-world sizes. An invented card explicitly labelled ten centimetres wide can assist a rough ratio only under comparable plane and perspective conditions; an unlabelled card is merely a shape cue. Log reference origin and applicability, leaving unreadable numbers unknown instead of guessing them after zooming.

## Separate within-panel ratios from cross-panel comparisons

With sufficient conditions, describe a within-panel approximate ratio as an image estimate. Across panels, first inspect scale, perspective and close-ups. Rotation and paired-page viewing change display size, not fictional dimensions. Fit-to-width is not an authorial scale bar. Identify what an inset enlarges before using it. Attach conditions to any ratio instead of presenting decimals that exceed manual precision.

## Separate compositional emphasis from in-story growth

A figure filling a panel may reflect a closer view or emotional exaggeration rather than growth. Check neighbouring references, reactions and wording. Conversely, do not dismiss explicitly depicted shrinking or enlargement as style. Compare close-up, depth change and actual growth using distinguishing evidence. Without scale conditions, avoid physical conclusions; an imposing composition can be described as an expressive effect rather than a measurement.

## Test the initial judgement with a counterexample

Find another completed appearance with a clear posture or viewpoint change and test the original size claim. Differences between standing straight and bending or crouching require revised comparison conditions, not claims of fluctuating dimensions. Retain inconvenient evidence and state which inference it weakens. One useful case suffices without collecting every appearance. If only changing image proportions are established, stop there rather than declaring an authorial error or contradictory world rule.

## Keep complete-page and reference locations

Save supported references or an external log for the question, stated dimension and counterexample, with target/reference panel positions. Leave the reader and return using the record, first inspecting the whole page and then the detail so plane relationships remain recoverable. Label your own diagrams as not necessarily to scale. Recheck after source or cropping changes instead of reusing screen measurements. Do not stretch artwork to equalise objects; that changes the material rather than solving comparability.

## Finish the condition list and size conclusion

Finish with comparison goal, reference source, spatial conditions, supported ratio and unknowns. Familiar cups may have unknown dimensions; one panel can contain unequal depth or tilt; zoom changes display rather than fictional size. Where conditions fail, state that actual size remains undetermined and retain the supported compositional observation. That result identifies needed evidence without turning unverified screen numbers into world-building facts.

## Related guides and sources

[ManYue inset-panel reading: check boundaries and viewpoint](<https://allluckly.cn/en/guides/manyue-inset-panel-viewpoint-boundaries/>); [ManYue maps inside comics: read the legend before checking a route](<https://allluckly.cn/en/guides/manyue-in-world-map-legend-route/>).

Checked on November 5, 2026: [Apple public version information](<https://itunes.apple.com/lookup?id=6753895889&country=cn>) lists ManYue 2.0.4, requiring iOS / iPadOS 15.0 or later. Feature scope follows the [official App Store description](<https://apps.apple.com/cn/app/id6753895889>) and the installed version. This article provides reading and checking methods you can perform; it does not claim step-by-step physical-device or private-server testing. Manual records, external tools and actually visible controls are identified separately, and reading analysis is not presented as an existing automatic application feature.

