Communications & Triage Portal

Contact & Technical Support Routing

Need help with your virtual controller configuration or have a legal inquiry? Please review our specialized communication channels below to direct your request to the right place.

🐛

Bug Reports & Code Exploits

Driver bugs are tracked upstream, not by email. For v2.2.2.0, report issues to BrunnerInnovation/vJoy on GitHub; for force-feedback issues, use njz3/vJoy on GitHub; for the original 2.1.9.1, use the SourceForge vjoystick project forum. Please do not email code logs privately.

BrunnerInnovation/vJoy — GitHub Issues
🕹️

Game & Peripheral Remapping

Struggling to map your physical HOTAS hardware, setup OpenTrack profiles, or bind axes inside DCS World or MSFS? Active gaming communities solve these deployment queries daily.

Visit Community Forums
⚖️

Site Contact & Compliance

For server mirror issues, advertising requests, DMCA takedown filings, or licensing compliance concerns, send an email to the site maintainer.

Email: [email protected]
Before You Write

Site & Content Guidelines

Please review these notes on security flags, file indexing, and licensing before sending an inquiry to the site maintainer.

Suggest a vJoy fork for our guides

Know a vJoy fork we should document? Send us the public repository link and we will review it for a future guide — we only link upstream release files.

What is your policy regarding security software flags or false positives?

Because virtual driver frameworks require direct integration with the Windows kernel layer, security networks like Microsoft SmartScreen or Windows Defender occasionally flag unindexed release configurations as a “false positive.” If you represent a cybersecurity firm or security engine vendor and require verification documentation on our mirrored binaries, please contact the site maintainer directly.

How do you handle licensing and intellectual property inquiries?

vJoy is free and source-available software (SourceForge lists it as public domain; the GitHub forks carry the MIT licence). We do not own the copyright to the source code, nor do we sell commercial enterprise variants. For licensing or intellectual property inquiries, please contact the site maintainer by email.