shindawg

Hi @Sneep, I seem to be having an issue with this version. It will close almost immediately after it opens. Managed to grab a screen capture before it closed and it wasn't showing any errors. Renamed the dcslm.json to see if a freshly generated version would help, no joy. Have 7-zip installed Rolled back to the previous version and all is good Cheers

Big +1 from me as well

Scratch that, no sooner had I posted the above, I found my solution within the examples of the dcs-bios-arduino-library. RotaryAcceleratedEncoder DcsBios::RotaryAcceleratedEncoder ufcComm1ChannelSelect("UFC_COMM1_CHANNEL_SELECT", "DEC", "INC", "FAST_INC", "FAST_DEC", 19, 18); Work a treat!! Cheers

HI, I've been trying to setup a rotary encoder and I'm currently seeing it increase/decrease by 4 channel numbers each detent. I was thinking this might be a bouncing issue as it can be a little erratic, but as there seems to be a function to change the steps per detent, I thought I would give that a go first (grasping at straws as I don't know if this is even related or would fix this issue) Each of the examples I've found though fail to compile Examples: DcsBios::RotaryEncoder<2> ufcComm1ChannelSelect("UFC_COMM1_CHANNEL_SELECT", "DEC", "INC", 18, 19) DcsBios::RotaryEncoder ufcComm1ChannelSelect("UFC_COMM1_CHANNEL_SELECT", "DEC", "INC", 18, 19, 2) DcsBios::RotaryEncoder ufcComm1ChannelSelect("UFC_COMM1_CHANNEL_SELECT", "DEC", "INC", 18, 19, DcsBios::TWO_STEPS_PER_DETENT) Current sketch line: DcsBios::RotaryEncoder ufcComm1ChannelSelect("UFC_COMM1_CHANNEL_SELECT", "DEC", "INC", 18, 19); Current dcs-bios library: dcs-bios-arduino-library-0.3.5 If I look in the Encoders.h source file I can see that the capability must be there, but I can't seem to work out where I'm going wrong. I'm not very experienced with writing sketches, so I'm sure I'm doing something wrong. Any help or a simple kick in the right direction, would be much appreciated Cheers

Hi ya Thalvid, When setting up tacan between fighters you need to maintain a channel seperation of 63. The below link will give you some background. Though written for the A-10 it should be the same for other NATO aircraft https://www.mudspike.com/how-to-use-the-air-to-air-tacan-in-dcs-a-10c/ Excerpt below is taken from the linked article "The trick to know here is that when you set a TACAN channel, you’re actually setting two different frequencies: a transmit frequency specific to that channel and a receive frequency that’s 63 MHz higher. TACAN channels are spaced by 1 MHz between channels, so setting a radio to a channel 63 higher than the transmitting aircraft (77X in our example) will mean you’re tuned to that’s aircraft TACAN transmissions. This is why the transmitting aircraft should be a channel between 1 and 63, so the receivers can tune to 64-126. The channel selected needs to be the same X or Y, as these represent completely different frequency sets, and the same TACAN mode (A/A T/R) needs to be selected to enable range calculation." Cheers

Hey Zetrocker, using standalone, and confirmed using actual device and that it's working. I thought for a bit that there was some conflict between my Logitech cam which has a mic, but this has now been removed. News flash: I was able to get it working this afternoon. The example adds possibly to something trying to claim my headset mic. Senario: 1. Loaded voice attack and confirmed I could both receive audio and transmit through my headset 2. Loaded DCS and lost both audio reception and couldn't transmit. 3. Restarted voice attack and test again; to my surprise it worked. I'm not able to test anymore tonight, but this result is more then I had before, so I'm encouraged. I'm not seeing any errors within voice attack Cheers Sent from my Pixel 3 XL using Tapatalk

Oh - I also forgot to mention that I reset the export profile as well and removed everything else from it leaving only Viacom in there

Hi @MAXsenna, thanks for the tips, gave me something else to check. I can confirm that my VIACOM profile has the "send commands to this target" set to Active Window. I even loaded a fresh VIACOM profile just to make sure it stayed the same. I also might not have been very clear the last time, when I said I could see the keypresses (meaning MIC actions). The is being passed to voice attack fine (tuned in-cockpit radio is being picked up) while it's behind the game. The only part which doesn't happen while voice attacks is minimised/behind the active game is the voice commands are not being passed through to voice attack. Its almost like my mic is being hijacked by something else in DCS, which is why I asked about the DCS built-in chat feature. Anyway thanks again, its appreciated; I'll keep digging around for a bit longer and then maybe give a re-install of my headset drivers and voice attack a go. oh, this only seems to affect voice attack (viacom) I can still use SRS and other chat programs like DISCORD fine. really confusing me this one Cheers

Voice commands not working when voice attack does not have focus Hi Guys, I'm not even sure where to start searching for a solution on this one, I've never had an issue before now, and I've run out of ideas. For some reason, I can only get Viacom/voice attack to recognise any commands when it has the focus in-game, that is it's being displayed on top of the current game; when it is it works flawlessly. As soon as its no longer in focus (behind the active game) nothing works. I can still see the key presses, but it's not registering the receipt of any commands, almost like my mic on the headset is also losing focus of the application. Its been a while between games and the last time I played the chat settings in DCSD were not a thing. Have there been any reports of this new DCS feature messing with VIACOM? Cheers

If the update which got installed was KB4515384 uninstall it. This update has been proven to mess with a number of things, including network cards, sound cards etc. I was getting a similar issue where SRS was throwing an error because it couldn't find or load the audio driver. Removing the update fixed it for me, as well as stop a DCS crash I was having. Sent from my Pixel 3 XL using Tapatalk

Hi All, some pics and thoughts from my journey’s with VRK. First off, a big thank you to Rider the creator of this amazing piece of software and a great guy. I went with the option of using a pen tablet for the same reasons Rider has already described, • Size options • Weight • Ease of use • Price My aim was to have something which would be as close as possible to what you would use IRL, and for this, my foundation was an actual pilot’s kneepad strap You can get these from most local pilot supply shops, I’ve included the product link as a starting point. Pricing is pretty good at around $40 US. In my part of the world slightly more at $60 AU https://www.flyboys.com/kneeboards.html The pen tablet I’ve gone with is the HS64 by Huion https://www.huiontablet.com/huion-hs64.html You can get some great deals on Amazon for about $40 US The writing area dimensions of this sweet little tablet match almost perfectly with the kneeboard I’m using, with the buttons extending (in my case as a lefty) over the edge slightly. It is limited to only having 4 programmable buttons (some others have 6 or more), but for what I want it’s just perfect. The top 2 = TAB Up/Down The bottom 2 = PAGE Up/Down The space left in between makes for a nice wrist stabilizing area while I write something Now let’s assemble You can remove the clipboard from the kneeboard strap (the one on the right), what I’ve then done is use some Command M3 picture hanging strips and applied to both the back of the clipboard and Pen Tablet https://www.command.com/3M/en_US/command/products/~/Command-Large-Picture-Hanging-Strips/?N=5924736+3294529207+3294737318&rt=rud Once you've joined the two parts together, you can then use the clip part of the board to fasten it in place to the kneeboard strap (pic is of the underside of the kneeboard strap) Lastly, a couple final pics showing it all together, and one final one which was using my initial choice the XP-PEN G640S as an example of how it could look using a tablet with the buttons on the top. XP-PEN G640S Note: At the time of writing this, the G640S is currently not supported by VRK, so don’t buy it What else can I say except this application is revolutionizing the way I fly DCS in VR, both as a mission and training tool. Hope this helps people make the right decision for them. Have fun and safe flying shindawg

Hi baco, If it hasn't been mentioned already, make sure your using something like notepad++ to make any changes. Normal windows notepad will tend to add extra characters to the file which would corrupt the file. Cheers Sent using Tapatalk

[emoji106][emoji106] Sent using Tapatalk

If you haven't done so already, double check you key mappings just incase something's changed. Cheers Sent using Tapatalk

You only need it on the machine you're HMD is connected to. Cheers Sent using Tapatalk

Hi Rider, loving the app, works great using a surface. I did love your WinTab option more after reading about it and decided to make this the direction I would use due to the smaller footprint offered and cost (I'm In AUS). The product I chose was the X-PEN G640S, which was a good price at $45. Unfortunately and like the Huion its severely lacking in the driver department and doesn't allow an application-defined passthrough option for the pen and tablet short cuts, which is disappointing as it does pass them through without the driver installed, but doesn't allow me to then adjust the orientation of the tablet 90deg so it sits better on my leg and of course you loose other required options to make it work as desired usign VRK :( I'm currently compromising by allowing windows ink which is a driver setting I can use to control the pen and tab shortcuts. Doing this at least gives me an eraser/pen option selection on the pen itself and I can scroll using the tablet shortcuts. by making the zoom setting in the cockpit a little more extreme it compensates for the most part not having a pinch-zoom or gestures pen capability. I've also reached out to X-PEN support to see if they are able to include an application-defined function in the driver, but I was wondering if it would be possible to add a key functions capability to VRK? What I mean by this, is being able to use a key combo to select a feater like gestures etc (same as you would if using an application like photoshop), as this is something I can program in the driver options. Anyway, just thought I would pass on my findings in case anyone else was looking at the X-PEN option. Great app and something I will continue to use more and more as it matures Cheers

Went through the same crap with iiNet and after 4 days of me and a mate getting stuffed around we both moved ship to Aussie broadband. Smooth sailing since.[emoji869] Sent using Tapatalk

If this helps, its only affecting me when using Microsoft edge. When I do, i get the maintenance message as well as not being able to connect using the local webgui. As I normally use chrome i wasn't seeing this, so became curious. Cheers

Nice one [emoji106] The white lettering looks great Sent using Tapatalk

Not necessarily. The 3rd party is most likely developing the module for DCS under licence from Eagle Dynamics anyway. This could deem the module as shared IP, as the module was developed for the sole purpose of use/sale from within DCS. It could be reasonable to expect that full access to the module is released to ED if the third 3rd party leaves. This would be more so, if the module makes use of ED game engine specific code. Of course I'm no expert, and in reality it's usually way more complicated then this simplistic opinion [emoji16] Sent using Tapatalk

Nice pickup TechRoss, fixed it for me as well; I do have the Harrier though. From what I can see its probably due to there not being any code written for the harrier to get exported, which could be causing the BIOS.lua to hang?? No expert, so i'm probably way of track.

Thanks Andrew, I'll continue testing tomorrow as I seem to have developed the same issue as TechRoss a few post ago, where I can't seem to initiate a comms connection. If I use a control it records what has been done in the command window, but as there is no active connection does nothing. The live browser plugin confirms this as well. Funny thing is, even going back to the original version, is having the same issue. Putting down to me and the machine being tired, so maybe a rest will create some magic tomorrow. Thanks again for the great F-18 addition to this fantastic software. Cheers

Using a rotary encoder for the UFC channel selector Hi Andrew, I'm using a rotary encoder for the UFC channel selector, mainly because it also has a nice momentary button function as well. It does work, however only in one direction, it either INC only or DEC only. I've also performed a test using the browser interactive plugin and i'm seeing the same result. /* UFC */ DcsBios::RotaryEncoder ufcComm1ChannelSelect("UFC_COMM1_CHANNEL_SELECT", "-3200", "+3200", 2, 3); Just wondering if this is something that hasn't been implemented yet. Or, and most likely I'm doing something wrong. I have validated the wiring against the encoders single line wiring diagram as well I've only just started my journey down the pit building path, so I'm sure I've messed something up or need to read up on something, so any advice appreciated. Cheers Shane Oh, in-case anyone is wondering the UFC design I've used was created by the wonderful Brun in this thread https://forums.eagle.ru/showthread.php?t=218874. I'm stoked with how its turned out so far using a single Arduino Mega

Here is one which has already been setup to use a mod manager https://www.digitalcombatsimulator.com/en/files/3300689/ and here is a link to the mod manger I use. works a treat https://forums.eagle.ru/showthread.php?t=171956 cheers

Order placed, so excited for this. Sent from my Pixel using Tapatalk