AMVI_Rider

Well, there are few reasons for the latency you are experiencing: 1. The standard InkCanvas doe not support injection of stylus points (probably because of security in signing applications) so I have to mimic the behavior ... this costs some performance 2. The VR refresh is fps limited to avoid using too much CPU, this can be improved and tuned (and I will) 3. The unavoidable latency of the two-passages (tablet -> VRK -> VR) Moving to next big things: I'm actively using all my resources on the Oculus "native" implementation. It will take some time because Oculus does not provide any capability to create overlays from another application. This means I have to finds a way to inject some code in between DCS and Oculus DLL (wrapping or detouring), learn hot to create the overlay and all the utility functions needed to manage it the way OpenVR does. Easier said than done!

Here some troubleshooting steps: Can you confirm that the custom driver is loaded? It should appear in the device manager: If this is ok, have you enabled the custom driver in VRK options? Can you send me the VRK log file? (C:\Users\<username>\VRK\Logs) Support for keyboard, USB devices (and more) will be released in a couple of minutes :smilewink: POVs and additional commands (zoom and pan) are not there yet ... they will follow shortly

Version 2.1.3.1 has been released (V2.1 is now in release stage) It is mostly a bug fix release, but includes also some generalization to speed-up F-16C development (WIP)

Thank you. I just had a look at your latest stream and I'm happy that VRK is there! The upcoming version will include keyboard/hotas commands to complement gestures and physical buttons. It may be useful to map the zoom out without sacrificing a physical button. Also playing with vJoy and/or voice control you can do nice things. I will look into Twitch APIs, let's see how much effort is needed to add the feature.

From the "MUDSPIKE AMA WITH EAGLE DYNAMICS SENIOR PRODUCER MATT WAGNER" article published here: https://www.mudspike.com/mudspike-ama-with-eagle-dynamics-senior-producer-matt-wagner/ "It’s a good idea to have the possibility to make notes on a pad in VR. We’ll think about it and implement as additional game feature in VR mode." I think everybody here agree :smartass:

The capability to control VRK with other devices (keyboard, stick/hotas, controllers, USB I/O) will come. It was not the priority because I focused most on innovation rater than superimposing the feature set with existing tools. Now that VRK core is "good enough" I'm switching to support the DCS kneeboard in various ways. This will include the capability to use it without additional HW (except for writing of course).

You just need to add a "Tab" on the Kneeboard to activate the kneeboard overlay. Either adding a Notes tab or a document will make it show.

The good part is that you won't see it while flying :)

I'm quite interested in the M, let me know how it behaves in the practical scenario. Something should have changed in the latest build with the supersampling improvement. If you have some time to "waste" I would like to know how it is running now. Thanks

That's funny: why it deletes the files if it is on the exception list? Have you tried putting the whole directory to the exception list? Anyway, another version will be released today. I hope the problematic fingerprint is not present in the new one. You can do almost anything without the buttons, still, I strongly suggest to buy a pen tablet with buttons: it is much faster and who knows if something in the future will require them. Consider that active area is always noticeably smaller than the device size. Having a too small active area is worse than a larger device. That's why I choose the H950P over the Intuos S. BT latency is slightly worse then USB, but irrelevant in VRK. Anyway, the BT can be used in USB mode too. The reviews about latency are oriented to digital artists, they care about speed and latency. Cheers

I own the Intuos S, the pros: - good quality - tablet button are very well recognizable without looking (anyway on my Huion I put some tape close to buttons to recognize them) - BT/battery option the bad: - tablet buttons are very sensitive, it happens sometimes to hit them by mistake - cost is higher than Huions - "only" 4 buttons Pen operation is at par to Huions for VRK use. VRK is measuring the document size and try to match it, but the expected layout of the document is portrait. I had a document similar to yours and I split it in two. Also, the 9-line is best used into a "Form" tab.

I just tried with Kasperky VirusDesk (passing all the files contained in the installation) and it reports that no issues were found. This report may came from the heuristic engine of the AV, if you send me a screenshot of the AV message I can try to look deeper. As Gruman suggested you can add VRK to the ignore list and just use it. It seems an aspect ratio problem, can you share your original PDF with me? About the position, it's something I need to investigate: yours is not the first report on the pen/display offset. One little thing: when you use the Surface be sure to have WinTab disabled.

Hey Gruman, thank you, I thought later about the opportunity of posting in the input section too, but I'm not sure if forum policy allows cross-posting. Anyway if the tool will be good enough I think the voice will spread anyway by forum members :smilewink: Can you post a screenshot of the distortion you are describing? I can try to replicate the issue as far as I better understand the issue. In the upcoming 1.1.3.12 there will be the possibility to choose what side of the kneeboard to put the tabs (and the bookmarks) to better use the available extra space. Still, the distortion should not happen. The kneeboard is visible on SteamVR home also, so, you can position it without launching DCS. In 1.1.3.12 there will be the apply button on the config window to ease the operation. It seems that DCS is not starting in SteamVR mode, have you put/checked the option in the launch link? Is DCS showing in the SteamVR "Display Mirror" window? Two additional notes: - each time you close the config window with Ok, the seated position is reset, so keep the visor in a position compatible with your head when you press ok. (I will change this behavior soon). - if you look to the kneeboard from behind it will not show: I don't know yet how to make the overlay double-sided. I voluntary didn't put any button to go back to win mode to avoid hitting it by mistake (same applies for the upper toolbar that can be called back with Ctrl-Alt-T). The way it is supposed to go back to windows apps is to use windows button of your device. Then operate via windows taskbar. Is physical windows button available on the surface? Anyway it is easy to put a button to switch from fullscreen to windowed if this is not enough for usability. About pen tablets sizes it strictly depends on you and your cockpit. Bigger tablets are little invasive but I feel writing text easier. If you have space and on the side and you are tall enough it may be good. In my case (I'm 1.80m) the H950P takes almost the full length of my leg to the knee (see post #37). The other size is the Intuos S / H640P / HS64 which is very appreciated by the community. There have a smaller drawing surface but they also fits very well for strapping. My suggestion is to start with the small size. In the worst case you'll find writing less comfortable and you may switch to a bigger size (if cost is not a problem). Cheers

For Windows tablets with pen you have little options. Modern designs are too big and I don't know of any 8" Windows tablet with pen. Older models you may find used are: Asus M80TA, Dell Venue 8 Pro, Lenovo Yoga 2. There's also a Chuwi model but I can't remember which one it is. If you meant Pen Tablets, in the small size, you may look at: Huion H640P (6 tablet buttons) Huion HS64 (only 4 tablet but cheap) Wacom Intuos S (doesn't need the custom driver, BT option) All three models have already been tested. After testing both the windows tablet and the pen tablet I'm staying with the pen tablet because of some factors: - pen tablets are thinner, lighter and rougher - pens are usually bigger (with the exception of the surface pen) and better - touch is good, very good, but just for zoom, pan and page change. With some practice the pen tablet is good enough - pen tablets are cheaper and available on the market in various sizes and configurations - programmable tablet buttons - display is useless when you wear the HMD Generally speaking, my suggestion is that if you have to buy, then go for a pen tablet.

Version 1.1.3.11 is out [NEW] Custom driver for Huion pen tablets [NEW] Zoom Out function [NEW] Configurable delay in transition from focused to un-focused mode [NEW] Clickable page change buttons

If it feels "too low" you can raise it a little: - raise it by increasing Y value (unit is cm, reference is your head) - make it less horizontal by decreasing the pitch value (unit is degrees, reference is vertical)

Do you have Discord? It may be more interactive (and faster) chatting with us. In my understanding you are using Rift S and Surface + pen. Your steps are: 1. switch DCS from OVR to SteamVR mode (I already sent you some instructions) 2. install VRK in server-client mode and check that the kneeboard appears in VR by launching VRK If you complete both steps you just need to load a PDF doc in the surface and check that it appears in the VR, otherwise let me know where you stopped.

It feels good when a piece of code start working without tweaking. It tells you that you are on the right way :D So we cleared also the H640P. Today I'm waiting for the G640S because it is driving me and Shindawg crazy. Once this device will work too I will release a public version. There are some very good ideas coming from you guys!

You (and anybody else interested in the tool) may join the brand new Discord server https://discord.gg/mxqSSa4 I created a support channel for testing and technical support If you know a little about USB, I need the USB Product ID of your device. If not you can open a Windows Command Prompt and type: wmic path CIM_LogicalDevice where "DeviceID like 'USB\\VID_256C%'" get /value It will output a list of properties. I'm interested in the DeviceID. As soon as I have it I can build the driver and we can start testing to H640P ;)

Theoretically speaking it is possible to use DirectInput to share keyboard, mouse and hotas controls with DCS without disturbing the flight controls. This will reduce the number of keys/buttons,hats available on the controllers. It's long time I don't play with this thing + DCS and something may have changed. Anyway, other tools do the same thing so it is still feasible. The minimum amount of "buttons" required are 4 (page up/down and tab up/down), but it grows to 10 to support zoom & pan. Anyway, this can easily enter in the development slot of the VR Controller.

The idea is that, in the future, you will be able to navigate the documents with the VR controllers, but in my opinion this will take out the 90% of the purpose of the tool. This is a low priority for VRK because there are many other solutions that are already available like general purpose VR overlays and the DCS kneeboard itself. I'm pushing for the additional HW becuase it adds so much to the experience that it is worth the price.

Thank you! 1. The support is intended "per brand". There are some differences between devices BTW. Some are already covered in VRK, others may not work and other partially. I can't be sure until we test and that's where I need your help. I will support any device of the listed brands as soon as someone will test it and help me fixing. Anyway to summarize: Wacom: all devices supported via WinTab mode (Intuos S tested). No reason to think that other models will have problems. Huion: H950P supported and tested via Custom Driver. Other models may require a driver upgrade. I'm really interested in the H640P. XP-Pen: many of their device are already supported by the Custom Driver. G640S will be fully tested by the driver release date. My personal list of usable devices is: Wacom Intuos S - TESTED Huion H640P XP-Pen G640S - IN PROGRESS Wacom Intuos M Huion H950P - TESTED IMHO smaller or larger devices are poorly usable. 2. I use an aluminium kneeboard like: You can also use glue some elastic band with stretch to the tablet. I guess that there are many other options out there. 3. I use a pen loop attached to the stick base. The loop should be of large size (you may also build your own with an elastic band). Learning from real life you can use a pilot pen loop like: https://www.flyboys.com/fb1062.html Or use small magnets: glue one to the pen and another one where you want the pan to stay. Sometimes I put the pen between my leg and the chair. This final choice depends on your "cockpit" design. 4. It already works with any DCS module. Some of my squadron mates are using it with the Hornet too. 5. Yes there are tabs on the left side. In the "standalone demonstration" video you'll see me switching from charts to notes to 9-line form. Switching tabs is done either by clicking with the pen on the tab name or assigning buttons to the tablet

Exactly, I'm completely bypassing company driver and Windows HID (for those who know what I'm talking about).

Pages can be switched in many ways. 1. Using a tablet, when page is not zoomed, you can swipe up and down (also left and right) 2. Using a pen tablet with tablet buttons or gestures 3. Also with mouse scroller, but this is useless in DCS If you are starting from scratch, using a pen tablet is the cheapest way. Huion and Xp-Pen are around 40-60 euros. The custom driver is complete and I plan to release it this week. Wacom are more expensive. The choice on these three brands depends on you and how do you intend to use the tablet. Strapped on the leg the H950S (Huion) is big but still wearable (don't go for anything larger), smaller ones like G640S (XP-PEN) or Intuos S (Wacom) are more ergonomic, but writing is slightly trickier due to reduced active surface. Just click on the blue icon and VRK will download.

A little update about Huion and Xp-Pen tablets. After some days of mail back and forth with their (technical) support service, I had to give up with their WinTab driver! It was time to go lower level and completely bypass the Windows driver provided. Lucky me both brands (and others) are based on the same electronics so a single custom driver will do the magic. The custom driver will not allow to use the tablet outside VRK, but I guess the most of us will not need to. In that case a quick switch between the original and the custom is possible via Device Manager. Today I was able to fully use my Huion and with some polish and refactoring I'm pretty sure that both brands will be usable with VRK.