Bison’s Creative & Development Notes

Cape Lighthouse: build a geometric seascape with 17 closed paths in VectorPaint

2026-10-23T07:25:17+08:00

This lighthouse uses a square 1080 × 1080 px canvas, named for the Cape Lighthouse square project. A warm sun sits on the left; purple mountains and a blue sea establish the horizon below. The lighthouse stands on the green cape at the right, sending a triangular beam out from its lantern room. The white sky is generous and the tower is white too, so I added a black outline to the tower at the end.

Although some shapes look circular or rectangular, this piece uses closed pen paths drawn point by point. The sun is an eight-point polygon. The lantern room, bands and wave highlights are independent closed colour shapes too. The exercise is about placing nodes, closing paths and stacking flat colours.

The demonstration uses an iPhone Duo simulator and a local VectorPaint build, 1.0.7 (6). Tool positions follow the build shown in the video; the App Store version may differ.

A small palette separates sea and lighthouse

The recording uses black, white, terracotta, amber, moss green, blue and purple from the favourite palette. The HEX values below are sampled from large flat areas in the exported PNG to help you make a close version.

Use	HEX
Sun, lantern light and beam	`#F7B53D`
Distant mountains	`#875CBA`
Sea	`#4578D6`
Cape	`#4A7A59`
Rock, roof and tower bands	`#E04C2E`
Door, window, lantern frame and tower outline	`#000000`
Tower, wave highlights and white space	`#FFFFFF`

Warm colours are concentrated in the sun and lighthouse, while blue and purple separate the sea and mountains. The green cape gives the white tower somewhere to stand; the warm-red rock at the lower right echoes the roof and bands. Begin with this palette, then compare colour changes once all objects are complete.

Decide which shapes will cover which

The depth order is simple: the sun is furthest away, the mountains cross in front of it and the blue sea meets their base. The green cape and lower-right rock cover part of the sea, with the lighthouse on the cape.

Draw the large shapes in that order so new colour areas naturally sit in front. This piece uses one layer and 17 closed-path objects. The door, window, bands and lantern light can each be selected separately.

Use this list to check the objects kept in the final piece:

Content	Object count	Relationship to adjacent shapes
Sun, distant mountains and sea	3	The mountains cover the sun’s lower edge; the sea meets the mountain base
Cape and foreground rock	2	Cover the lower-right part of the sea
White tower	1	Stands on the green cape
Black lantern room, warm light and triangular roof	3	The light sits inside the black lantern room; the roof covers its upper edge
Two warm-red bands	2	Run across the tower
Black door and upper window	2	Sit in the lower and upper parts of the tower
Three white wave highlights	3	Spaced across the left-hand sea
Warm light beam	1	Extends from the right of the lantern room
Total	17	Excludes mistaken short lines deleted during drawing

Begin by looking only at the first five objects. Once the sun, mountains, sea, cape and rock fit together, the scene already reads as a coast before the lighthouse appears.

Make a closed colour shape with the pen

The repeated operation is to select the pen, tap nodes at the outline’s corners and return to the first node to close the path. Then set the current object’s fill and turn off any unwanted stroke.

Corners are the key. A simple mountain or a tower band does not need extra nodes along each straight edge. More nodes make later selection and editing harder. Keep a few clear turning points, close the path and inspect the shape.

After finishing an object, switch to the selection tool and confirm that the new object is selected. Open Object Properties → Appearance, set the fill and turn off Enable Stroke where it is not needed. In Favourite Palette below, confirm that the colour targets the fill, choose it and tap Done. Then begin the next object. This check helps where small shapes crowd together: the yellow lantern light is close to the black frame, and the bands cover part of the white tower.

The other 16 objects have no stroke, so their colours meet directly. The tower alone receives a black stroke at the end, with a width of 4 pt. Its white edge is weak against the white sky; the outline makes the silhouette readable from top to bottom.

Use the sun and mountains to set the heights

Draw the sun first. Close eight nodes around a nearly circular outline, add the warm fill and remove the stroke. This polygon sun shares the mountains’ angular style; it does not need a perfectly smooth circular edge.

Close the distant mountains with eight nodes as well and fill purple. Vary the peak heights, dipping through the middle before the second mountain. The range passes in front of the sun and hides its lower edge, establishing the first overlap.

The blue sea meets the mountain base. Define a horizontal sea line, then close a large area below it and fill blue. Leave room for the cape and lighthouse. This step is only for the large colour area; add no waves yet.

Check three things before adding detail: enough sun remains visible, the mountain base meets the sea cleanly, and the blue area forms the main lower part of the picture. Small details can wait until those relationships work.

Give the lighthouse a base with cape and rock

The green cape rises from the lower part of the picture towards the upper right, leaving a relatively level place for the tower. It covers one corner of the blue sea. A few angled edges describe the slope without a fragmented outline.

Add a warm-red rock at the lower right. It meets the green cape and closes the composition along the bottom. There is no rock texture here; the foreground supports the lighthouse through larger colour areas and sloping edges.

Close both shapes with the pen, fill them and remove their strokes. Pause to check where the lighthouse will stand. If the tower is too near the cape’s edge it may look suspended. Keeping its base inside the green area makes the relationship steadier.

Draw tower, lantern room and roof separately

The white tower is a quadrilateral, narrower at the top and wider below. Leave the top for the lantern room and meet the cape at the bottom. Keep it upright, with its sides spreading slightly outwards, and postpone decoration.

Draw the black lantern room, then place a smaller warm-coloured light inside it. The black is the lantern room’s own fill, rather than a thick stroke around a yellow rectangle. Two stacked objects make the structure clear.

Use a warm-red triangle for the roof. It is slightly wider than the lantern room so a little eave extends on each side. Add two tower bands in the same warm red, then a black door near the base and a black window higher up.

Each small part is a separately closed and filled object. Order the roof, bands, door and window according to which should appear in front.

The first small window did not close properly and left an unwanted line. I selected that mistaken line with the selection tool and deleted it normally, then drew a taller window, closed it and filled it black. The deleted line is not part of the final 17 objects.

If windows or wave highlights will not close, check node spacing

A failed detail is not always a colour-setting problem. In a small window or narrow wave highlight, neighbouring nodes can be too close. The start, corners and closing point crowd into a tiny screen area, making the final tap hard to place confidently.

I also deleted the first narrow wave highlight, then redrew it with the nodes further apart. The finished image keeps three long, narrow white triangles. They are separate shapes, not one continuous curve.

When following along, zoom in before drawing details. That changes the view, not the artwork dimensions. Check the closed outline before filling. If you accidentally create a short line, selecting and deleting it before redrawing is easier to judge than repeatedly tapping around a tiny endpoint.

The door, window and wave highlights need not be as thin as possible. At full-composition view, the door should still read as a door, the window should stand apart from the tower, and white wave marks should separate from the blue sea. That is enough.

Use a triangle to point the final beam

Add the warm light beam last. One end narrows beside the lantern room; the other spreads towards the right-hand edge, making a clear triangle.

The beam uses the same amber as the sun and lantern light. It is a separate closed, filled triangle.

After drawing, check the white tower against the white sky one final time, then enable the 4 pt black stroke for the tower alone. Keep the other large colour shapes flat and without strokes.

Check the lighthouse in three iPhone Duo states

After finishing and confirming the Saved indicator, use the bottom of Device Hub to switch through Open → Partially Open → Closed → Open. The end of the video shows these steps through sampled simulator-window views. Waiting is removed so the states are easier to compare.

In this session the open view showed 56%, the partially open view about 29%, the closed view about 27%, and reopening returned to 56%. These percentages describe the editor view; the artwork and PNG remain 1080 × 1080 px.

After each switch, wait for the interface to settle. Then check the light inside the black lantern frame, the continuous black outline around the white tower, and the separation between the three wave highlights. When closed, the left-hand tools are more compact and small objects are harder to select. Return to Open for awkward detail work so the start and corner nodes are easier to confirm.

Switching displays briefly produced a black screen before the app recovered. The video keeps a little of this transition footage and labels the material as sampled device-window views shown step by step.

Check canvas dimensions and PNG pixels separately

The app exported a 1080 × 1080 px PNG with a white background. The artwork image on this page uses that native export directly.

The editable original and the webpage PNG have different jobs. The original keeps separate objects so you can change a band, adjust a mountain or move a wave highlight. PNG flattens the current view into one pixel image.

Open Share → Export & Share → PNG Image. Choose Full Canvas, 1× scale and a white background, then tap Export PNG. Check the white sky and outer edges in the preview, then verify the PNG’s actual pixel dimensions. Editor zoom affects the view, not the exported size. For a white sky, check the export background too; empty space is not necessarily a white background object you drew.

Open the exported image on its own and view the whole composition. Check that the tower’s black line is complete, that the three wave marks have not joined, and that the lantern light remains inside the black frame. Then zoom in on details to distinguish path-outline problems from a webpage simply displaying the image at a small size.

For the basics, read fills and strokes; for object organisation, see layers and groups. Compare PNG, SVG and editable originals in choosing export formats. For canvas units versus output pixels, see canvas size and units.

Moonlit Pines: build a geometric night landscape with Aquarell polygon selections

2026-10-23T06:22:25+08:00

I wanted a quiet night landscape: two small pines on the left, a taller one on the right, mountains across the middle and a moon in the upper-right sky. Rather than covering the lake in ripples, I placed just three bright reflections below the moon.

I settled on a flat, geometric approach. The mountains, snow, pine crowns and moon keep their angular edges: define each outline with a polygon selection, then fill with the current colour. The twelve small stars are separate marks made with a 10 px brush at 100% opacity.

This demonstration uses an iPhone Duo simulator and a local Aquarell build, 1.0.5 (1). The instructions follow the build shown in the video; the App Store version may have a different interface.

Save the bright colours for the moon and snow

The canvas is 1400 × 1000 px. This piece uses only five main colours:

Use	HEX	Role in the composition
Sky and lake base	`#101830`	A continuous deep-blue base for the whole picture
Distant mountains	`#486884`	Separate the mountains from the sky
Snowcap	`#B8CDDF`	Brighten the tallest central peak
Pines and near shore	`#080F1D`	Anchor the lower edge as a foreground silhouette
Moon, stars and lake reflections	`#FFF1CC`	Lead the eye to the upper right, then back to the water

The colour panel accepts six-digit HEX values. For an eight-digit value, end with FF to keep the colour opaque. Edges are antialiased, so sample near the middle of a flat colour area.

The deep blue serves as both sky and lake base. The horizontal edge at the foot of the mountains helps establish the water. Warm white appears only in the moon, stars and reflections, while the snow is cooler; the two bright areas therefore remain distinct.

Four layers: check which one is active

The piece keeps four layers. From bottom to top they contain the deep-blue base; the mountains; the pines and near shore; and the snow, moon, stars and reflections. Before every fill, check the active layer in the layer panel, then return to the canvas.

Set the background colour to 101830FF and use Fill Layer to lay down the deep blue. The ending FF makes the colour itself opaque; it is separate from brush opacity. Check colour opacity again when switching to the mountain, snow, foreground and warm-white colours, so the previous transparency setting does not carry into the next shape.

In this local build, the background-fill path is More → Settings → Layer Tools → Fill Layer. The menu at the top of the layer panel mainly handles duplication, merging and grouping; it is not the background-fill entry point used here.

Use Selection for individual shapes. Fill Layer acts on the whole layer, while Fill in the selection panel acts on the selected region. Laying down the base before making local selections saves unnecessary rework.

Set the mountain rhythm with one polygon

The first mountain shape uses a ten-point polygon selection. Start low on the left, pass through the left peak, the taller central peak and two rises on the right, then close along the foot of the mountains. Fill the completed selection with the current mountain colour, #486884.

A polygon selection lets you inspect the outline before adding colour. The peaks need not be evenly spaced in height: the middle peak is tallest, the left is lower and the right valley dips again. One flat colour can still describe an undulating mountain profile.

To follow this composition, put the highest peak about two-fifths of the way across the canvas and leave enough sky around the upper-right moon. Keep a stable, horizontal base so you do not need a separate line to explain the shore.

Open Layer Tools → Selection → Polygon → Draw Selection. Tap each corner on the canvas, then finish. With a valid selection, reopen the selection panel and choose Fill under Selection Actions. Set the selection mode to Replace before the next shape so it does not reuse the previous region. After finishing, use Deselect in the selection panel to inspect the actual colour.

One snowcap gives the mountain a direction

Use #B8CDDF for the snow. Extend it to either side of the tallest peak, with several turns along the lower edge to make an asymmetric snow line.

Keeping snow on the central high peak concentrates the main shape. A piece of mountain colour pushes upward into the lower edge, stopping the snow from becoming a neat little triangle pasted onto the summit.

Think of the snow as folded paper laid against the peak. Follow the mountain along the upper edge, then vary the width below. Detailed rock textures can wait; get a readable silhouette first.

Frame the scene with three pines

Use #080F1D throughout the foreground. Keep two smaller pines on the left and a taller one on the right, then join their bases with a gently uneven near-shore silhouette.

The crowns are geometric outlines too. Keep the top narrow, extend wider branches lower down, then turn back towards the trunk. Tap a selection around the branch corners, close it and fill to make each pine silhouette.

The two left pines differ in height, and the tall right pine does not touch the far-right edge. The open lake between them leaves room for reflections. Even imagined in black and white, the side trees, central peak and upper-right moon remain readable as separate parts.

The shore only needs to connect the tree bases and anchor the lower edge. Keep it dark rather than adding another bright area at the bottom.

An angular moon, twelve stars and three reflections

The moon uses the same warm white as the stars, #FFF1CC, with visible polygon corners. It sits in the upper right, noticeably larger than the stars and offset from the central snow peak.

Before adding stars, use Deselect in the selection panel and confirm that no local selection or selection overlay remains. Otherwise, brush marks may be clipped to the old region and the on-screen colour may be harder to judge.

There are twelve stars in the finished sky, each placed with a 10 px brush at 100% opacity. They are not evenly scattered: spacing varies around the moon, on the left and above the mountains. The empty sky is part of the composition.

Add only three reflections on the water. They widen from top to bottom, roughly below the moon, while keeping long, angular silhouettes. Draw each separately, like three narrow strips of bright paper laid over the deep-blue lake.

Three reflections are enough to suggest water. More detail would fill the quietest central area, so I stopped there.

Check the native PNG for missing edges

Choose PNG in Share & Export and keep the size at 1400 × 1000 px. The finished image on this page comes directly from that app export. Keep the editable project in Aquarell for further changes to trees, colour and layers; use PNG for the blog and sharing.

After export, zoom in on three things: the snow-to-mountain boundary, the thinnest pine trunks and the small stars. In a narrow webpage column, the browser shrinks 10 px stars until they look tiny or intermittent. That is different from missing export content.

Then zoom back out and check that the moon, snow peak and reflections lead the eye through the whole picture.

Check iPhone Duo open, partially open and closed

After finishing the piece, use the bottom of Device Hub to switch through Open → Partially Open → Closed → Open. The end of the video shows these four actual states as sampled simulator-window views, with waiting removed.

First inspect the full composition while open, then observe the canvas and toolbar positions when partially open, and finally check the more compact closed view. A brief black screen can appear during a switch. Wait for the app to return before touching the canvas.

In this local build, the Closed state still kept a large canvas view, obscuring part of the moon’s upper edge. Reopening made the whole landscape visible again. If a closed view is incomplete, return to Open to check the composition and compare the native PNG above; a partial outer-screen view alone does not show that an artwork edge is missing.

Device state and canvas pixels are separate: the original and exported image stay at 1400 × 1000 px. A viewport change only changes how much is visible at that moment.

What to try next

For your own version, change one thing first: move the moon to the left or replace the tall right pine with a shorter group. Keep the five main colours and generous sky space so the effect of the composition change is easy to compare.

For more app practice, try the three-layer workflow, limited-palette exercise and colouring inside a selection. For export pixels versus webpage display size, see checking a blurry export.

Aquarell creative process: paint a night scene with soft pools of light

2026-10-23T02:46:01+08:00

This exercise paints out-of-focus lights at night. Mint and lilac spread along a diagonal, with one warm light in the upper left and a few small bright points connecting the empty areas. It is a simple composition for feeling how one brush changes with size and opacity.

Prepare a deep-blue base and a layer for light

The canvas is 1400×1000 px. Fill the background with deep blue #101830, then add a layer above for the lights so later adjustments leave the base intact. Find Fill Layer under More → Settings → Layer Tools → Canvas.

The video starts with this background already filled. Choose a soft-edged round brush and test a short mark: a coloured centre fading towards the edge suits the exercise. The same size setting can look different with another brush, so inspect a test mark before deciding whether to resize.

Use very short drags: move a little and release, leaving an almost round spot. If the mark becomes too long, shorten the next movement. For the basic controls, read the brush size and opacity tutorial alongside this exercise.

Colours and settings used in this session

Every opacity value below is brush opacity. The sizes are for this 1400×1000 canvas. If you halve the canvas, try halving the brush size first, then adjust by eye.

Use	HEX colour	Brush size	Brush opacity	Count in this piece
Deep-blue base	`#101830`	Fill Layer	—	1 layer
Mint glows	`#6CF0D7`	220 px	50%	4
Lilac glows	`#B49CFF`	220 px	50%	3
Warm-white focal light	`#FFF1CC`	260 px	75%	1
Small stars	`#FFF1CC`	32 px	100%	5

To change colour, open the colour panel, enter and apply the HEX value, then return to the canvas. Read colour and opacity together: a light colour at 50% over deep blue appears darker and softer than its palette swatch.

Stagger mint and lilac along a diagonal

Set the brush to 220 px and 50%. Place mint marks from the lower left towards the centre and upper right. Keep the lower-left pair closer together and the upper pair a little further apart. The deep-blue gaps are part of the composition; leave them until all colours are in place before deciding whether to add more.

Switch to lilac while keeping the same size and opacity. Stagger three marks below and to the right of the mint ones. The lower-left lilac can overlap a mint edge; leave more space around the other two.

Pause after this group. Repeated strokes in the same place accumulate colour and brightness, changing the delicate effect. Compare on an extra layer before deciding which version to keep. For layer adjustments, see the layer opacity tutorial.

Finish with a large light and a few small stars

Switch to warm white #FFF1CC, set the size to 260 px and opacity to 75%, then make one mark in the upper left. A little larger and brighter than the nearby glows, it gives the eye somewhere to settle. Keep the edge soft without drawing an outline.

Keep the colour, reduce the size to 32 px and raise opacity to 100%. Place five small bright points in dark areas above, left, below and right, avoiding the most crowded glows. They regulate the spacing rather than fill the picture; a small number is enough.

Finally, hide the toolbar and inspect the full canvas. Look at the light–dark balance before judging each spot’s roundness. If everything is equally bright, removing a few points is often more useful than adding more.

Keep the original, then share the image

The video ends on the complete composition. Afterwards, I chose PNG through Aquarell’s Share & Export and saved it to Files from the system share sheet. The export remains 1400×1000 px.

The PNG presents the exercise; keep the in-app original for colour and layer changes. For a separate project backup, read saving and backing up native artwork.

Open the 1400×1000 finished image · Continue with a limited palette

VectorPaint creative process: a sunset mountain scene in three colours

2026-10-23T02:33:05+08:00

Sunset Mountains uses only three colour shapes. The sun keeps eight corners, the two mountains have different heights and the white canvas has no added texture. The exercise is about placing shapes and seeing how a later object covers an earlier one.

Keep the composition simple

Create a square 1080×1080 px canvas and give it a name you can find again. The canvas already exists when the video starts; every subsequent shape is drawn point by point inside VectorPaint.

Leave roughly the lower quarter empty. Place the sun in the upper half, slightly right of centre; put the taller blue peak on the left and the lower purple one on the right. The shapes do not have to fill the canvas. Empty space makes the edges clearer.

This session uses Amber, Blue and Purple directly from Favourite Palette. Draw the composition first; it is easy to try your preferred colours afterwards.

Close the sun with eight points

Choose the pen and tap eight nodes around the sun: top, upper right, right, lower right, bottom, lower left, left and upper left. Tap the first node again to close. No curves are dragged out, so the result is an angular octagon.

The sun is about half the canvas width. The nodes need not be mathematically equidistant, but balance its left and right extents. The temporary fill before closing may look like an irregular fan; continue around the outline to complete it.

Select the whole sun, open Object Properties → Appearance and turn off Enable Stroke. Find Favourite Palette below, confirm that the colour targets Fill, then tap Amber. If nothing changes, check the panel title: edit the selected object rather than the default style for the next path.

Give both mountains a common baseline

Keep the pen and draw a triangle at the lower left: left end, peak and right end, then return to the start. Put the peak just below the sun’s centre and the baseline about three-quarters down the canvas. Turn off the stroke and set the fill to blue.

Let the blue mountain cover part of the sun to establish depth. Keep this overlap; there is no need to cut the sun or make a mask.

Place the second mountain on the right, with a slightly lower peak. Extend its left end into the blue mountain and put its right end near the canvas edge. Match the first mountain’s baseline, close the path, fill purple and remove the stroke. The later purple object covers part of the blue one, making a slope between the colours.

If the mountains merge visually, first increase the colour difference, then compare peak heights. If a small uneven edge appears along the bottom, move the bottom nodes rather than hiding it under a thick line. Continue with the pen and paths tutorial for node editing.

Return to the whole composition

Switch to the selection tool and tap an empty canvas area to deselect, removing the node handles. Check three things: breathing room above the sun, space between the mountains and canvas edges, and one straight baseline across the blue and purple shapes.

Leave out gradients and text for now. Three flat colours are enough to describe the sunset and mountains. For another version, move only the sun or replace its octagon with a circle and compare. To add a title and develop a poster, see the geometric poster tutorial.

Save the original and export a white-background PNG

After checking the Saved indicator, open Export & Share → PNG Image. This session uses Full Canvas, 1× scale, 1080×1080 px and a white background. Tap Export PNG, then use Save to Files when the file appears in the system share sheet.

White suits this small square image and its empty space. To place the mountains over another design, export an additional transparent version, while keeping the editable original. For different uses, see PNG, SVG and PDF export options.

The image below is the PNG exported from VectorPaint in this session, with the complete canvas retained.

Open the 1080×1080 finished image · Continue with fills and strokes

Yearn virtual controller: adjust size, opacity and haptic feedback

2026-10-23T00:00:00+08:00

Start by checking whether your thumb reliably reaches the intended button, then whether controls cover the game. Yearn's controller settings include size and transparency. This guide compares them in the same game menu instead of proposing one set of values for every phone.

Use a consistent grip before adjusting

Choose a game that starts successfully and stop at a menu that does not require continuous reactions. Hold the phone normally: two-handed landscape and one-handed portrait place your fingers differently, and testing on a table does not fully represent handheld use. Keep the default size first, test all four directions and two common action buttons, and note where accidental presses happen most easily.

If a physical controller is connected, disconnect it first and see whether virtual buttons return. External-controller connection can affect on-screen controls. Do not mistake hidden controls for a transparency setting that made them invisible. Preparation only requires a stable set of touch controls; there is no need to change skins and aspect ratio simultaneously.

Start with a small size change

Return to Settings, open the controller page and find the size slider in the virtual-controller section. It offers scaling within a range, plus Compact, Default and Large presets. Starting from the default, move one step in one direction, return to the same game scene and repeat the button actions.

Larger buttons make targets easier to find but may reduce space around the picture. Smaller buttons look cleaner without necessarily making moving inputs easier. Judge accidental presses and grip comfort rather than assuming a larger control looks more professional. To reposition the entire layout, check the controls actually offered by the current skin and interface. A size slider does not mean every button can be freely dragged.

Use transparency to keep buttons recognizable

When adjusting transparency, use a game scene containing both light and dark areas. Buttons clear against a black menu can disappear over a light scene. Start with fairly high opacity to keep them visible, then reduce it slightly after learning their positions.

After every change, check that directional outlines, action-button letters and Menu remain recognizable. Fainter controls do not enlarge the actual game picture; they only change the visibility of the overlay. To see more of the image, examine orientation and game scaling next rather than continually changing button transparency.

Test directions and action buttons separately

Test up, down, left and right first, then diagonal movement. A game may accept only four directions or may not accept diagonals in its current menu, so test in a scene with a movable character. Hold a direction and move your finger slightly to see whether it easily touches Menu or another function button by accident.

Check an action button with a brief action such as confirm, jump or back. If the game needs simultaneous presses, verify each button separately before combining them. When a combination fails, note the two buttons, phone orientation and scene rather than immediately resetting every size to another extreme.

Check haptic feedback separately

General settings include haptic feedback, and related switches may also appear on the controller page. Compare enabled and disabled feedback on a device that supports it before deciding whether you want the cue. iPads and different iPhones have different hardware capabilities. No vibration does not mean a button failed to send input to the game.

Haptics help confirm that a touch occurred, but the game's actual action remains the input result. If feedback is distracting or tiring during longer use, turn it off and test whether you can still operate accurately. When the sensation differs, compare device hardware and system settings before deciding whether the input actually worked.

Allow a test round for each orientation

After testing portrait mode, rotate the device and compare the controls with the game picture in landscape. The wider orientation changes where your thumbs land; a size comfortable in portrait can feel cramped in landscape. Stop at a safe menu before rotating rather than changing grip during an important action.

Record preferences such as default size in landscape with clearly visible buttons, or one step smaller in portrait. Every slider value need not become a standard answer. If the current interface saves only one configuration, use your more common orientation as the baseline and accommodate the other by changing grip or making temporary adjustments.

Questions and check results

Why do I still press the wrong button when the buttons are large? Your thumb's natural landing position may not match the button, or the skin's shape and game artwork may make the target difficult to distinguish. Return to the default appearance for comparison, then change only one size parameter.

What if controls still cover the picture after adjusting transparency? Transparent buttons still occupy touch areas. Try landscape, a slightly smaller game picture or a paired physical controller, checking the control and visual results separately.

Aim for settings that reliably support directions, confirm, back and pause in your usual orientation. Small, comparable changes make a suitable combination easier to find than repeatedly switching every preset.

Yearn speed controls: fast-forward through waits and slow down actions

2026-10-23T00:00:00+08:00

Fast-forward can help with repeated opening animations and slowly appearing text, while slow speed can help you observe actions. Yearn provides speed controls in the game menu as well as an on-screen fast-forward control. This guide first establishes a baseline at normal speed, then changes the pace a little at a time to distinguish the effects of speed settings from those of device performance.

First save a checkpoint at normal speed

Open a game that already runs reliably, stop in a safe place, and first confirm that it is running at normal speed. Save a checkpoint manually and note the scene and save slot so that you can return to a known position while experimenting with speed changes. For your first attempt, avoid critical scenes where you only get one chance, and do not overwrite your only save with an experimental state.

Play a short section at normal speed and observe animation timing, text speed, and audio. Return to the same point for every later comparison: you are assessing changes caused by the speed setting, rather than differences in frame rate, dialogue length, or sound effects that naturally occur between scenes.

Start with a lower fast-forward multiplier

Open the speed option in the game menu, choose a setting slightly faster than normal, then return to the game. Shorter waits through animations and faster character movement indicate that the actual execution timing has changed. If only the interface shows a multiplier while the game appears unchanged, note the current platform and scene. Do not immediately conclude that the setting has no effect on any content.

Try holding the on-screen fast-forward button briefly, then release it and check whether the speed indicator and actual pace return to normal. Check the speed level selected in the menu separately as well; before any action requiring precise input, explicitly return to normal speed, then continue.

Use fast-forward separately for dialogue and action

For repeated dialogue, fast-forward reduces waiting; when it is time to choose an option, return to normal speed in advance so that a single button press does not skip through multiple choices. In walking or action scenes, fast-forward reduces your reaction time, and a distance that was easy to control may suddenly take you past the target, so test it in an open area first.

Do not treat enabling fast-forward and repeatedly pressing Confirm at the same time as the default way to play. You could skip important text, trigger menu options, or write an in-game save without realizing it. For your first comparison, speed up the parts that run automatically while continuing to control your inputs deliberately.

Use slow speed for observation and still check normal operation

After selecting slow speed in the speed menu, choose an easily recognizable action, such as a character jumping, an object moving, or a menu animation. Compare it with the same action at normal speed to confirm that what you are seeing is the action taking longer, rather than the screen freezing or input becoming unresponsive.

Audio may behave differently at slow speed, and some content may not be suitable for prolonged operation at a nonstandard pace. After observing, restore normal speed and test directional input, confirm, and pause. If an issue occurs only at a nonstandard speed, include the multiplier in your report rather than describing it as an error that necessarily occurs during default operation.

A speed multiplier does not guarantee device performance

Selecting a higher multiplier only sets a faster execution target; the device and emulation core may not be able to sustain it. More complex platforms, demanding scenes, or device heat may limit actual speed. If audio stutters or the display becomes unstable, return to normal speed for comparison instead of raising the multiplier further to try to ‘compensate.’

You can record your observations in two rounds: first, whether normal speed is stable, and second, whether a particular faster setting is useful. If normal speed itself is unstable, address the basic running problems first. Increasing the multiplier will not automatically make a slow device faster, nor can you use it to infer compatibility and performance for every console.

Distinguish fast-forward from turbo input

Fast-forward changes the timing of game execution; turbo simulates repeatedly pressing a particular button. They work differently even though both can make actions look faster. To troubleshoot, first restore normal speed and check whether the same button still triggers repeatedly. This lets you assess execution speed and input state separately.

For example, if a menu scrolls rapidly on its own, first check whether a direction or confirm button is still held, then check the speed multiplier. A character repeatedly performing one action may indicate an input-state issue; if the whole image and music speed up, execution speed is more worth checking. Observing this distinction usually points you in the right direction faster than resetting settings at random.

Questions and final checks

The audio sounds wrong after fast-forwarding. Do I need to import the game again? First restore normal speed and compare the same scene. If normal behavior returns, simply note which multiplier caused the change. There is no need to alter the original file immediately.

What if the character keeps moving after I return to normal speed? Release all buttons, pause, and check controller input. Speed settings and an input that remains held are separate issues. If necessary, reconnect the controller and compare with touchscreen controls.

When you finish the exercise, confirm that normal speed has been restored, then save a separate checkpoint that you are satisfied with. The ideal result is to understand which kinds of waiting suit fast-forward, which actions benefit from observation at slow speed, and how to return reliably to normal play, rather than finding the highest multiplier.

Keep each comparison brief

For the first test, observe just one menu animation or a short straight route. Run it at normal speed, speed it up, and then return to normal. Keep the starting point the same for each run and note any audio stuttering or input that overshoots the target. If you need repeated attempts, keep the starting point in a separate practice slot rather than overwriting a confirmed milestone. A short, repeatable comparison makes suitable uses easier to identify than prolonged, aimless acceleration.

Yearn screenshots: save a game image and organise your records

2026-10-23T00:00:00+08:00

When you reach a special scene or want to report a display problem, use Yearn’s screenshot option to save an image first. A screenshot stores the image visible at that moment and is useful for recording and sharing; you still need a separate save for game progress. Manage the two kinds of files separately so you can find what you need later.

First decide what the screenshot is for

If you are recording a game’s completion, first advance to a point where all the text and characters are fully displayed. If you are reporting a problem, keep a scene that clearly shows the issue instead of cropping it down to a tiny fragment. When comparing the effects of a setting, keep both screenshots on the same screen as closely as possible.

For constantly changing content, open the game’s pause menu before using the screenshot option. Check the saved result to see exactly what the screenshot includes. Save game progress before important actions, and especially avoid repeatedly resetting or exiting the current game just to capture an image. A visual record and a recoverable state serve different purposes.

Save an image from the game menu

Open the pause menu on Yearn’s gameplay screen, find the screenshot option, and use it. Note any completion or error message from the app, then return to the game. If the scene is still changing, first check whether the screenshot captured what you wanted before deciding to retake it. There is no need to press the button repeatedly in quick succession.

A save message indicates that the app ran its screenshot procedure, but you still need to open Photos to confirm the actual result. Device permissions, system state, and whether the image was successfully captured can all affect the final file. Treating ‘tap Screenshot’ and ‘see the saved image’ as two separate steps prevents discovering only when you are ready to share that the file is missing from its expected location.

Check the file and permissions in Photos

Open the system Photos app and check recently added items for the corresponding image. Zoom in to inspect the text and all four edges, making sure it is not a previous frame, a black screen, or an unexpected menu state. If you cannot find it, return to Yearn and look for an explicit error, then check the app’s Photos permissions in system settings.

Depending on the system version, permissions may be under the app’s page in Settings or a privacy-related page. Use the options your system actually provides, then return to Yearn and take an easily recognizable test image. When a save message appears but no photo can be found, start with this small test instead of repeatedly capturing the same hard-to-distinguish scene.

Distinguish app screenshots from system screen captures

Yearn’s screenshot option saves the game image. An iPhone or iPad system screen capture records what is currently displayed on the device screen and may include controls, menus, and system interface elements. Try the app’s option first for a clean game image. To show a button’s location or an error message, a system screen capture is usually more direct.

The two methods may produce images with different dimensions and contents, so identify which type of file each is before comparing them. Do not use a system screen capture cropped in Photos to judge whether an original game screenshot is missing its edges. Keep the originals and make copies for sharing to simplify later troubleshooting.

Develop a way to organize your screenshots

Create a game-record album in Photos and organize images by game or purpose. A few clear categories, such as ‘Completion Records,’ ‘Display Comparisons,’ and ‘Issues to Report,’ are easier to maintain than numerous empty albums for individual play sessions. Keep a few images that demonstrate the result, then review and remove the redundant ones.

If you also save an image to Files, you can use the naming pattern ‘game abbreviation_date_purpose.’ For example, ‘示例游戏_20261023_画面边缘’ is a suggested personal filename, not a fixed name automatically generated by the app. Before sharing, check that the image contains no unrelated personal notifications or account information, especially when using system screen captures.

Describe a problem with two images

When reporting a display issue, keep the full screen in the first image; the second can enlarge the specific area. In your written description, include the game’s platform, portrait or landscape orientation, whether you use a physical controller, and what you did just before the issue appeared. The full image supplies context, while the close-up makes text or edges easier to inspect. The combination is usually more effective.

For example, to report a cropped display, first capture a menu at normal proportions, then capture the same menu after changing the scaling and point out which line is missing. Do not send only an enlarged detail and leave the recipient to guess what should have been there. For audio or input-lag issues, a still image can show only the interface state; also describe the action and result in words.

Common questions and checks after saving

Can a screenshot restore a game? No. A screenshot is an image and does not contain the full state required for the emulator to continue running. Before exiting or switching devices, make a separate in-game save or save state and check that you can load it using the corresponding tutorial.

What if the app says it saved an image but there is nothing in Photos? First check Photos permissions and recently added items, then test again with a clear, still image. The app’s internal files and the system photo library are separate locations. If necessary, use a supported file-sharing procedure to inspect the app’s documents, but do not delete the app as a way of looking for images.

After taking a screenshot, confirm that it opens in the expected location, shows the complete content, and has a clear purpose. When sending it, select the correct original or sharing copy and keep your own record afterward. The next time a similar problem occurs, you can compare what changed without having to recall the settings from memory.

Yearn screen size: adjust scaling, aspect ratio and margins

2026-10-23T00:00:00+08:00

A small-looking picture in Yearn may reflect a mismatch between the phone and original console's aspect ratios, or space occupied by virtual controls. Establish what you want to enlarge before changing picture size, so that larger text does not push status information and controls against the screen edges.

Choose a fixed scene that is easy to compare

Open a working game and stop at a menu containing title text, circular shapes and a border. Text helps assess sharpness, circles reveal horizontal stretching, and the surrounding border shows cropping. Compare the same scene where possible rather than drawing conclusions from two screenshots with differently sized characters.

Record the current orientation, whether a physical controller is connected, and whether touch buttons appear. All affect available space. If the picture shifts when a controller connects, first check whether virtual controls hide with the connection state, then investigate scaling. This avoids mistaking an ordinary layout change for a display fault.

Distinguish aspect ratio from picture size

Picture size determines how much space the same image occupies; aspect ratio determines its width-to-height relationship. Proportional enlargement keeps circles round and characters' proportions intact. Widening only horizontally makes characters broader and changes spacing between text strokes. A wide phone screen does not mean the game needs to cover every part of it.

Consoles do not all share one original aspect ratio. Handhelds, home consoles and dual-screen systems can naturally leave different borders on the same phone. Judge proportions using known in-game shapes before deciding to enlarge the picture. This is more reliable than judging quality from border width alone.

Change one scaling setting at a time

In Yearn's display settings, find Picture Size or Scale, following the labels actually shown on your device. Record the current value, increase it slightly, and return to the fixed comparison scene. Check top status information, bottom text and both sides before deciding whether to enlarge it further.

Inspect all four edges after every change. Important information is not always central: speedometers, character status and notes below menus may sit at the edges. An enlarged central character is easy to notice, while a missing corner line may remain unnoticed until play. Checking edges after each adjustment reduces repeated resets.

Use empty space for the controls

With touch controls, empty space keeps fingers and virtual buttons away from important content. Try your normal grip and watch whether your thumbs often obscure a character or dialogue. A slightly smaller picture with reliably reachable directional controls is often easier to use than a completely filled screen.

If the buttons are too large or opaque, adjust virtual-controller size and transparency separately. Shrinking the entire game to solve every control overlap also sacrifices text legibility. Check picture completeness and ease of control as separate questions to find the setting that actually needs changing.

Recheck landscape orientation and a physical controller separately

After adjusting portrait mode, rotate the device and view the same scene again. Landscape offers different available width and height, so a scale that suits portrait may not suit it. Check system orientation lock before deciding whether the layout failed to change or the app is using a landscape layout while retaining the content's aspect ratio.

Check the edges and center again after connecting a physical controller. Hidden touch controls may make a larger picture preferable, but retain the complete content. For dual-screen platforms such as NDS, inspect both displays separately. If one is clear and the other too small, address the dual-screen layout before enlarging everything.

Keep a simple record of your choices

In Notes, record five items: device, orientation, platform, picture size and controller state. Add an observation, such as portrait touch controls with readable subtitles and complete bottom notes, or landscape with a physical controller and side borders without distortion. This is more useful than a slider value alone because the same value may look different on another screen.

To restore a setting, first return to the original orientation and controller state, then restore its value. Matching the scene conditions makes comparison fair. Screenshots help, but enlarged viewing in Photos changes their apparent size. Also check the actual play view on the phone.

Questions and final checks

Edges look stair-stepped after enlarging. Is the setting wrong? Older games' pixel edges become more visible at larger sizes. Distinguish the original pixel style from stretched proportions and cropping before reducing scale. Increasing display size alone cannot add detail absent from the original game.

Why do black borders remain? When the game and phone have different aspect ratios, showing the complete picture normally leaves empty space. Filling the screen may require cropping or stretching, so decide which result matters more. A complete picture is usually easier to verify in games with information in their corners.

Return to real gameplay: move continuously, open menus and read some text. Check portrait and landscape. Once the main content is complete, character proportions look natural and controls are easy to reach, use these settings as a starting point for everyday play. Repeat the comparison for a different console's picture later.

Yearn on a TV: check picture and delay with iPhone screen mirroring

2026-10-23T00:00:00+08:00

To put Yearn's game display on a TV, start with the iPhone or iPad's system screen mirroring. It displays the current device screen on a compatible receiver and lets you assess the larger image and controller use. Smooth results depend on local performance, the wireless network and TV display settings together.

Prepare a device that supports screen mirroring

Confirm that the TV, Apple TV or other receiver supports Apple's screen mirroring, and enable it according to that device's instructions. Connect the iPhone or iPad and receiver to the same wireless network where they can discover one another. Hotel or public networks may isolate devices, so an identical network name does not guarantee that they can connect.

For the first setup, place phone and TV fairly close so that weak coverage and compatibility are not tested simultaneously. Prepare a game you already own that runs normally on the phone. Play briefly to confirm picture, sound and button response before connecting, giving you a clear local reference for any later problem.

Establish the system connection in Control Center

Open Control Center on the iPhone or iPad, choose Screen Mirroring, then select the TV or receiver. If a code appears on the TV, enter it on the phone as prompted. Apple provides these system controls; their appearance may vary with the system version.

After connecting, stay on the Home Screen or an ordinary page and confirm that the TV shows the same content. Then open Yearn and the test game. Establishing system mirroring first separates two problems: the TV is not connected, or the game is connected but displayed unsuitably.

Understand whole-screen mirroring first

System screen mirroring follows the device's current screen. Opening Control Center, switching apps or showing a system prompt may also appear on the receiver. Arrange notifications and screen orientation before playing for a more consistent TV picture. To finish, return to Screen Mirroring and choose Stop Mirroring.

Mirroring the whole screen differs from sending only game video to an external display. For this process, first check whether the TV shows the complete phone screen. If borders remain, compare the phone's aspect ratio and orientation, then check the TV for additional scaling or overscan settings.

Adjust orientation and keep the edges visible

Observe portrait orientation first, then rotate to landscape and confirm that system orientation lock does not prevent rotation. TVs usually suit landscape better, but games have their own aspect ratios. Use text in all four corners of a game menu to check whether the TV crops top or bottom information.

If the phone shows everything but the TV crops the edges, the TV's display-area setting is a more likely cause. Look for the receiver's original-aspect or fit-picture options and change one at a time. Do not begin by greatly shrinking Yearn's picture to offset TV cropping, or you will need to restore it when playing on the phone alone.

Observe input delay in three stages

Before mirroring, press a physical or virtual button and watch the phone's response. Enable mirroring and compare phone and TV together. If the phone responds promptly but the TV updates later, most delay lies in transmission or the receiving display. If both are slow, check local game performance and controller connection first.

Choose repeatable actions, such as moving a menu cursor or walking a short distance. Do not rely only on an unpredictable battle. If the TV offers a game display mode, try it according to its official instructions and compare the same action again. Network improvements and display-mode changes require observed results; a switch's name alone cannot establish that delay is solved.

Troubleshoot missing picture or sound one layer at a time

If the receiver is absent from the list, check that it is powered on, mirroring is enabled, and both devices are on a network that permits communication. If it appears but connection fails, look for a confirmation prompt on the TV, then end the connection and select it again. Apple's official troubleshooting also includes updating software and restarting the relevant devices.

If there is picture but no sound, confirm that the phone itself can produce sound, then check TV volume, mute and the selected output device. If the picture disconnects while the game continues on the phone, pause before restoring the connection. Save important progress in advance using the save guides, rather than blindly pressing Back or Exit while the TV picture is missing.

Questions and real-use checks

If the game appears on TV, is it suitable for action games? You also need to check the response from a button press to the displayed action. Delay feels different in turn-based or slower games, so judge your own use case. Compare briefly before deciding to use the TV as the main display.

Can I turn the phone screen off and keep displaying the game on TV? This guide uses system mirroring of the entire screen. Lock-screen and background behavior depend on the system and app state. Test while the device shows normal gameplay rather than treating continued output with the screen off as a guaranteed feature.

Finish by checking three things: complete edges on the TV, sound from the intended device, and input delay within your acceptable range. Stop mirroring when finished and confirm normal phone display. Record the receiver model and network environment so future connection issues have a direct comparison rather than requiring you to guess through the entire process again.

Yearn save states: keep key progress in separate slots

2026-10-23T00:00:00+08:00

Save states create checkpoints at identifiable moments, such as before a level, after an action sequence, or before new settings. Yearn's save list provides multiple slots. This article distinguishes saving from loading and verifies the scene a record restores instead of assuming that a timestamp means progress is safe.

Understand the two buttons' directions first

The save list in the game menu commonly offers Save and Load. Save writes the current runtime state into the slot; Load brings the slot's state into the running game. One changes the saved record, the other changes the current game. Pressing Save when you intended to restore old progress may overwrite it with the present scene.

Learn with one practice game and an empty slot. Write 'store = Save; restore = Load' in your notes and remember the current slot number. Do not make your first experiment on the only save from a long game or tap a button simply because its color is prominent. Read the action name first.

Give slots different purposes

Use the first slot for a fixed milestone, the second for current practice, and another for temporary comparisons. The app need not name their purposes automatically. Record them yourself, such as Before Level Two, Before Jump Practice, or Before Speed Adjustment. Then Slot and a timestamp are enough to identify each record.

Multiple slots preserve different checkpoints, not repeated copies of one state. Before saving, check the character's position, current menu, and existing timestamps. If you cannot explain why a slot should be overwritten, choose an empty one first. Verify the new record before deciding whether the old one is still needed.

Verify loading through scene changes after saving

Save at a recognizable position, return to the game, and move forward slightly or open another menu. Reopen the same slot, tap Load, and observe whether the scene returns. Character direction, objects, or menu options can be references, provided the before and after states are clearly distinct.

If the timestamp changes but the loaded picture does not visibly change, the two states may be too similar or loading may have failed. Try a more recognizable checkpoint and watch for errors or a waiting state. Do not judge by repeatedly pressing Load; allow time to observe each operation.

After success within one run, check reopening

After the first successful load, exit safely through the game menu, reenter the same game, and inspect whether the slots remain. This differs from testing in one run: it checks whether the app finds the associated records when it identifies the game again.

Rescanning, renaming, reimporting, and changing devices all require rechecking game-to-save associations. Complete this check on first use. If slots are empty after reopening, retain current app data and originals. Do not delete the game and retry or create many new records that overwrite useful diagnostic clues.

Treat game-version and core changes cautiously

Save states are generally tied to the game data and emulation state at the time. Do not assume another regional version, modification, or file sharing the same name can load an old slot. After app or core updates, test copies and noncritical records first. Identical filenames do not establish complete identity.

Keep the relationship among original ROM, app version, save time, and slot purpose. It is more helpful than only a Save Successful screenshot. Before trying another edition, make an independent backup rather than silently replacing active content through same-name overwriting.

Check the scene before overwriting an old slot

Before overwriting an old slot, recall its purpose and compare the displayed time. If the character is in a failed state, pause menu, or temporary test scene, choose another empty slot rather than replacing a reliable milestone.

Before a key scene, place a reliable milestone in a separately documented slot and use another slot for repeated temporary attempts. The list selects current records; it does not automatically retain history before every overwrite. Read the slot's purpose before deciding whether its old record is worth replacing.

Questions and final checks

Why is Load unavailable? Check whether the slot contains a record or shows Empty. An empty slot has nothing to load. If an existing record cannot load, note the game version, slot number, and error instead of overwriting it first.

Does a missing slot after exit mean its file was definitely deleted? Not necessarily. The visible list and its association with underlying records are different matters. Retain data and begin with backup and diagnosis instead of reinstalling and potentially removing material that still exists.

At completion, you should have two slots with different purposes, at least one verified scene restoration, and a record of the result after reopening. Apply the process to important progress only after confirming those facts. Keep failures as unresolved issues rather than replacing checks with 'it should have saved.'

Keep two checkpoints visibly distinct

Put one checkpoint before a level and another at a recognizable place within it. After loading, compare scene, character position, and menu state rather than only time. If the records are too similar, create an obvious difference in the practice copy and check again so nearly identical pictures do not make the button seem ineffective.

Yearn file recognition: distinguish platform formats and disc companion files

2026-10-23T00:00:00+08:00

Before importing a self-supplied game file into Yearn, understand what it is. A console name in the filename may be unreliable, and extensions are not converters. This article builds a personal file checklist so wrong file selection, missing tracks, and game incompatibility can be investigated separately.

Record the files as originally received

Inspect file information in the system Files app and record the full name, extension, size, and whether it came as one file or a folder. For a long name, open its information panel to confirm the suffix rather than guessing from a thumbnail. Keep a source description in a neighboring text note so the file's purpose is still clear weeks later.

Do not rename or convert yet. Files that work together may reference each other by name, especially disc indexes and tracks. Copy a complete practice set and organize that copy. Renaming is useful organization only when you understand the internal format. Changing zip to gba does not create a runnable handheld game.

Classify single-file formats

Yearn lists NES, SNES, GB/GBC, GBA, N64, NDS, Genesis, and PS1. Common single-file extensions provide initial clues: nes for NES; sfc or smc commonly for SNES; gb and gbc for Game Boy; gba for GBA; nds for NDS; and md or gen commonly for Genesis.

These mappings help selection and inspection; they do not guarantee compatibility for every file with an extension. For a file named Practice Game.gba, expect it in GBA after import. If it appears under an unexpected platform, revisit the source instead of hiding the identification difference with a cover or rename.

The common N64 forms n64, z64, and v64 belong to the same platform. Retain the original extension initially, check whether Yearn recognizes it, then assess runtime. There is no need to rename every suffix uniformly for appearance.

Inspect disc-image files together

PS1 files may use bin, cue, img, iso, pbp, or chd. CUE is particularly easy to misunderstand: it normally describes disc tracks and associated files, so a small size does not mean a small game. A cue of only a few hundred bytes without its referenced tracks cannot usually restore missing data by being imported alone.

Keep a game's companion files together with their original names and letter case. For multiple tracks, read the CUE filenames in a text-capable tool and compare each with the directory. Do not organize by deleting BINs that look duplicated; different tracks may hold data or audio.

Extract archives into inspectable files first

A download or transfer may produce a zip, rar, or 7z container, which is not itself a ROM. Yearn's public platform support does not imply that every archive can be extracted directly. Extract through system file tools or an existing archive utility first, then inspect the actual files.

After extraction, inspect the innermost contents rather than handing the app an outer directory full of notes, screenshots, and duplicate copies. Resolve password, damage, or missing-volume errors in the archive first. Yearn cannot repair a game file that has not been fully extracted. Do not gamble on supposedly universal conversion programs from unfamiliar pages either.

Use a checklist for small-batch import

Create three columns: source filename, expected platform, and import result. Choose three clearly sourced samples from different platforms, import them individually, and record Yearn's category. If one fails, you still know whether the other two succeeded instead of treating one batch as entirely successful or failed.

Watch same-name files on the same platform particularly carefully. Current import behavior places files in the app directory by filename, so reimporting an identical name may replace a copy. Distinguish regions and versions before importing. Renaming CUE-related files also requires updating references, not just one visible filename.

Check file presence separately from successful operation

A library entry after import means the file has at least entered identification. Reaching the title screen, accepting input, and continuing to run are later checks. Record distinct results such as Unrecognized, Visible After Import, Startup Error, and Normal After Title Screen. These are more specific than Will Not Open.

File contents may also help identify an unknown bin or iso. If it is assigned to an unexpected platform, verify the real format at its source rather than insisting based on its extension. Use the dedicated track-file tutorial for complex PS1 images, keeping this article focused on format identification and preparation.

Frequently asked questions

Must manuals and covers in a game folder be imported too? Retain them as your own supporting material, but select only required main files and companion tracks when importing a game. Distinguish images, text, and runnable content.

Can different regional versions of the same game share saves? The title alone cannot determine this. Content version, emulator core, and save type may affect loading. Retain the pairing between the original game file and its saves, then test loading with copies.

The checklist works when you can identify each file's role, expected platform, and companions before import. Even if compatibility problems appear later, you will no longer confuse archives, index files, and complete games.

Import PS1 disc images into Yearn: CUE, BIN and multiple tracks

2026-10-23T00:00:00+08:00

PS1 images often consist of several files. If you see a small CUE and a large BIN, retain them as one set before choosing the launch entry point. Organizing companion relationships before import is more useful than repeatedly changing extensions after a black screen.

Keep the complete original folder first

Prepare a game image you lawfully possess and are entitled to use. Create a separate directory in Files and keep every file from the same disc together. Make an import copy while retaining the unchanged original. Include the game name and disc number in the directory name so multi-disc files do not become mixed.

Confirm that files have fully downloaded to the device. Cloud filenames do not mean large track files are local. Check sizes after downloading. For an archive, extract it with a supported tool and inspect its real contents. Yearn identifies game files; an arbitrary archive is not necessarily a directly runnable image.

Distinguish CUE and BIN roles

A CUE is usually text describing track-to-file relationships, while a BIN may hold actual disc data. A tiny CUE without its referenced tracks is not a complete game. Conversely, one BIN may not retain all track information for a disc, especially a title with audio tracks.

Use a plain-text reader to inspect your CUE copy, focusing on referenced filenames. Compare spelling, extensions, spaces, and disc numbers with the actual files beside it. Reading requires no changes to track types or addresses. If those fields are unfamiliar, keep the original contents and return to completeness checks.

Start importing with a simple single-track pair

For the first check, choose a clearly sourced simple CUE/BIN pair already sharing a base name. In Yearn's Add flow, select file import and select the related files together. Inspect platform and name in the library afterward, then try launching. Retain the original folder for preparing another copy if needed.

Matching names are only a common convention; actual references follow the CUE contents. Do not rename files just to make names match and forget the references. Do not import only the smallest file and assume every other track copied too. Verify through complete startup, reading, and sound behavior.

Multi-track images need extra checks

If the directory has several Track-numbered BINs, count them and compare the CUE references. Keep every related file in one working directory rather than selecting only the first data track. Yearn's import handling may vary across companion structures. Judge complex multi-track content by actual import results in the current version.

For a title screen without music, check missing audio tracks or references that cannot find files. This differs from unreadable main data. Record the scene where content is missing instead of immediately changing the extension. Renaming a suffix neither restores lost tracks nor converts the image format.

Separate BIOS issues from image issues

PS1 startup may also need suitable BIOS files. Check BIOS status in Yearn's settings and follow the relevant tutorial for files you are entitled to use. Missing BIOS and missing disc tracks are different problems: one concerns system files, the other disc material. They cannot substitute for one another.

If another PS1 game runs and only this image fails, prioritize this set's completeness and format. If all PS1 games fail while other consoles work, focus on PS1 BIOS and platform requirements. This comparison reduces unnecessary reimports.

Avoid same-name overwriting and multi-disc confusion

Before importing, check for an existing same-name file in the library. Back up important progress and clarify your goal before reimporting a corrected image. Identical names may cause replacement. Repeated import is not version management that automatically retains every historical copy.

Retain clear Disc numbers and separate companion relationships for multi-disc works. This tutorial covers file preparation and one image's runtime check only. Confirm an appropriate mid-game disc-switching entry point in the actual version. Verify the first disc before relying on the title for long-term play.

Questions and final checks

The list shows similar CUE and BIN entries. Which should I delete? First identify the actual file and startup behavior behind each entry, then address duplicate display. Do not delete one merely because of size or name; the other may still depend on it. Keep a complete external copy before organizing so restoration is easier.

Does CHD or PBP support mean every such file runs? An extension describes a container or format class. Internal content, creation method, and platform compatibility still affect results. Confirm that the file belongs to the target platform rather than treating a format list as a guarantee for every game.

Finally, check the title screen, game start, scene transitions, and sound, covering an actual disc-read operation where possible. Record the file list, platform, BIOS status, and failure point together. For feedback, these facts and screenshots without private paths are sufficient; you need not upload game content or personal storage addresses.

Prepare Yearn for offline travel: games, BIOS and saves

2026-10-23T00:00:00+08:00

For Yearn on a flight or without stable internet, the key is actual local files plus a short offline test, not simply opening the app beforehand. This article limits preparation to one main game, one backup option, and recoverable progress so missing material is found before departure.

Choose the content you will actually use first

Choose one or two games that already run rather than importing many unfamiliar files at the last moment. Record their platforms, complete filenames, and current app version. For several revisions sharing a title, identify the one you will use so you do not discover offline that a save belongs to another edition.

Keep lawful originals in your own backup location and the intended copies on the device. Covers and descriptions may come from the network and do not prove local file availability. The real result is entering and operating the game without a connection.

Confirm that source files have downloaded

For ROMs from iCloud Drive or another provider, finish downloading in the system Files app before importing. A visible cloud filename does not mean the contents are local. If importing still needs a network fetch, do not leave it until the trip.

After import, return to Yearn, clear search and platform filters, and confirm the target is visible. For disc images, prepare the main file and all companion tracks together. One index file or a cover cannot replace actual game data.

Confirm BIOS and runtime requirements beforehand

For PS1 and other cases needing extra system files, check BIOS status and launch the target to its title screen. For NDS, inspect the built-in status and the specific content's runtime result. Another game on the same platform opening does not prove this one complete. Test at least the games you actually plan to play.

If missing files or loading errors remain, resolve them before departure or switch to a verified backup. Finding files and checking sources is harder without a network while traveling. One reliable backup game is more useful than a large unchecked library.

Perform an actual airplane-mode check

After preparation, save and exit the running session, then enable airplane mode. Reopen the target game in Yearn and check its title screen, sound, directional controls, and action buttons. This verifies offline behavior for the current device and content rather than assuming every file works offline from the app description.

For a Bluetooth controller, enable Bluetooth as needed after airplane mode and verify the connection. Inspect airplane mode and Bluetooth states separately. The airplane icon alone proves neither that the controller disconnected nor that it remains connected.

Load the save again while offline

Load the saved slot or use the game's own Continue menu. Compare the scene with the pre-departure record, perform a short action sequence, and save and exit normally. Reopening from the library is more meaningful than testing only within one uninterrupted session.

Cloud synchronization during offline use must wait for connectivity to return. Do not treat sync status as the result of local saving. Keep an independent backup of important progress. If an offline check fails, retain working records on the original device and note exactly which step failed.

Check battery, display, and control habits

Play briefly in the orientation you will actually use, checking grip, brightness, and picture size. For longer sessions, set comfortable brightness and prepare suitable charging. Devices, battery condition, and platform workload differ, so your own observed power use is more informative.

Fast-forward can change runtime load and control rhythm. Verify stability at normal speed before choosing acceleration. Connect and test headphones too, avoiding the discovery in a quiet location that audio still comes from the speaker. Judge each accessory by the actual connected result.

Common questions and a departure checklist

Can a game still run if its cover disappears offline? The cover is display information. Determine playability through local launch and input. If the game works, do not reimport merely to recover its cover.

Does opening the game before departure count as an offline test? Not enough. Reenter with the network disabled and load a record. Keeping the original session alive proves only that it is still running.

Finally, record four facts: the target launches in airplane mode, required BIOS status is clear, controls and sound work, and a save has loaded offline. Mark unresolved items before departure and take verified backup content rather than relying on unchecked features during travel.

Keep instructions locally before leaving too

Write a local note covering common buttons, normal exit steps, and save-slot purposes. During travel troubleshooting, restore this verified state before trying other settings. If the backup game uses another platform, note its confirm button and pause method too so instructions need not be searched without a network.

Organise the Yearn library: search, favourites, covers and recent games

2026-10-23T00:00:00+08:00

Once a library spans several screens, the most useful organization often connects filenames, platforms, and your habits rather than endlessly changing covers. Yearn offers search, platform filters, sorting, grid and list views, and favorites. This article uses roughly ten imported items to establish a maintainable lookup method.

Use list view to inspect basic information first

Switch to List in the library's upper-right view menu and inspect names and platforms individually. Grids aid image recognition; lists expose duplicate or overly long names and wrong platforms. Do not delete apparently identical entries yet. Compare file information in their details first.

Keep a name reference list. For different regions or editions, use version information already present in the source rather than guessing from cover colors. Renaming underlying files after import may affect recognition and save associations, so organize copies beforehand where possible. Keep stable names and originals for games already in progress.

Combine search with platform filters

Select one platform first, then enter the most distinctive part of the name. For a handheld practice game, filter to GBA and type two or three characters. With no results, clear search first and restore all platforms next. This is the shortest way to rule out excessive filtering.

Search finds objects in the current library; it does not download games from the internet. Try shorter fragments for spelling differences, regional abbreviations, or English names. No search result does not immediately mean a file was lost. Check filters first, then whether import assigned the expected platform.

Use sorting for different lookup purposes

Name sorting suits comparison with your file checklist; platform sorting suits grouped browsing of a mixed collection; date-related sorting suits recently organized or used content. Inspect the selected sort option rather than assuming the list always follows the order you remember.

Switch between two sorts on the same ten-game batch and confirm that entries merely move rather than appear or disappear. If a name seems gone, search for it and see whether it moved to another section. Separating sort changes from file changes reduces accidental deletion.

Favorites expresses your priorities only

Favorite the two or three games you genuinely plan to play next, then confirm them on the Favorites page. Favorites then serves as a shortlist while the library remains the full collection. Favoriting everything immediately produces a second equally crowded library.

Unfavoriting should change only the favorite marker, not delete the game. Actual deletion has a separate action and confirmation. After organizing, leave and return to check the markers. Keep a personal list for more important long-term selections. After reopening or changing devices, compare it with Favorites to recover frequently used entries promptly.

Use covers for recognition, not file verification

Find Change Cover in the game information page and use an image you are entitled to use. Choose a clear subject without tiny text and check recognition in list or grid thumbnails. Cover ratios and card presentation may crop the image, so keep the subject central and important details away from extreme edges.

For inaccurate automatic metadata or cover matches, verify title and platform before replacing anything manually. A correct cover does not prove ROM completeness, and a missing cover does not prevent running. Executable files, metadata, and display images serve separate purposes. Checking them separately is more effective than repeated imports.

Use Recently Played to return to recent content

Recently Played helps reopen a game from a short time ago. Confirm its file and platform, especially when several versions share a name. The recent list is not a save list: after opening, you still choose where to continue through the game itself or save page.

Before clearing recent items, confirm whether the interface refers to history or game files. The consequences differ. To retain progress, do not delete and reimport a game merely because it disappeared from Recents. Search the full library first, then check its available saves.

Common questions and a daily organization order

Why do favorites and recent history need an extra check? They depend on how the app identifies game entries, while saves and files have their own associations. Returning and reopening after establishing a list is safer than relying on one icon for all important information.

What if a corrected cover does not make the game open? A cover only changes presentation. Return to checks of file, platform, BIOS, and startup errors rather than repeatedly replacing the image.

For weekly organization, clear filters to view the full library, verify new names, favorite two or three games, and inspect recent items. You should then be able to find targets through search and explain the difference between unfavoriting and deleting. Larger libraries benefit more from clear names and a few useful markers than memorizing every thumbnail position.

Troubleshoot Yearn launch: from a successful import to a running game

2026-10-23T00:00:00+08:00

A game in Yearn's list means the app recognized an item it can list. Playing still requires a complete file, appropriate platform identification, necessary system files, and working runtime and input. Following this order preserves useful evidence more easily than repeatedly deleting the app.

Describe the failure precisely first

Record where failure occurs: rejected during import, no entry afterward, returning to the list after tapping, persistent black screen, or a visible picture with unresponsive controls. These concern different stages. Add platform, extension, Yearn version, and device model to create a reproducible description first.

For example, 'import succeeded, listed as PS1, black screen on opening, pause menu still appears' is more useful than 'the game is broken.' Test on a retainable copy and back up important saves. Change one condition per round and record whether it helps instead of changing BIOS, filenames, and controller settings together and losing the cause.

Start with file completeness

In system file management, confirm that the original downloads locally, has a plausible size, and is not an unextracted outer archive. For multi-file disc images, retain all references and companion tracks. A filename visible in the cloud differs from complete local contents.

Recheck the extension and actual platform. Renaming one extension to another is not conversion. For unclear sources or unknown internal content, return to your lawfully held originals rather than trying arbitrary extensions at random. Settings cannot easily compensate for an unreliable file foundation.

Confirm platform identification in the library

Open the entry information and inspect its assigned platform. Generic extensions, especially BIN or ISO, may be used by several systems and do not prove a PS1 file. Compare the displayed platform with your file information before proceeding.

If the platform is clearly wrong, stop launch attempts and inspect the imported material and original format. Do not arbitrarily change the title to remove the wrong label; a title change does not change the underlying format. Keep the original and import record and report identification details if necessary instead of letting a wrong category distort later checks.

Check required BIOS files separately

If the platform needs BIOS, inspect its state in Settings. For PS1, verify that your supplied system file has both a recognized name and correct contents. A correct name with wrong contents can still fail to launch. A Present status is not final proof of every game's compatibility.

Compare another lawfully usable game on the same platform that previously ran. If all games on that platform fail, inspect platform requirements first. If only one fails, revisit its structure, edition, and compatibility. Do not delete all platform data for one game's problem.

Check pause and input after a picture appears

If the title screen appears but buttons do nothing, check whether the game is paused, demonstrating play, or waiting for a specific button. Try the virtual controller, then the physical one. If touch works but the controller does not, investigate pairing, recognition, and button response rather than reimporting the game.

If the picture freezes while the pause menu works, try resuming normally or exiting and reopening, and record where it happened. Reset restarts the current game session. Confirm recoverable progress before using it. When save state is uncertain, do not treat reset or force-quit as harmless routine controls.

Use narrow comparisons for performance problems

If a game starts but picture and audio stutter, restore normal speed and check whether a high speed multiplier was enabled accidentally. Close unnecessary background load and keep temperature and power conditions suitable for normal use. Compare the same scene before and after rather than mistaking different level workloads for improvement.

Record whether the issue is limited to one platform or game. Platform support does not mean every title behaves identically on every device. Verify the basic process with stable content, then document individual compatibility problems. One failed title does not establish that the whole app is unusable.

Common questions and a feedback checklist

Will reimporting automatically repair saves? Import mainly handles game files. Saves also involve separate files and associations. Before reimporting, keep external copies and existing progress so same-name replacement does not add variables. Investigate saves separately through loading and backup checks.

Why does another emulator run it while this one fails? Emulators can differ in cores, format handling, and version support. The comparison is informative but does not establish the specific cause. Platform, format, failure location, and reproducible steps are more useful than naming only the other app.

Summarize the result in four lines: environment, steps, expected result, and actual result, with necessary screenshots. Omit private directories, accounts, and game content itself; extensions and companion-file structure are enough. Record a successful change too, so similar files can be checked from a clearer starting point later.

Yearn landscape and dual screens: give the game and controls their own space

2026-10-23T00:00:00+08:00

Landscape is more than a rotated portrait image: it changes grip, controller space, and picture margins. NDS also has two screens, so single-screen experience cannot be applied directly. This article stabilizes orientation and layout before deciding whether to resize the picture.

Start in a scene that can be paused

Choose a game already working, save a checkpoint, and pause through the menu. Before rotating, confirm that system orientation lock permits landscape. If the device lies very flat, sensors may struggle to determine orientation. Hold it upright normally, rotate it, and observe the interface.

Hold the phone steadily in landscape and check that menu, directional, and action buttons are reachable. On iPad, window width and multitasking can change the layout. Establish a full-screen baseline before trying your usual window size.

Check whether the original aspect ratio is preserved

Choose a scene with a circle, square, or character and compare shapes before and after rotation. More horizontal room does not mean the original picture must fill every pixel. Borders at the sides or top and bottom often preserve the source shape rather than waste screen space.

If characters widen or circles become ellipses, inspect the aspect-ratio mode. Enlarging the controller or lowering its opacity cannot correct image shape; those are separate settings. Distinguish display size from aspect ratio for more directed adjustments.

Leave room for both thumbs and picture

Start with default controller size in settings and recheck in landscape. With thumbs resting naturally at the sides, directional and main action buttons should be easy to reach. Menu or pause also needs a clear position so ending play does not require reaching across the whole picture.

If the picture and controller are too close, adjust game-image scale slightly rather than changing every button parameter. Return to the same scene after each change and compare a character or text. A smaller picture can improve sustained grip, but if text becomes hard to read, reconsider the tradeoff.

Identify both NDS screens first

For NDS content, identify which screen shows the main game and which handles menus or touch input. Games differ, so do not assume the upper position is always the main view. Understand both screens' roles before choosing how to hold the device.

If the current version offers NDS screen-layout settings, record the default result before trying alternatives. If a preset controls an option that cannot be changed, follow the interface explanation. After each adjustment, check both displays and touch positions, recording which arrangement suits this game.

Verify touch positions separately

For NDS games requiring touch, start with a clear, large menu button. Tap the displayed target and see whether the game selects the same position. Repeat after rotation or layout changes to confirm alignment before attempting precise touch actions.

For misaligned touch, restore the default layout and scale, then compare one variable. Do not simultaneously switch layouts, rotate, change ratios, and tap different screens; even recovery would be hard to explain. If the default still fails, record the affected screen, orientation, and target.

Confirm the layout through brief play

After checking while paused, perform a short sequence: move the character, use the main action buttons, open the menu, and pause safely again. Observe whether your hands cover important text, menu mis-taps increase, and the exit is easy to find. A good layout must work in operation, not only in a still screenshot.

Recheck after connecting a physical controller because changes to virtual-controller visibility may alter the available picture area. TV mirroring adds another display layer. Make local landscape mode work first, then handle TV proportions and margins rather than mixing two screens' problems.

Frequently asked questions

What if the device rotates but the game does not? Check system orientation lock first, then whether the app menus rotate. If menus rotate but the content does not behave as expected, record the game platform and display settings rather than immediately reimporting the ROM.

Can a dual-screen game display only one screen? Use the layouts actually offered by the current interface. Even if a single-screen option exists, check whether the game depends on the other screen's information or input. Do not ignore its role merely to enlarge the main picture.

Finally, retain one reliably usable configuration and note its device orientation and layout. If a new setting provides no clear improvement, returning to the baseline preserves usability better than piling on more adjustments.

Recheck menu placement after layout changes

After rotation, open the pause menu and confirm that Resume, Save, and Exit remain easy to find before playing again. With a stand or case, check whether grip blocks edge buttons. For dual-screen content, capture the default layout first and compare screen bounds and touch targets after adjusting, making it easier to restore a usable state.

Yearn iCloud save sync: check cloud status before switching devices

2026-10-23T00:00:00+08:00

Yearn Settings includes iCloud save sync. First aim to confirm cloud availability and completed file handling, then check whether a second device recognizes the same progress. A completed Sync indicator and actually continuing the game are separate results requiring separate checks.

Prepare a local checkpoint before syncing

On the primary device, choose a practice game, create a manual save state, and record the slot, time and scene. Save through the game's own menu too if it has one. Verify loading locally before syncing. Without a verified local record, later problems are difficult to attribute to saving or the cloud.

Before preparing another device, keep the original ROM and its version details. Sync handles save-related data; do not assume that ROMs, BIOS files, covers and every setting have also been transferred. Running the same content on a second device still requires your own legally obtained files and the necessary environment.

Check system and app cloud status

Confirm that the device is signed into the Apple Account you intend to use and that iCloud is available. The saves section of Yearn Settings includes an iCloud Sync switch. Enable it, then check the status area for unavailable, waiting or error messages.

If Manual Sync is unavailable, address the account, network and cloud availability according to the current status. Repeatedly toggling switches is not a useful new test. Resolve insufficient iCloud storage in system settings too. Record the error description when troubleshooting; public feedback does not need your email address, account identifiers or personal cloud-drive contents.

Start one manual sync and wait

Once the local record is established, run manual sync and wait until the in-progress state ends. Check the last sync time or any error afterward. Avoid saving competing progress on both devices during the process. Let one finish before checking the other so that older and newer data remain distinguishable.

Do not delete local saves or move app folders during sync, or repeatedly change networks to hurry it along. If the operation fails, retain the records and error message, confirm network and cloud availability, then retry once. Success means that sync process ended; it does not automatically prove that another device can correctly recognize every game's records.

Confirm matching material on the second device first

Install the appropriate app version on the second device, import the same ROM you retained, and prepare any required BIOS. The same game name does not mean identical files: region, revision and patches may differ. If the material does not match, stop and compare it rather than testing by overwriting cloud records.

Enable sync under the same account and wait for completion. Open the target game and inspect both its save-state list and in-game records. Compare the scene noted on the primary device instead of merely looking for a timestamp. Only loading into the expected location verifies continuation for that particular combination.

When sync completes but no record appears

Keep the primary device as the reliable source, rather than alternating between two devices to create competing latest progress. An empty list may involve either file transfer or the association between a game and its saves. Compare app versions and game material on both devices before checking sync status. Reimporting adds variables, so retaining the current state can make diagnosis easier.

Record both devices' app versions, game filenames, sync status, visible slots and actual loading results. Before further file operations, make an independent backup and ask support to assess this information. Do not guess internal identifiers and rename save files, or delete content that still works on the original device.

Sync and backup have different roles

Sync generally brings two ends toward the same state, while a backup should retain a historical copy you can identify. Even with sync enabled, back up important progress separately before migration, updates or major cleanup. When both devices can write data, a newer timestamp alone cannot tell you which record is most valuable.

Use a fixed sequence: save and verify on the primary device, complete sync, load and check on the second, then decide which device to continue using. If loading on the second has not passed, retain the first device's files and settings rather than rushing to uninstall the original app.

Common questions and completion criteria

Does iCloud sync automatically transfer game ROMs? No. This entry concerns save-related data. Prepare and check game files and BIOS files separately. A healthy cloud status does not mean the second device already has everything required to run the game.

If sync fails, can I switch it off and delete the local records first? Do not use deletion to troubleshoot a network problem. Retain the local source that still loads, check the account, storage space and network, and address the reported error.

Finishing this guide does not require an immediate successful migration. It requires clear facts: which record exists on the primary device, whether the cloud operation completed, and whether the second device recognized and loaded it. Keep the original device if the last step fails, so an unverified sync does not become your only source of progress.

Record a clear migration status

Keep three separate notes: the primary device loads correctly, the sync process completed, and the second device's loading result. If the last check has not passed, retain the primary device as the current source and do not overwrite its usable progress. Even if you return days later, you will know the exact stage reached rather than merely remembering that you once tapped Sync.

Yearn getting started: import your own first game and exit safely

2026-10-23T00:00:00+08:00

Yearn initially has no ready-made games to choose from. Prepare a game file you are entitled to use and import it through the library's plus button. This article focuses on one game: reach its title screen, operate it, save, and verify loading the save. That keeps relationships among file, platform, and settings clear when a problem occurs.

Prepare an easily verified sample

Use explicitly licensed homebrew or your own lawful backup, starting with a single-file handheld game, such as a gba file. Record its original name, size, and source description, and retain an unchanged original. Practice Game in this tutorial is only a sample filename, not content bundled with the app.

Put the sample somewhere browsable in the system Files app. If a cloud-download indicator remains, finish downloading before import. There is no need to bring in every console and hundreds of files or change advanced settings initially. A clear small sample distinguishes an unreadable file from a particular game's compatibility problem.

Add a file from the game library

Open Yearn's library, tap the upper-right plus button, and choose file import. In the system picker, enter the prepared directory, select the game file, and wait to return to the library. Import copies it into app-managed storage while leaving the source in place for later verification.

Back in the list, inspect the name and platform first. Names generally come from filenames. Cover availability and successful file import are separate matters. For an empty list, clear search text and platform filters, then check whether you selected an archive, explanatory document, or unsupported extension. A selectable file is not necessarily a loadable game.

Confirm the platform before entering

Inspect the entry's game information and confirm that the platform matches the source file. Identically named games may have versions for different consoles, so a cover is insufficient. Platform checks for a single-file handheld sample should be straightforward. PS1 disc images may additionally need BIOS and track companions; a dedicated tutorial is more efficient for those.

After pressing Start or entering the game, wait for its title screen. For a BIOS notice, inspect the corresponding platform in settings rather than renaming a ROM as BIOS. Retain full error text and note whether it appears before opening the game or after loading. This is more useful than repeatedly exiting and reentering.

Check controls with three actions

Test directional controls in the title menu, use a confirm button to enter, and finally test Start or a pause-related action. Press one button at a time and observe the menu or character response. If an opening animation is playing, wait until input is accepted before judging. A noninteractive demo does not mean the controller failed.

Keep the default layout for touchscreen controls initially. After connecting a Bluetooth controller, confirm recognition on the controller settings page. Letters on a controller's shell may not match old-console button positions. Record practical results such as bottom button confirms and right button returns before deciding whether to adjust your habits. The first check need not use every button.

Create a manual save-state checkpoint

At a clearly recognizable position, open the game menu, enter the save list, choose an empty slot, and tap Save. The interface may retain the English labels Slot, Save, and Load. Save writes the current state; Load returns the game to the state recorded in that slot. Their directions are opposite. Note the slot number and displayed time, then move a little farther.

Load that same slot and confirm that the character, scene, or menu actually returns to the checkpoint. A timestamp only shows a visible record; the restored scene is more direct evidence. Do not use your only important progress for the first experiment. Learn the Save and Load directions on a practice sample.

Check again after exiting

End the session through the game menu and return to the library. If the game has its own save menu, save there first too. Force-quitting interrupts the running session abruptly, so swiping the app away is not a routine exit step.

Reenter the same game and see whether the previous save remains available and loads. This matters: loading within one session does not prove that reopening or another device will recognize it. If it disappears or fails, preserve app data and the original ROM. Do not troubleshoot by deleting the game, reimporting it, or overwriting slots. Organize the symptoms with the save troubleshooting tutorial first.

Questions and final checks

Why is the screen black after a successful import? Import only copies and identifies a file. Runtime also depends on completeness, platform, BIOS, and emulator-core compatibility. Observe loading errors first, then compare another known-complete lawful sample instead of changing many settings.

Does a cover mean the file is correct? Covers are display information. They do not establish ROM completeness or replace startup and control checks. Similar filenames may even match metadata for different editions.

After this article, you should be able to state where the sample is stored, its Yearn platform, the save slot used, and whether it reloads after exiting. If a step has not passed, investigate that layer before batch importing.

Yearn folder import: organise a batch of games and check omissions

2026-10-23T00:00:00+08:00

Once single-file import works, folder import makes a batch easier to bring in. The goal is not to fill the library immediately, but to record counts, platforms, and same-name relationships so you know what copied and what needs separate handling. Practice with fewer than ten items before expanding.

Choose a directory with a clear scope

Create a dedicated import directory in the system Files app containing only ROMs you are entitled to use and necessary disc companions. Keep screenshots, download notes, old archives, and temporary files elsewhere to avoid irrelevant clutter. Subdirectories can organize consoles, but do not guarantee that the app will retain the same library hierarchy.

Prepare a short checklist of the expected game count. Games and files are different counts: one disc may have one CUE and several BINs while still representing one game. The file picker's item count is not necessarily the number of library entries that should be added.

Resolve duplicate names before import

Check for exactly identical filenames within a platform. For example, Practice Game.gba in two subfolders may map to the same destination filename after import. Different directories do not guarantee permanent distinction. Give source copies identifiable names, such as region or version markers, and retain a naming reference.

Rename disc files more carefully. A CUE may reference track names; renaming a BIN without updating those references breaks the relationship. Prefer retaining the entire original naming set, checking it separately, then adding it to the batch. On the first organization pass, importing fewer games is better than breaking a complete image for uniform names.

Open folder selection from the plus button

Tap the plus button in Yearn's library and choose folder import. The system folder picker differs slightly from single-file selection. Enter the target folder and use the system's Open or Select button to grant access. Download cloud files beforehand so network and file-reading problems do not arise midway through the operation.

The app scans recognizable files in the selected directory and its subdirectories. This is an import, not continuous monitoring. Later additions to the source folder should not be expected to appear automatically. For new content after an import, prepare an incremental directory and start another import.

Recheck by platform after completion

Stay in the app during import and observe the current file and progress. Back in the library, clear search and inspect platforms separately. Compare main-file names with your checklist first. PS1 companion files may not appear as separate games, which is not necessarily an omission.

Choose three representative samples: the first game, the last, and one with companion files. Check each information page's platform and size, then try reaching its title screen. A thumbnail in the library is not a runtime check. Batch copying completed and every game is compatible are different conclusions; record them separately.

Narrow the scope for missing items

If a whole batch creates no entries, confirm that the folder contains extracted ROMs and that source files are actually downloaded to the device. If only one game is missing, try importing it individually and observe unsupported-format or read errors. This separates directory permissions, file types, and individual-file faults.

If fewer entries appear than expected, check same-name destinations and disc companions before repeating the whole batch. Reimporting identical names may replace current copies and is especially unsuitable for games with important progress. List missing items and retry only those, retaining the unchanged source directory.

Manage source directories and app copies separately

Folder import copies supported content into app-managed storage; the source is not the only working location. During storage cleanup, distinguish originals in the import directory from copies in Yearn's library. Deleting a game inside the app may also affect associated saves. Existing source files do not mean all progress is safe.

After checking, store originals and the checklist in a clearly identified backup location. Do not immediately delete your only source or interpret iCloud save synchronization as a ROM backup. For a collection kept long term, record import date and platform categories so later additions can follow the checklist instead of requiring another full directory review.

Common questions and completion criteria

Will subdirectory names become game groups? Folder import finds and copies files. The library mainly organizes them by recognized platform. A source folder named Weekend Games does not automatically create a favorites group with that name. Use the library's own filters and favorites after import.

Why does one disc image set create only one entry? The app tries to avoid listing companion files beside a main file as duplicate games. Check whether the entry launches correctly rather than trying to give every extension its own library tile.

The batch is organized when every checklist item has a clear result and representative samples reach their title screens. Label unlaunched items Imported, Awaiting Check so an unverified batch is not later mistaken for a fully tested library.

Troubleshoot Yearn controller input: button positions, D-pad and stick dead zones

2026-10-23T00:00:00+08:00

If a controller works but confirm and cancel seem reversed, first establish the relationship between physical positions and the original console's buttons. A stick that keeps moving after release is a separate problem requiring different treatment. This guide uses an input table to relate button positions, game actions and stick behavior.

Build a table of actual responses first

Choose a working game and a menu you can revisit. On paper or in Notes, list up, down, left, right, lower button, right-hand button, left-hand button, upper button, shoulder button and Start, leaving space beside each for its game action. Avoid A, B, X and Y labels at first so different brands' layouts do not confuse your records.

Press and release each button separately, observe the cursor or character, then fill in the table. Holding a button and tapping it once may produce different results, so start with brief presses. If a game uses only two action buttons, the other two face buttons doing nothing does not necessarily indicate an app fault. Test within the buttons that platform actually uses.

Distinguish layout differences from incorrect input

Modern controllers and emulated platforms may label their face buttons differently. Yearn passes input to the emulator according to physical button position, so the letters printed on the controller alone cannot establish the expected game action. Check what the lower button actually triggers, then compare it with the game's settings or instructions.

If two games use opposite confirm conventions, the difference may be in the games themselves. Compare settings by repeating tests with the same controller in the same game. Do not immediately remove pairing when letter labels differ: pairing again will not usually change what the game designed each button to do.

Use the directional pad to check the basic input path

Test the four directions using only the directional pad and see whether movement stops when you release it. Follow the same route with the left stick. If the pad works and the stick does not, the basic connection and game are probably receiving input. Focus the investigation on stick settings and hardware condition.

If none of the four directions works, return to the title screen or another interactive page and check whether the current scene accepts input. If touch works but the controller does nothing, revisit controller connection checks. If neither input works, check for a paused game, stalled loading or demonstration mode instead.

Adjust the deadzone in small steps

In controller settings, find the stick deadzone: the range of input around the center that is ignored. Record the current value, raise it one step, and return to the same scene with the stick released. If unwanted movement decreases, also test whether a gentle push still responds promptly.

A larger deadzone is not always better. Too much inactive range near the center forces you to push farther before movement begins and can reduce precision. Compare settings by checking for no drift during ten seconds after release and reliable movement when slowly pushing the stick. Then confirm the feel during actual play.

Check left-stick-as-directional-pad

Controller settings include an option to use the left stick as the directional pad. For older games mainly using digital directions, it determines whether the stick can perform the pad's role. Testing with it off helps distinguish converted stick input from a game's own analog input path.

Keep other settings unchanged during the test. If turning the option off leaves the directional pad working but stops the left stick from performing the same actions, record that. Platforms and games differ in their stick requirements; reuse the table to check again when changing content.

How to evaluate custom mapping controls

If changing a mapping does not change the actual buttons, record responses as described here and report them. Test the lower button, right-hand button and Start in the same menu, noting their actions before and after the change. This helps establish whether the setting affects the current game.

Before trying system-level controller customization, confirm that your iOS version and controller support it, and use the options actually provided. Return to the same game menu afterward and fill in the response table again; only a changed action confirms a result. Avoid changing app, system and game settings simultaneously, or the cause becomes difficult to trace.

Questions and information to include in feedback

What if one button never responds? First try a scene that clearly uses that button, then compare the same controller in another game known to accept input. If the same physical button consistently fails, consider hardware or connection problems.

Why does control still feel different after resetting defaults? Game state, portrait or landscape orientation, controller reconnection and system settings can all affect what you observe. Resetting app settings does not clear every system or game configuration. Check each layer against your notes for a more reliable diagnosis.

For feedback, provide the controller model, game platform, physical button position, expected action and actual action. A response table without personal information communicates the issue more clearly than simply saying the buttons are reversed, and helps identify the specific failure.

Record a repeatable pressing method

Complete two rounds using the same hand and menu. Fully release each brief press before trying the next button. If trouble appears only during rapid repeated input, record single presses and repeated presses separately. Note diagonal pad input too—for example, whether up-left activates both directions. These records distinguish button position, pressing rhythm and combined input, making the actual failure conditions clearer in feedback.

Yearn Bluetooth controller: pair and check button responses

2026-10-23T00:00:00+08:00

Connected in Bluetooth settings is only the first step in connecting a controller to an iPhone. You still need to confirm that Yearn recognizes it and that the game receives directional and button input. This guide checks pairing, recognition, input and recovery after disconnection separately, rather than stopping at a connection icon.

Prepare the controller and a test scene

Charge the controller first and consult its own pairing instructions. Brands and models use different button combinations for pairing mode, so do not apply one sequence to every controller. If it was previously connected to a console or computer, check that it has not automatically reconnected there. Disconnect it from the old device if necessary.

In Yearn, prepare a legally obtained game that works with touch controls, and stop at its title menu or a safe position. Touch input then provides a comparison if the controller does not respond. Choose a sample that can test direction, confirm, back and pause separately, rather than a long opening animation that is not yet accepting input.

Complete system Bluetooth pairing first

Put the controller into pairing mode. Open Bluetooth in iPhone or iPad system settings and select it from the discoverable devices. Wait until the connection stabilizes rather than returning to the game as soon as you tap its name. If a pairing code is requested or an unsupported-device message appears, follow that model's official instructions.

If the system cannot find the controller, move it closer, check its charge and confirm that its pairing light is still flashing. If it is connected elsewhere, disconnect that connection before trying again. Refresh in the app only becomes useful after system pairing succeeds; repeatedly opening Yearn Settings cannot replace that step.

Check recognition in Yearn

Open the controller page in Settings and see whether the device name appears under Connected Controllers. If the list has not updated, use Refresh before returning to the game. The name may come from information supplied by the controller and differ from the full product name on its box. Identify it by observing what appears when you connect and disconnect it.

Back in the game, observe whether the on-screen controls change. The input path specifically handles extended gamepads; this does not mean every device capable of a Bluetooth connection is a game controller. A keyboard, remote or device implementing only part of a protocol may appear in the system list without replacing a full gamepad.

Test four input categories in order

In the first round, use only the directional pad to move the menu cursor up and down. Next, test the lower and right-hand face buttons, noting each action. Test the shoulder buttons in the third round, then check what Start, Menu or Options does in this game. Change one input at a time so that simultaneous presses do not obscure which one worked.

Older consoles have their own button layouts, while modern controllers have their own letter labels. The same letter does not necessarily occupy the same position. Describe results as the lower button or right-hand button, then compare them with the game's confirm and cancel actions. If the positions merely differ from your habits, read the input troubleshooting guide before assuming the controller is faulty.

Evaluate the stick and directional pad separately

If left-stick-as-directional-pad is enabled, use both the directional pad and left stick to follow the same route. If the pad works but the stick drifts, check the deadzone and whether the stick returns to center. If neither moves anything, first check for a disconnected controller or a scene that does not currently accept input.

The stick deadzone in Yearn Settings ignores small inputs near the center. Make small adjustments around the default value. Release the stick to see whether movement continues, then slowly push it toward the edge. An overly large deadzone can also ignore gentle movements, so do not maximize it to eliminate one instance of drift.

Test disconnecting and reconnecting too

Save a verifiable checkpoint in the game, then pause and disconnect the controller. Check whether touch controls return. Once you can use the menus again, reconnect. This confirms that you have an exit path after a temporary disconnection; there is no need to test during a critical battle or a one-chance scene.

If only some buttons work after reconnecting, return to the game library and reopen the current game. Record the device orientation, controller model and system version when the issue occurs. Do not start by uninstalling the app: that complicates files and progress without directly addressing Bluetooth pairing.

Frequently asked questions

The system says Connected, but Yearn does not respond? Check the app's controller list, whether the game permits input in the current scene, and whether touch works, in that order. If the app does not recognize that device type, use a supported controller type first. A system connection does not establish app compatibility.

Can a wired connection replace Bluetooth? Some compatible controllers can connect through a data-capable cable and adapter, depending on the device and controller. A charge-only cable may not carry input. Follow the hardware instructions.

Record the connection name, working inputs and reconnection behavior. Once you have a stable combination, consider a permanent stand, TV display and holding position. This controls variables more easily than buying many accessories before troubleshooting.

Yearn BIOS setup: check required files for each platform

2026-10-23T00:00:00+08:00

When Yearn reports a missing BIOS, first identify the platform. BIOS is a system file required by the emulation environment; a ROM contains the game you want to run. They cannot replace each other. This article covers status inspection, importing your own files, and checking results, without providing download sources for copyrighted files.

Read which platform the notice concerns first

Record which game shows the notice, which platform the library displays, and whether the error explicitly mentions BIOS. If a GBA sample is wrongly identified as PS1, check the imported file's real type before seeking a PS1 BIOS. Misidentified platforms and genuinely missing system files require different investigations.

Yearn's settings provide BIOS management. Inspect status by platform, especially the PS1/NDS distinction: the current interface describes a built-in open-source replacement for NDS, while PS1 provides a workflow for importing user-supplied system files. One platform requiring extra files does not mean every platform needs the same additions.

Prepare your own BIOS copy

Use system files you are entitled to use from a clear source, keeping an import copy separately from the original. Check filename and size first to ensure it is not a webpage, archive, or renamed empty file. Keep BIOS files separate from game ROMs rather than in one indistinguishable directory to avoid selecting the wrong item.

Common names in PS1 management include scph5500.bin, scph5501.bin, and scph5502.bin. These identify particular system files. Renaming an arbitrary bin to one of these names does not supply the same contents. If your material lacks version and source information, verify it with the lawful source instead of repeatedly renaming files until a notice disappears.

Choose import in Settings

Open BIOS management and choose Import BIOS File to bring up the system picker. Select the prepared copy, wait for completion, and inspect the list. Handle one file at a time so size mismatches, reading failures, and other notices can be linked to the correct material.

After import, check the displayed name, platform, and status. If it still shows missing, verify the selected file, whether a cloud placeholder has downloaded, and whether an extra extension was added—for example, a file that looks like bin but is actually bin.txt. Do not delete the entire BIOS directory after a failure; retain other working files.

Check the result with one game

Once the status is correct, return to the game that produced the message and try again. Record separately whether the BIOS notice disappears and whether the game reaches its title screen. Recognizing a system file does not prove every game image is complete or guarantee support for all regions and special formats.

If the notice disappears but the screen remains black, investigate ROM completeness and disc tracks instead of continuing to replace BIOS files. Keep verified settings unchanged and compare a lawful sample with a clear file structure. This avoids changing BIOS, image, and display settings together and losing track of which change mattered.

Understand the built-in NDS status

If the NDS section describes a built-in open-source BIOS, try the current default configuration first. It means the app includes replacement files for that path, not that every NDS game, touchscreen method, and save has been individually verified. Check results for the specific content.

If the built-in status is abnormal or reports missing files, record the app and OS versions and reopen settings to confirm. Do not copy similarly named files from another console's directory or clear all app data to repair one notice. For bundled-resource problems, clear error records are more useful for feedback than blind overwriting.

Keep a brief configuration record

Keep a table of platform, imported filename, source description, import date, and test game. Record only your own material, and do not post real personal file paths or device identifiers publicly. On a new device, the table reminds you which files need preparing again rather than assuming save synchronization also synchronized BIOS files.

Before a major device cleanup, retain lawful-source BIOS copies in your own backup location. Keep each file with its source description and record the app version in which it worked. During restoration, verify the file and compare with the same game to reduce reorganization time.

Frequently asked questions

Why does game loading still fail after BIOS import? BIOS is only one layer. A PS1 image may lack companion files, or the game file may be damaged or unsupported by the current core. Use the new error text to determine whether BIOS checking has already passed.

Will installing files for every region guarantee compatibility? No. File quality, game edition, region, and emulation implementation can all affect results. More files do not replace verification.

Can I rename a ROM to a BIOS filename? No. Extensions and names identify files but cannot change their internal contents. This exercise is complete when the platform status has a clear result and you can distinguish subsequent runtime issues from missing-BIOS issues.

Recheck the actual filename

Inspect the full name in system file information, not just the truncated list title. Record trailing spaces, duplicate extensions, and download-added numbers. Keep the original and correct verified names only in the import copy. Return to the BIOS list afterward, inspect status again, and retry the same game.

Yearn storage cleanup: back up before deleting games and saves

2026-10-23T00:00:00+08:00

Before freeing space in Yearn, distinguish deleting game files from merely hiding an entry in a list. The app's Delete Game operation handles the game and associated saved data; it is unsuitable for casual display cleanup. This guide keeps an independent copy first, then decides what to remove, distinguishing backup files from a successful restore.

List what needs to be kept for this game

At minimum, record the original game file, platform, current app version, save-state slots and in-game save status. For disc images, keep the index and tracks together; decide separately whether screenshots need retaining. Two ROMs with the same filename can be different versions, so include source and version notes in the backup.

Start organizing unimportant practice material and temporarily retain important progress that you can still load. Do not use deletion as a substitute for removing a favorite simply to make a list look cleaner. Removing a favorite changes a shortlist; deleting can remove actual files. Their consequences differ.

Save and end the current session first

Save through the game's own menu, then use Yearn's manual save state to retain a clear checkpoint. After verifying that it loads, exit the current game through the app menu and end the session. Avoid copying while the game continues writing the same data, or the copy may combine material from different moments.

Record the scene and slot timestamp corresponding to the backup. Even if you only inspect the files later, do not immediately treat the new backup folder as a complete replacement for the original app. It is first an independent copy for protection and investigation; whether a restore will recognize it correctly requires a separate check.

Keep a copy through file sharing

Yearn enables system file sharing. On a Mac, connect and trust the iPhone or iPad, open the device's Files tab in Finder, find Yearn, and copy the documents you want to keep into a separate backup folder on the computer. If the entry is missing, check the connection and device trust first rather than trying to change internal app permissions.

Name the backup folder by date and purpose, such as Yearn_before-cleanup_date. Preserve the existing hierarchy of folders such as ROMs, SaveStates, Saves and Screenshots rather than flattening everything into one directory. An unfamiliar identifier does not mean a save is useless. Do not rename internally associated files just to make their names look nicer.

Check that the copy really left the original device

After copying, inspect the backup location on the computer: confirm the files exist, their sizes are reasonable and the folders are complete. Make sure the copy is on the computer or your chosen independent storage, rather than still being only in the device's sharing list. If necessary, keep another copy in storage you control so that cleaning both the phone and computer cannot remove every copy.

This verifies the file copy, not a completed emulator restore. After reimporting, reidentifying a game or changing devices, you still need to check whether the app finds the corresponding saved data. Until you have actually loaded and checked the progress, avoid deleting the only app environment that can still run it and recognize its saves.

Confirm the scope of deletion again

Return to the game library and use Delete only on a practice game you clearly no longer need, reading the confirmation carefully. Do not rapidly delete several similarly named entries. Handle one, then check the resulting list. Deletion in the app and deletion from the source folder happen in different locations; clearing one does not automatically mean the other is cleared.

Deleting a game may also affect its associated saves. To shorten the recent or favorites list, use the corresponding history or favorite controls without deleting the game. Uninstalling the entire app has a wider impact: first ensure every needed file is retained. An enabled iCloud sync switch is not proof of a complete app backup.

Use separate material for restore practice

To test a backup, choose a practice sample that will not overwrite important progress. Check a ROM through the normal import process and confirm it starts. For saved data, confirm that the app finds the corresponding record and actually loads it. Copying a folder back is not, by itself, a successful restore.

If saved data is not recognized, leave the original backup untouched and investigate using a copy. Record the game file, app version, directory structure and loading behavior, then ask support for help. Do not guess what internal identifiers mean and rename files in bulk, or overwrite the original pre-cleanup backup with the result of a failed restore.

Questions and final checks

Do I still need a file copy when iCloud sync is enabled? Sync and backup serve different purposes. A sync status does not preserve a specific historical checkpoint for you, nor does it prove that the ROM, BIOS and every related item are in the cloud.

The backup folder is large. Can I keep just one state file? Keeping an isolated file can lose important context before you understand its associations and restore process. Retain the complete relevant folders and original game material first, and simplify only according to a method you have verified.

Before finishing cleanup, you should be able to identify the independent copy's location, exactly what was deleted, the usable progress that remains, and any restore steps still unverified. If these facts are unclear, delay deletion. Retaining control of the material is easier than trying to recover it after it is lost.

Yearn in-game saves and save states: verify that saved progress loads

2026-10-23T00:00:00+08:00

Selecting ‘Save’ inside a game and selecting Save in Yearn’s menu save different layers of information. The game itself decides what the first method stores; the second records the emulated running state. This tutorial uses the same game with in-game saving support for two independent checks, so you know exactly which record you will rely on when continuing next time.

First find the game’s own save function

After entering the game, inspect its own menus, save points, or save prompts. Some games allow saving only at specific locations, some have a save option in a menu, and some have no long-term saving system at all. First find a reliable saving method according to the game’s own rules. Do not assume that pausing, returning to the title screen, or finishing a level automatically means your progress has been saved.

After saving within the game, note the character’s location, level, time, or save name. If a ‘Saving’ message appears, wait until it ends before doing anything else. Success at this layer is reported by the game itself. You still need to exit and reopen it afterward to determine whether the app retained the corresponding data.

A save state keeps a separate checkpoint

Open Yearn’s game menu, create a save state in an empty slot, then move to a slightly different location. You now have two records at different layers: the game’s own save location and the current state stored in the slot. Label them clearly and separately instead of calling two different scenes ‘the latest save.’

Deliberately creating this difference makes it easier to tell which path you used when loading later. Selecting Load directly should restore the save state; choosing Continue from the game’s title screen checks the in-game save. If both methods lead to the same screen, it is actually harder to distinguish what was loaded.

Use a normal exit for checking saves

After saving, use the game menu to end the current session, giving the app a chance to stop emulation and process save data. Swiping the app away in the system app switcher, a depleted battery, and an unexpected app interruption do not follow this normal exit path. Verify the normal procedure during your first check before considering how to reduce losses from unexpected interruptions.

After exiting to the game library, reopen the same original file and first check Continue or the save records from the game’s own title menu. Do not immediately use the save-state Load command to bypass the title screen. That would only establish that the save state loads, without proving the in-game save works independently.

Check that the save-state slot still exists

After checking the in-game save, open Yearn’s save list, find the slot and time you noted, load it, and compare the scene. Record the results separately: ‘In-game save loads’ and ‘Save-state slot loads,’ or state clearly which check failed. Success with one does not guarantee the other.

After reopening the game, check the same slot and scene again to confirm that the app can still find the record. If an association has been lost, preserve the files and data first. Do not try to guess at a fix by deleting, reinstalling, or importing again; those actions may make troubleshooting harder.

Understand the automatic-save options

The store description mentions automatic saving, and Settings also provides automatic-save and interval options. Before relying on it, check that a new record exists and that you can load it. Merely waiting for a while without observing a specific record is not enough to confirm that saving succeeded.

To evaluate automatic saving, start with practice content, note the starting time and manual slot, then check whether a recognizable new record appears and actually load it. If you cannot find a clear record or verify the loading result, continue using your tested manual and in-game saving procedures, keeping the checkpoints you have already confirmed work.

Keep game files matched to their saves

Regional editions, patched versions, and copies from different sources of a game with the same name may not share the same data structure. Once you have made progress, keep the original ROM, its original name, and information about the app version wherever possible. Importing another file with the same name may replace an existing copy, so create an independent backup before updating the content.

When organizing your files, you can keep a small table with the filename, platform, in-game save location, save-state slot, and most recent successful load date. These notes cannot restore a game by themselves, but they help identify which backup belongs to which file and prevent blind loading among several similar copies.

Frequently asked questions

The game reported a successful save. Why is Continue missing when I reopen it? First confirm that you reopened the same file and version, then check whether you exited normally. If the problem persists, preserve the app data and save files and record the steps in detail. An in-game message does not establish that the app’s entire saving and recognition process has been verified.

Is keeping save states alone enough? Do not treat different types of saves as interchangeable. Keep in-game saves whenever they are available and also verify save states. Add independent file backups to reduce dependence on a single recovery path.

By the end, you should know where each loading method takes you and be able to identify any automatic behavior you have not yet confirmed. These records describe the actual condition of your progress more clearly than ‘all the switches are on.’

Use two different scenes to distinguish the saves

For example, save within the game in a village, then move to a nearby road and create a save state. After reopening the game, choosing Continue from the title screen should take you to the game’s own save location, while loading the save-state slot should return you to the road. This is only an example of the checking method; choose actual save locations according to the game’s rules. Making the two records visibly different prevents one successful load from being mistaken for confirmation that both saving methods work.

VectorPaint wordmark spacing: adjust the visual rhythm of a short name

2026-10-23T00:00:00+08:00

When a short name becomes a wordmark, the space between each pair of characters becomes conspicuous. This VectorPaint exercise types the fictional name 山间小屋, or Mountain Cottage, and compares a short English word, moving from overall tracking to local optical spacing. The goal is smooth reading, not mathematically identical gaps.

Establish the wording and final use size first

Create a 1000×500 px canvas and enter the practice name using a font already on the device and permitted for the intended use. For a real brand, check name and font usage requirements first. This exercise studies typography only and does not establish trademark or brand clearance.

Before adjusting, view the wordmark at its actual use width, such as a webpage header or a small title beside an avatar. Elegant thin strokes at a large size may become hard to read. Choose a clear base typeface and moderate weight before spacing; this is easier to control than repeatedly adding thicker lines afterward.

Keep the default layout for comparison

After creating the text, confirm the content is applied and duplicate it above as a labeled default version. Use the lower copy for adjustments, keeping size, color, and wording identical. Change only spacing to isolate its actual effect.

Check for unintended spaces, especially in pasted text. Full-width spaces, ordinary spaces, and tracking are different. Clean the content before judging the font's default arrangement. Extra spaces used to imitate tracking make later font and wording changes harder to maintain.

Adjust overall letter spacing in small steps

Select the lower text and find letter spacing in its text properties. It adds or removes space relative to the font's original spacing, in pt. Begin near zero, change a little at a time, and inspect the whole line to see whether it feels looser or tighter.

Increasing tracking widens the whole line, so recheck space at both ends without immediately compressing glyphs to retain the old width. If characters separate into isolated graphics, spacing may be excessive. If strokes touch and the name becomes unclear, loosen it. Use how easily you can read the full name as another guide.

Separate local problems from overall problems

An unusually open pair may result from the glyphs' openings or stroke directions. A character with extra space on its right followed by one with an open left side can create a conspicuous gap. Tightening the entire line then crowds pairs that were already correct.

For local treatment, split the short name into individual text objects in a practice copy, retaining the same font and size, then position them separately. This enables manual pair spacing but fragments content editing too. Keep a complete text version so future renaming does not require finding and replacing every character.

Compare visual rhythm through empty areas

Observe the white regions between characters, not merely distances between bounding boxes. Two upright strokes can feel tight, while diagonals may leave larger triangular gaps. Local movement aims to harmonize the rhythm of empty space, not give every pair the same numerical value.

Keep the left end fixed while comparing the second, third, and fourth characters in turn. Zoom out after each pass so focusing on one pair does not undermine the whole. You can briefly view the wordmark upside down to focus on spaces between shapes, then restore normal orientation and check that the name remains clear.

Compare reversed-color and small-size results

Place a dark wordmark on a light background, then make a light-on-dark version with the same shapes and size. Observe fine strokes and internal spaces. Reversed text may feel heavier, so identical local spacing may not suit it. Compare small adjustments and record the chosen version.

Check again at a smaller display width for merged strokes. If a font is unclear when small, change its weight or choose clearer letterforms rather than endlessly increasing spacing. Spacing fixes relationships between neighboring characters, not a typeface unsuitable for the purpose.

Decide whether to retain text or make an outlined copy

Editable text makes wording changes easy. Outlined copies suit some delivery workflows that require fixed letterform appearance. Keep a complete editable-text original before deciding whether the receiving environment needs an outlined version. Once converted to paths, changing a name is no longer a matter of typing replacement text.

Export PNG as an appearance reference and SVG as needed, checking fonts or outlines in the receiving environment. Name files with the wording, palette, and version so default, adjusted, and reversed-color variants are not confused. Every final delivery file should come from the same approved layout stage.

Frequently asked questions

Why do two words look differently spaced at the same value? Typefaces differ in glyph width and built-in space, so identical additional spacing does not produce identical visual results. Keep font, size, and display dimensions fixed before gradually adjusting.

Is separating every character more professional? It only adds local control and also increases maintenance. If default layout with slight overall tracking already works, keep the text as one object. Add separate objects only for a specific local problem. Finally, read the name to ensure no character has become ambiguous or missing.

Record repeatable comparison conditions

Note the font, size, overall tracking, and preview width beside the original, then move those notes into a separate record afterward. If the font changes, reassess letter pairs; old tracking values are only a starting point. Save default and adjusted versions with the same canvas bounds so different preview crops do not create a false impression of improved spacing. Clear comparison conditions make later revisions more grounded.

VectorPaint weather icons: balance sun, cloud and rain at one visual size

2026-10-23T00:00:00+08:00

A clear sun icon does not necessarily belong to the same set as your cloud and raindrops. This exercise creates sunny, overcast and rainy icons in VectorPaint, focusing on their visual size as a group and the rules they share. The result is three graphics that can be exported separately.

Set up comparison areas on one canvas

Create a 960×360 px landscape canvas and divide it into three roughly equal areas, one per icon. Use a grid or temporary reference rectangles to mark a shared centerline and baseline, leaving margins around the outside. These areas are working guides; hide or remove the ordinary reference objects before finishing.

This set uses dark lines and a small amount of warm yellow. Define the main stroke width and endpoint style before drawing. You can begin with a 4 pt stroke for comparison, then adjust it to the display size. The cloud and sun need not have identical bounding boxes; they need comparable visual weight, without being forced into the same silhouette.

Draw sunny weather with a circle and short lines

Use the Ellipse tool to draw an equal-width-and-height circle in the center of the first area, with a warm yellow fill. Draw a short line for a ray and set a consistent dark stroke and endpoint style. Duplicate, rotate and move the line around the circle. Start with rays above, below, left and right, then decide whether to add diagonal rays.

Check that the gaps between the rays and circle are similar, paying particular attention to the visible lengths of diagonal rays. Make sure duplication has not accidentally changed some line widths. Group the sun's parts, move the group, and undo to confirm that no ray was left behind. Grouping helps compare sizes later, while keeping the individual parts editable for now.

Shape the cloud's rises with a simple outline

In the second area, draw a closed cloud with the Pen tool: a fairly flat base and several rounded rises of different sizes across the top. You can first sketch a few circles as references, then trace a clear outer path. Let the largest rise carry the main shape, with smaller rises on either side connecting to the base.

Use the Node tool to inspect curve joins and remove unnecessary small bumps across the cloud's top. The cloud can be wider than the sun's central circle, but include the rays when comparing overall width. Do not push the cloud's base against the area's bottom edge: the rainy version still needs space for drops below, so leave room along the set's baseline.

Extend the same cloud into a rainy icon

Copy the finished cloud to the third area, retaining its outline and stroke. Reduce it slightly or move it up to leave room for rain. Draw a simple drop with the Pen tool, or use three short slanted lines. Choose one approach; stacking drops and rain lines together can add unnecessary complexity.

Finish the first drop's shape and color, then duplicate it into three drops and adjust their spacing and heights. The central drop can sit slightly lower, with the other two balancing it. Leave a visible gap beneath the cloud: when shapes touch at a small size, the drops can resemble a jagged cloud edge. Group the cloud and drops into one rainy icon.

Adjust visual size without stretching the shapes

Place all three groups near the shared centerline. Compare their outer edges first, then their solid areas. The sun has fine outward rays, the cloud has a wide continuous outline, and the rainy icon has details extending below it. Equal bounding boxes can therefore have different visual weights. Scale each group proportionally to preserve natural circles and drops.

Adjust one icon at a time. Balance sunny and overcast first, then add rain. If the rainy icon looks too tall, adjust the gap between the cloud and drops rather than compressing the entire group vertically. Hide the reference frames before judging: readers see the icons, without the geometric guides used to arrange them.

Check the shared rules at a small size

Export a landscape preview, then reduce it to roughly the size of a typical interface. Check that all three icons remain immediately recognizable. Reduce overly dense sun rays, combine small fragmented cloud curves, and increase the visible width of drops that are too thin. Each shape can be simplified differently while keeping the same stroke style.

Test the icons on light and dark backgrounds to decide whether another color variant is needed. If dark strokes disappear on a dark background, prepare an explicit light version rather than simply making the whole group more transparent. Record the main colors, stroke width and minimum display size as references for adding a snow icon later.

Export, questions and final checks

For separate exports, copy each finished group onto its own canvas of the same dimensions, retain consistent margins, and export transparent PNGs and any required SVGs. Match filenames to the correct weather, and retain the source document showing the whole set. Tight cropping to each object's bounds can make the icons appear inconsistently sized when placed in identical containers.

Must all three icons have exactly the same width? No. Keep their containers consistent, then adjust each graphic according to its visible area and recognizability. A narrow icon can retain more space at its sides; there is no need to stretch it to meet a width target.

What if the rainy icon always looks heavier than the sunny one? First reduce cloud details, shrink the drops or increase their spacing, then compare the overall area. Thinning every icon at once would also weaken a sun that was already clear; local adjustments make balance easier to find. Finally, check each outline, color and transparent edge before saving them as one set.

Try extending the set with a fourth weather type

After finishing the three icons, try just one partly cloudy draft. Keep the same cloud and place a smaller copy of the sunny icon's sun behind it, revealing part of its circle and rays. Check that it follows the same stroke, colors and clear space. If the new icon needs completely different lines to read clearly, review the shared rules rather than letting the fourth icon adopt its own style. This extension tests whether those rules are clear enough.

VectorPaint wayfinding: make consistent signs for three spaces

2026-10-23T00:00:00+08:00

Signs within the same space need to help people find their direction quickly. In this tutorial, we use VectorPaint to create three practice signs for a fictional reading area, exhibition area, and rest area, focusing on consistent arrows, names, and margins. These examples are visual-design exercises. For a real venue, verify the design against on-site circulation routes and applicable requirements.

Decide what information the signs actually need

Write three names and directions, such as Reading Area left, Exhibition Area right, and Rest Area straight ahead. Decide whether English supporting labels are needed. Edit long names early rather than finishing the signs and discovering that one only fits with much smaller type.

Create a 1200×900 px canvas and arrange three horizontal areas of equal width. First establish consistent sign proportions, outer margins, and text areas; leave decoration for later. Keeping all three signs on one working canvas makes their shared rules easier to compare. When you need separate exports, copy them to individual canvases of the same dimensions.

Draw one clear arrow as the master

Use a rectangle for the arrow shaft and draw a triangular arrowhead with the pen tool, adjusting their widths and the join between them. You can also draw the entire arrow as a single closed path. Start with a solid color and no gradient, then check whether its direction remains clear at a smaller size.

Once one arrow is finished, duplicate it and rotate or flip it for the other directions, preserving its proportions. Check that changing direction has not mirrored any text: edit arrows and text separately rather than flipping a complete, already arranged sign. Leave space between the arrowhead and the edge of the sign so it does not appear to collide with the border.

Give text a stable starting point

Create a separate text object on each sign, use the same font and font size throughout, and give the Chinese name the primary position. After entering the text with the text tool, confirm and apply it, then return to the selection tool to adjust its position. First test the available width with the longest practice name, ‘阅读区’ (‘Reading Area’), or the longest name in your actual project. Use the same starting position and font size for shorter names.

Text does not necessarily need to shift from side to side when the arrow moves left or right. Start with a fixed arrow column and align destination names to a shared boundary, reducing how much readers must search for information across signs. Compare the layout together with the directions it communicates, rather than judging each sign only by its symmetry.

Add simple graphics while keeping explanatory text

Use an open book for the reading area, a picture frame for the exhibition area, and a simplified cup or chair outline for the rest area. Build each graphic from only a few objects and use a consistent stroke width or solid-fill style. Make one clear icon first, then complete the other two using the same rules.

Graphics help people recognize a destination quickly; text removes ambiguity. A cup could mean a drinking-water point or a café area, so the actual name must still be clear. Do not distinguish the three destinations by color alone, or assume that a generic practice graphic already meets a specific public-signage standard. Before real use, check separately that its meaning suits the location.

Refine the hierarchy from near and far

Zoom out until all three signs are visible and notice whether the arrow or the name catches your eye first. Both should be easy to find within a few seconds; the icon and English text can be read afterward. If a border or decoration stands out more than the arrow, reduce its visual weight and compare again.

Next, zoom in to check the text and arrow details, making sure margins are consistent and no objects have been left outside the sign. Long and short names have different visual weights, so you may adjust the width or position of the text column while keeping the font size consistent wherever possible. Do not undermine the set’s shared reading rules to make one sign look better on its own.

Simulate a moment when someone must choose a direction

Export previews of all three signs at the same dimensions and view them in turn. Ask yourself, ‘I want to go to the exhibition area; which way do I go next?’ The direction is clear enough only if one glance gives you the answer. If you first need to read a legend or guess what a color means, the information relies too heavily on decorative coding.

In a real space, determine directions from where the viewer will stand. Moving the same ‘left’ sign to a wall on the other side may make it point the wrong way. Include the installation location and orientation in the design’s filename or delivery notes so that installers do not swap signs around simply because the graphics look good. Check dimensions and legibility again before production.

Common questions and delivery checks

Must all three signs be identical? Keep the shared rules consistent while allowing names and directions to vary. Above all, readers should not have to learn a new way to read each sign. Icons may have different outlines, but their size and visual weight should work together.

Can I use English alone to simplify the design? Base that decision on the language needs of the actual users. You can compare Chinese-and-English versions in the exercise, but real wayfinding must first make the information understandable to its intended audience. Do not sacrifice legibility simply to shorten the text.

Finally, check the three names, the three arrow directions, and each filename, and confirm that the previews and editable originals are from the same version. Keep the text editable and export PNG or PDF as required. For fire-safety, accessibility, or other signage subject to explicit requirements, those requirements must govern the design. This exercise’s proportions and colors are only for general visual practice.

Test the longest name first

Try temporarily changing ‘Reading Area’ in the exercise to ‘Children’s Reading and Activity Area’ and see whether the text crowds the arrow column. First try natural line breaks and adjustments to the text area, then decide whether the whole set of signs needs more height. When restoring a shorter name, keep the shared font size and margins instead of giving every sign its own settings. Testing a longer name can reveal problems before the series expands and helps you confirm name lengths with the people who will use the signs.

VectorPaint two-colour overlaps: compare opacity and stacking order

2026-10-23T00:00:00+08:00

Two translucent color shapes can produce a new visible color, but both the background and stacking order affect the result. This VectorPaint exercise separates color, opacity, and order on a two-color test board, then uses the findings for a simple abstract graphic.

Establish a baseline with fully opaque shapes

Create a 900×600 px landscape canvas with a light background. Draw two equal circles, one warm and one cool, fully opaque and without strokes. Overlap them partially and observe how the upper circle covers the lower.

Record which circle is in front and which behind. At this stage, the overlap mostly shows the upper object; do not expect a third blended color automatically. Understand ordinary occlusion before adjusting opacity so normal stacking is not mistaken for a color failure.

Change only the upper object's opacity

Select the upper circle and gradually lower opacity, comparing approximately three-quarters, one-half, and one-quarter. Keep the lower circle, background, and colors unchanged. Inspect both overlapping and nonoverlapping areas each time, noting that the upper circle itself is affected by the background too.

Do not change both fill-color transparency and overall object opacity together, or their contributions become unclear. Complete the exercise through one control before comparing the other. Record whether you changed the object or color so a later reset does not miss a change hidden elsewhere.

Swap stacking order for a second comparison

Copy both circles beside the originals, preserving colors and opacity while swapping only their order. Compare overlap colors and which edge covers which. Normal transparency compositing depends on order, so changing it may alter appearance.

If the two groups look nearly identical, verify that their transparency and colors allow an observable difference and that the intended objects were reordered. Do not change colors merely to exaggerate the difference; this round tests order only. Fixed comparison conditions identify the true cause.

Try a dark background

Add a dark background in a copy while leaving circle settings unchanged. Translucent areas combine with it, potentially changing the entire mood. This does not necessarily mean the original fill color changed; the compositing conditions differ.

Inspect the separately exposed part of each circle, then the overlap center. For stable use across backgrounds, increase opacity or make explicit light-background and dark-background variants. Satisfaction on a white editing background does not guarantee the same appearance on every webpage color.

Turn the experiment into a graphic

Choose a relationship you like from the test board and create or save a separate practice copy. Build an abstract graphic from two circles and a rectangle, limiting translucent overlap to an intended accent area and leaving space elsewhere. Define one focal point instead of covering the canvas with translucent fragments.

Use a rectangle as a stable base and two circles for soft overlap. Check stacking and group related objects if useful. Changing a group's overall opacity affects the entire combination and may differ from changing objects individually, so keep original parameter notes for comparison.

Check how overlap affects reading

For text over the graphic, find a relatively stable color area first. Text crossing multiple overlaps repeatedly changes contrast and may need a backing or revised layout. Attractive graphics and readable text require separate checks. Transparency need not solve every task.

Likewise, important icons should not depend only on subtle color overlap. View the graphic temporarily in grayscale or at reduced size to check its main silhouette. Color relationships add depth, but basic shape and space should work independently, especially at small sizes or low brightness.

Check exports on the actual background

For transparent PNG, exclude the test background and inspect the image on its real destination color. For a fixed appearance, provide a version with an explicit background alongside the transparent one, naming their purposes distinctly. A transparent file alone cannot guarantee identical appearance on different backgrounds.

For SVG, check layer order and opacity in the receiving environment. Include a PNG comparison reference while retaining the VectorPaint original for further editing. After export, verify that color, opacity, order, and background match the confirmed version.

Frequently asked questions

Does a third color in the overlap mean the app added an object? Not necessarily. Translucent shapes combine with underlying content to create visible results without a separate third shape. Hide objects individually to observe each contribution.

Does lower opacity simply mean a lighter color? On white, the result may look lighter; on dark, it may darken or shift in combined color. Opacity controls how much underlying content contributes, not simply lightness. Compare on a fixed background, then choose settings for the actual environment to make results more predictable.

Keep test backgrounds out of deliverables

Name background boards clearly in comparison copies, such as Light Comparison and Dark Comparison. Before exporting transparency, inspect layers so only the graphic remains. If the output still has a solid rectangle around it, check for a normal bottom rectangle rather than repeatedly toggling export options. A background object's color differs from the canvas display background; separate checks locate the problem faster.

VectorPaint timeline: arrange five stages with descriptions of different lengths

2026-10-23T00:00:00+08:00

Timeline dates are short while explanations vary in length. Five evenly spaced circles do not guarantee a readable sequence. This VectorPaint exercise creates a five-stage timeline for a fictional creative project, checking sequence, text ownership, and space.

Decide whether the timeline represents sequence or duration

Prepare five stages: concept, sketch, form refinement, color, and delivery. Give each a practice date and one-line explanation. Decide whether the graphic conveys sequence only or real proportional day counts. These require different spacing rules and should be distinguished at the start.

This example uses equally spaced stages and labels the diagram 'Stage schematic; spacing does not represent actual duration.' Create a 1200×700 px landscape canvas, reserving the middle for the main axis, the top for a title, and the bottom for notes. Verify dates for real projects; example dates are not publishable evidence of actual events.

Establish reading direction with one main line

Draw a horizontal open path with the line tool or pen, using a clear but not heavy stroke. The left is the start and the right the end. Begin with one consistent color. The line connects stages and need not overpower their titles.

Place five equal circles between the endpoints. Set the first and last positions, then arrange the middle three with distribution or manual references. Check center-to-center distances, not only gaps between circle edges. Keep all circles the same size and express importance in text for now, avoiding a second unnecessary encoding.

Arrange dates and stage names separately

Put dates above each node and stage names below, or reverse that arrangement consistently. Use a common date size and slightly stronger stage names. Create text objects separately, confirm their content, then position them.

Test space with the longest stage name, then adjust all node text areas. Do not squash only the long name's glyphs. Edit wording or choose a more suitable overall layout. Text must be close enough to show its node association without touching the main line.

Place longer notes in stable reading areas

Give each node a similarly sized text area despite differing note lengths, using consistent left alignment or centering. Left alignment usually helps with explanations longer than two or three lines. Limit each note to one stage's main point instead of letting one become a full project summary.

If neighboring notes collide, alternate them above and below with short leader lines to identify their nodes. Alternatively, use a vertical timeline with a wider explanation region per stage. Changing layout is more effective than shrinking all text beyond readability. Let content length guide the choice.

Keep explicit wording with status colors

For Completed, In Progress, and Not Started, use dark, accent, and pale colors if desired, but include text or clear symbols too. Color alone can lose meaning in monochrome print or low-contrast display.

Status and date are different information. A past date does not automatically mean completion. Verify real progress before changing node colors. For this fictional exercise, neutral colors can establish reading order first, with status coding added later.

Read it aloud from start to finish to find problems

Starting at the leftmost date, read each stage and explanation and see whether the next node follows naturally. If the third note's circle is unclear, change distance or leader lines. If one long title keeps pulling attention away, shorten it or reduce its visual weight.

Reduce the diagram to its actual display width. A horizontal timeline may be too long on a phone, shrinking all its small text. Create a portrait version with the same content rearranged if needed. Name horizontal and vertical versions separately instead of compressing the entire landscape image into a portrait ratio.

Keep an update reference and inspect exports

Organize the main line, nodes, dates, and notes clearly in the original. Group related stages for movement. Keep a text list as the update reference, changing content first and then checking that graphics and dates agree. Do not update only text in a PNG while leaving the editable original outdated.

After export, check cropping at both ends, dates and explanations for every node, and the intended five-stage order. For real project communication, state the date through which information is current. It should reflect actual content updates, not imply new progress every time a file is exported.

Frequently asked questions

Must all five stages be equally spaced? It depends on purpose. Equal spacing may express sequence if explicitly stated; actual durations require one consistent time scale. Do not let decorative spacing be mistaken for real elapsed time.

Can a long explanation be reduced to a few keywords? Extract its most important action and move detail into accompanying text. The short note must still explain the stage independently rather than becoming internal shorthand only its author understands. Reading it again after a break is a simple completeness check.

Check two stages occurring on the same day

If two stages in a real project happen on the same day, retain the shared date and explain their sequence or parallel relationship in the notes. Do not invent different dates just to make every node look distinct. In a version drawn in proportion to elapsed time, same-day node labels may need to be staggered vertically. In an equally spaced stage diagram, continue to make the meaning of the spacing explicit. Make the time information accurate first, then solve the label placement.

VectorPaint sticker illustration: draw a white backing and check transparent edges

2026-10-23T00:00:00+08:00

A sticker's white border can keep an illustration clear across different background colors. This article draws a manual white backing for a simple design in VectorPaint, focusing on thickness and small gaps. It creates a visual effect; an actual print cutting line needs separate preparation to the producer's specifications.

Choose a moderately simple silhouette first

Prepare a small animal, flower, or geometric character and save an original copy first. Create or confirm a square canvas with sufficient room around the subject. A clear silhouette without very thin protrusions is easier for the first border exercise than a design with many hairs or fine branches.

Temporarily place the design on mid-gray and inspect its outer contour and inner holes. Decide which small gaps should remain and which the white backing may bridge. A sticker outline usually needs to be simpler than the illustration's details, or the border becomes many confusing little spikes.

Draw one complete backing behind the subject

Use the pen to draw a closed path around the subject at a roughly even distance. Fill it with a conspicuous color for inspection, place it behind the subject, and change it to white. This separate backing shape can be adjusted independently without altering the illustration's original paths.

Place nodes at major contour turns, use curves for rounded areas, and soften sharp corners as appropriate. A point beside every detail makes the edge wobbly. Start with a fairly loose outline and adjust inward section by section; this makes spacing easier to judge than tracing tightly from the beginning.

Judge border thickness by visible distance

Zoom in and follow the space between subject and backing around the perimeter, checking for thin areas or sudden excessive width. The goal is visual consistency. Proportionally enlarging the entire subject does not necessarily produce a constant-width outer border.

For irregular contours, overall enlargement may leave too little space in recesses and too much at protrusions. Adjust the relevant nodes and handles while keeping neighboring curves smooth. After local corrections, return to the full view and make sure the white border does not dominate the subject.

Simplify recesses and narrow gaps

Bridge narrow gaps between leaves or between an arm and body as appropriate with the white backing to create a more continuous exterior. Do not force the border into every tight space, producing long spikes that may become specks at small sizes.

If an internal hole is a defining feature, decide whether it needs transparency and arrange paths for the intended result. White fill differs from a transparent hole, especially on dark backgrounds. Compare both background types before choosing the treatment that suits the design.

Check the white border on dark and light backgrounds

Group the subject and backing and place them on dark blue, light gray, and a simple textured background. The white border is conspicuous on dark backgrounds and may nearly disappear on white, but the subject should remain clear. Add a very light outer gray line if needed, first checking that it does not make the design too heavy.

If an unusually bright strip appears on only one side, check for a duplicate backing or extra stroke. Hide objects individually to locate the cause rather than changing every opacity at once. Remove test backgrounds afterward or keep them in a clearly identified checking copy.

Export with transparency and check the bounds

Enable a transparent background when exporting PNG and confirm that no solid board covers the canvas. The outer white border should not touch the canvas edge; leave a little transparency around it. Place the exported image on dark color and inspect the completeness of the white backing.

PNG suits screen stickers and visual previews. Keep the original for contour edits. If SVG or PDF is required, inspect its object relationships and boundaries too. Transparent export does not automatically generate a machine-cutting path. File format and production requirements need separate confirmation.

Prepare separate instructions for physical printing

For physical stickers, confirm final size, bleed, cutting line, and file requirements with the producer. Distinguish the visible white backing from the real cut boundary and explain which parts are artwork and which are references. Do not claim that a hand-drawn white border is a machine-compliant die-cut file.

First provide a PDF proof with dimensions so both parties confirm graphic size and border width, then supply production files as required. After a small test print, inspect corners and edges and simplify the original if needed. Fine concave corners on screen may not suit every material or cutting method.

Frequently asked questions

Is a thick white stroke on the original always enough? A stroke may be convenient for simple paths, but results need checking for complex groups, images, or separated objects. A manual backing lets you choose the overall exterior, especially when the design needs small gaps bridged.

Does a wider white border always look more like a sticker? Too wide a border makes the subject look small; too narrow a border separates it poorly from the background. Compare several widths at actual use size and choose one that aids recognition without overpowering the design. Finally, retain the white border, transparent areas, and original appropriately so the structure remains reusable after a subject-color change.

Check continuity of small separate parts

If the illustration has a separate star or distant small circle, decide whether it is a separate sticker or shares the subject's white backing. For a shared backing, connect it with a gentle contour; for separate stickers, give each its own margin and clear name. Avoid a thin white bridge barely visible on screen that disappears in small output. Decide component relationships early to keep the exterior simple.

Bison’s Creative & Development Notes

Cape Lighthouse: build a geometric seascape with 17 closed paths in VectorPaint

A small palette separates sea and lighthouse

Decide which shapes will cover which

Make a closed colour shape with the pen

Use the sun and mountains to set the heights

Give the lighthouse a base with cape and rock

Draw tower, lantern room and roof separately

If windows or wave highlights will not close, check node spacing

Use a triangle to point the final beam

Check the lighthouse in three iPhone Duo states

Check canvas dimensions and PNG pixels separately

Moonlit Pines: build a geometric night landscape with Aquarell polygon selections

Save the bright colours for the moon and snow

Four layers: check which one is active

Set the mountain rhythm with one polygon

One snowcap gives the mountain a direction

Frame the scene with three pines

An angular moon, twelve stars and three reflections

Check the native PNG for missing edges

Check iPhone Duo open, partially open and closed

What to try next

Aquarell creative process: paint a night scene with soft pools of light

Prepare a deep-blue base and a layer for light

Colours and settings used in this session

Stagger mint and lilac along a diagonal

Finish with a large light and a few small stars

Keep the original, then share the image

VectorPaint creative process: a sunset mountain scene in three colours

Keep the composition simple

Close the sun with eight points

Give both mountains a common baseline

Return to the whole composition

Save the original and export a white-background PNG

Yearn virtual controller: adjust size, opacity and haptic feedback

Use a consistent grip before adjusting

Start with a small size change

Use transparency to keep buttons recognizable

Test directions and action buttons separately

Check haptic feedback separately

Allow a test round for each orientation

Questions and check results

Related tutorials and sources

Yearn speed controls: fast-forward through waits and slow down actions

First save a checkpoint at normal speed

Start with a lower fast-forward multiplier

Use fast-forward separately for dialogue and action

Use slow speed for observation and still check normal operation

A speed multiplier does not guarantee device performance

Distinguish fast-forward from turbo input

Questions and final checks

Keep each comparison brief

Related tutorials and sources

Yearn screenshots: save a game image and organise your records

First decide what the screenshot is for

Save an image from the game menu

Check the file and permissions in Photos

Distinguish app screenshots from system screen captures

Develop a way to organize your screenshots

Describe a problem with two images

Common questions and checks after saving

Related tutorials and sources

Yearn screen size: adjust scaling, aspect ratio and margins

Choose a fixed scene that is easy to compare

Distinguish aspect ratio from picture size

Change one scaling setting at a time

Use empty space for the controls

Recheck landscape orientation and a physical controller separately

Keep a simple record of your choices

Questions and final checks

Related tutorials and sources

Yearn on a TV: check picture and delay with iPhone screen mirroring

Prepare a device that supports screen mirroring

Establish the system connection in Control Center

Understand whole-screen mirroring first

Adjust orientation and keep the edges visible

Observe input delay in three stages

Troubleshoot missing picture or sound one layer at a time

Questions and real-use checks

Related tutorials and sources