Recent Posts

Ah, maybe I didn't make it clear, I was talking about Virtual Desktop when it came to remapping, it has a bindings page. OpenVR2Key works fine with my Vive controller/tracker even on the newest release.

I think I just got confused and I saw the author of OpenVR2Key say he didn't have a vive anymore only index so it made sense.

But this is pretty handy anyway. The only issue is there's no repeating function which I think is a limitation of the program to begin with, if you hold a button down it only sends the input once, which means it's not very useful for games with machine guns.

I've made a change to the OpenVR2Key program and now it will hold down the mouse click while the button is being held down on the controller. I'll attach the updated version.

If it were possible to get Virtual Desktop to remember the last window position to essentially save the calibration, it'd just be superior.

I tried out Virtual Desktop, I had used it on the Quest but didn't realise it was a different app on PC. So I can see how you align it to the screen, moving it's rotation and position and then changing size and distance.

So it seems that Virtual Desktop will save the size and distance settings but when you start it again the rotation and position will be out depending on where the headset is in space.

The only thing I can think of at the moment would be to intercept the openvr_api.dll that is in the program folder and send a saved set of rotation/position co-ords to the virtual desktop exe when the program first starts up. And then it will need to resume normally after that.

I think it's possible but will take some time to work out. Also it will need for a position to be captured while setting it up that can be used to replay via dll as it will be specific to your lighthouse setup / monitor position.

By the way, I also found while searching there is another virtual desktop type app called Desktop+ , it's free on Steam and is also on github with source code.

But I think maybe it's not going to be as good as VD.

I do have the ultra small form factor optiplex 3020 if that matters.

Specifically what did you change from auto to windows in mame.ini?

Change this . . .

Code: [Select]

#
# OSD OUTPUT OPTIONS
#
output                    auto

. . . to this.

Code: [Select]

#
# OSD OUTPUT OPTIONS
#
output                    windows


Scott

Just an update on this particular problem

I re downloaded both mame and FFB plugin. Then changed the mame.ini file to say Windows instead of auto. And everything is PERFECT!

I hadn't seen your post. I believe we are talking about the same problem. Specifically what did you change from auto to windows in mame.ini? I didn't understand.

Back box panel insert completed:

Little spidey speaker grill:

Working on the rest of the back box today.

Thanks for the info Randy, I ended buying the Creality V3 KE. My discount to myself was generous 

Reprinted a few parts for my project with some improvements.  I'm happy with the results:

vk

Now it works perfectly, thank you very much, now I will continue testing things, this is a great project with more memory, more processor and a world of functions that can be added like the analog ones 

Do you happen to have any documentation on how you performed this? I have the Xbox version and was looking to do this same thing. are you able to keep the functionality of all the buttons?

-Thanks

You mean modding a Top Shot Elite? It's not very hard. I made a basic adapter plate to fit a Pico (w/ headers) where the original's mainboard sat in. The back analog stick and buttons will work just fine--but if you're using a 3D printable mount for the camera to fit at the front barrel, then you'll have to remove the original front buttons/right stick board to make room.

I could be horribly wrong on that last part, but it's what I had to do (and I've found my front buttons board was super finicky and wasn't cooperating - plus most RP2040 boards only has enough pins to support one stick anyways).

Is there any known reason the IR camera in a Top Shot wouldn't work?

Because it's not the same camera at all and wouldn't be compatible? Unless you have proof of it being the same Pixart sensor.
Would be really nice if it was compatible! But that's not how it works.

So I had a look at OpenVR2Key, I hadn't seen it before and I didn't realise it was open source. I setup my vive controller but thought I was going to have an issue as you said it needed an Index controller to map and he mentions that's what he has.

Ah, maybe I didn't make it clear, I was talking about Virtual Desktop when it came to remapping, it has a bindings page. OpenVR2Key works fine with my Vive controller/tracker even on the newest release.

I dug around a bit in the code and figured I could probably make mouse clicks work but would need to hijack some keyboard keys to test it quickly and not bother with the user interface side of that.

So I've mapped F1 to left mouse, F2 to right mouse and F3 to middle mouse.

I'm attaching my build of the exe and the source code.

But this is pretty handy anyway. The only issue is there's no repeating function which I think is a limitation of the program to begin with, if you hold a button down it only sends the input once, which means it's not very useful for games with machine guns. I found that by adjusting the click detection threshold to 1 (might not be necessary) and the dragging threshold to 10 in the Vive Mouse config, the trigger is a lot more responsive, there's no weird delay. You could probably go even lower than 10ms, I think the code just waits for whatever the dragging threshold is before it actually sends a click which is why it's so slow by default.


The other day I had demulshooter running with VD, but now I can't figure out how to get it to respond to clicks with vive mouse or VD anymore. Might have to restart and see if that fixes it, maybe the blocker stuff for vive mouse affected VD somehow, it might use user32 too to send fake mouse inputs to games. In testing I also think VD just responds better than vive mouse. Virtual Desktop is right in line, there's very little delay between moving the gun and the mouse following. With vive mouse it's like there's maybe a 50-100ms latency, if I waggle it back and forth I can see it lagging behind. I have stabilization in the config set to off and the average set to 1 in case that applies anyway, but it doesn't seem to make an impact. If it were possible to get Virtual Desktop to remember the last window position to essentially save the calibration, it'd just be superior.