goldleader

Also with this bug once you join an airframe you cannot leave the second seat of an airframe and go back to spectators as you never left spectators when you entered the seat, to leave you need to enter a pilot seat in a different airframe then click back to spectators

That is odd, just ran it as Admin and had no crash but earlier tonight ran it twice as normal user and crash after between 10-20mins both times.

Is anyone having the issue when running XRNecksafer that after about 15-20 mins a windows BSOD with PAGE_FAULT_IN_NON_PAGED_AREA DCS OB Standalone, Native OpenXR, HP Reverb G2 Running XRNEcksafer with normal privileges, should it be run as Admin?

Yeah that is what I thought but wanted to get confirmation if it is a bug or correct behaviour.

All the Desync fixes and little QOL updates today are great, just have a question related to the UFC. Tacan, ILS, Waypoint, Radio all now synced and is great, at present if the WSO selects the R Alt to show on HUD using the Data page and button 9 on the UFC RAlt shows on the HUD Repeater in the back seat but not on the HUD itself, is this correct behaviour or just not synced yet?? Loving this module, looking forward to all the additional things yet to come.

Yes, that would be optimal, but also having it save the position separately for each airframe/cockpit would be good. but a good start would be a file where we can change the values simply and would probably not need too much coding, basically you would need the kneeboard position, size and opacity within the current file system to reference the new kneeboardconfig.lua file and place said file in config folder of saved games.

Currently in the Saved Games\Config folder there is a LUA file to set the position of BDA, Chat, Voice Chat and if used SRS, would be great if ED could utilise a similar file in saved games for kneeboard size and position, although it probably is not that simple due to legacy code and such.

I am having the same issue on 2 Instances on the Same Box, People can connect to SRS but DCS Server is not showing in the Master Server List

Start with this post and follow the thread for a little while and it will give you the info you need to run MT with the old app. as Kaltokri said the new one is coming, but we do not know when and we should leave Skatezilla in peace until he releases it.

This looks amazing, thanks for all your hard work over the years, remember starting to use this back in its original days and it has been very beneficial since. Hope everything goes smoothly with your recovery and do not stress about getting this finished before you are properly recovered, as much as we want this new and improved app your recovery is more important.

Having the same issue with 64Gb of RAM and a 2080Ti

@Hollywood_315 Do you know if there is a solution to this?

Hi, I believe Ramp 21 has already been reported for AI issues, but it also causes player aircraft allocated there to spawn in mid air, as does Ramp 51 also at Al Dafayr.

Yep I am aware the Pilot has the -159 but the RIO has ARC-159 Volume and Display Brightness and these binds are functioning properly. Full Radio is ARC-182 as you say, Volume Binds do not work.

The Default Keybinds in the RIO Pit for the ARC-159 seem to be fine, but the Default Keybinds are broken for the ARC-182 With the ARC-182 the increase and decrease keybinds seem to control the Squelch switch on or off depending on where you put the Radio Volume If Radio Volume (using Mouse) is above 50% both keybinds turn the Squelch On If Radio Volume (Using Mouse) is below 50% both keybinds turn the Squelch Off

Thank you so much for confirming it is not just my rig. :thumbup:

As per Jabby's Post The Default Keybinds in the RIO Pit for the ARC-159 seem to be fine, but the Default Keybinds are broken for the ARC-182 With the ARC-182 the increase and decrease keybinds seem to control the Squelch switch on or off depending on where you put the Radio Volume If Radio Volume (using Mouse) is above 50% both keybinds turn the Squelch On If Radio Volume (Using Mouse) is below 50% both keybinds turn the Squelch Off Video Attached showing that I do not have anything bound to the Squelch switch I use Num 0 and Num . first to change the volume of the ARC-159 Radio and all is well. Then I use Num 1 (Decrease Volume Keybind) for the ARC-182 with the volume below 50% and the Squelch goes off, then I roll the Volume up above 50% and use Num 1 again and squelch turns on Then I do the same thing but using the Num 2 (Increase volume keybind) and the squelch switch goes off below 50% and on above 50%.

I have done some more testing and completely re installed Both OB and Stable and I am still getting the same thing on both versions OB with all modules and VR Scratchpad, VAICOM, SRS and TacView all installed and a brand new Stable install with only the A-10C and Persian Gulf Map installed, with none of the companion apps installed (Tacview, VAICOM, SRS, VRScrathpad etc...), but it only occurs with the following settings Terrain Object Shadows - Default Shadows - Low or Medium would you be willing to change your shadow settings and do another video if you have the time to spare, I would greatly appreciate it if you can.

Thank you for that, good to know it is either something on my end or VR related, now if I can work out what is causing it. More testing required.

So I noticed while ago that this was happening but have only just had a change to report it. I am getting some very strange things happening with shadows, I mainly noticed it in VR as this effect on the shadows happens on the peripheral of the extremities of the sides of each eye, but on further investigation it happen in 2D as well, it only happens when Terrain Object Shadows is set to Default but nonetheless it happens in both VR and 2D. I experimented with turning MSAA on and adjusting the Mask Size in VR options, but this had no effect in either 2D (As I expected it would not) and VR. I am running no mods, earlier today I deleted the following folders from my install and ran a repair and cleanup just to make sure it was not something related to that and also for another reason. \Eagle DynamicsDCS World OpenBetaBazarshadersmetashaders \Eagle DynamicsDCS World OpenBetaMods errainsPersianGulfmisc \Eagle DynamicsDCS World OpenBetaMods errainsPersianGulfshadingOptions \Saved GamesDCS.openbetafxo \Saved GamesDCS.openbetametashaders2 Both Videos were taken in the Persian Gulf Cold and Dark A-10C Instant Action mission In this very short video recorded of my VR Mirror, hence the lower quality, you can see the shadows changing as the camera pans left to right, lok at the two beige hangars to see it best This video is longer and shows that there is a very peculiar shape seemingly affecting the shadows This is also present in Stable and I deleted the same folders (But in the Stable Game Folder) and also did a repair and cleanup and similar results. My question is is this a bug that is being seen on other peoples installs or is there something I can do to fix this if it is just on my machine. Screenshots are ingame settings when videos were taken, the only setting that made any difference was terrain object shadows to either off or flat.

I had a feeling that would be the answer, :( I found a workaround which while not perfect will suffice. Have just mapped two positions that are most used to those encoders, not perfect but will do.

So here is one for you... I have built a button box with several rotary Encoders which I am hoping to use for a number of dials in the A-10C. Most of them are working as planned, but I am having trouble with some of the binds that are of the type multi-position_switch_limited The example below is from clickabledata.lua for the A-10C and is the UHF Radio 100Mhz and 10Mhz dials. elements["PTR-ANARC164-100MHZ-SELECTOR"] = multiposition_switch_limited(_("100 MHz Selector") , devices.UHF_RADIO, device_commands.Button_2, 162, 3, 0.1) elements["PTR-ANARC164-10MHZ-SELECTOR"] = multiposition_switch_limited(_("10 MHz Selector"), devices.UHF_RADIO, device_commands.Button_3, 163, 10, 0.1) Based on that I would think the operation of both would be the same the only difference apart from the Button number and Argument Number as expected is the number of arguments. from the default.lua in the joystick folder you have these binds already {down = iCommandPlaneUHF100MhzSelector1 , name = _('UHF 100Mhz selector switch 1'), category = _('UHF Radio')}, {down = iCommandPlaneUHF100MhzSelector2 , name = _('UHF 100Mhz selector switch 2'), category = _('UHF Radio')}, {down = iCommandPlaneUHF100MhzSelector3 , name = _('UHF 100Mhz selector switch 3'), category = _('UHF Radio')}, {down = iCommandPlaneUHF100MhzSelectorA , name = _('UHF 100Mhz selector switch A'), category = _('UHF Radio')}, {down = iCommandPlaneUHF10MhzSelectorDec , name = _('UHF 10Mhz selector decrease'), category = _('UHF Radio')}, {down = iCommandPlaneUHF10MhzSelectorInc , name = _('UHF 10Mhz selector increase'), category = _('UHF Radio')}, as you can see for the 100Mhz Selector you have a bind for each position but for the 10Mhz dial there is a bind for Increase and Decrease, which when I bind them in game they work as I expect, each click of the encoder increases or decreases the digit by 1, but I cannot find a way to make the 100Mhz selector work in the same way. I have tried the following but all that happens is the encoder changes them between position 1 and position 2 (In Pit values of 2 and 3 respectively) {down = 3002, cockpit_device_id = 54, value_down = 0.1 , name = _('UHF 100 MHz Selector Increase '), category = _('Button Box Special')}, {down = 3002, cockpit_device_id = 54, value_down = -0.1 , name = _('UHF 100 MHz Selector Decrease '), category = _('Button Box Special')}, I cannot find anyway to make the button press increase the value by 0.1 instead of send the value of 0.1 if it is possible. Any and all help would be appreciated

Don't forget there are two bindings for the Autopilot Engage disengage 1. AAP Engage/Disengage which is default bound to the A key and the Black button on the warthog throttle next to the Autopilot mode three position switch (ALT:ALT/HDG:PATH) 2. Left Throttle button which is default bound to the Q key and the Red Pinky button on the front of the left throttle handle AAP Disengage/Engage (A) is not functioning as designed, Left Throttle Button (Q) is functioning as designed quick fix is to bind both buttons on your hardware to the Left Throttle Bind in the game.

Hi, I don't know if this will help but this is my Export.lua using TacView, DCSBios (Facepanels Version) SRS and VAICOM, I found that the order in which everything goes in the export.lua makes adifference, I am not sure why mine works in this order, but everything is working like this. local dcsbioslfs = require('lfs'); dofile(dcsbioslfs.writedir()..[[scripts\DCS-BIOS\BIOS.lua]]) --BIOS = {}; BIOS.LuaScriptDir = [[C:\Program Files\DCS-BIOS\dcs-lua\]]; BIOS.PluginDir = [[D:\Users\Matt\AppData\Roaming/DCS-BIOS/Plugins\]]; if lfs.attributes(BIOS.LuaScriptDir..[[bIOS.lua]]) ~= nil then dofile(BIOS.LuaScriptDir..[[bIOS.lua]]) end --[[DCS-BIOS Automatic Setup]] local tacviewlfs=require('lfs');dofile(tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[scripts\VAICOMPRO\VAICOMPRO.export.lua]]) -- load the DCS ExportScript for DAC and Ikarus local dcsexportlfs = require('lfs'); dofile(dcsexportlfs.writedir()..[[scripts\DCS-ExportScript\ExportScript.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Tech\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil); Also I did notice you have local twice before the tacview line in your post of your export.lua Hope this is of some help

Hopefully this has not been asked before too recently, but 429 pages of messages to go through is a lot, so apologies if it has. Havinig a minor issue in the Huey while using SRS, if I set the SRS setting "Use DCS Cockpit PTT" to On everytime I press any of my Viacom keybinds my SRS Radio latches on, I have tried a few things but the only thing that seems to resolve it is turning that setting off, it only seems to affect the Huey Module, but I would like to be able to keep that on, as Intercom has just been implemented and I would like to use the two seperate PTT buttons (RADIO and ICS) for their dedicated purpose and use Vaicom without broadcasting everything on SRS.