{
  "server": "Hyperfy",
  "title": "Hyperfy Discord - 2025-08-10",
  "date": 1754784000,
  "stats": {
    "totalMessages": 104,
    "totalUsers": 17
  },
  "categories": [
    {
      "channelId": "994775534733115412",
      "channelName": "💻│developers",
      "summary": "# Discord Chat Analysis for 💻│developers\n\n## 1. Summary:\nThe chat primarily focused on technical discussions around free camera implementation in Hyperfy. Shiffty proposed a version with fixed linear interpolation instead of an easing function, which ash confirmed felt identical to v1. The implementation involves two parts: a section in the update() function and a setFreeCamTarget method. There was also troubleshooting for local installation issues where Valiant encountered build failures, which ash helped resolve by suggesting npm install, restart, and adding ASSETS=local to the .env file. A minor issue with primitives in the dev branch was reported by Shiffty but appeared to be related to Git issues that were resolved by wiping and cloning the repository. The conversation indicates ongoing development and refinement of camera controls in the platform.\n\n## 2. FAQ:\nQ: Are primitives broke in dev? (asked by Shiffty) A: nah i'm on latest dev right now (answered by ash)\nQ: wen DOF slider? (asked by vox) A: Unanswered\n\n## 3. Help Interactions:\nHelper: ash | Helpee: Valiant | Context: Build failures after local installation | Resolution: Suggested running npm install, restarting with npm run dev, and adding ASSETS=local to .env file\nHelper: Shiffty | Helpee: Unknown (possibly ash or vox) | Context: Free cam implementation with fixed linear interpolation | Resolution: Created version that felt \"100% the same to v1\" according to ash, with plans to make linear interpolation configurable\n\n## 4. Action Items:\nType: Technical | Description: Remove quadratic easing completely and make linear interpolation configurable with default to 0.05 | Mentioned By: Shiffty\nType: Documentation | Description: Check .env.example for proper environment configuration | Mentioned By: ash\nType: Feature | Description: Implement DOF (Depth of Field) slider | Mentioned By: vox",
      "messageCount": 29,
      "userCount": 7
    },
    {
      "channelId": "958209074045026327",
      "channelName": "⚡│general",
      "summary": "# Discord Chat Analysis\n\n## 1. Summary\nThe chat primarily revolves around Hyperfy V2 features and technical discussions. A significant focus was on camera functionality, particularly comparing the V1 drone camera with V2's free cam. Ash mentioned that the V2 drone can replicate V1 functionality, which used lerp/slerp interpolation at 0.05, and promised to share the V1 camera code. Vox expressed difficulty replicating the \"super fine maneuvering\" of V1 despite adjusting easing settings. Another technical discussion centered on depth of field (DOF) functionality, which Ash indicated would be easy to add but needed configuration guidance. There was also discussion about a world created by Vox that experienced intermittent connection issues, eventually traced to an Audio App set to preload. The chat included references to GitHub activity, documentation resources (transition from hyperfy.how to docs.hyperfy.xyz), and optimization for mobile devices. Vox's experimental world showcasing UV scrolling and PBR capabilities received significant praise for its performance and visual quality.\n\n## 2. FAQ\nQ: Is it possible to get depth of field going? (asked by MetaRick) A: Easy to add, but not sure how it should be configured or used (answered by ash)\nQ: Can you describe what is different with the drone camera in V1? (asked by Shiffty) A: V1 free cam was just `[` to slow movement, `]` to speed up and then all interpolation was lerp/slerp to target @ 0.05 (answered by ash)\nQ: Will Hyperfy v2 be announced with a major release and promotion? (asked by Saracismo) A: Unanswered\nQ: Is hyperfy.how coming back? (asked by Mtv969.eth) A: Domain had to be changed. It's not coming back. (answered by 𝕽𝖔𝖚𝖘𝖙𝖆𝖓)\nQ: Can you make a Hyperfy tutorial video for smartphone and windows? (asked by Xukonth) A: It natively works on smartphone, nothing special to do. For servers, use docker, nodejs locally, fly.io, or hyperworld.host (answered by HypPrivakos - HyperWorld.Host)\n\n## 3. Help Interactions\nHelper: ash | Helpee: Shiffty | Context: Understanding V1 camera functionality | Resolution: Ash explained V1 free cam used lerp/slerp @ 0.05 and promised to share the camera code\nHelper: Shiffty | Helpee: vox | Context: Replicating V1 drone camera feel in V2 | Resolution: Offered to try implementing the exact lerp at .05 from the old version\nHelper: vox | Helpee: Mtv969.eth | Context: Looking for updated documentation | Resolution: Shared the new docs.hyperfy.xyz link\nHelper: HypPrivakos - HyperWorld.Host | Helpee: Xukonth | Context: How to use Hyperfy on different platforms | Resolution: Explained smartphone compatibility and server hosting options\nHelper: vox | Helpee: Self-diagnosed | Context: World connection issues | Resolution: Identified and fixed issue with Audio App set to preload\n\n## 4. Action Items\nTechnical: Implement depth of field functionality | Description: Add DOF capability to Hyperfy for cinematic effects | Mentioned By: MetaRick\nTechnical: Replicate V1 drone camera feel in V2 | Description: Implement the exact lerp/slerp @ 0.05 interpolation from V1 | Mentioned By: vox\nTechnical: Fix reference to hyperfy.how | Description: Update media to remove references to deprecated domain | Mentioned By: Mtv969.eth\nFeature: Add depth of field to core functionality | Description: Make DOF available but off by default, configurable via hyp files | Mentioned By: MetaRick\nDocumentation: Update references from hyperfy.how to docs.hyperfy.xyz | Description: Ensure consistent documentation references | Mentioned By: Mtv969.eth",
      "messageCount": 72,
      "userCount": 17
    },
    {
      "channelId": "1326789867312775290",
      "channelName": "🪙│hyper",
      "summary": "The chat segment is extremely brief with only two messages. The first message from Xukonth is requesting community members to engage with Hyperfy's social media posts on X (formerly Twitter). The second message from Sharp appears to be a personal question unrelated to technical discussions. There are no technical discussions, problem-solving activities, or implementations present in this limited exchange.",
      "messageCount": 2,
      "userCount": 2
    },
    {
      "channelId": "1022421054582423562",
      "channelName": "🐞│issues",
      "summary": "The chat contains a single message from user \"ash\" highlighting a technical limitation where meshes with skeletons cannot be selected through raycasting. The issue stems from raycasting being performed on the CPU while skeletons are processed on the GPU. This creates a disconnect that prevents proper selection of skeletal meshes. The user mentions this is a common problem in other platforms like Unity but is particularly problematic in Hyperfy v2. The user indicates they have some potential solutions in mind but doesn't elaborate on the specific approaches.",
      "messageCount": 1,
      "userCount": 1
    }
  ]
}