-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Virpil support #23
Comments
That is a beast of a stick I've got a few other devices lined up for 3D modeling and those take a long time for me to produce so for now I suggest we wire it up using the Warthog joystick model. Could you run JoystickProxy.exe from the latest release https://github.com/mdjarv/JoystickVisualizer/releases/tag/v0.11.3 Find and select your Virpil stick, move the stick fully top-left and screenshot the application and attach the image here |
Aah, unfortunately there's no support for two devices of the same USB ID at the moment... the current implementation can not handle it as the visualizer uses pre-made game objects and can't spawn new ones at this moment. I'll look into adding the Mongoos using the Warthog model tomorrow if I can find the time |
Sorry for the delay, I have been quite busy with real life stuff and this kind of slipped between my fingers. I've added initial (untested) support for the T-50 in 0.11.7, try it and let me know how it goes. Unfortunately I still do not have a solution for multiple sticks of the same type |
I've done some work with unity and Blender 3D modelling. If you were keen, I could create an accurate 3D model of the T-50 (which I also use). Feel free to contact me if you think this might help, thanks. |
@xXBoofleXx Help to make a proper model would be much appreciated, and I will of course credit you in the README.md just as I've done for the others that have helped out. 👍
Hope it makes sense, if all of these are done correctly it makes it much easier to add it to the Unity and future changes to the model will "just work" without any manual changes in the Unity project Commenting on this issue works just fine, but if you want a more active discussion about the modelling or show some progress pictures you're more than welcome to join my Discord server as well: https://discord.gg/4nc3XtQ |
Hey Mathias,
Roger to all of the above, sounds good man. I've already started, I'll
swing by the discord at some stage fo shiz and let you know if I have any
questions. Done a fair bit of game dev and model/texturing in Blender for
Unity, that said everyone has a slightly different pipeline and way of
doing things, so I'll definitely check with you. Thanks for the detailed
email, helps me get sorted. I'll let you know how it progresses.
Cheers
…-Nath
On Sat, May 19, 2018 at 4:22 AM, Mathias Djärv ***@***.***> wrote:
@xXBoofleXx <https://github.com/xXBoofleXx> Help to make a proper model
would be much appreciated, and I will of course credit you in the README.md
just as I've done for the others that have helped out. 👍
.blend files work well and if you use the Blender Rederer the materials
will import into Unity as well. I do however have a few points on my
model-wishlist if you want to help out:
- Any individually moveable part needs to be a separate object in the
model
- Model objects should be arranged in a proper hierarchy for example:
Base -> Stick -> Button 1
> Button 2
> POV Hat
- Objects origin should be set so movement and rotations of the
"active element" look correct (i.e. if I rotate the stick it should rotate
around the gimbal center inside base and not the center of the handle)
Hope it makes sense, if all of these are done correctly it makes it much
easier to add it to the Unity and future changes to the model will "just
work" without any manual changes in the Unity project
Commenting on this issue works just fine, but if you want a more active
discussion about the modelling or show some progress pictures you're more
than welcome to join my Discord server as well: https://discord.gg/4nc3XtQ
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AljFrHD5-K-iyuv4Yn2qhqoXAuoCv7wKks5tzxFkgaJpZM4TbMxO>
.
|
Unfortunately it's not that simple. USB ID's have to be implemented in both the Proxy and the Visualizer so to make such a change requires a similar change in a Unity script as well as rebuilding the whole Unity application. I did recently add the following for someone else with a similar setup:
perhaps you could change the USB ID of your device to match the VPC-Star-Citizen-L version above? I have started planning for a more flexible implementation where every device-specific thing is pure configuration and easy to change and share, but that's still in its planning phase and quite a ways off |
so.. we are getting closer. |
Did you update to 0.11.13 or just change the https://github.com/mdjarv/JoystickVisualizer/releases/tag/v0.11.13 |
oh, im on JoystickVisualizer-0.11.11 |
also, please join HOTAS/HOSAS/SIMPIT discord |
we have devs / vendors and joystick owners discussing all kinds of things there |
I noticed that supported joysticks doesnt include Virpil MongoosT-50
Any chance we can have this?
The text was updated successfully, but these errors were encountered: