Wiki: drop stale 'Last updated for PadForge 3.2.0' footers (22 pages) Every page on the wiki carried a '*Last updated for PadForge X.Y.Z.*' italicized footer hard-coded to 3.2.0. With 3.3.0 shipped, those footers become a lie on every page that wasn't actually re-audited for the new version — bumping them to 3.3.0 wholesale would just swap one lie for another since most pages haven't been touched since 3.2.0. Removing the footer entirely: git history of each page is the honest source of truth for currency. Wiki contributors who need to know whether a section reflects the latest behavior can read the page's commit log; no in-page label needed.

hifihedgehog committed May 25, 2026

Polish: drop stale v2.2.1 version markers, banned 'Essential' wording, image-caption em-dashes

hifihedgehog committed May 21, 2026

Wiki dev pages: fix 3 more stale 2-variant references 2D-Overlay-System.md: 'How All Views Relate' step 5 said EnsureModel maps PlayStation->DS4 and everything else->XBOX360. Now reflects the actual 5-way HMaestroProfileCatalog.ResolveAssetFolders dispatch. XAML-Views.md: Controller Tab Type Icon DataTrigger value was listed as 'Microsoft', actual value is 'Xbox'. Also clarified that the icon resource keys cover the whole family, not just DS4/360. Input-Precision.md: PlayStation slot header was 'DS4 protocol' only; broadened to 'DS4 / DualSense protocol' since DualSense profiles also emit 8-bit sticks and triggers.

hifihedgehog committed May 21, 2026

Input-Precision: math fix — 16-bit (65536) vs 15-bit (32768) is 2x the resolution, not 16x

hifihedgehog committed May 21, 2026

Pass 10/25: refreshed screenshots for 3.2 + image refs on every user-facing page Screenshots - Recaptured all 21 PNGs in images/ against a 6-slot setup (Xbox + Xbox + PlayStation + Extended + KBM + MIDI) so every controller-type screenshot reflects the live 3.2 UI. - New pad-gyro.png covers the dedicated Gyro tab (Calibration, Sensitivity, Response Shaping, Engage, Easy Aim cards). - pad-adaptive-triggers and pad-lighting captured on slot 1 where a DualSense source makes those tabs visible. The old captures were the Controller 3D view instead of the actual tab content -- the Tab(...) Click was being called before the tab strip had switched, and on PS slot 3 the AT/Lighting tabs are hidden when a DS4 (not DualSense) is the source. capture.ps1 + convert-screenshots.ps1 - capture.ps1 now self-elevates. PadForge runs requireAdministrator; a non-elevated UIA reader returns zero descendants (UIPI), which silently made every Nav/Tab call fall through to a no-op. - Dropdown captures target by AutomationId (DeadZoneShapeCombo, SensitivityXCombo, TriggerPresetCombo) instead of iterating every ComboBox looking for an item by name -- the old approach kept expanding the HMaestroProfileCombo and assigned-device combo by accident. - Tab() ScrollIntoView before Click for wrapped tab strips. - Capture for Gyro / Adaptive Triggers / Lighting on slot 1, gated on each tab being visible (Tab returns false if collapsed, the Cap call is skipped instead of capturing whatever's stale on screen). - convert-screenshots.ps1: added pad-gyro / pad-impulse-triggers / pad-shift-layers to the name map. Image refs on pages that previously had none - Gyro.md: pad-gyro.png - Installation.md: add-controller-popup.png (first thing you reach after install) - DSU-Motion-Server.md: dashboard.png (the Motion Server card lives there) - Troubleshooting.md: settings.png (where most troubleshooting starts) - Input-Precision.md: pad-sticks.png (where the precision pipeline ends up visible) - Shift-Layers.md: pad-mappings.png (shift layers live in the mappings tab strip) - Impulse-Triggers.md: pad-forcefeedback.png as a stand-in (Impulse Triggers tab is only visible when an Xbox One+ pad is assigned, which the dev environment doesn't have; the Force Feedback tab shares the same layout pattern).

hifihedgehog committed May 20, 2026

Pass 2/25: italic hook consistency, Related pages normalization, em-dash sweep - Italicized hook line on 12 user-facing pages that had plain hooks (Stick-Deadzones, Trigger-Deadzones, Force-Feedback, Adaptive-Triggers, Lighting, Devices, DSU-Motion-Server, Web-Controller, Settings, Driver-Management, Input-Precision, 3D-and-2D-Visualization) and Troubleshooting. - Normalized Related-pages bullet formatting across 16 user-facing pages to one convention: '- [[Page]]: lowercase description.' - Home.md: cut filler 'long list of smaller wins' from the 3.2 intro paragraph; replaced em-dash pseudo-colon with a period; converted em-dash pseudo-colon in Gyro motion bindings bullet. - Controller-Slots.md: Open-a-slot tab list now reflects 3.2 reality (Gyro tab, Adaptive Triggers and Lighting on PS slots, Impulse Triggers on Xbox + PS). Related pages expanded to link the new pages. - Devices.md and Impulse-Triggers.md: em-dash pseudo-colons converted to periods.

hifihedgehog committed May 20, 2026

Wiki rewrite: simple-English voice across all user-facing pages Rewrites 18 user-facing pages and adds hooks to 7 dev-deep-dive pages. Each user-facing page now opens with H1 then a one-sentence hook, strips banned vocabulary, replaces em-dash pseudo-colons with periods, and ends with a version marker. User-facing rewrites - Installation, Dashboard, Controller-Slots, Button-and-Axis-Mappings - Stick-Deadzones, Trigger-Deadzones, Force-Feedback, Adaptive-Triggers, Lighting - Macros, Profiles, Devices, DSU-Motion-Server, Web-Controller - Settings, Driver-Management, Input-Precision, Troubleshooting - 3D-and-2D-Visualization New 3.2 content woven into Force-Feedback (Impulse Triggers, Audio Bass Trigger Rumble, Constant Trigger Force) using actual in-app labels from Strings.resx. Profiles documents the new Toggle Virtual Controllers Disabled shortcut mode. Settings notes the stable-across-language-switch fix. DSU Motion Server covers the Gyro Aim Engage picker subtitle. Dev-deep-dive hooks added - Input-Pipeline, Settings-and-Serialization, ViewModels, XAML-Views, Engine-Library

hifihedgehog committed May 20, 2026

Lighting tab reset buttons + v3 terminology sweep Refreshes pad-lighting screenshot to capture the four new reset buttons (Lightbar Mode, LED Brightness, Player Pattern, Mute LED Mode) plus the rest of the slot-0 PadPage tabs and slot-type config bars against the post-deploy build. Wiki prose: drops residual v2 phrasing (ExtendedConfig.IsGamepadPreset, DualShock4 / Xbox 360 enum names, "Microsoft" / "Sony") and routes through the v3 OutputType / VirtualControllerType vocabulary instead.

hifihedgehog committed May 4, 2026

Deep v3 resync: vJoy purge, Microsoft→Xbox terminology, current features Sweep residual v2 vJoy / ViGEmBus content out of user-facing pages and replace stale dev-page class names with the v3 unified HIDMaestro pipeline. Restore correct family-name terminology (Xbox / PlayStation / Extended, not Microsoft / Sony — those enum identifiers exist purely for v2 PadForge.xml back-compat per the in-source enum comment). User-facing pages (Home, Dashboard, Controller-Slots, Devices, Settings, Driver-Management, Troubleshooting, Force-Feedback, Web-Controller, 3D-and-2D-Visualization, 2D-Overlay-System, Installation, Stick-Deadzones, Trigger-Deadzones, Input-Precision): - vJoy slot type, "vJoy driver limit", and vJoy install steps removed - Troubleshooting: "vJoy Phantom Controllers" section deleted (v2 N²-bug, doesn't exist in HIDMaestro), other vJoy sections rewritten for HM - Force-Feedback: HID PID 1.0 framing for Extended; new Sony Report 0x01 rumble passthrough section - 3D-and-2D-Visualization: PlayStation touchpad preview (live finger spheres) and click-to-map TouchpadClick documented - 2D-Overlay-System: touchpad highlight visual spec (sampled colors) - Web-Controller: DS4 layout button-11 collapse for TouchpadClick Dev pages (Architecture-Overview, Engine-Library, Build-and-Publish, HIDMaestro-Deep-Dive, Input-Pipeline, SDL3-Integration, Services-Layer, Settings-and-Serialization, Driver-Installation-Internals, ViewModels, XAML-Views, Virtual-Controllers, Button-and-Axis-Mappings): - Stale Xbox360VirtualController / DS4VirtualController / ExtendedVirtualController / VJoyRawState references replaced with the v3 unified HMaestroVirtualController + ExtendedRawState - Step 5 prose updated to HMContext.SubmitState / SubmitRawReport with Sony Report 0x01 passthrough - HIDMaestro-Deep-Dive: HM 1.1.x → 1.2.0 - Services-Layer: false claim that Extended slots reset to "Microsoft (Xbox 360) gamepad preset" replaced with the actual behavior (ProfileId = GetDefaultProfileId(type), Custom "PadForge Game Controller" for Extended) - Three broken [[vJoy Deep Dive]] links retargeted to [[HIDMaestro Deep Dive]] - Virtual-Controllers gets a top-of-page editor's note flagging it for a full hand-rewrite (the deep sections still describe deleted v2 classes) Microsoft references kept where they are real: NuGet package Microsoft.Windows.Devices.Midi2, registry paths under SOFTWARE\Microsoft\, ".NET runtime download from Microsoft", literal VirtualControllerType.Microsoft enum-value citations, MaxXbox360Slots constant name (preserved from v2), [XmlEnum("Sony")] attribute string, OpenXInput Microsoft-trademark disclaimer.

hifihedgehog committed Apr 27, 2026

Input-Precision: Extended triggers are now 16-bit PadForge's Extended profile builder now passes bits=16 to HIDMaestro's AddTrigger in both call sites (BuildCustomProfile + Step5 layout-override builder). 65536 trigger positions instead of 256. Page text updated to reflect this: trigger row in the Extended-slot table matches the stick row, and the summary table 'Trigger axis resolution' reads 65536. Constraint note clarified — HIDMaestro requires axis bit depths to be a multiple of 8, so the only valid alternative is 8-bit.

hifihedgehog committed Apr 26, 2026

Input-Precision: reframe around custom HIDMaestro controllers The page is most useful to users building custom controllers via Extended slots — flight sticks, HOTAS, racing wheels, peripherals with non-standard axis/button layouts. Lead with the standard data characteristics that HMProfileBuilder gives you (16-bit unsigned sticks, 8-bit triggers raisable to 16-bit, 128 buttons, 8-way continuous POV, etc.) and treat the Microsoft (Xbox 360) and PlayStation (DS4) virtual-controller types as protocol-constrained alternatives. Stage 5 reordered: Extended first, with the inline note that 16-bit sticks exceed every consumer ADC's effective resolution. Microsoft and PlayStation follow as 'here's what each protocol limits you to'. Summary table renamed and re-keyed to lead with the Extended numbers. Intro rewritten to set expectations: this is the data-characteristics reference for users building custom controllers, organized as the input value's journey from SDL through deadzone math to HIDMaestro.

hifihedgehog committed Apr 26, 2026

Fix mojibake throughout the wiki + rewrite Input-Precision Stage 5 for v3 Mojibake sweep: 1067 sequences across 17 .md files. Earlier passes had round-tripped UTF-8 punctuation through a CP1252 layer, baking the literal three-character mojibake into the files (em-dash → â + € + ", en-dash, right arrow, box-drawing chars, middle dot, multiplication sign, etc.). Restored to the proper Unicode codepoints: — – → ↔ ← │ ├ └ · ×. Input-Precision Stage 5 rewrite: the page still described 'Stage 5: vJoy Output (15-bit unsigned)' which doesn't exist in v3. v3 has a single HIDMaestro Output stage with three sub-cases: - Microsoft (Xbox 360): signed 16-bit sticks, 8-bit triggers - PlayStation (DS4): 8-bit sticks AND triggers (DS4 protocol) - Extended (HM custom HID): 16-bit unsigned sticks, 8-bit triggers by default, raisable to 16-bit per profile Verified against HIDMaestro's HidDescriptorBuilder.cs (AddStick default bits=16, AddTrigger default bits=8) and PadForge's HMaestroVirtualController.cs (SubmitGamepadState normalizes through float at the SDK boundary). Output Throughput section: dropped the vJoy single-IOCTL note, replaced with HIDMaestro single-call SubmitState description. Summary table axis-resolution rows now reflect per-VC-type wire bit depth. Stage 3 callout pointing at Stage 5. Pseudo-colon em-dash converted to period per the project style rule.

hifihedgehog committed Apr 26, 2026

Bulk v3 terminology sweep across remaining wiki pages (23 files) Mechanical s/// pass on the names that don't depend on architectural context: ViGEmBus -> HIDMaestro, ViGEmClient -> HIDMaestro SDK, VJoy -> Extended (the C# enum value name appearing in narrative text), 'DirectInput (vJoy)' -> 'Extended (HIDMaestro)', 'Xbox 360 / DualShock 4' (slot type pair) -> 'Microsoft / PlayStation', etc. Pages already hand-rewritten upstream were left alone (Home, Installation, Driver-Management, HIDMaestro-Deep-Dive). Virtual-Controllers got the same pass since it's a central reference. Caveat: many of the deeper architecture pages (Driver-Installation- Internals, Input-Pipeline, ViewModels, XAML-Views, Engine-Library, etc.) still describe v2-era *implementation* (vjoy.sys SetupAPI device-node creation, ViGEm.Client P/Invoke surface, etc.). The TERMINOLOGY now matches v3 but the IMPLEMENTATION DETAILS in those pages are still v2 and need a follow-up content pass to reflect the HIDMaestro SDK surface, the OpenXInput shim, the HM thread-pool lifecycle, the bubble-up cascade, etc. See HIDMaestro-Deep-Dive.md for the v3-correct version of that material.

hifihedgehog committed Apr 26, 2026

Sweep em-dash pseudo-colons across developer reference pages

hifihedgehog committed Apr 18, 2026

Standardize "dead zone" spelling to "deadzone" per Microsoft convention Rename Stick-Dead-Zones.md → Stick-Deadzones.md and Trigger-Dead-Zones.md → Trigger-Deadzones.md. Update all wiki content and internal links to use one-word "deadzone" spelling. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

hifihedgehog committed Apr 12, 2026

Replace -- with em dashes (—) in prose text across wiki pages Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

hifihedgehog committed Mar 15, 2026

Sync wiki with v2-dev: KBM, MIDI switcher, sensitivity curves, dead zones, screenshots - 23 wiki pages updated (+823 lines) covering KBM virtual controller, MIDI type switcher, sensitivity curves, dead zone shapes, 3-tier polling timer, auto-idle engine, HidHide whitelist - 21 screenshots retaken/added: all pages, all 4 slot types (Xbox360, KBM, vJoy, MIDI), MIDI piano keys, KBM keyboard+mouse preview, vJoy config bar + schematic - New screenshots: pad-kbm-preview, pad-midi-configbar, pad-vjoy-configbar, pad-vjoy-schematic, settings-hidhide - Strict content boundary enforcement: zero developer jargon in user guide pages Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

hifihedgehog committed Mar 13, 2026

Update wiki: trigger precision, uninstall guards, decimal precision, screenshots - Input-Precision: Fix trigger resolution from byte to ushort (16-bit internally) - Driver-Management: Add MIDI uninstall steps, HidHide/MIDI uninstall guard notes - Settings: Add auto-save description - Virtual-Controllers: Fix trigger types, add MIDI auto-mapping section - Stick-Dead-Zones: Add decimal precision, digit values, rectangular preview - Trigger-Dead-Zones: Add setting values section with precision details - Retake stick and trigger screenshots showing new digit value fields - Developer docs: updated by audit agents Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

hifihedgehog committed Mar 8, 2026

Add Input Precision wiki page with flight-sim-grade analysis Covers polling architecture, axis value pipeline at each stage, dead zone math precision, POV hat support, and output throughput. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

hifihedgehog committed Mar 7, 2026