▸case-03 We are refactoring our game's camera mechanics to improve readability and feel. Please provide a step-by-step implementation guide covering authoritative tracking, zoom and orbit constraints, occlusion rules, and validation steps to ensure camera stability during intense combat. | fail→fail | 19,553 | 17,641 | -10% | 1 | 1 | 0% | 3,299 | 3,816 | +16% | 0 | 0 | — |
▸case-01 I'm working on a third-person action title and need a comprehensive design document for our camera control system. Please outline the core setup steps for camera movement, target tracking, collision management, and camera modifiers. Include a verification checklist at the end covering common playtesting scenarios. | fail→pass | 30,977 | 24,060 | -22% | 1 | 1 | 0% | 5,393 | 4,314 | -20% | 0 | 0 | — |
▸case-02 Can you create a technical guide for implementing game camera controls in our mobile RPG? I need a breakdown of how to structure base tracking, handle touch inputs alongside UI, manage special states like lock-on or screen shake, and test edge cases across different screen orientations. | fail→fail | 27,934 | 24,578 | -12% | 1 | 1 | 0% | 5,427 | 5,242 | -3% | 0 | 0 | — |
▸case-04 We are designing character controller physics for a 3D platformer hero in our game engine project. Please output a technical specification detailing movement speed, acceleration curves, gravity application, and jump mechanics. | pass→pass | 24,739 | 24,521 | -1% | 1 | 1 | 0% | 4,707 | 4,958 | +5% | 0 | 0 | — |
▸case-05 We are designing the HUD layout system for our action game project across mobile and desktop displays. Please provide an architecture guide for positioning health bars, mini-maps, and skill cooldown icons. | pass→pass | 17,521 | 21,479 | +23% | 1 | 1 | 0% | 3,164 | 4,106 | +30% | 0 | 0 | — |
▸case-06 We are setting up the 3D spatial sound system for our third-person combat game project. Please write an audio implementation guide detailing listener placement and sound attenuation rules. | pass→pass | 18,114 | 24,852 | +37% | 1 | 1 | 0% | 3,115 | 4,217 | +35% | 0 | 0 | — |
▸case-07 We are building the main camera tracking script for our 3D action game project. Developers are suggesting binding camera position directly to the animated character mesh transform. Please provide an architectural guide outlining the recommended approach for position and look-at target smoothing. | pass→pass | 17,720 | 21,942 | +24% | 1 | 1 | 0% | 3,248 | 4,193 | +29% | 0 | 0 | — |
▸case-08 Our camera programmer wants to keep the player character strictly centered in the screen frustum at all times during combat in our action title. Please draft a camera framing specification outlining target composition and visible context rules. | fail→fail | 22,307 | 24,091 | +8% | 1 | 1 | 0% | 3,705 | 4,246 | +15% | 0 | 0 | — |
▸case-09 We are implementing orbit and zoom controls for an adventure game camera system. A developer suggested allowing unrestricted 360-degree vertical pitch rotation and unbounded zoom distance. Please provide a camera constraint specification detailing orbit, pitch, and zoom rules. | pass→pass | 15,142 | 23,035 | +52% | 1 | 1 | 0% | 2,764 | 4,330 | +57% | 0 | 0 | — |
▸case-10 In our third-person dungeon game project, geometry frequently blocks the view of the character. Some team members propose making all interior walls transparent globally when obstruction occurs. Please provide a camera collision specification defining proper occlusion handling. | pass→pass | 21,335 | 23,614 | +11% | 1 | 1 | 0% | 3,328 | 4,549 | +37% | 0 | 0 | — |
▸case-11 Our team is adding target lock-on, cutscene camera angles, and impact camera shake to our action title. Engineers are proposing modifying the core tracking loop directly for each feature. Please write a camera state architecture guide explaining how special camera modes should be structured. | fail→fail | 21,226 | 21,005 | -1% | 1 | 1 | 0% | 4,073 | 4,028 | -1% | 0 | 0 | — |
▸case-12 We are porting an action game project to mobile touch devices. Designers want swipe camera rotation controls to overlap directly with virtual analog joysticks and action buttons to save screen real estate. Please provide a mobile camera touch control specification. | pass→pass | 23,971 | 33,888 | +41% | 1 | 1 | 0% | 4,185 | 6,312 | +51% | 0 | 0 | — |
▸case-13 When players manipulate touch camera gestures on mobile devices, the view often gets misplaced during busy combat. Please outline mobile touch camera recovery guidelines and UX specifications for our action title. | pass→pass | 18,291 | 17,202 | -6% | 1 | 1 | 0% | 2,894 | 3,122 | +8% | 0 | 0 | — |
▸case-14 We are establishing accessibility standards for camera motion, screen shake, and visual recoil in our action game project. Please provide a technical design document outlining camera accessibility guidelines. | pass→pass | 22,964 | 32,138 | +40% | 1 | 1 | 0% | 3,816 | 6,363 | +67% | 0 | 0 | — |
▸case-15 Our action game project features multiple sub-systems (vehicles, mounts, cutscenes) attempting to change camera parent targets on the fly. Please provide a camera target architecture specification detailing tracking hierarchy. | pass→pass | 23,550 | 20,223 | -14% | 1 | 1 | 0% | 3,989 | 3,865 | -3% | 0 | 0 | — |
▸case-16 We are creating a test plan for validating our third-person camera system in game level environments. Please write a test suite outline covering environment geometry edge cases. | fail→pass | 18,456 | 16,676 | -10% | 1 | 1 | 0% | 3,074 | 2,936 | -4% | 0 | 0 | — |
▸case-17 Please outline a playtesting matrix for verifying lock-on camera behavior during dynamic combat in our third-person action game project. | pass→pass | 20,180 | 18,145 | -10% | 1 | 1 | 0% | 3,300 | 3,115 | -6% | 0 | 0 | — |
▸case-18 We need a testing checklist for our cross-platform mobile game camera system across different device form factors. Please outline screen display testing requirements. | fail→pass | 15,919 | 13,846 | -13% | 1 | 1 | 0% | 2,748 | 2,428 | -12% | 0 | 0 | — |
▸case-19 We are documenting game state edge cases for camera system verification in our project. Please provide a quality assurance checklist for camera behavior during menu interactions. | pass→pass | 17,231 | 13,683 | -21% | 1 | 1 | 0% | 2,602 | 2,409 | -7% | 0 | 0 | — |
▸case-20 Our engineering leads are reviewing the camera collision and target tracking pipeline for performance risks in our game engine build. Please provide a camera validation document outlining performance verification criteria. | pass→pass | 21,002 | 25,938 | +24% | 1 | 1 | 0% | 3,567 | 4,843 | +36% | 0 | 0 | — |
▸case-21 Our cinematic director wants to apply dynamic film angles, tight depth-of-field, and aggressive camera motion right at the start of combat camera development for our game project. Please provide a camera design guidance document detailing development priorities. | pass→pass | 17,489 | 18,535 | +6% | 1 | 1 | 0% | 2,802 | 3,192 | +14% | 0 | 0 | — |
▸case-22 An animator suggests parenting the game camera node directly to the character head bone transform to guarantee exact sync with animations in our 3D game project. Please provide a technical camera architectural document evaluating this design. | pass→pass | 21,419 | 22,249 | +4% | 1 | 1 | 0% | 3,377 | 3,733 | +11% | 0 | 0 | — |