Quest Recenter / Wake-State Bug
You isolated drift between IsTracked and UserPresence, built a recenter utility, and identified vehicle-entry state as the clean trigger path.
JUSTIN × FORGEBOT
30-DAY WORK SNAPSHOT
30-DAY WORK SNAPSHOT
Welcome to your ForgeBot workbench
Hey Justin. I found the grind.
You’re operating as a Unity developer and autonomous simulator troubleshooter—mostly on John Deere VR, with a successful TeleOp Trainer launch now behind you. Here’s where I can absorb repetitive work without getting in your way.
172Slack posts found in the 30-day search
130posts in John Deere production
8+VR tutorial fixes handed your way
1first simulator shipped on JACKS
What You’ve Been Working On
The strongest pattern is hands-on Unity diagnosis: isolate the actual state failure, test it in-headset, inspect project architecture, then land the least invasive correction.
Grunt Work I Can Pick Up
These are concrete outputs I can produce from a Slack thread, Jira case, build log, screenshot, video, or repository target.
Source-Grounded Root-Cause Briefs
Trace a reported Unity/VR failure through the John Deere source and return likely cause, affected systems, risks, and the smallest safe test.
Deliverable: concise diagnosis with exact source references.Repro & Regression Matrices
Turn headset observations into a clean matrix across editor, packaged build, VR, PC, headset sleep/wake, vehicle entry, and hardware reset.
Deliverable: test sheet ready for Jira or QA.Ticket Cleanup & Triage
Consolidate tutorial cases, identify duplicates and dependencies, sharpen acceptance criteria, and flag the tickets most likely to cause rework.
Deliverable: ranked ticket brief with suggested next action.Help-Menu Capture Factory
Inventory every help section, map reusable tutorial graphics, process screenshots, and convert recordings into optimized low-frame-rate GIFs.
Deliverable: named, compressed, implementation-ready media pack.Texture & Asset Audit
Inspect dimensions, compression, alpha usage, import overrides, duplication, and likely build-size offenders before manual optimization begins.
Deliverable: exception-only optimization report.PR & Build Evidence Packs
Summarize what changed, which Jira cases it covers, what was tested, and what remains uncertain—without making you rewrite the same status three times.
Deliverable: paste-ready release and review notes.Technical Knowledge Capture
Turn solved problems—localization conflicts, canvas/shader behavior, recenter logic, input architecture—into durable notes for the next developer.
Deliverable: short internal runbook with evidence links.Support-Hour Reconstruction
Reconstruct likely support activity from your Slack and Jira timeline so logging does not become an archaeology project at month-end.
Deliverable: dated draft entries for your review.Workstream Digest
Condense open asks, active bugs, awaiting decisions, completed fixes, and the next best move into one low-noise snapshot.
Deliverable: a daily or on-demand action sheet.Best First Handoff: Help-Menu Media
I can start by turning the approved help-menu direction into a section-by-section asset inventory, reuse map, capture list, file naming scheme, and optimization targets. You keep ownership of the Unity implementation; I remove the media bookkeeping and processing loop.