Jump to content

AMVI_Rider

Members
  • Content Count

    189
  • Joined

  • Last visited

Everything posted by AMVI_Rider

  1. It happened to me and it was caused by the relocation of the sim directory using NTFS Junction which worked flawlessly for years. In my case C:\Sim was relocated into D:\Sim and the junction took place of C:\Sim. The solution was to launch the updater from the real directory ( D:\Sim ) and not from the linked one. Sorry for posting in he english here, I hope the fix will work anyway
  2. There's a bug that causes VRK to show only Blue infos. IT is already fixed and will be delivered with next version. I can't find a proper way to deliver a good mouse experience. As you already know "capturing" the mouse will make DCS unresponsive to flight controls, on the other side getting mouse events "in parallel" can lead to unwanted clicks in DCS cockpit. The middle-tier solution is to use DCS scratchpad to take text notes and have them displayed in VRK.
  3. No beacuse as soon as VRK tries to probe SteamVR, it completely starts and probing is necessary to be done at VRK startup
  4. A little follow up: the latest version (V 1.4.3.07) contains the fix for the memory leak which was part of SteamVR code. I stopped posting changelogs here, but you can find them in the Discord server or GitHub release. Regarding FS2020 is highly likely that SteamVR will work day 1. Given the design of the sim I think that injecting Oculus into it will be very hard (harder than DCS and others). Time will tell, but, again, I'm very disappointed to see how closed is their API (compared to SteamVR).
  5. The S Bluetooth can be used also in USB mode. Latency and disconnections may be resolved by putting the BT dongle closer with an USB extension or hub (if you are using an USB dongle).
  6. There is no on/off option for the 2nd kneeboard, but you can do it by: setting the Width to 0 for the one you want to disappear and Active Kneeboard Switching mode to Manual.
  7. You should not poiunt the DCS_Updater exe but the DCS exe which is in the bin directory. Mind that you should launch DCS_Updater manually from time to time to let DCS update. It is possilble with the old 1.2 version which is not supported anymore => No new features Generally speaking I advise to avoid tablets because because of the weight, thickness and the value of the device. I already hit my tablet several times against the desk/stick mount and the risk of scratching/breaking the display is real. The Surface, in particular, is more expensive and generates some heat (per repor
  8. To enlarge the are in which the kneeboard becomes active (and changes it size) without moving the kneeboards you can use the Default Focus Factor for Width and Height. My settings are 1.3 for Height and 1.1 for Width.
  9. The .20 complaining about "wrong" hook is because the script has been upgraded to support briefings. Probably a better wording is needed there. Just going into configuration and "Install hooks" will upgrade the script (maybe better wording there also). If you open the hook script which version do you see? To debug this I need a log, if you don't mind loosing the settings you can erase the profiles forlder ( C:\Users\<win_username>\VRK<Profiles ) and it will revert to a working state. Gnerally speaking: I'm in the middle of a product release, so I'm a bit overloaded of
  10. There are some things you can check 1. check how much RAM is used by VRK. Latest version improved a lot the RAM usage but since VRK moved from 64 bit you can go well beyond normal RAM usage without noticing if you load many pages documents 2. avoid leaving your pen over the tablet: this will cause a constant triggering of kneeboard refresh 3. check you video RAM usage. Stuttering sometime happens because of that. Removing VRK is just freeing some video RAM improving the running condition Generally speaking VRK is designed to not interfere with DCS: if you don't move the pen VRK doe
  11. If you are upgrading from 1.3.3.07 (included) or newer you can just install the new version and your setting will be there. Mind the size change, that's something you have to change manually. If you want to be sure, make a backup copy of: C:\Users\<windows_username>\VRK\Profiles Panther suggestion is the way. If you have Cougar MFCDs you can map VRK brightness control to brightness/contrast/sym/gain switches. That's convenient and saves precious tablet buttons.
  12. Version 1.3.3.20 is available for download This version contains a number of relevant new features and fixes. It should have been called 1.4, nonetheless it is an important step forward. Over the previous release the big one is the HW acceleration for the renderding. It brings the pen-to-VR latency down improving the feeling and the writing. This feature is a big change and may have some side effects. In SteamVR flickering has already been reported and already partially resolved At the current state it should not be annoying (if not, please report again). DPI scaling has been fixed,
  13. Things changed in the config due to various new features and sometimes the quick start guide is not promptly updated. In this respect I think I've fond the proper equilibrium and I don't expect big changes anymore (except for new feature of course). To answer some more questions: - Tablets (and specifically Ipads): I left the tablets options because of the lack of sustainable use cases. I know many of you already have tablets, but it is a huge effort to support both worlds and everybody that tested the tablet (at the time) then quickly moved to the pen tablet. I know that someone may wa
  14. Hello guys, I try to answer all your questions in a single post... The kneeboard not loading has been reported. I will investigate as soon as I finish the performance improvement campaign. Sadly OpenVR didn't liked the HW acceleration technique which is giving so good results. In theory it shouldn't matter and I'm investigating why. The image distortion is fixed and will be released with next version. For the moment stay with 1:1 aspect ratio or be patient. I have the old installer for the client / server and I will add the link as by tomorrow for anybody interested. In any case con
  15. Version 1.3.3.16 is available for download This version is mostly dedicated to bug fixing. Changelog: [1.3.3.16] [FIX] Wintab doesn't register strokes starting with light pressure on tip [FIX] Tablet events routing causing multiple actions and wrong target kneeboard [FIX] Image aspect ratio [FIX] VR Toggle not properly restoring [CHG] VR Toggle global effect [NEW] Oculus: option to disable sim launch on profile load [NEW] Support for high res images (do not scale down to VRK resolution) [NEW] Maximum zoom increased to 16x Official download location: https://www.amvi.it/downlo
  16. I've just released a version that fixes your problem (was a known bug)
  17. That's Fox Delta video, anyway, the tab on the left are documents which are create for any document you "add" to the kneeboard (notes, pdf, directory...). On top there are Bookmarks. You can rename them by just right clicking with the mouse. To change the location (left, right, top, bottom) there are drop down lists in the VR tab of configuration. As per DCSMP I already started F-16, but VRK is taking most of my free time and it's slowly progressing.
  18. Thank you! Well, to be hones I forgot to add a function to cycle bookmarks. The PREV/NEXT Tab is used to cycle trough "documents". I will add it in the current dev version ( 1.3.3.18 ). I take the opportunity to give a little insight about the 1.3.3.18. It is mostly around performance optimization and tuning: I notice that the current version is not rendering at a very good framerate. The latency pen to VR is higher than I expected. Going deeper I found that rendering into offscreen surfaces (that's required to support supersampling) is done in software mode causing the CPU to struggle i
  19. No, but it has already been fixed in the test version (1.3.3.16). That's why Fox Delta (which is testing) doesn't see the problem anymore. If you want to join the testing, go to VRK Discord and look in the test-version channel.
  20. Hey, no worries. When users push to get things working it is always because they found the tool valuable. Frankly I still don't get why you need to push so hard while I can keep my settings so relaxed. I'm not sure if you are following on Discord, but I have published there a test version that should fix the pen problem for Wacom. I'm not sure if it will fix the sensitivity too. Can you try it and give me feedback?
  21. I've just found an issue there that happens if you start the stroke with a very "light" tip pressure. In this case the stroke is not drawn, also if you increase the pressure later and this can cause also the joint letters problem. Confirmed to be a bug, easy fix in the code. What doesn't add up is that, in my case, I had to press with the lightest touch I was able and never happens with a normal pressure. This must have something to do with tip sensitivity in Wacom Tablet Properties or my unit (I hope not). Here you can find my settings, can you share yours?
  22. I'm trying to reproduce the issue, sorry for the troubles. In he meanwhile you can revert to 1.3.3.07 by running the setup (no need to uninstall). You will have to remap the table physical buttons. @epolta it this happening to you too?
  23. The input system changed a lot because both 64 bit (the Wacom WinTab SDK was not really ready for 64bit) and multi-tablet support. The problem is to understand if it is the hysteresys that is causing problems or something else. I own a Intuos S and tested personally, so, it may be just something into your configuration (VRK or tablet). Can you sent me the logs (C:\Users\<windows_username\>\VRK\Logs) via PM or email? I will check if everything is ok.
  24. Hi, I guess you are using a Wacom tablet (which is the one that is causing this problem to some users). You have two solutions: Lower the Tip Feel in the Wacom Tablet Properties (Wacom configuration uility) or Enable the Relative Buttons mode in VRK. The first is preferrable because it keeps the hysteresis logic enabled in VRK (which prevents boucing clicks on kneeboard buttons), the second is the last resort.
  25. Probably something happened during conversion. There is no info on the manual because the work exactly like stick buttons: when the cell becomes red, you have to click the tablet (or pen) button. If you still have problems we can also continue on Discord and maybe start a remote troubleshooting session. I wonder why your old config hasn't been converted automatically.
×
×
  • Create New...