mirror of
https://github.com/libretro/RetroArch.git
synced 2026-11-22 10:50:15 -10:00
codex/android-native-streaming
407
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
862614ded5 |
X11: Display Pacing On VBlank Events holds on the window's CRTC vblanks
The X display server gains the vblank clock the setting's hold waits on. It asks the Present extension for a notification at the vblank count after the last one seen; the answer carries that vblank's count and its time on the monotonic clock, for the CRTC the window is on. The requests are made with xcb's own request call, so nothing beyond libxcb is linked, on a connection of the clock's own: a wait is a bounded poll of its socket, there is no thread, and no other thread's events are read. A window destroyed, a server without Present or one whose stamps are of another clock leave no clock, and the timer paces. The GLX context says its swap tears with no swap interval where no compositor shows the window: it asked to bypass one, or none runs. samples/gfx/x11_vblank runs the clock against a real server in CI. |
||
|
|
22d3a9ee88 |
KMS: Display Pacing On VBlank Events holds on the CRTC's vblanks
The KMS display server gains wait_vblank. The CRTC's sequence is the count and its stamp the time; the next vblank is a sequence event, queued on a file description of the server's own - the context's carries its page flips, which are left to it - and waited for with the caller's bound. No thread. An inactive CRTC, one with a variable refresh rate on, and a kernel or libdrm without the sequence ioctls count nothing, and the timer paces as before. The hold needs a present that tears, which on KMS is an async page flip: the KMS context answers present_immediate as it queues one. KMS shows nothing but fullscreen, so the hold no longer waits there for the Fullscreen setting; that test moves from the wrapper to where the frame info is filled. The setting is listed on KMS builds. display_servers_kms_test drives the clock over a FIFO standing in for the device, and drm_vkms_live runs it on a real kernel's vkms: thirty vblanks one by one, a page flip's event still the master's. |
||
|
|
213247f4d3 |
Vulkan, OpenGL: presented through DXGI, a tearing present is immediate
Display Pacing On VBlank Events holds only where the driver says its present goes straight to the scanout, and Vulkan and OpenGL said nothing once they presented through the DXGI bridge. The bridge now answers: it may tear, and its chain's output flips a fullscreen window itself rather than leave it to DWM - asked through IDXGIOutput6 when the chain is made and after each resize, by its vtable slot, since dxgi1_6.h is not in every SDK the bridge builds with. Vulkan passes the answer on for the interval it presents with; OpenGL has no poke for it, so the context driver gains present_immediate, WGL answers there, and the threaded wrapper asks the context where the driver has no answer of its own. The dxgi_present sample checks the query and its slot against the tree's dxgi1_6.h, and that a resize asks again; the harness checks that a context's answer reaches the hold. |
||
|
|
c92579e47b |
Threaded video: Display Pacing On VBlank Events
A setting, off by default. With Display Pacing, vsync off and fullscreen, the hold releases each core frame on a vblank the display server counted instead of sleeping to a deadline: the vblank nearest the frame's due time, which accumulates in the content's period on the clock, so 60 on 120 Hz and 59.94 on 60 Hz keep the content's rate. It holds only where a frame's start cannot cost latency: the driver says its present tears (the new present_immediate poke: Direct3D 11 and 12, Vulkan in immediate mode), no variable refresh rate is in use, and the content is no faster than the display. Everywhere else the timer schedule paces, as it does with the setting off. The display server's wait_vblank now returns a vblank count and the latest one's time, with a bounded wait for the next. On Windows a thread of its own sits in D3DKMTWaitForVerticalBlankEvent, which takes no timeout, and counts; it parks unasked, and when the wait fails or comes straight back. The hold waits two content periods at most, takes no vblank that is old, and stands down when vblanks stop or do not keep the display's grid - for good the second time running. The harness drives the hold from a vblank clock of its own: the rate at 60, 120 and 144 Hz, each case it stands aside for, and each way it stands down. samples/gfx/win32_d3dkmt runs the Windows clock under Wine on entry points of its own. |
||
|
|
670e274643 |
core signatures: let test-key builds hide their notice
Builds that trust the test signing key get a Test Signing Key toggle in Notification Visibility. Off hides the on-screen reminder; the log line saying the build trusts a test key stays on every launch. Release builds have no such setting. |
||
|
|
8498482587 |
xmb: Ribbon Particles setting
The ribbon's drifting specks of light are drawn only with Ribbon Particles on, off by default like Ribbon Glow and Plastic Effect. With it off the ribbon draws its sheet alone, as Simple Ribbon does, and the glow is made of what the ribbon draws. The Wii U, which builds the specks on the CPU, skips them too. |
||
|
|
08a6f540cb |
xmb: new ribbon, Ribbon Glow and Plastic Effect
The Ribbon is a lit sheet with drifting dust, worked out from the menu's clock alone, so every frame shows it at its own time at any refresh rate. Plastic Effect shades XMB icons and text as translucent plastic, and Ribbon Glow adds a soft bloom to the Ribbon; both are settings of their own, off by default, since both cost GPU time. The Simplified Ribbon draws from the Ribbon's mesh. Drivers: - Every driver draws the sheet on the GPU from the mesh's positions, read in place; the Wii U works out only the dust on the CPU. - The ribbon's data reaches the GPU straight from gfx_display: its own buffer index on Metal, written into the mapped constants on D3D10/11/12, bound only for the ribbon draw. - With float images the glow takes one output pass. Vulkan, GL and Metal draw its capture and blurs before the frame's first pass, so the pass the menu draws in is never split, which on a tiled GPU would store and reload the whole target. Based on PR #20101. Co-authored-by: Jean-André Santoni <[email protected]> |
||
|
|
2436aa14a3 | Menu: Use dropdown and more precision for viewport anchor bias | ||
|
|
6ed8c05efd | Menu: Smaller step for windowed size range | ||
|
|
bfb8c1517d | Menu: Standardize portrait vs landscape messagebox size and usability | ||
|
|
68d25aa5bf | Add option for quick scrolling with left+right (#19860) | ||
|
|
1656558977 |
video: add Skip Duplicate Frames
A repeat the core sends as a NULL frame is left unpresented, so the display receives the content's own frame rate and frame generation or interpolation tools see the real cadence. It stays out of the way where the presents are the effect (Black Frame Insertion, shader sub-frames, Threaded Video Frame Repeat, a headset) and with the menu open, fast-forward or a cached frame shown again. While repeats are being skipped, the runloop holds the loop to the content's period with its timer wherever only VSync or the threaded hold would have, since neither can block on a frame that is never presented, and the driver's release stands aside. Lanes in samples/runloop/pacing and samples/gfx/threaded_video pin both halves. Idea from beetle-psx-libretro#1013 by Razor221. |
||
|
|
2c80e1abd6 | Add Bluetooth settings visibility option | ||
|
|
b1a347a984 | Show Scanline Sync Offset only when Scanline Sync is enabled | ||
|
|
026a7aa690 |
iOS screen margins: keep iPad multitasking and iOS-only settings
Follow-up to the scene window and screen margin change. Sizing from the window made the iPad multitasking test compare the view with its own window, which it always fills, so Split View, Slide Over and Stage Manager stopped being detected and the safe area was applied to them. Compare the window with the screen. The four settings were registered on every platform, adding keys to every retroarch.cfg. Registering them under TARGET_OS_IOS, as audio_respect_silent_mode is, keeps them off the others. They also had no sublabel: the description never appeared because sublabels are bound through the table in menu_cbs_sublabel.c. The margins were copied into an NSData, queued to the main thread and stored in an ivar, on a path borrowed from the screen orientation setter. All of it runs on the main thread already, so the layout now reads the settings directly and a change only asks for a layout. That also stops every slider step from re-requesting the orientation, and drops CMD_EVENT_VIDEO_APPLY_STATE_CHANGES, which ran before the asynchronous layout it was meant to follow. Margins are rounded to whole device pixels so the layer is not resampled at a fractional position or size. |
||
|
|
ed38dd6394 | iOS: preserve scene windows and add configurable screen margins | ||
|
|
5756db8659 |
Input: Plays As, several controllers on one player, with hotkeys of their own (#19916)
* OpenXR: the controllers' slots are not read from the driver's view
A joypad driver that keeps its pads' state lends it to the snapshot
bridge through view(), and the bridge reads that in place of a copy
(
|
||
|
|
18128e1fa5 |
menu: a display for each screen, Menu Follows, Menu Display and Notifications
On Android, Separate Screen Windows reads "Game Screens on Other Displays". While it is on, Stereo 3D & Screens lists a Game Screen N Display row for each screen, Menu Follows (Game Screen 1, Game Screen 2 and each further screen the core has, or Separate), Menu Display (only when the menu follows no screen) and Notifications (With the Game or With the Menu). A Menu Follows screen kept from a core with more screens stays until it is changed. A display row offers Auto, each display by name with its product and size, such as "Display: DP Screen (DELL U2720Q 2560x1440)", and Off. OK opens a dropdown of the displays listed now. "Game Screen" and "Display:" keep a game's second screen apart from a panel Android calls Screen-2. The name is what is saved, so the same port is found again whichever monitor is on it; a display no longer listed shows as "Display: <name>" and counts as Auto. video_screenN_display, video_menu_follows, video_menu_display and video_notifications_window are saved in the config and in core and content overrides. They replace video_screenN_window_mode: an old Hidden loads as Off, Attached and Separate as Auto, and the old key is no longer written. The mode setting is gone, and the monitor row is listed on no platform; video_screenN_window_monitor stays in the config for the desktop. Until placement reads them, screen 1 stays in RetroArch's window and the others go by Auto unless Off. |
||
|
|
665064a6f4 |
Android: custom Vulkan driver packages (Turnip) on Adreno (#19955)
* Android: load custom Vulkan driver packages on Adreno Sideloaded arm64 builds can load a Vulkan driver package (a zip with meta.json and one .so, such as Mesa's Turnip) on Adreno GPUs with Android 9 or later. As libadrenotools does, a private copy of the system Vulkan loader is opened in a linker namespace of its own, where a small hook library hands it the custom driver as its HAL. The new video_vulkan_driver_path setting names the zip; empty is the system driver, and core, content-directory and game overrides carry it. The package is checked and extracted to internal storage once per version. Packages from any vendor are accepted. Only Mesa ones have been tested, so any other vendor logs that it is untested and that its load cannot be confirmed. A Mesa package that leaves the stock Qualcomm driver running, as the hook does when the custom library fails to load, counts as failed. When the custom driver fails to create an instance, a device or the first swapchain, the context is redone on the system driver in the same process. A driver that takes the process down during its init is turned off for that core until it is picked again, and a "Safe start" launcher shortcut starts RetroArch once on the system driver. Play Store, Quest and API 16 builds do not carry any of it. Co-authored-by: lim2222 <[email protected]> * Menu: Custom Vulkan Driver setting Settings > Video > Output gains a Custom Vulkan Driver row on builds and devices that can load one. OK opens a browser for driver zips in <system>/vulkan_drivers, Start goes back to the system driver, and the sublabel says when the chosen driver crashed during its last start and is off for the running core. While RetroArch runs from the Safe start shortcut, the row reads "System (Safe start)" and the sublabel names the driver the next normal start uses. The choice applies at the next Vulkan start; picking a driver never restarts video. Co-authored-by: lim2222 <[email protected]> * archive: a streamed Deflate member writes no more than its size A Deflate member streamed to its file a window at a time is now refused as soon as it inflates past the size its headers give, so no more than that size reaches the disk, as for Deflate64, LZMA, zstd and bzip2. Both the zlib and the built-in inflate paths. Lane: archive_stream_test "inflate bound", a member of stored blocks that holds 1 MiB under a 300 KiB size, counting what the VFS writes. * Vulkan custom driver: merge onto master, ask the GPU once The menu row moves one entry up its table, clear of the manual-scan row master renamed. Whether the device can take a custom driver is asked once and kept, rather than each time the Video settings list is built. * Vulkan custom driver: extract a picked package in a task Picking a driver pushes a task that checks the package and extracts it on a worker, into the dir the next Vulkan start looks in, so that start only maps the library rather than inflating up to 64 MiB while the main thread waits. The task reads only what it was handed. It writes through a .prep dir of its own; a context init that gets there first extracts through its .tmp as before, and whichever finishes second keeps the other's. The once-per-process prune leaves .prep dirs alone while a task runs. A driver set by an override, never picked, is still extracted at its first start. --------- Co-authored-by: lim2222 <[email protected]> Co-authored-by: LibretroAdmin <[email protected]> |
||
|
|
33d69e1e6c | On-Screen Display visibility option sublabel clarification | ||
|
|
6ebf66b643 |
OpenXR: per-screen placement for headset screens, and Edit Screens to arrange them by hand (#19945)
* video: per-screen geometry for the headset's floating screens Each floating screen, by the core's logical screen id, gets its own offsets, yaw, pitch, roll, scale and visibility (video_screen_xr_t), applied on top of where the layout puts it. video_views_xr_reset gives the defaults and video_views_xr_normalize clamps each value to its range: offsets to 10 m either way, angles to 180 degrees, scale from 0.1 to 10. A planner given no screens uses the defaults, so nothing moves until a setting does. * configuration: save per-screen headset geometry video_screen<N>_xr_x, _y, _z, _yaw, _pitch, _roll, _scale and _visible keep each floating screen's adjustments for screen ids 1 to 8, and survive configuration overrides like the other video settings. A minimal save writes only the values that differ from the defaults. The video_screens settings sample checks the round trip and the override cases, and runs in the OpenXR input and Wine views jobs. The defaults fixture now links video_views.c, which the reset uses. * menu: per-screen controls for the headset's floating screens Stereo 3D & Screens gains Screen, which picks a floating screen by its logical id among those in the current frame's map, and for it Horizontal, Vertical and Depth Offset, Yaw, Pitch, Roll, Scale and Visible, with Reset Screen and Reset All Screens. The rows apply live and are hidden where they cannot apply, such as a tracked projection's eyes. Stepping between screens reads one snapshot of the map and is bounded, so a tracking change mid-step cannot leave it walking an empty map. docs/openxr.md describes the controls; the video_screens sample drives them through the shipping menu actions. * video: apply per-screen headset geometry to the frame snapshots Each XR planner, Vulkan's and GL's, takes the normalized screen settings with the frame snapshot, so a screen moves, turns, scales or hides as its rows change, while paused too; recentering and tracked projections are unaffected. Screen images are kept between frames, so shader feedback survives a placement change. A retained XR target that cannot be allocated is skipped quietly, remembered by its size so it is not retried every frame; only the desktop UI and canvas targets log the failure. Covered by openxr_core_test, the video_screens sample, the e2e runner's feedback shader case and the new vulkan_views_target sample. * android: keep the OpenXR EGL context C89 gl_xr_egl_init declared its extension string after statements. * video: pose inverse, layout spots and grab maths for headset edit mode Each item's layout spot comes from one helper that placement uses and the quad set records per slot, so a shown pose turns back into the settings that placed it. Grab maths: the item follows the aim, level unless tilting, offsets clamped to the settings' range; the stick pushes along the ray and resizes. Edit picking sees every item and takes the menu by a handle bar under it. * video: a frame without a view map is screen 1 in the headset A core without a views map (SNES, say) had no screen to select, so its frame could not be moved. Its whole frame now takes screen 1's offsets, turn, scale and visibility, and the selector lists Screen 1. gl's window stays as laid out while the menu is open over it. * video: the headset's menu in front of screen 1, or where it was put The menu sat at a fixed spot, so moving screen 1 closer left the menu behind it. It now floats 10 cm in front of screen 1, facing as it does, at its default angular size and never nearer than 0.4 m, while screen 1 floats and shows, and is still submitted after the screens. A menu place (video_openxr_menu_xr_* with video_openxr_menu_placed) overrides that; it is saved like the per-screen keys, and Reset All Screens clears it. * input: Edit Headset Screens mode for the OpenXR controllers Edit Screens starts from a hotkey, a headset action, the HEADSET_EDIT_SCREENS command or a Stereo 3D & Screens row, and stops on the same, on opening the menu, on a video reinit or when the session ends. It syncs its own action set in place of the game's, points the lasers at every item whatever the Laser Pointer setting, keeps the menu's quad up while editing, and with While Editing Screens set to Pause pauses only content that was running. A runtime that refuses its bindings keeps the game's and leaves edit mode unavailable. The setting reaches the headset's poll with the others, and the pause and resume are asked of the frontend as platform requests, so the input driver issues no command and takes no settings itself. A Laser Pointer value past its choices, which a hand-edited config can hold, reads as Auto rather than as edit mode's. * input: grab, tilt, push and resize headset screens in edit mode A grip on an item takes it in the screens' frame: it keeps its pose relative to the hand, stays level unless the trigger is held, and the stick pushes it along the laser and resizes it, past a deadzone. Each poll writes the item's offsets, turn and scale where the menu's rows write them, through named frontend calls, clamped so it waits at a limit and resumes from there. The menu is taken by its handle; a menu that follows screen 1 is placed as large as it shows. The main button resets a free item as Reset Screen does, or puts the menu back in front of screen 1. A recenter, a screen leaving the map and leaving edit mode let go, counted for the frame snapshot; an untracked hand holds its item still. * openxr: held screens follow the hand at the headset's rate The main thread publishes what each hand holds through a seqlock; each headset frame re-places a held item, both eyes of a stereo screen, from that frame's own aim, so it no longer waits for the next video frame. An item let go stays where the hand left it until a quad set planned at or after its release (an edit count carried in the frame snapshot) shows it, even once the hand holds another item, so nothing steps back. Lazy Follow holds its glide while anything is held. Edit mode outlines every item, brightly the one under a laser, and draws the menu's handle bar under it, from the laser's image, now an atlas of the dot, two outlines and two handle bars. They take only the layers the screens leave after the dots. * openxr: edit mode end-to-end cases and documentation The test layer's aim can roll, and the e2e runner drives edit mode against Monado: grabs that follow the hand on every headset frame and stay where they are let go, level and tilt, the stick, resets of a screen and of the menu, the menu taken by its handle and following Screen 1 at its size, outlines and the handle, a no-map core, a views core's fallback frame, Follow Head, Lazy Follow, recentering, two hands, pausing, and what starts and ends edit mode, including the headset's hotkey bits with no command interface. The cases whose work is a host's or driver's own run on glcore and gl too. docs/openxr.md explains editing screens in the headset and where the menu goes. * openxr: a laser beam from each controller to its dot A thin strip runs from each hand's aim to its dot, or 1.5 m into nothing, turned about its own axis each headset frame to face the head so it never shows edge on. It comes from the laser's image, so it needs no new swapchain, and uses layers left after the dots and edit mode's outlines, so it is the first to go when the runtime has few. The new Laser Beam setting shows it in edit mode only (the default), always, or never; outside edit mode, Laser Pointer and its hotkey hide it with the dot. * openxr: edit mode outlines in three bands, outside the item A light band between two dark ones shows on white, black and busy borders alike. The rim now sits wholly outside its item, 5 mm clear of it even after filtering, so it never covers the picture; its region grows to keep two texels a band at about the old thickness. Screens' outlines are submitted before the screens, so a neighbour placed flush covers the part of a rim over its picture, while the menu's outline and handle bar stay on top. The handle bar moves 5 mm below the menu's outline, which it would otherwise cover, and gets the same bands, faint and bright. * input: choose a headset edit item with Select Next and Previous Edit mode steps from the laser through the screens it can move and the menu. A chosen item is the one lit, either hand's grip takes it from wherever the hand is, and Reset resets it, so a screen hidden behind another can be moved. Whatever a hand holds stays lit. A ray on the menu's handle bar takes the menu before any screen in front of it. Within 3 cm of the bar, a ray that came from the bar keeps the menu even over a screen, and one that came from elsewhere takes it only where no screen is hit. * openxr: snap a held headset screen to the screens near it Snap to Screens, on by default, turns a held screen parallel or square to a nearby screen and lines up its plane, edges or centre. Each pull is exact within 3 cm or 5 degrees and fades out over as far again, so the screen catches up with the hand rather than jumping, and snapping fades in over the first 5 cm or 10 degrees after a grab, so taking a screen never moves it. With several screens near, the snap that leaves the least error wins, so a near screen's exact pull beats a far one's fading pull whatever their order. One stateless function inside the grab serves the main thread and the headset's thread, so a screen is saved where it was shown. The holding hand buzzes as a snap takes hold, once, and not again until the screen has left that pull. * input: turn a held headset item with the free hand's stick A quarter turn of a held screen needed the controller turned a quarter turn, which swung the screen round the hand on its long reach, so a square snap could not be reached. Now the stick of the hand holding nothing turns what the other hand holds about the vertical through its middle, faster the further it is pushed, and snapping still catches it parallel or square. A carried item keeps its pitch and roll and its angle to the way the hand points across the floor, so raising, lowering or twisting the hand no longer tips or swivels it; the trigger lets it ride the hand rigidly. * openxr: smooth the controller aim in edit mode A screen held about 2 m out on the laser magnified every tremor of the hand. In edit mode each hand's aim now goes through a One Euro filter, which smooths a slow hand hard and a fast one little, with its rate taken from the headset frame's own time step. The headset's thread filters once a frame and hands the result to the main thread, which grabs, moves and lets go from it, so a screen is saved where it was shown. The new Edit Smoothing setting picks Off, Low, Medium (the default) or High; outside edit mode the lasers are never smoothed. * openxr: name the chosen edit item beside the controller Edit mode now shows a faint tag just above the hand that last pressed Select Next or Previous, reading Laser, Screen N or Menu, so what the grip will take is plain without a notice. The words are drawn once into the laser's image in the default font and the interface language, light over a dark halo like the outlines so they read on any background, and the tag is one more headset layer; when the runtime is short of layers the beams are dropped before it. On a runtime whose swapchains are too narrow for the words, the laser's image keeps its old width and there is no tag. * input: tilt a held headset item with the free hand's stick In edit mode the free hand's stick already turns the item the other hand holds. Its up and down now tilt that item too, about the item's own left-right line through its middle, at the turn's rate and with no limit: up tips the top back, as when pushing a monitor's top back. It works whether the item is carried or rides the hand with the trigger held, and snaps as the turn does. Within about 25 degrees of left or right the stick only turns, and within about 25 degrees of up or down it only tilts, so a push meant for one does not drift into the other. Edit mode's starting notice lists the turn and tilt and stays about 8 seconds. * input: snap a turned or tilted headset item to angle steps While the free hand's stick turns or tilts a held item in edit mode, the item clicks into steps of the new Snap to Angles setting (15 degrees by default; 30, 45, 90 or Off), so it is easy to set straight. The turn counts from facing the user's head across the floor, the tilt from upright. Within about 2 degrees of a step the item holds there and the holding hand buzzes once; the stick's own angle keeps adding up, so pushing on leaves the step. Only the stick steps: carrying an item or tilting it with the trigger never clicks, and a snap to another screen that would engage wins over a step. * openxr: show the back of a headset screen turned away Runtimes draw only the front of a quad layer, so a screen or the menu turned away from the head vanished. When the head is behind a quad's plane, the frame now submits a plain dark panel in that quad's place: a solid grey cell of the laser's image, at the quad's size, turned to face the head. It takes the quad's own layer, so the layer count and cap are unchanged. Edit mode picks either face, so an item turned away stays grabbable, and its outline, handle and dot turn with its back. * input: keep a screen snap's angle once the free stick lets go A snap to another screen shows a held screen square or parallel to it, but the item's own angle stays where the stick or the hand took it, up to several degrees off. The next turn with the free hand's stick started from that hidden angle, so the screen left the snap early on one side, late on the other, and caught up with a lurch. Now, as the free stick returns to its deadzone and as a push starts, a snap engaged on the turn becomes the item's own angle: the carried turn, or the orientation the trigger tilts. A snap still fading in never does, since that would hop the screen into it. The place is left to the hand, and carrying alone never keeps the angle, so pointing still pulls a screen out of a snap. Letting go of the grip leaves the item where it shows, as before. * openxr: hinge a held headset screen to a neighbour's edge Snap to Screens now also hinges a held screen to another along a shared edge at any angle between them, so a DS or 3DS pair can be opened at a slant: an edge within 5 degrees of parallel to one of the other's, within 3 cm of its line and sharing some length with it, turns exactly parallel and moves onto it, centres or ends level, its angle left free. The pull fades in over the first 3 cm of shared length, so a screen slides off the end of the other's edge without a jump, and a diagonal neighbour never hinges. Screens that would overlap do not hinge; the pull is whole from flat to square and fades out folded shut. Flat and square snap as before and report a hinge at 0 and 90. A turn to the same screen pivots on the shared edge, so the edge stays on the line as the screen leaves flat or square. The snap still keeps nothing between calls; its result carries a hinge bit, and video_xr_snap_hinge also says which edge and line, for the stick to swing about. * input: swing a hinged headset screen about the shared edge While a held screen is hinged to another, the free hand's stick axis that turns nearest the shared edge, the tilt for a top or bottom edge and the turn for a side one, now swings it about that edge, so it stays attached; the other axis still turns or tilts it and can pull it off. Where the swing leaves it, angle and place, it stays as the stick lets go. Snap to Angles counts a hinged screen's steps from flat with the other screen. A hinge counts only while the screen's own edge is within its range, not when other snaps alone hold it on the line, so a swing never carries a screen round a line it is far from. A square corner is a side hinge at 90 degrees, so the turn stick there now swings the screen about the corner's edge. Main thread only; nothing new reaches the frame loop, which still shows the grab through video_xr_grab_pose. * openxr: leave a gap between hinged headset screens Edges that meet in edit mode, side by side, at a corner or hinged at any angle, now click to a set gap from within 1 cm and otherwise keep the gap the hand gives them, still hinged, up to 10 cm (letting go by 13). Screens no longer have to touch, which made them overlap. Each grab carries the gap, so the edit poll and the frame loop snap alike; until a setting sets it, it is 0. Pushed past touching, a hinged edge stops there for the first centimetre of the push, the stop fading out by 3 cm, and ticks once per push. A swing pivots on the held screen's own edge, so the gap keeps through it, and a commit keeps the hand's gap unless the click holds it. After a swing lets go past square, that stick axis and its steps keep pivoting on the same edge until the edge leaves the hinge's reach, so a flick past square and back does not creep. Of two neighbours within the 5 degree turn snap, the nearer edge wins the turn and the hinge, by one measure for every screen, so a screen stacked behind, one off the ends of the edge or a side wall at a corner never outranks a hinge the turn holds. * menu: add Hinge Gap for headset screens Hinge Gap (0, 1, 2, 3, 5 or 10 cm, default 2) sets the gap edit mode's Snap to Screens leaves between screens that meet edge to edge, side by side, at a corner or hinged. Edit mode takes it as it starts and gives it to each grab; the click to it buzzes like the other snaps. * menu: put Edit Screens under Headset Output Stereo 3D & Screens now lists Edit Screens and its snaps right under the switch that reveals them, then the headset's own setup, then where the screens go, with the per-screen rows last and Visible first among them. * openxr: track each held screen's hinge on the frame loop The frame loop already re-snaps each held screen every frame. It now also keeps, per hand, the hinge that snap holds whole, until the edge leaves the hinge's 4.5 cm reach, where the frame draws it, so edit mode can mark it. A kept hinge whose target no longer matches is dropped. video_xr gains the hinge line's ends, along the overlap of the two real edges and midway across the gap, an outline cut that drops one edge's rim, and a green strip in the laser's image, before the tags. * openxr: mark a hinged headset screen with a green line While a held screen's hinge holds, the two edges that meet drop their outline rim and a 6 mm green line runs along the hinge where they overlap, midway across the gap, so it is clear when the hinge has taken hold. The line is drawn as the beam is, a centimetre nearer the eye than the edges, since SteamVR does not keep the order of overlapping quad layers, and comes after the outlines in the layer budget; hidden rims cost no layer. * input: buzz longer as a headset screen hinges A hinge taking hold now gets one 150 ms buzz at 0.8 on the hand carrying the screen, against the 20 ms snap tick, so the attach can be felt. It fires again only after the edge leaves the hinge's reach, hinges elsewhere, or the other hand takes the screen it hinges on, so a swing past square and back does not repeat it. Ticks due while it plays are skipped rather than cutting it short. * openxr: find headset screens resting in a hinge Two screens no hand holds rest in a hinge when their poses pass the test that engages a carried screen's hinge, with either one carried, and the hinge, held whole with nothing else pulling, leaves the carried one where it is. So a hinge found at rest stays hinged when its screen is taken. The engaged test moves into its own function so both use the same one, and one target can pull whole whatever the grab's fade. * openxr: keep a headset screen's hinge shown at rest In Edit Screens, two screens no hand holds that rest in a hinge keep the green line and their hidden rims, whether let go hinged or loaded that way. The main thread counts them only when a resting screen changes and sends them with the hands' record, so a release and its resting pair arrive together; the frame loop places each line from the screens it shows. A screen hinged at rest on two adjacent edges still keeps one of those rims. The hands' record now outgrows the quads, so the seqlock's copy is sized to the larger of the two. * openxr: pick up a hinged headset screen still hinged Taking up a screen that rests in a hinge starts the carry on that hinge, whole from the first poll, with no buzz and no jump, until it leaves the hinge's reach, another hinge takes hold, or the other hand takes the screen it hinges on. Until the grab's own snapping has faded in, the kept hinge's target still pulls whole, so a straight pull out does not hop. The grab carries the hinge so both threads hold it the same; of several, the one the snap ranks best carries over, and only where holding it moves nothing. While the other screens fade in, the hinge's screen also leads the turn, so a nearer one still fading does not take it. * openxr: end a headset screen's hinge where a push passes the stop Pushing a hinged screen into its neighbour holds the edge at touching for 3 cm of push, fading out by 5.5 cm. Where it stops holding, the hinge ends: the line goes, the rims come back, and the lid and buzz are cleared, so screens pushed into each other show no hinge that a let-go there would not rest in. Pulled back, the hinge takes hold again 5 mm short of where it ended, with the long buzz, so a tremor there does not flicker it. The grab carries that through flag, and the frame loop keeps its line until the main thread sets it, so the two threads never disagree for more than a poll. At Hinge Gap 1 a pair let go touching rests hinged and is taken up hinged, as at every other gap. A screen swung into a square corner gets the long buzz on arrival, and the other hand taking the target does not hop the carried screen by the push's depth. * input: let go of a headset screen where it was before the grip opened Opening the grip twitches the hand, and the poll that sees the grip open would move the screen by that twitched aim. Half a degree of pitch moves a screen 1.8 m out by 1.6 cm, enough to knock it off its hinge's gap or out of level, so it would not rest hinged. Each hand keeps a short trail of where, turned and as large as its screen showed, entries at least 10 ms apart, and a grip let go puts the screen as it showed 80 ms before (INPUT_OPENXR_EDIT_REWIND_US), or as it was taken if held for less. Edit mode's end and a recenter let go where the screen shows. * openxr: find where a let-go headset screen settles in its hinge A screen let go while its hinge shows should land exactly in that hinge, so the hinge still shows at rest and a pick-up is hinged. video_xr_hinge_settle holds the hinge whole from the hand's pose, then moves the edge to the set gap from within 3 cm of it (touching stays where the stop holds it) and levels it along the edge within the level pull's reach. Its result must pass the rest test, and it turns no further than a grab's hinge engages, which shares that test. A pair resting inside a settle band but off its point is no longer listed at rest, since a pick-up and let-go would move it. A touching rest is taken 5 mm deeper into the push stop, at every Hinge Gap, so a hand that drifts less than that apart before letting go settles touching rather than at the gap. * openxr: settle a let-go headset screen into its hinge A screen let go while its hinge shows now goes exactly into that hinge: to the set gap from within 3 cm of it, touching from the stop's hold, and level along the edge from within the level pull's reach. It then rests there, listed and green, in the same publish, and is saved there. Elsewhere it stays where it shows, as before. Each trail entry also records where the hand put the screen with no snap and whether a let-go there settles. At the let-go the rewound entry is settled again against the screens as they are now, at that entry's size, and put in one go. * openxr: let a hinged headset screen rest at any fold Snap to Screens' turn to flat, and its turn to square at a corner, is whole within 5 degrees and fades out by 10, so a hinged screen held there shows at twice its angle off less 10. No fold shown in that fade read as a rest: the pair was not listed, a let-go there did not settle into its hinge, and taking it up would have moved it. Where a hand takes a rest, it now holds the screen at the angle the turn's fade shows it from, the inverse of the turn's pull, so every fold rests, is listed and is taken up unmoved. Held snapping is unchanged. * input: keep a headset screen's hinge through a shaking hand Edit Screens' hinge buzz, lid and push stop followed the snap's own engage and reach on every poll. A hand shaking half a degree (1.6 cm at the screen) about a hinge's edge flipped them many times a second, each flip a long buzz. Each hold now keeps one mark: the hinge a let-go would settle into. It takes hold at once, with the long buzz, and lets go only once polls have seen the hand out of where a let-go would settle for 150 ms, each poll counting at most 50 ms, so a stalled main thread or a spell untracked never lets it go alone. The other hand taking its target, hinged elsewhere or not, the target leaving and the let-go end it at once. The lid waits for the mark to go, the push stop follows it, and a let-go while it shows settles into it from where the hand last would have, edit mode's end and a recenter included. * openxr: draw a held screen's hinge as the main thread marks it The grab carries the main thread's hinge mark, and the frame loop draws a held screen's green line and cuts its rims from that mark alone, through video_xr_grab_marked, while it snaps the screen every frame. A frame loop taking the hinge by itself between polls would flicker the line for a hand shaking at the edge of the hinge's range while the mark held. A mark whose target the frame does not show cuts no rim. The other hand taking the mark's target ends it, and the lid, on any poll, tracked or not, so a lost hand's line does not come back when that hand lets go. video_xr_grab_near_hinge loses its past argument, which only the frame loop's keep used. * openxr: keep edit mode's hinge layers in place SteamVR does not keep submission order for overlapping quad layers, so a layer added, dropped or moved to another index can pop the edit outlines in front of the screens, as a wobble at a hinge would do to its line's layer. The hinge lines are fixed slots: one for each hand holding a screen, hand 0 first, then one for each pair at rest. A slot with no line to show is drawn in place from its screen's middle, at rows of the laser image that are empty either way up. The layer count and every index change only at a grab, a let-go or a re-count of the pairs at rest; a mark only changes crops and which rows a slot shows. * input: date a let-go's trail by frame and stop it at a stall Each trail entry is dated by the frame its aims are from, one a frame and per hand, and the release poll records a new frame's aims first. The rewind stops at a stall, entries more than 2.5 frames apart, a frame counted as at least 20 ms so a fast headset's close entries never read as one. Under load a stall of 0.1 to 0.3 s can come just before the release; the entry from 80 ms back would then hold the pose from before it and step the let-go back across all the stall's motion. With Edit Smoothing on, which damps the twitch, a let-go that does not settle into a hinge stays where and as large as it shows: a rewind there would step back by what the smoothed aim still lags. The hinge decision and the settle use the trail either way. * openxr: cut edit outlines from cells instead of turning them Cutting a top or bottom rim from the one outline image turns both outline quads a quarter turn and swaps their width and height, and on SteamVR that can blink every edit outline as the hinge takes hold or lets go; side cuts, which never turn, do not. The laser's image carries twelve pre-cut outline cells after the tags, faint and bright, for a cut top, bottom, left, right, top and bottom, or left and right, so a cut only picks a cell and the quads keep their pose and size. The image is then 5582 texels wide. A runtime whose swapchains are narrower, or that does not say how wide they can be, keeps the turned and cropped outline at 2498 or 1208 wide. One log line at the laser's creation gives the width chosen and the runtime's limit. GL writes the top and bottom cells swapped for its bottom-up rows, and Android's copy of the image is allocated rather than static. The edit-hinge-3ds-narrow e2e case runs the turned cut at RA_XR_LAYER_MAX_WIDTH=4096, on Vulkan and the GL EGL lanes. * video: draw headset screens straight into the runtime's images Each headset screen was drawn into an image of the driver's own and copied from it into the runtime's on every new frame, Vulkan with a render pass and GL3 with a blit. Screens are now drawn into the runtime's image itself, as before per-screen placement, with no image of the driver's and no copy. A screen drawn again with no new frame - resized, made again or moved while paused - replays the last frame's final pass from the chain: build_viewport_pass_replay draws it at the new size from what it read then, the passes' outputs, their feedback and the history that frame saw, with that frame's count. Nothing else runs, feedback does not swap and history stays, so a feedback or history preset holds still while paused. A chain made to replay keeps one more history image, so the frame's end writes where the last frame did not read; the window's chains keep what they did. This also has movie frames reach the headset, which the copy held at the first one, and draws a screen resized while paused at its new size rather than stretching the old image. * openxr: leave what users who never edit see as it was Screens seen from behind turn to their grey backs only while Edit Screens is on, where screens are turned around; outside it nothing changes and no head is located for them. The grabs carry whether editing is on. The menu opens at its own spot, straight ahead of the anchor, as it did. Menu in Front of Screen 1, off by default, keeps it just in front of screen 1 and moving with it. The frame loop copies the main thread's grabs only once their stamp moves, so outside edit mode no frame copies them. A new session clears the frame loop's own copy and passes over what was published before it, rather than publishing itself: the main thread stays the grabs' one writer. On Touch, the left menu button that opens the menu from edit mode is spent until let go: held on as edit mode ends, it is no Start and does not toggle the menu again after a second. --------- Co-authored-by: libretroadmin <[email protected]> |
||
|
|
5361e1bc8f |
netplay: lockstep for cores whose states are too large to roll back
Rollback keeps a savestate for every buffered frame and serializes every frame, which a state in the tens of megabytes (Dolphin) cannot afford, and needs states that restore deterministically enough to rewind on. Lockstep runs a frame only once every player's real input for it has arrived and never rewinds, so all delta frames share one state, used only to hand a joiner the game or to resync. Desync checks hash the core's system RAM, or the RAM in its memory map, rather than a whole state; a state is serialized for them only when the core shows neither. Input latency rises by a frame whenever lockstep has to wait and falls again once input keeps arriving early, so it holds full speed over a slow link. A host keeps sending while it waits on a joiner, grows its buffers if the core's state has grown, and starts on the running game instead of reloading it. A client takes a state labeled with a frame whose input it already has, and loads it there. Lockstep is a local choice and plays with rollback peers of this protocol, and it is on by itself for cores past 32 MB of state and for cores whose savestates load but cannot be rewound on, which netplay used to refuse. The Lockstep setting asks for it everywhere. Older clients cannot join a lockstep host. samples/network/netplay_e2e runs a host and a client over the loopback on a test core: sticks synced or not, lockstep, a lockstep host with a rollback client, a desync mended and a 40 MB state. |
||
|
|
a0d408f0ce |
netplay: sync the analog sticks of joypad ports
Netplay sent a joypad port's buttons only, so a core reading the sticks of a joypad port (N64, GameCube and others) desynced or saw them at rest on every remote player. The host now sends joypad ports as analog, three words instead of one, with bit 30 marking them; each side hands the core the joypad device it set, so nothing changes for the core. This is protocol 8. A host with Sync Analog Sticks on, the default, turns away older clients with the out-of-date message rather than letting them desync; with it off, any version still joins. |
||
|
|
5c82bce0ed |
overlay: D-pad and face buttons read a finger's contact area (Android)
A touchscreen reports each finger as an ellipse, not a point; Android gives its axes and orientation (AMotionEvent_getTouchMajor/Minor and getOrientation). A thumb laid across up and right, or resting between two face buttons, covers both - and read by its centre alone presses one. After RetroArch-Lite's contact-area input. "D-Pad Input Method" and "ABXY Input Method" choose how each reads a touch: "Direction" - the way the centre lies, as always, and the default - "Contact Area", every way the contact covers, or "Both". Each tip of the ellipse's two axes presses the way it lies from the area's middle, past a small dead zone there. "Contact Area Size" scales how large a contact counts. Measured in pixels per axis against the pointer's own space; RetroArch-Lite measured both against the screen's height, which skews a contact on a wide screen. Android's reader keeps each pointer's contact beside its position, and the driver hands them to the frontend each poll (input_driver_publish_touch_contacts). A finger with no contact size, and every other driver, read by the centre's way. The rows show on Android, where an overlay has the area they apply to. overlay_contact_test holds the geometry: fingertips, thumbs across two ways, upright and level contacts, magnification, wide screens. |
||
|
|
e48ff3f2ad |
Input: add Hotkey Enable Tap Delay (#19871)
Where Hotkey Enable is also bound to a game button (Select, most often), the game saw it for the first frames of every hotkey use. With "Hotkey Enable Tap Delay" set, the game buttons sharing the enabler's button or key are kept from the core until it is known whether a hotkey follows: - let go with no hotkey used, the press is given to the core then, for as many frames as it was held (two at least); - held past the delay (real milliseconds) with no hotkey, it is the game's from then on, along with the other buttons; - used with a hotkey, the core never sees it, or stops seeing it the moment the hotkey fires. Off by default; when off nothing runs. The core's read tests it with the core hold's existing branch. A frontend harness lane covers taps, holds and hotkeys. |
||
|
|
00a3de3cd7 |
Temporal upscaler: HAVE_TEMPORAL_UPSCALER gates the subsystem
HAVE_NGX gated the whole temporal upscaler - the interface handed to cores, the settings, the threaded wrapper's carry and the DLSS, FSR and XeSS backends alike - under the name of one vendor's library. A MetalFX backend on the Metal driver would have to be built under a define that reads as NVIDIA's. The subsystem is now HAVE_TEMPORAL_ UPSCALER wherever HAVE_NGX stood, in the build files, the drivers, the menu, the samples and the compile matrix; nothing changes in what is built. |
||
|
|
dda31fef21 |
Temporal Upscaler: DLSS loads once; Neural Rendering toggles in place
DLSS's feature libraries, Super Resolution's and Neural Rendering's, stay loaded once NGX has loaded them, so NGX set up again on the next content's device or after a driver restart finds them in instead of loading and checking them again. NGX's start-up, and the making of each feature, is timed in the log. Turning Neural Rendering on or off no longer restarts the video driver: its device extensions are asked for (once a run) whenever its library is in the DLSS directory, and the core asked about it then too. Turned off, its model is kept, and turning it on again takes the next frame. |
||
|
|
11370445cf |
Temporal Upscaler: DLSS takes frames in any of its modes; less at start-up
A core that renders in steps, such as a multiple of the console's resolution, can land outside the one DLSS mode's range and was shown without upscaling, saying nothing. The request now names the range DLSS takes over all its modes, and a frame outside its mode's runs in the mode whose range it is in, the nearest to its size; a frame no mode takes is said once in the log. NGX's extension names are kept for the life of the process instead of asked again, with its feature libraries loaded and checked, every time a context is made. Neural Rendering's library is asked about only while it is turned on; turning it on or off now restarts the video driver. |
||
|
|
ccd885c4f2 |
Temporal Upscaler: DLSS Neural Rendering
DLSS 5's Neural Rendering model runs over DLSS Super Resolution's output when its library, nvngx_dlssnr.dll, is in the DLSS directory. It goes through the same NGX session as Super Resolution: the driver's NGX core loads the library from the directory it is given at init, creates the feature (18) on the frame's command buffer and evaluates it on Super Resolution's output with the core's depth and motion vectors at render size. Cores before its driver (616.64) have no such capability; the session then marks it unavailable and Super Resolution goes on alone. Settings > Video > Scaling > DLSS Neural Rendering holds the switch, off by default, and the model's tuning: preset, style, intensity, local structure, local tone, skin structure and auto skin mask. The entry is shown only with DLSS selected, the library found, NGX not OptiScaler's, and no session having found the driver without it. The settings reach the backends as one word. The model reads its tuning only at creation, so a changed setting rebuilds the feature once it has held for 30 frames; turning it off retires the feature through the same ring as Super Resolution's. System Information and the log name the library's version, read from its file without loading it, or say the driver needs updating. The upscaler samples drive both backends against stand-in NGX cores that know the feature: the tuning at creation, the evaluate's inputs and guide sizes, the rebuild after a change holds, the release when off, and a core without it; the loader sample finds the library and reads its version. |
||
|
|
a3e0639a15 |
Temporal Upscaler: the DLSS runtime's version, OptiScaler, presets A to O and sharpness
The DLSS feature library says its version through its own export (NVSDK_NGX_GetSnippetVersion), which the loader now reads from the DLSS directory before NGX loads the file; System Information and the log name it. OptiScaler standing in for NGX is known two ways: its module's version resource names it at the probe, and every parameter table it hands out carries its key, which the session checks after init. The status says "via OptiScaler". The preset setting carries every letter NGX numbers, A to O, in NGX's own numbering, so a newer runtime's presets can be asked for without a new build; a letter older than the runtime found is marked as not in it, and one the runtime does not know falls back to its default. A sharpness setting (percent) rides in the mode word: FSR sharpens with its own pass, DLSS 2.5.0 and older and OptiScaler's RCAS take the NGX Sharpness parameter, XeSS and newer DLSS ignore it. A sharpness change alone makes no new feature. The loader samples read the version from a stand-in feature library and see OptiScaler's key and, under Wine, its product name; the upscaler samples check the status, the sharpness reaching each backend and the feature kept across a sharpness change. |
||
|
|
aca5868b04 |
Temporal Upscaler: FSR and XeSS beside DLSS
The setting gains AMD FSR and Intel XeSS, on the Vulkan and Direct3D 12 drivers as DLSS is. Each runs on its vendor's library, loaded at run time from a directory of the user's and never bundled: FSR through the FidelityFX API (amd_fidelityfx_vk.dll for Vulkan, FSR 3.1; SDK 2's amd_fidelityfx_loader_dx12.dll or SDK 1.1's amd_fidelityfx_dx12.dll for Direct3D 12, where the newest version the library offers the device is taken, FSR 4 on the GPUs that have it), XeSS through libxess.dll on either driver. The FSR and XeSS directories are settings beside the DLSS one, upscalers/fsr and upscalers/xess in the RetroArch directory by default. libretro-common gains the loaders (gfx/amd/ffx_loader, gfx/intel/ xess_loader), C89, with the SDKs' descriptor layouts and type numbers declared so no SDK header is needed, and samples that pin those layouts to the SDKs' sizes and offsets and drive the loaders against stand-in libraries. The drivers go through one dispatch (vulkan_upscaler, d3d12_upscaler) over the three backends, which share the output image, the layout moves around a dispatch and the ring that retires an image and context after the frames in flight. XeSS builds its pipelines in the library's background thread and the frames are shown as they are until they are ready; nothing on the frame path waits. The frontend's mode word carries the quality and preset as set and each backend translates it, so the DLSS preset keeps its meaning and the others ignore it. The upscaler samples run FSR and XeSS behind the dispatch on lavapipe and on Wine's D3D12 against the stand-ins, with the inputs' flags, formats, states, scales and reset read back from the descriptors the libraries were given. |
||
|
|
5c763e756e |
Temporal Upscaler: the DLSS render preset, and the mode named in the log
A Temporal Upscaler Preset setting picks the DLSS model: the runtime's default, or the transformer presets K (the best image, at more GPU time) and J (less ghosting, some flicker), the two the SDK still offers an application. The mode is one word on the way to the backends, the quality and the preset, and a change of either makes the feature again; the preset is set as the SDK's hint for every quality. The log names the mode and the preset when the feature is made. The upscaler samples' fakes record the preset hint and the tests check it; they also clear the runtime they plant, so a run after another starts without it. |
||
|
|
ca3f823755 |
Low-latency power plan: turn off USB 3 link power management
The copy now also sets USB 3 Link Power Management to off on AC, so xHCI links stay out of U1/U2 and connected controllers answer without a link wake. Like the other device settings it is best effort: a system without the setting applies the plan without it. The win32_power_plan harness checks the value on the copy, that the user's own plan keeps its setting, and the missing-setting case. |
||
|
|
98767d6024 |
Temporal Upscaler: the DLSS runtime in upscalers/dlss
The DLSS Directory's default moves from the System directory's dlss to upscalers/dlss in the application directory, beside shaders and system, where other upscalers' runtimes will sit too. |
||
|
|
a9ba46af7a |
Temporal Upscaler: the core interface and DLSS on Vulkan
A hardware-rendered core now has a way to feed a temporal upscaler: RETRO_ENVIRONMENT_GET_HW_RENDER_UPSCALER_INTERFACE hands it an API-neutral interface with get_request, which says whether an upscaler will take the frame and what render size it wants for the mode (so the core renders smaller, jittered and without its own temporal AA), and set_inputs, which brings the frame's depth, motion vectors, jitter and optional exposure and transparency masks beside the color image the existing render interfaces hand over, under the same lifetime and sync rules. Images are the context API's own handles, so the same contract serves Vulkan and Direct3D 12, and later FSR and XeSS. No existing interface version changes; a core that never asks is unaffected. The Vulkan driver runs DLSS Super Resolution over it through NGX (gfx/common/vulkan_ngx.c): a session on the device, the mode's render sizes from NGX's optimal-settings callback, a feature made for the mode's full dynamic range and the output size and re-made only when those change, the frame's size as the render subrect, the output image handed to the filter chain in the core's place, inputs in a depth layout moved for the evaluate and back. Retired features and images go after the frames in flight; nothing waits. The context enables the device and instance extensions NGX asks for, on a device the core makes as well, only while the setting is on, which now reinitializes the driver so they can be. A Quality setting picks the mode (Auto, Native, Quality, Balanced, Performance, Ultra Performance). samples/gfx/vulkan_upscaler pins the glue on lavapipe under the validation layer against a stand-in NGX core library, built with gcc and mingw in the samples-gfx workflow. |
||
|
|
1de580c353 |
Temporal Upscaler: NGX runtime discovery and the setting
The groundwork for DLSS Super Resolution on the Vulkan and Direct3D 12 drivers, with nothing of NVIDIA's built in or shipped. libretro-common gains two run-time loaders under gfx/nvidia, shared by frontend and cores alike: nvapi_loader.c, the NVAPI probe the Direct3D drivers carried themselves, now behind one nvapi_query(); and ngx_loader.c, which finds the driver's NGX core library (beside the program, else where the driver's registry keys point, libnvidia-ngx.so.1 on Linux), resolves the Super Resolution entry points for Direct3D 12 and Vulkan with the parameter accessors, and restates only the SDK interface it takes. A sample drives both against stand-in libraries on Linux and under Wine, and is wired into the libretro-common samples workflow. The frontend side (HAVE_NGX, Windows and Linux builds with Vulkan or D3D12) adds the Temporal Upscaler setting under Video > Scaling, hidden until both the NGX core library and the user-supplied DLSS feature library are found, and the DLSS Directory setting it is looked for in (<system>/dlss by default), plus a System Information line that says what was found. The setting selects nothing yet: the drivers' evaluate path and the core-side buffer exports follow. |
||
|
|
ccffeb553a |
slang: drop vendored glslang and SPIRV-Cross
rslc is the slang compiler everywhere. ./configure --enable-glslang --enable-spirv_cross links the system's glslang and SPIRV-Cross next to it when both are found, and only then does Settings > Drivers offer a Shader Compiler choice between the two: one setting read per stage picks the path, with nothing copied. The MSVC 2010 project builds Vulkan and rslc. Samples that used the vendored copies run on rslc or the system's SPIRV-Cross. |
||
|
|
bb079d496c |
media: match fullscreen playback to advertised display timing
Add opt-in desktop refresh matching and CRT SwitchRes source timing to the shared fullscreen viewer. Windows and X11 capture a temporary output lease and restore only when their applied mode is still current. Preserve core AV timing and reuse the owned mode across queued episode admission. Clear unstable cadence without treating an audio-only repeat tail as variable picture timing. Validation: strict controls with GCC/Clang ASan+UBSan, GCC TSan and threadless; player loop regression and private sanitizer lanes; compile matrix, MSVC6 stand-in, complete Linux graphics and threadless menu jobs; native four-menu source tests and clean Vulkan/D3D11/D3D12 moving-pixel checks with a static negative. X11 live fractional refresh and conditional restoration pass. Windows physical refresh switching remains unverified: this session refuses CDS_TEST even for its current mode. No VRR policy or physical HDR claim. |
||
|
|
a352690514 |
media: add continuous folder playback and fullscreen settings
Advance naturally sorted folder movies only after clean playback completion. Retain the final frame, stop on decode errors, and expose previous/next and settings controls in all four menu drivers. Drain terminal AV1 output and update preview audio repeat policy without reopening the player. Cover completion, queue lifetime, invalid next files, toolbar actions and native menu presentation. |
||
|
|
edd71e2cf0 |
media: load SubRip sidecars and render cues in fullscreen menus
Parse UTF-8 SubRip tracks in bounded task slices, retain active-session ownership and publish cue text without reading files on the render thread. Draw cues in texture menus and the RGUI framebuffer, including while transport controls are hidden or playback is paused. Add subtitle enable/delay settings and parser, ownership, drawing and four-menu sidecar coverage. |
||
|
|
74b7b06fa5 |
Android second display output for video views (gl and vulkan) (#19905)
* android: drain the sensor queue with both sensors off
Losing focus disables the accelerometer and gyroscope, but an event
already in the sensor queue stays there, and android_input_poll_user()
only read the queue while a sensor was on. The queue's fd stays
readable, so ALooper_pollOnce() keeps returning LOOPER_ID_USER and
android_input_poll() spins at full CPU. The pause and stop
acknowledgements wait for the next runloop iteration, which never
comes: RetroArch logs "App thread did not acknowledge activity state",
the launcher shows late and the app hangs until it gets focus back.
A swipe home hits it often, since focus is lost before onPause.
Always drain the queue and apply the events only while a sensor is on.
* gl2: make a regrown pass texture as the pass's first one
gl2_recreate_fbo() gave the larger texture no filter, so it kept GL's
default GL_NEAREST_MIPMAP_LINEAR with a single level. On GLES that
texture is incomplete, and once a viewport-scaled pass grew, the next
pass sampled black; desktop GL with texture storage gets a complete
one-level texture. Make it with gl2_create_fbo_texture(), as at init, so
it also keeps the pass's filter, wrap mode and float or sRGB format. The
feedback texture is regrown the same way.
* video: per-screen window settings and the screens' window plan
Each screen gets window settings in the config,
video_screenN_window_mode, _x, _y, _width, _height, _monitor and
_fullscreen: Attached, Separate or Hidden, and where a window of its own
goes and how big it is. Screen 1 is always Attached; the others default
to Separate. video_windows_enable, off by default, is the switch that
lets screens leave the main window at all.
video_windows_plan() turns those settings into a frame's plan: the
screens the main window draws, the ones that go to windows of their own
and the hidden ones. A screen stays in the main window while the switch
is off, where the driver has no windows, or once the renderer has sent
it back. The views layout takes exclude_screens, so the main window lays
out only the screens it keeps, and a window only its own.
This is the base the desktop secondary windows and the Android second
display share. The video_windows harness, run in the Linux gfx samples
workflow, checks the plan and a layout with screens left out.
* video: contract for secondary screens' native windows
A context can offer windows of their own for secondary core screens
through an optional gfx_ctx_window_driver_t, the last member of
gfx_ctx_driver_t: create, update, poll and destroy, and bind and
present for GL contexts. Requests, native handles and events carry a
generation from video_driver_window_generation(), a frontend counter
that a driver or context restart does not reset, so an event that
outlives its window cannot be taken for its replacement's.
GFX_CTX_FLAGS_VIDEO_WINDOWS is what a video driver will report once it
draws to such windows; nothing sets it yet.
* egl: window surfaces for secondary screens
egl_window_surface_new/bind/swap/free give a secondary screen's window
a surface on the main context's display and config, with the main
window's attributes. Bind makes the context current on it at swap
interval 0, or on the main surface again; free puts the main surface
back first where the freed one is current. None of them log.
* video: share the secondary windows' event bookkeeping
What a native layer keeps of each secondary window for the frontend -
its owner, record, request, position, the events waiting one bit per
kind, and whether it closed - is a video_window_common_t at the start
of its own state, and the rules on it live once in gfx/video_windows.c:
marking a window closed (CLOSE, with FOCUS_LOSS where it had the focus,
a waiting gain or resume dropped), poll's drain in its fixed order with
whatever has no room left waiting, and the sweep of an owner's windows
at context teardown.
* video: one placement clamp for secondary windows
video_window_place_rect() puts saved bounds on a monitor or its work
area: bounds partly on it are moved onto it, automatic ones and those
not on it at all are centred, and the size is clamped. Whether bounds
are on it is judged as saved, before the size is clamped, so an
oversized window partly on it keeps its position on the other axis.
* video: frame snapshot for secondary windows
A frame presented with views now carries what a driver needs to make,
place and lay out the screens' own windows without reading settings:
each screen's window settings, the window plan, the core's own map and
frame size, the layout parameters and a restore count, from which
video_driver_window_layout() lays out one screen's window. The snapshot
lives in video_driver_state_t and video_frame_info_t points at it, NULL
while windows are off or the driver cannot make them; the threaded
wrapper copies it into the frame's slot, as it does the statistics text.
While the driver can make windows, the main window's layout leaves out
the screens that have one of their own or are hidden.
video_driver_restore_windows() clears the screens a close attached and
counts the request, and window generations can be taken on any thread.
* video: published layouts and translate for secondary windows
A renderer publishes each secondary window's layout as drawn, with the
core map it was made from and the window's client size, through
video_driver_publish_window_layout() from the thread that runs the
context. Latest wins with no lock: each window has three slots handed
over by index exchange, as the window title is, and NULL clears it.
video_driver_translate_window_point() maps a point in a window to the
core's frame: window 0 through the viewport, as before, and a secondary
through its published layout, scaled from client to drawn pixels. A
point in a window that has no layout, was cleared or has another
generation is not mapped.
* input: window-aware pointer and touch publication
input_driver_publish_window_pointers() and _touches() take each device's
and each touch's window: 0 for the main window, else a screen's own with
its generation. A device in a screen's window is placed through that
window's layout for the pointer and the lightgun, and has no place on
the main window's screen; one whose window is gone reads off-screen.
Relative motion, buttons and the ports' devices are as they were.
input_driver_publish_pointers() and _touches() publish into the main
window, so the input drivers that call them need no change.
* samples: video_screens harness for the screens' own windows
The shared windows base is tested against the shipping configuration,
video and input objects: per-screen window settings across saves and
overrides, a screen's own layout, the frame snapshot and its copy
under the threaded wrapper, published layouts and point translation,
window-aware pointers and touches, and window generations. build.py
links the test with a configured non-Qt build's objects; the OpenXR
desktop jobs, which make one, run it.
* video: the window plan can keep a screen other than 0 attached
video_windows_plan() takes the screen that stays in the main window
whatever its mode, and screen 0 takes that screen's mode. Callers pass
0, which plans as before. Android's external monitor rule needs it:
screen 0 goes to the monitor and screen 1 stays on the device, where
the touch screen is.
* video: route the separate screens to a platform's displays
video_windows_route() chooses the display a platform's Separate
screens go to, from a list the platform publishes. A screen's monitor
setting N names the display of ordinal N; 0 is Auto, which takes an
on, valid and physical display that is neither private nor the main
window's: an external one (DIRECT or TRANSITIVE) first, then the
lowest ordinal. On an external monitor Auto puts screen 0 there and
keeps screen 1, so the touch screen stays on the device. One display
takes screens at a time; a screen bound for another stays attached.
Each display also carries its size, for the menu's display picker.
* samples: a touch through a second output's layout
A touch on a second display's surface, mapped through the layout drawn
there, lands in the touched screen's part of the packed frame: one
screen on a 1240x1080 panel, two screens sharing it, and screen 0 on a
monitor; the letterbox reads off-screen when asked.
* samples: pin the attached screen, picker and pillar cases
The plan keeps a screen other than 1 attached with screen 0 in its
mode, and falls back to Attached with no settings. The picker refuses a
private display but takes one that is off, and Auto never takes an
entry without an ordinal. A touch in a pillar beside two screens, not
reported off-screen, is held to the nearer one.
* video: route the screens' windows through a platform's display list
A platform publishes its displays from its UI thread, latest wins,
through three slots as the window layouts are handed over. Each frame
takes the newest list, routes the Separate screens with
video_windows_route() and plans with the screen it keeps attached; a
screen with nowhere to go stays in the main window. All screens bound
for one display share one window, led by the lowest one, and the frame
says which screens each window shows. Taking a list restores the screens
a failed window sent back, and video_driver_attach_windows() lets a
renderer send them back from any thread. A request names its display,
and Android gets a native window kind.
A screenshot or GPU recording through the threaded wrapper draws the
cached frame again on the video thread. That redraw takes no list: it
keeps the app thread's last route, as it reads the forced and restore
state, so a renderer keeps the second display's window and the capture
shows the right screens. The route is written only when it changes, so
Win32, which routes nothing and whose modal redraw runs beside the app
thread, never writes it while it is read.
The video_screens harness redraws the cached frame through the real
threaded wrapper and checks that it keeps the frame's route and plan.
* video: let a platform take the secondary windows back
video_driver_windows_retire() has the renderer let go of every
secondary window, through a new optional poke hook. It is for a
platform command such as Android's second surface going away, never a
frame. With the threaded wrapper up it is queued to the video thread
behind the frame being drawn, and nothing waits for it: a hook the
caller passes runs there just before and just after, for the platform
to hold its own requests back and to hear when it is done. Without the
wrapper all of it runs before the call returns. One is queued at a
time; false says the video thread cannot take it yet.
video_screens checks that a retire queued behind a frame being drawn
returns at once, and runs after the frame, between the hook's calls.
* video: one slot hand-over for the window layouts and displays
The window layouts and the display list are handed over the same way,
through three slots. Two small helpers publish and take a slot for both,
with the same memory orders. No behaviour change.
The harness adds two display list checks: a longer list keeps its first
VIDEO_WINDOW_DISPLAYS_MAX, and a get of capacity 1 fills only the first
entry.
* android: native side of the second display
The Java controller hands native code the display list and the second
display's surface through three natives. The list goes to
video_driver_publish_window_displays(). A surface becomes a node holding
one ANativeWindow reference, exchanged in for the video thread to take,
with a generation the touches carry. A size change of the same window
keeps the generation; a different window first gives up the old one.
Giving one up uses the main window's ticket handoff: the UI thread waits
while the app thread drops the node and queues the renderer's letting go
of its windows. The thread that lets go of them acknowledges once it is
done, so the UI thread is not left waiting for the app thread's next
poll; a retire the video thread cannot take yet is tried again from the
input poll. Native code asks Java to show or hide the display through
setSecondDisplay(), which posts and never waits, and asks nothing while
the renderer is letting go of a surface. The app state gets a 64-record
ring for the display's touches.
The natives run on the UI thread and read its own app state,
g_android_early, which android_app_free() clears unless a re-created
activity has already replaced it, so a callback after onDestroy finds
none. A display name GetStringUTFChars cannot read leaves no exception
pending for the next JNI call.
* android: second display windows for the gl and vulkan contexts
Both Android contexts give the renderer the secondary-window table.
Creating a window asks Java to show the display it is routed to and
returns unconfigured. Until Java publishes its first display list a
Separate screen resolves to display 0, which names no display, so its
window is refused and the renderer keeps the screen attached until a
list arrives. An update takes only the request's settings; another
screen or request generation is a new window, the renderer's to make.
Its poll hands it the newest surface native code received, raising
GEOMETRY and publishing which window and surface the input poll maps
touches through. The EGL context makes the window's surface on the main
context the first time it is bound after a surface arrives, at swap
interval 0, with the native visual id queried once at init, since the
query logs on failure and binding sits on the present path; the Vulkan
context gives the renderer the ANativeWindow and leaves the surface to
it.
Each request native code sends Java carries a number, and each surface
comes back with the number of the request it was made for. Destroying
the window drops the surface it held, then asks Java to hide the
display. When it was the last window, that hide gives up every surface
made for an earlier request, including one that reaches native code
after it: no window takes one, and its surfaceDestroyed frees what is
left and returns without the ticket handoff. A hide native code starts,
for closing or switching content or reinitialising the video driver,
never holds the UI thread.
* android: touches on the second display reach the core
Each touch on the second display crosses from the UI thread in the ring
with the generation of the surface it was on. nativeTouch sits with the
other second display natives and reads the UI thread's own app state,
which android_app_free() clears. A down or a move goes in only when it
leaves room for an up of every finger the input driver tracks, and an up
only when its down went in, so a full ring never drops a lift and leaves
a finger pressed for the core. MAX_TOUCH moves to platform_unix.h for
the native and the input driver to share.
The input poll drops the touches of any surface but the one the renderer
shows, maps the rest through that window's published layout into the
core's frame, and keeps the fingers after the main display's in the
core's pointer list. They never move the mouse, count as a quick tap or
reach the frontend's own screen pointer, so the menu and overlay stay on
the main display.
* input: the second display's fingers on a device of their own
With an overlay's pointer on, or one of its buttons held, the frontend
answers RETRO_DEVICE_POINTER from the overlay or not at all, and a
windowed overlay polls that device as its own touches. So the second
display's fingers cannot share it: the Android driver answers them on a
frontend-only RARCH_DEVICE_POINTER_SECOND and keeps RETRO_DEVICE_POINTER
to the main display. The frontend lists them for the core after the main
list's pointers, whoever answers for those: the overlay, none while the
pointer is blocked, or the driver. A driver with no second list answers
with its main list alone.
The pointer_second harness checks those answers against a stand-in
driver with both lists, through input_state_device() and the overlay's
pointer answer extracted from input_driver.c.
* android: a Presentation for the second display
SecondDisplayController lists the displays for native code - whether
each is the Activity's own, valid, on, private, a real panel or monitor
(product info, API 31+), its connection, name and size - and shows a
Presentation with a SurfaceView on the display native code asks for. The
window is not focusable and not touch modal and the view is not
focusable, so touching it neither pauses the core nor takes the gamepad;
it keeps the screen on and, on API 29+, keeps system gestures off it. It
follows the Activity from onStart to onStop, holding a request made
while stopped, and a frame after a display or configuration change
publishes the list again when it changed. A display it cannot show on
stays invalid until the list changes, so the display events a
Presentation coming or going may fire do not retry the failing show in a
loop. Each Presentation carries the number of the show request it was
made for and hands its surfaces to native code with it; touches go with
the surface's generation.
* android: second display failures and Presentations Android dismisses
Every display a show failed on stays invalid until the list changes or
the Activity starts again. A single failed id would not do: of two
displays that both refuse a Presentation, marking one failed makes the
other valid again, native code routes back to it, and the two take turns
failing forever. Starting again retries a one-off failure when the app
returns.
Android cancels a Presentation itself when its display's metrics change
(API 17-29). A dismiss we did not make clears it, so the dead
Presentation does not leave its display counted as shown. While native
code still wants that display, it is shown on again if the dismissed
Presentation's view had a surface. One cancelled before that cancels
itself, for example on stale display metrics, and rebuilding it would
loop at message rate; it counts as a failed show, so its display is
published invalid until the list changes or the Activity starts again.
* video: which screen windows a renderer makes and lets go each frame
video_windows_steps() tells a renderer, from one frame's snapshot,
which of its windows to let go of (no screens now, or another
display) and which to make. A window that closed or failed is not
made again until the restore count moves, so frames already queued
do not bring it straight back. Renderers share the rule instead of
each keeping its own.
* gl2: views draw into a given output; the preset's targets can grow
gl2_views_render() takes the layout, size and canvas it draws with
instead of reading the main window's, and the loop that grows the
preset's targets on a resize becomes a function of its own. Nothing
changes for the main window; a screen's own window will draw through
both.
* gl2: draw the screens' own windows
With a context that can make windows of their own for screens, gl2
reports GFX_CTX_FLAGS_VIDEO_WINDOWS while it may draw views. Each frame
it makes and lets go of the windows the frame's snapshot asks for and
draws each one's screens through the views compositor, with the preset's
passes where one is loaded. A window's pass targets grow only once its
surface is bound, so a failed bind has nothing to undo. A window is
drawn after the main window's frame and swapped at interval 0 before the
main swap, which stays the only one that can wait. The menu, OSD,
widgets and overlay stay in the main window.
A window that cannot be made or drawn hands its screens back to the main
window until the next restore and logs once. A window its context closes
hands them back too, and a restore that lands in the same frame does not
make it again; one closed with no screens left is not marked failed, so
it can be made again when its screens come back before the next restore.
The poke's windows_retire lets go of every window at once, for a
platform that takes a surface back.
The gl2_pbo_readback and gl_last_pass_fbo samples include gl2.c; neither
draws windows, so their shared stubs answer the frontend's window calls
with no-ops.
* samples: views test core logs a second finger, and asks for GLES 3
With a finger on each of two displays the second display's finger is
pointer 1. The core reads, maps and logs pointers 0 and 1 through one
helper, each with its own last state; pointer 0's lines and crosshair
are unchanged. Android's gl driver only gives GLES contexts, so a gles3
value of video_views_test_hw lets the core render through hardware there
too. gles3 with the checker or noise pattern logs an error at load:
those patterns upload a BGRA texture, which GLES 3.0 does not take.
* vulkan: the window-system surface switch as a helper
vulkan_surface_create() made the VkSurfaceKHR for each window system
in line. The switch moves into vulkan_wsi_surface_create(), which
takes the instance and returns the surface, so a second output on the
same device can make its own surface the same way. VULKAN_WSI_DISPLAY
stays where it was, since it needs the context's GPU. No behaviour
change.
* vulkan: a second output on the context's device
A vulkan_output_t is a surface of its own with a swapchain on the
context's device and queue, for a screen shown on another display. It
never waits in a frame. The acquire takes no time and uses a fence,
never a semaphore, so nothing the second display's presentation engine
signals ever enters the queue the main output's frames share. The fence
is polled, and an image not yet free is kept for the next frame. Out of
date remakes the swapchain at once; suboptimal remakes it once and then
keeps it, as the main chain does. On Android the swapchain takes the
size the window reports, since the surface's currentExtent can lag an
in-place resize and Android scales any extent to the window. A lost
surface is dropped. A swapchain let go of is destroyed once a fence
queued behind its last present has signalled. Only teardown waits, on
the output's own fences.
The harness runs the real code against a fake device and checks that no
frame-path call waits, that only completed objects are destroyed, and
that everything made is freed.
* vulkan: draw screens in windows of their own
Where the context has a windows table (Android's second display), a
screen the plan sends to a window of its own is drawn there with its
views' chains, sized for the window, and the frame's own view copies.
The window is drawn in the frame's command buffer, after the main pass
and before the chains end their frame. Its image comes from a fence
already signalled, so the frame's submission waits on nothing new; it
signals the window's semaphore, and the window presents after the
submission and before the main present, which stays the only one that
waits. The menu, OSD, widgets and overlay stay in the main window.
A window that can't be made, drawn or kept puts its screens back in
the main window until the next restore. One whose output is not done
yet is let go of on a later frame; the poke's windows_retire and the
driver's teardown wait for it, on the output's own fences.
* video: separate screen windows on by default on Android
On Android a Separate screen goes to a second display, which is what a
device with two panels is for, so the switch starts on there. Desktop
windows stay opt-in. The settings table records the Android default;
the harness checks that an override carries the switch and a screen's
mode.
* menu: a window mode and a display for each screen from 2 on
Each screen past the first gets two settings rows: Attached, Separate or
Hidden, and the display it goes to when it is Separate. The display
picker offers Auto and the displays the platform has published, shown as
the monitor index is ("2 (Screen-2 1240x1080)"), and keeps a display set
elsewhere until it is changed. It widens only up to the most displays
that can be published, so a hand-edited value in the thousands cannot
build a list that long on the main thread. The row's sublabel says that
the display RetroArch is on keeps the screen attached. Each screen's
rows have their own enum, as the per-port input rows do, so the dropdown
and the sublabel find the right one. A change to any of the rows gives a
screen the renderer sent back to the main window another try.
The settings harness checks the rows, the left key's clamp, and that a
change to any of them restores closed windows.
* menu: show the screens' window rows where the driver has windows
Stereo 3D & Screens shows Separate Screen Windows when the video
driver reports secondary windows. While it is on, it also shows the
mode and display of screen 2 and of each further screen the core has.
On Android the switch reads "Show secondary screens on another
display". A screen row's dropdown takes that row's label as its
title.
* android: show the second display again after its metrics change
On Android 10, a density or size change on the second display left it
empty until the app restarted. Android cancels a Presentation when its
display's metrics change, and the one made to replace it got the
display's resources from a cache keyed by display id, still holding the
old metrics. Presentation.onStart() found them stale and cancelled it
before it drew, so the display was marked failed and both screens stayed
on the main display.
Bring the new Presentation's resources up to the display's current
metrics before showing it. The refresh runs only before Android 12; from
then on a Presentation has a window context of its own.
* android: read input queue keys and sticks through their fields
The key and stick helpers of the input queue take the few fields
they read instead of the event, and the default loop's slot lookup
and key path become functions of their own. Nothing changes for the
queue; the second display's window can then hand its keys and stick
moves to the same code.
* android: a focus rule for the Activity and the second display's window
Once the second display's window can take focus, RetroArch's focus
comes from two windows. Where each display has its own focus, the
second window keeps its display's focus while the keys go elsewhere,
so it counts only while in use: after a key, stick move or touch from
it, a focus it gained while the Activity had none, or a hand-off of
the one focus from the Activity. Any other change of the Activity's
focus ends that, so a notification shade still pauses as before.
The rule is a header without NDK types; a host test replays the
sequences the AYN Thor's focus modes and a one-focus system produce.
* android: keys and sticks from the second display's window
Keys and joystick moves the second display's window receives cross
from the UI thread in a ring of their fields; the input poll handles
them with the input queue's own code, so mapping, device ids, axes,
hats and hotplug behave the same. The window's focus comes in as two
commands, and the focus of both windows is acted on once per poll by
the focus rule, only when it changes.
A paused app thread sleeps in its looper, so writing to either of the
second display's rings wakes it, and the poll reads both rings after
the looper so the woken poll acts on what woke it. The app thread
keeps a reference on its looper for those wakes until the activity is
freed.
* android: the second display's window takes focus and passes keys on
The second display's Presentation can take focus, so a tap on it or a
focus mode that locks the gamepad to its display (the AYN Thor's Bottom)
gives it the pad. Its keys and joystick moves go to native input as the
Activity's do. Each key gets native code's answer, so Android makes no
fallback key (BUTTON_B as BACK, BUTTON_MODE as HOME) of a key RetroArch
uses. It is not cancelable, so BACK stays with native code, and it never
becomes the soft keyboard's target. The IME refuses the Activity's text
field while the second display's window holds the focus, so the Activity
asks for the soft keyboard again when it regains focus.
When RetroArch dismisses the Presentation while it holds the focus, it
first brings its own task to the front, which takes REORDER_TASKS
(granted at install). Android keeps one focus for all displays, so it
would otherwise pass to that display's launcher and leave RetroArch
without focus until the next tap on the main display.
* android: hand the second display's surface back without waiting
surfaceDestroyed and a window change on the second display return at
once. The renderer's own ANativeWindow references keep the window
alive; a frame still drawing into it gets an error from the abandoned
queue, and the next frame's poll finds the surface gone, drops it and
lets the EGL surface or Vulkan output go, the output on later frames
while the presentation engine still holds an image. Nothing waits on
the video thread or the GPU, so the UI thread can't stall into an ANR
behind a slow frame, and the window keeps its display for the next
surface. The going surface also gives the windows another try, so a
failure it caused is not held against the next.
vulkan_output_finish() is the driver's teardown only. An acquire it
gave up on keeps its fence, which is never destroyed while it may still
be signalled.
* video: build the screens' own windows only where a platform has them
HAVE_VIDEO_WINDOWS gates the secondary windows: their state in the
video driver and the threaded wrapper's slots, the drivers' window code
and its per-frame calls, the second output and EGL window surfaces,
the input layer's second pointer list and window places, and the
per-screen settings with their menu rows and config keys. Android
defines it; elsewhere ./configure --enable-video_windows does, and the
CI job that runs video_screens_test builds that way. A build without it
compiles none of this and carries none of its state, which is about
15 KB of the video driver's state alone.
* video: a window failure counts only for the restore it was drawn under
A renderer reports a window it could not make or keep with the restore
count of the frame it was drawing. Failures travel in one word, the
screens beside that count, and the main thread takes them only when
the count is still its own. Under threaded video a frame laid out
before a display or surface change can fail after that change; its
failure no longer keeps the screen on the main display until some
later event.
* android: the jelly-bean package may reorder tasks too
It builds the same second display controller, which brings RetroArch's
task back to the front when it dismisses the second display's window on
a one-focus system; without REORDER_TASKS that call throws and the focus
stays on that display's launcher.
---------
Co-authored-by: libretroadmin <[email protected]>
|
||
|
|
d6a23c320a |
video: simulated input resolution for slang shaders (#19675)
Shader settings gain Simulated Input Resolution with a width and height, off by default. While it is on, a slang preset's first pass is told its source has that size, so resolution-sensitive shaders such as CRT and edge-smoothing ones treat an upscaled frame as the small image they were written for. Later passes keep their real SourceSize. The size is recorded in the preset when it is loaded and every slang backend reads it from there: glcore, Vulkan, D3D10/11/12, Metal and gx2. Changing a setting reapplies the preset. The rows appear in the shader quick menu only when the video driver takes slang. slang_hlsl_backend checks that the size reaches the first pass alone and survives the copy the D3D drivers make of a pass's semantics, and runs in the gfx samples workflow. Co-authored-by: libretroadmin <[email protected]> Co-authored-by: hunterk <[email protected]> |
||
|
|
7a3bcbdc28 |
media: route image and movie activation to the internal viewer
Open supported external media in the fullscreen menu viewer and keep image confirmation there across all four menu drivers. Disable the legacy imageviewer core in normal build configurations while preserving its sources and Griffin guard. |
||
|
|
650cf882db |
Add shared Media Player settings below File Browser
Expose fullscreen seek interval and controls auto-hide preferences through shared menu navigation. Preserve the existing five-second seek and three-second hide defaults, keep zero-delay controls visible, and publish the configured seek interval for matching button captions. Exercise actual navigation, editing, persistence and kiosk visibility in all four menu drivers. |
||
|
|
9033b5ef9d |
configuration: keep the generated setting rows in tables
The bool, float, uint and int rows the settings/ def files generate were each added to their list by an inline block of code. They are now static tables of key, settings_t offset and default, copied into the same lists, in the same place, by one loop per kind. With the menu a key is stored as its label's offset in the packed label blob, so the tables carry no pointers to relocate. microphone_block_frames had a configuration row on every platform but its label only on mobile; it is registered by hand off mobile. The capacity check and settings_check.py count the table rows, and the harnesses that include configuration.c stub RARCH_ERR, which the copy loop's full-list report now reaches. |
||
|
|
efe0797f15 |
menu: store descriptor handlers as indices
A settings descriptor row named its handlers through seven pointer fields, almost all of them NULL. Each row now carries a one-byte index per handler into a shared table, generated together with its SDX_* index names from menu/menu_setting_handlers.h; a handler a row names but the list lacks fails to compile, and each entry is checked against its slot's type. The label ids and flags are stored at their real 16-bit widths. A row shrinks from 128 to 72 bytes on 64-bit targets and from 88 to 60 on 32-bit ones. A row's handlers are now set as one actions tuple interned once, rather than one interning lookup per handler. The settings built from the rows are unchanged. |
||
|
|
628ea4dcf7 |
android: the input block timeout keeps presses back instead of waiting
The poll waited up to the input block timeout for an event, and again after each one, so that a press a pad sends as several events a few milliseconds apart landed in one poll. That stalled every frame by the timeout, pressed or not, on the main thread. The poll no longer waits in the foreground. Instead a pad's presses in a poll are shown at its end unless the newest of them came within the timeout of it, by Android's own event times: then they wait for the next poll, and the rest of the press, coming before that, is shown with them. Nothing waits more than one poll, an older press is shown at once, and a press let go before it was shown is shown for one poll. At 0, the default, nothing is kept back and it costs nothing. The keeping back is android_press_group.h, which samples/input/android_block_timeout holds to all of that. |
||
|
|
fd0b29f740 |
settings: keep Driver Pacing help within C90 string limits
Preserve the backend, clock, conflict and pacing guidance in 460 characters. The 633-character help added by the Display Pacing integration exceeds the 509 characters ISO C90 requires compilers to support, failing the actual Griffin stand-in compile with -Werror=overlength-strings. |
||
|
|
f896928838 |
video_thread: Display Pacing keeps the vblank under Driver Pacing
With Threaded Video Display Pacing and Driver Pacing both in effect, the hold stood aside for every frame the driver released. The driver's minimum interval keeps the content's rate but not where the frame falls against the display's refresh, so with vsync off nothing placed the present any more: its phase was whatever the last hitch left - at start-up, the content load and a state load - and the tear stayed on screen. Toggling Display Pacing let the hold place frames again for a moment (the menu, the Driver Pacing re-negotiation) and the driver kept that phase, which is why the tearing went away after the toggle. Where the presenter has the display's own vblank (present timing from the display, DWM's vblank on Windows), the hold now still places a released frame on it; the driver's sleep after it, a period from the last release, has nothing left to wait, so the frame still sleeps once. Without a display vblank the hold stands aside as before. samples/gfx/threaded_video: the driver pacing lane gives the presenter a vblank grid and a release that never sleeps, adds a 30 ms hitch, and requires the released frames to keep the content's rate and one phase on the grid, at start-up and after Display Pacing is turned off and on, on the same phase both times. It fails on the old wrapper (30 frames in 6 ms, 5 of 30 on one phase). |
||
|
|
80398df3b1 |
runloop: Driver Pacing alone keeps the content's rate
With Driver Pacing in effect and nothing else holding the loop - vsync and audio sync off, no rate control, Threaded Video Display Pacing off - the minimum interval handed to the driver was 0, and the driver's release, which never sleeps for a rate it was not given, let the core run unthrottled. The interval is now the content's period there too, as it already was under Display Pacing; the timer's period still goes where the timer would hold, and nothing where vsync, audio or a scanline already hold the loop. Fast-forward never reaches the driver's release. The choice moves into runloop.h as runloop_pace_driver_interval(), and samples/runloop/pacing checks it against the whole pace decision (the "driver alone" row fails on the old expression). |