AMVI_Rider

If you are using the "Reload last layout" just go to C:\Users\<your_username>\VRK and remove any .vrkl file you find. Otherwise you have to clear the configuration in C:\Users\<your_username>\AppData\Local\Vrkneeboard\<whatever>\1.2.3.5\user.config But please keep anything you remove so I can check what is happening later.

You can User Oculus Mirror which is the equivalent of the SteamVR mirroring function. You can find it in: C:\Program Files\Oculus\Support\oculus-diagnostics\OculusMirror.exe Frankly I don't know why they are confining this tool in the "dignostic" domain.

Version 1.2.3.05 is out Most important news is the official release of the Oculus native support! This and other features required a deep rework of some common parts and some bugs may arise also for SteamVR users, so, please let me know if something is broken.

https://www.anandtech.com/show/13446/the-quiz-on-cpu-0-playing-scheduler-wars-with-amds-threadripper-2990wx It is a 1 year old article, but gives some explanations about the cpu0 ...

Some days ago I decided to upgrade my MB BIOS and I started experiencing some problems of microstuttering and buzzing noise every some seconds. I did a quick search on the forum and tried almost anything "recent" on the matter but with no success (mouse update, hot-plug disabled, ...) I'm pretty sure that the BIOS update was causing the problem so this evening I started playing with power profiles and CPU priority/affinity. Many comments about microstuttering found on internet were referring to core parking and the need of disabling it by selecting the High Performance power profile for the CPU ... not in my case. I then installed Process Lasso and tried playing with process CPU and I/O priorities, nope. I then ended with manually selecting the CPU affinity and noticed that by just deselecting CPU0 in the affinity the problem disappeared. Note that doing the same with any other CPU available had no effect. The video below demonstrates how by simply deselecting the CPU0 solves the problem in my case, but I'm really puzzled. Note that instead of the buzzing sound OBS is capturing silence, so, the stuttering is less evident, but still noticeable also in the images. I'm posting because it may help someone else, but I'm also trying to understand how just CPU0 can affect the sim in such a way. My system is a Ryzen 5 3600x (6c/12t) - 32Gb 3200 C14 - X570 AORUS Pro (BIOS F11 - 1.0.0.4 B).

I just updated my BIOS (and DCS in the same day) and the sim started to stutter, sometimes with buzzing sound, every few seconds. I know that AMD changed something in the microcode to "better" support frequency scaling. I will look further into this thing, but it's worth to start playing with CPU boost settings, affinity, SMT and stuff like that. My specs are in the signature. MB is a Gigabyte X570 Aorus PRO, BIOS is F11 (AGESA 1.0.0.4 B) coming from F4i (AGESA 1.0.0.3 ABB) edit: I found some interesting clues playing with the process affinity. This seems not related to this thread and I'm opening a new one.

Shouldn't. It's a long shot, but it may be due to some "configuration" stored in the tablet which has been erased when you disconnected the USB... Anyway, so far so good.

Have you changed anything on the system? Did you upgrade VRK? The code to emulate clicks with the pen time hasn't change since very long time. Now I have a change to be tested which should improve this behavior.

It was happening in the very first versions, but I fixed it long time ago ... It may be a regression. I will test it tonight as soon as I get home!

I'm going slightly on the edge of this topic, but since you asked about Oculus, XP and VRK: I have two outstanding problems: one causing the sim to freeze and another just a little annoying, but the most is working.

As Gruman pointed out, VRK is designd to run anywhere, but let me go a little technical.... If you have a SteamVR visor everything should work out of the box. If you have Oculus you should care about what 3D API are used. Xplane 11 is OpenGL, P3D is DX11. Pre-release Oculus support is for DX11 (tested with DCS only), but I have OpenGL already drafted. I'm using Xplane too, so it will be easy to test it. Planned by the end of this week. TL; DR yes, but you have to wait a little for it (and that's why I didn't announced it on XP forums yet).

Xmas is coming for Oculus users Habu_69, I took note and I will do a debug session for the client/server as soon as the Oculus implementation will be released.

With normal I guess you mean either Android or Apple ... short story I have no plan to implement them right now. I moved the "tablet" implementations to low priority because everybody using a tablet (me included) opted to buy the graphics tablet. Usability is much better and the cost is not much (and you don't risk to destroy your tablet). Other features seemed more important for the user base. VRK works with any version of DCS (also with any SteamVR software). Oculus implementation is progressing ... I made it show into Oculus demo application, DCS is still complaining but I'm tracking the problem.

Yes, you can use the "Forms" tab (second from the left).

Focus factor enlarges the sensitive area to enter the focused mode Go to post #177 for more details

The problem with OculusVR is that it doesn't support external overlays at all. That's why the most of the overlay tools require SteamVR to run. To be able to "inject" the kneeboard, I'm putting VRK in between DCS and Oculus APIs which Oculus made as difficult as they can. Moreover Oculus does not support any means of "virtual" headset so I can only test things when I'm home (nights and weekends when I'm not travelling). Everything is already in place, but I'm debugging a problem that I hope to fix in a matter of days. The rest should be straightforward.

Yes and no.... You have to use SteamVR (aka OpenVR), the VR API of Steam which can be installed from Steam interface. This doesn't mean that you have to use Steam version of DCS, but just to force DCS to run in StamVR/OpenVR mode by means of commandline parameters. Also, I'm actively working on the Oculus Native implementation to get rid of all this and improve performance to Oculus user. Version 1.1.3.19 is out Changelog: [1.1.3.19] [NEW] Custom Focus Logic [NEW] Pan & Zoom functions

Native Oculus is still in progress. As it's taking more than expected (also because of personal things) I decided to merge and release some requested features. Also, it will be good for me to have people testing the Custom Focus logic before releasing the big thing. I just forgot to add that the upcoming version will contains the pan and zoom functions for supporting pen-less installations.

As a subproduct of the work done for the native Oculus implementation, I'm about to release an upgrade containing the custom "focus" management and the possibility to enlarge the detection area. You will find four more parameters in the configuration to set the detection area factor for width and height targeted to focused and unfocused mode. The factor means the 1.0 is 100%, 1.3 is 30% larger and so on. This should be enough for the most cases. Also, the detection now is far more responsive. As I'm about to close this version, if you have some bug to notify, please let me know!

I noticed you post just after clicking submit to mine. In the last few days I was absent in the forum and you're giving me the opportunity to share the reason. As you may have noticed from my avatar, some days ago during AMVI annual workshop we lost Ruggero (Rugerone). He was a friend, a father and one of the most experienced pilots I have ever met. This tragedy hit our community deeply and doing anything related to sims is difficult if not painful. I'm personally starting to go back to usual lightweight activities like reading posts and VRK development. Thank you for reading this post and sharing a thought for his family.

Seems that DCS is still not using SteamVR which make me thinks that you are not starting DCS with "--force_VR --force_steam_VR" options added to its link. If you don't or you are not sure, I suggest you to make a new link to DCS.exe, open its properties and add the above options as described in the Quick Start Guide. Added to the TODO list.

The popup area is not definable because it is controlled by SteamVR. The API provideS the indication if the user is looking at the overlay or not. Of course it can be custom implemented and it is something I have to do anyway for the Oculus ... it will came for free also for SteamVR.

The mouse is bound to DCS, the kneeboard is added later in the visualization process by the VR so there's no way to use it without grabbing the focus from DCS. Looked at the numbers and I noticed some performance loss too, probably had more margin to compensate. Other pilots are reporting the same. In the last few days I tried several different approaches and today I finally made the injector work. Now I need some more days to have something visible because, with Oculus, I need to be home to test: no virtual HMD is supported and my laptop is not VR ready. Frankly it's out of the radar for me. I don't have experience in developing for Apple and the costs involved are not helping. Also, the usage of msater/slave is dropping because pen tables are more ergonomic. I'm using the 950 and left the Intuos S for other purposes. I like the larger size. The buttons of the Intuos are easier to find, but I improved the situation by putting some pieces of tape to mark recognizable spots. "Muscle memory" does the rest. Never tried the Intuos M.

Do you mean the capability to add a desktop window to the "dash"? Or did I missed something? In this case this way there's no control (from VRK side) over position, size, opacity and the "focus" feature. Oculus is really making this thing difficult. I'm finding plenty of demonstrations that they keep the framework close on purpose. I'm starting to regret spending my money on their HW!

It is 2.1 but I moved the Development stage form RC to Release 2.1.1 is Beta 2.1.2 is RC 2.1.3 is Release I know it was public ... still I use these stages to remind how much I feel confident about the code :smilewink: https://en.wikipedia.org/wiki/Software_versioning#Designating_development_stage