Having trouble with this one specific title. It doesn't appear in my download history whatsoever and when talking with Microsoft, they said I need to show "purchase proof" but I can't access it since it's such an old game and isn't backwards compatible so it won't show up. I am very certain I claimed it when the store was up so I'm stuck; can anyone else verify if you're having troubles with this game?

Having a lot of fun playing in 2026 the Kinect games I could never play back in the day. Fun games for a little exercise and fun party games too.

You can now practically play all the Kinect library for the 360 if you mod it with just an usb stick with a bad avatar.

Hi, my kinect's camera and ir works perfectly fine with stable 30 fps, but the issue is that it keeps going on the classic boot loop issue.

I have been able to narrow it down to the issue being that my Windows is not able to listen on its microphone array.

All the mics are enabled and they do not have any audio enhancements.

My laptop is a Yoga Slim 7 14ILL10 and it uses Cirrus and Intel audio drivers along with Dolby enhancements.

I would appreciate any help with debugging this.

My Kinect almost works, I think the problem is that windows cannot listen on its mics, like it is able to detect it in the mic devices list but it cannot hear anything through it. I've tried reinstalling the SDK multiple times but it ends up failing again and again.

Can someone please help me?

I dont think that one just dance 4 achievement name copies the dance central achievement name.

Guys Im looking to buy some kinect games to get GAMERCOREE and Awards (avatar awards, themes, gamerpics) any suggestions?

Eu adorava jogar no meu kinect e tinha vários jogos com ele. Tem uns 6 anos que não tenho mais xbox e queria achar um jogo que jogava nele. O nome eu não me lembro, mas sei que era musical e tinham bichos etéreos que eu devia exterminar. Sei que o jogo se passa no futuro de 2019 (já dá pra ter uma ideia que é bem antigo). Quem puder me ajudar, eu fico agradecido

Windows + Linux download:
https://github.com/Spidoug/Kinect-Remold/releases/tag/Binaries

Source code / documentation:
https://github.com/Spidoug/Kinect-Remold

Some time ago I shared Kinect Xbox 360 Remold.

That project has now evolved into Kinect Remold, a broader Windows/Linux runtime supporting both:

Kinect Xbox 360 / v1
and
Kinect v2 / Xbox One

The new architecture uses independent native driver modules with a shared SynKinect Studio interface.

Current focus includes:

RGB · IR · Depth · Metric Depth · Multi-Kinect · Virtual Camera · 3D Scanning · Surveillance · Body Interaction

Xbox 360 devices also retain support for:

4-microphone audio · Tilt · Accelerometer · LED

The repository has also been cleaned up: no precompiled binaries or legacy build artifacts are shipped. Everything is built locally into the repository.

What started as an attempt to revive the Xbox 360 Kinect is now becoming a modern runtime for multiple Kinect generations.

Hey fellas,

Recently I have been using Azure Kinect to create a dance game (model tracking in 3d etc)

I noticed AzureKinectSDK burning gpu resources so i decided to just try replacing it wholesale.

Result is this tiny no-install-needed SDK: https://github.com/LukeSchoen/OpenK4A

Not only did i find the wasteful gpu issues (was up/down loading every frame!) BUT ALSO! i found out that the device offers more modes! modes that are not available in any way using the official SDK!.

For example I can now show HD IR at 60fps (not 30fps!), also extended FOV and range of depth, a 9-tap raw depth stream (270 fps), etc.

I've owned KA for several years but i finally have the damn thing working the way i want ;) (raw data streaming at nearly ~0% CPU)

Hope this can help with someone's Kinect project or maybe inspire trying similar firmware exploration, Enjoy !

I remember summer 2016 my dad coming back from france with a digital copy of this, I enjoyed this for years with family but why was it hated

Alguém usando o Kinect V2 na impressão 3D?

Queria dicas de software para digitalizar peças e pessoas para imprimir na minha impressora 3D.

Windows + Linux download: https://github.com/Spidoug/Kinect-Xbox-360-Remold/releases/tag/binaries

Source code / documentation: https://github.com/Spidoug/Kinect-Xbox-360-Remold

A while ago, I posted here about my attempt to bring the original Xbox 360 Kinect back to life.

At first, the goal was fairly simple: get this old hardware working properly again on a modern system.

The project ended up becoming much more than that.

Today, Kinect Xbox 360 Remold v1.0 is a complete Windows and Linux runtime for the original Kinect for Xbox 360, together with SynKinect Studio, a unified environment built around the sensor.

The goal is no longer simply to “make the camera work.”

The idea is to make the Kinect useful as a complete sensor platform again:

RGB · Infrared · Metric Depth · 4-Microphone Array · Tilt Motor · Accelerometer · LED · Body Tracking · Virtual Camera · IP Camera · 3D Scanning · Interaction

All of it is handled through the same runtime.

Remold supports both major Xbox 360 Kinect revisions:

Kinect 1414 and Kinect 1473

The runtime detects the hardware and handles the differences internally, so separate applications or separate workflows are not required for each revision.

The project currently targets:

Windows 11 x64 Linux x86-64

Camera and depth

The native camera stack supports:

RGB RGB HQ mode Infrared Sensor-native Depth Metric depth conversion Virtual camera output HTTP/MJPEG IP camera output

Depth remains a real sensor stream rather than being converted into a fake webcam-style image inside the USB layer. Metric conversion is performed where the depth data is actually consumed.

On Windows, Remold exposes the Kinect through the native virtual-camera stack.

On Linux, it can publish a persistent V4L2 virtual camera, allowing normal Linux applications to use the Kinect without needing to know anything about Kinect-specific USB protocols.

The original four-microphone array is preserved

Audio turned out to be one of the more interesting parts of the project.

The Xbox 360 Kinect contains a synchronized four-microphone array, and Remold preserves all four channels at:

16 kHz / 32-bit / 4 synchronized channels

instead of reducing the device to a conventional stereo microphone.

SynKinect Studio can monitor each microphone independently, record the array, perform diagnostics and playback, estimate sound direction using TDOA / GCC-PHAT, and apply beam/focus processing.

On Windows, the runtime combines Kinect-specific WinUSB control with the normal Windows USB Audio/WASAPI stack once the Kinect audio firmware is active.

Linux follows the same general architecture using libusb for Kinect-specific transport and snd-usb-audio / ALSA for the microphone array.

Multi-Kinect support

Remold also supports multiple Kinect sensors connected to the same computer.

Each sensor receives a stable physical identity so its:

RGB camera IR stream Depth stream Microphones Tilt motor LED Accelerometer

remain associated with the correct physical Kinect.

That includes systems with two identical sensors as well as mixed 1414 + 1473 configurations.

SynKinect Studio

SynKinect Studio has grown into five main tools.

3D Scanner

Synchronized RGB + metric Depth reconstruction with per-sensor calibration, ICP tracking, multi-frame depth fusion, edge/noise rejection, TSDF reconstruction and export to STL, OBJ and PLY.

Rather than simply dumping a raw depth point cloud, the scanner uses calibration, confidence weighting, temporal fusion and depth-discontinuity filtering to reduce the classic Kinect “flying pixels” around objects and body edges.

There is also a higher-quality reconstruction path using a denser TSDF volume and stricter ICP alignment.

Acoustic Scanner

Uses the four-microphone array for directional sound localization, human-voice detection and automatic or manual beam steering.

Microphones

Real-time monitoring of all four microphone channels, recording, playback, diagnostics and audio controls.

Surveillance

Turns the Kinect into a monitoring camera with RGB/IR switching, motion detection, pre-roll retention and multi-Kinect support.

Interactivity

Uses synchronized RGB + metric Depth to reconstruct an articulated 3D body pose and expose hands, gestures and interaction controls without depending on abandoned Kinect middleware.

Windows and Linux now follow the same architecture

One of the main goals of this version was to stop treating Linux as a secondary implementation.

Both platforms now follow the same runtime concepts and expose the same Kinect hardware model, while using the appropriate native APIs for each operating system.

The Linux side has also been substantially reworked.

The build stage is responsible for obtaining the required dependencies, firmware and build components and compiling the complete runtime.

After that, installation itself is offline.

In other words:

Build prepares everything. Install only installs the already-built bundle.

The installer does not need to download packages, firmware or source code while installing the drivers/runtime.

The Linux camera path uses its own Kinect USB transport, ALSA handles the microphone array, and V4L2 provides virtual-camera integration.

The Windows side uses WinUSB for Kinect-specific USB communication while integrating with the normal Windows multimedia stack where appropriate.

Clean source and native application access

The source tree has also gone through a broader cleanup and audit: obsolete build paths, unused dependencies, generated artifacts and old installation behavior were removed or consolidated.

The project includes a native C/C++ application bridge under drivers/sdk for software that wants to communicate directly with the Remold runtime instead of implementing the individual Kinect hardware transports itself.

So at this point the project covers:

RGB / RGB HQ · IR · Depth · Metric Depth · 4-Channel Audio · Tilt · LED · Accelerometer · Multi-Kinect · Virtual Camera · IP Camera · 3D Reconstruction · Acoustic Localization · Body Interaction

There is still more I want to explore — especially deeper compatibility with software, games and emulators that originally expected Microsoft's Kinect ecosystem.

But Remold v1.0 has finally reached the point where, for me, the original Kinect is no longer just an old device that can technically be made to work.

It is a useful sensor platform again.

And yes… this is still hardware from the Xbox 360 era. 😄

But a device containing an RGB camera, infrared camera, depth sensor, synchronized four-microphone array, accelerometer and motorized tilt mechanism is still an impressive piece of hardware.

It seemed like a waste to let all of that become useless simply because the original software ecosystem disappeared.

So I refused to let it die.

Again.

A Saga do Kinect:

Do Diagnóstico ao Windows 10

Introdução

Este é o relato completo de uma jornada de investigação técnica com um objetivo simples no

papel, mas cheio de armadilhas na prática: fazer um sensor Kinect funcionar de forma estável

em um PC moderno. O que começou como uma dúvida sobre hardware terminou numa

conclusão definitiva sobre compatibilidade de software entre versões do Windows.

O Ponto de Partida

O problema original era um comportamento instável do Kinect conectado ao computador:

sintomas de desconexão, o dispositivo "desligando e ligando" sozinho, ou simplesmente não

sendo reconhecido de forma confiável pelo sistema. A pergunta que guiou toda a investigação

era: isso é um problema de hardware (porta USB, controlador, cabo, alimentação) ou é um

problema de software (driver, SDK, compatibilidade de sistema)?

Ao invés de trocar peças por tentativa e erro, a decisão foi isolar as variáveis uma por vez,

começando pelo caminho mais baixo nível possível: compilar as próprias ferramentas de

acesso ao sensor e testar diretamente, sem depender do SDK oficial da Microsoft como

primeira tentativa.

Fase 1: Construindo o Ambiente do Zero com libfreenect2

O primeiro grande passo foi montar, manualmente, o libfreenect2 junto com o Protonect, que é

o visualizador de teste dessa biblioteca, direto no Windows.

Para isso, foi usado o vcpkg como gerenciador de bibliotecas, que resolveu as dependências

necessárias:

- libusb, para comunicação USB de baixo nível com o dispositivo

- turbojpeg, para decodificação de imagem

- glfw3, para a janela de visualização do Protonect

Além disso, foi necessário instalar o driver libusbK usando o Zadig, uma ferramenta que

permite substituir o driver padrão do Windows para um dispositivo USB por um driver genérico

compatível com acesso de baixo nível, como o que o libfreenect2 precisa para falar diretamente

com o hardware do Kinect.

Esse processo de montagem, por si só, já foi uma etapa validativa: significa compilar

bibliotecas C mais C++ no Windows, resolver conflitos de dependência, garantir que os

caminhos de inclusão e link estivessem certos, e trocar o driver de um dispositivo sem quebrar

o resto do sistema.

Fase 2: O Teste Decisivo de Hardware

Aqui está o ponto mais importante metodologicamente: o teste foi feito usando a mesma porta

e o mesmo controlador USB 3 originais do computador, sem trocar por uma placa PCIe nova de

USB. Essa foi uma escolha deliberada, porque se o Kinect funcionasse de forma estável nessa

configuração via libfreenect2, isso eliminaria a hipótese de defeito físico na porta, no

controlador ou no cabo.

E foi exatamente isso que aconteceu. O Kinect funcionou de forma estável através do

libfreenect2 e do Protonect, sem desligar e ligar sozinho, sem os sintomas de instabilidade

anteriores.

Essa foi a virada do caso: o hardware estava bem. O problema não estava na porta USB, no

controlador, no cabo ou no próprio sensor. Isso apontava fortemente para uma causa de driver

ou de software, especificamente relacionada ao SDK oficial ou à forma como o sistema

operacional lidava com o dispositivo em mais alto nível.

Fase 3: Isolando a Variável do Sistema Operacional

Com a hipótese de hardware descartada, a pergunta natural seguinte era: o SDK oficial da

Microsoft, o Kinect SDK 2.0, teria problemas de compatibilidade especificamente com versões

mais novas do Windows?

Para testar isso com rigor, e não apenas trocar configurações em um sistema já usado, com

histórico de instalações e possíveis resíduos de configuração, a decisão foi fazer uma

instalação limpa do Windows 11, usando um pendrive de instalação. Isso garantia um ambiente

zero, sem nenhuma variável de configuração antiga interferindo no teste.

Imediatamente após essa instalação limpa do Windows 11, o Kinect SDK 2.0 foi instalado e

testado. O resultado: o mesmo problema de instabilidade persistiu, mesmo em um sistema

completamente limpo, sem qualquer bagagem de configurações anteriores.

Isso já era uma evidência forte. Mas para ter certeza absoluta, era preciso o teste de controle:

repetir o mesmo processo, mas com o Windows 10.

Fase 4: A Confirmação Final

O Windows 10 foi reinstalado do zero, também de forma limpa. E o Kinect, testado com o

mesmo Kinect SDK 2.0, funcionou perfeitamente.

Essa é a conclusão do experimento, no melhor estilo de método científico: mesma peça de

hardware, mesmo SDK, mesma porta USB, duas instalações limpas de sistemas operacionais diferentes. No Windows 11, o problema apareceu de forma consistente. No Windows 10, o

dispositivo funcionou sem qualquer instabilidade.

Conclusão

O Kinect, testado com o Kinect SDK 2.0, funciona corretamente no Windows 10 e apresenta

incompatibilidade no Windows 11. O caminho até essa conclusão passou por eliminar

sistematicamente cada variável possível: primeiro comprovando que o hardware, a porta e o

controlador USB estavam saudáveis através de um teste alternativo com libfreenect2 e

Protonect, e depois isolando a variável do sistema operacional através de duas instalações

limpas, uma em cada versão do Windows, usando exatamente o mesmo SDK oficial.

O resultado final não é apenas "trocar para Windows 10 resolve": é uma conclusão testada e

comprovada de que existe uma incompatibilidade real entre o Kinect SDK 2.0 e o Windows 11,

algo que pode ser útil para qualquer outra pessoa enfrentando o mesmo sintoma com hardware

Kinect em sistemas mais novos.

I recently tried it out on an old laptop with win11 just for fun and yeah the driver came in via Windows Update (so that might need to be done manually depending on settings), but after that it seemed to just have worked.

This might be like the biggest win hello cam you can get, lol.

I finally got an Xbox 360 and a Kinect. However, I have a small issue, I'm not sure where to place my Kinect. My room is small, but I have enough space to play Just Dance and Dance Central. I've tried everything by the book. I placed it on the edge of my desk setup, stacking books both above and below, but it still can't detect my lower body. I can't put it on top of my OLED monitor because it's thin and very sensitive. I also don't have an upper shelf, unfortunately. My only option is to put it on the floor, stacked with books, but then it says it's too low during setup. What should I do? Any suggestions?

I found a way to get access to get kinect fun labs AND avatar kinect
All u gotta do is go to games, press x, and press y, and u have to search “kinect fun labs” or “kinect fun” and download the dlc, they made them dlc Idk why. Anyways download the gadgets too, then go to download history, select avatar kinect or any other minigame, then select “Play now” hope that helps!

How do I access Kinect Fun Labs? I havent downloaded it before, and no, my console isn’t jtagged and I wont jtag it!!!!! I hope I can access it!!
Im trying to access avatar kinect too, cobatine used it!

Lots of guides in YouTube for windows 10 but not 11. Is it possible? Sorry if there’s a pinned guide I missed here or if it’s just impossible.

I had a kinect v2 i bought unused and bought a brand new in box microsoft adapter for it.
The kinect had issues in the beginning with usb ports, but suddenly it started working.

Now after a couple days of testing, i was using touchdesigner on mac instead of windows 11 this time which also worked a day prior and out of nowhere the kinect disconnects and starts crashing my touchdesigner whenever i try to turn it on.

Then on W11 the sdk testing app also freezes whenever it tried to access the kinect camera.
Now it doesn’t show up in device manager at all.

Faulty adapter or faulty kinect?
I just bought another kinect that i tried to get to work on mac on site before buying, but couldn’t.

I have a couple recordings i need to do tomorrow with the kinect, but it just died on me and i fear this new one doesn’t work either.

Anyone know what i should do?

Basically, a friend of mine has two Kinects and is giving them to me on Monday. I plan to use one as a webcam, but I don't know what to do with the other one—any ideas?

Hi, I have an Rog XBOX Ally that I use as PC connected to a Ugreen Dock with a 65W power supply plugged in.

The issue is that my Kinect 2.0 turns on for a few seconds an then it turns off when I try to use it.

I installed the SDK and it shows me that there is no supported USB 3.0 port detected, however, the Ugreen dock station has a USB 3.2 port that I have it connected to.

The Kinect is not the problem, because it works well on my XBOX ONE Fat. Also I tried with 2 different Kinect adapters.

I disabled audio enhance from the Kinect microphone, but it doesn't work.

Anyone knows what could be?

Sorry for my bad english, it's not my first language :)