scuba82

Although in VR, I'm exporting several viewports to individual monitors. To restrict the mouse pointer to the dimension of my main screen, I use the "VR-Mirror" directive. However, having this option set, Kneeboards are no longer displayed correctly in VR. When activating the Kneeboard the Kneeboards border, as well as the change page buttons are visible, but there is no content within the border. At the same time the Kneeboards is correctly displayed on my main screen (VR-Mirror). If you need any logs or screenshots I would be happy to help.

Not exactly what you're asking for but there's a fork of DCS-BIOS which enables the wifi functionality of esp32 MCUs. https://github.com/pavidovich/dcs-bios-arduino-library . With it DCS-BIOS (on esp32) can comunicate over Wifi only so there's no need for an USB connection or port forwarding via socat.

@Tonester thank you for mentioning the "Input Command" thing... In my case the "Input Command Injector" Mod from Quaggles was causing the issue. After uninstalling the mod and repairing DCS the menu works as expected. I've totally missed that there is an updated version of the MOD available which solves the issue and totaly works with 2.8.

Maybe already reporter: the Axis tune menu seems to be broken. By klicking in the button, while having an assigned axis selected, the Menü doesn't pop up... at least for me..

Yesterday evening a tested the deadzone on the "not sticking axis" and can confirm that even that solves the issue for me on the warthog throttle along with the deltasim slew stick upgrade. So to summarize the issue, we have no clue why this is happening but have come up with two possible workarounds: 1) Set a small deadzone on the non sticking axis 2)Set a cure >=9 on the center position of the non sticking axis @Roastie@Ramsay thank you for your tests

Funny... you seem to have discovered the same thing but come up with an inverse solution to mine... That seems to partially negate my hypothesis... I have to test the bigger deadzone with my setup as well to see it also does the trick... I've also noticed the "stickiness" of the cursor when it's locked to an IR source but guess that has nothing to do with initial issue of not beeing able to slew in one direction.

Thanks for testing and sharing the video ramsay. Gonna investigate further on this and maybe also try some other input sources.

The slew sensor upgrade seems to be too good/precise for the harriers IRMAV cursor . There seems to be a bug where the IRMAV cursor won't move in vertical directions while there is no input on the horizontal axis at the same time. With the original TM slew sensor this behavior seems not to be that obvoiuse, since it's much harder to keep the horizontal axis still while moving the vertical one. I've posted my discoveries in this thread Slewing problem with IRMV in Harrier and would highly appriciate if someoine could test it too and give a short feedback if the issue occures for you at all respectively if my workaround solves the issue.

I did some more investigations on this topic and I think, now I know what's happening and maybe have found a workaround... First at all, it seems to be a general issue which not only effects the deltasim ministick but is more obviouse with it. What I've found: The IRMAV cursor slews perfectly in horizontal directions but wont move at all in vertical direction, if there is no input on the horizontal axis at the same time. I've tested this with TDC horizontal/vertical inputs beeing bound to two sperate analog axis on potentiometers. While having the horizontal axis centered, the vertical doesn't move. (Maybe you could also reproduce it with the TDC horizontal input not bound to any physical device?). Giving just a slight input on the horizontal axis allows the vertical one to move freely. That seems to be, why the issue is not that obviouse with the default TM throttle slew sensor, since it's really hard to move only one axis there, without interfering the other one. While with the deltasim stick you can move one axis while the other one stayes still in center position. This may also explains the "jumping" of the cursor... If you try to move in vertical direction (nothing moves) and suddenly give a small pulses on the horizontal axis, the cursor seems to jump. With this hypothesis, I tested again with the original TM slew sensor and yes, the vertical axis is also is behaving the same, but it's harder to reporduce because of the above mentioned reason. My workaround(?): I've slightly modified the TDC horizontal axis curve, to be much more aggressive in the center spot. (see screenshot) Now the slightest touch on the deltasim ministick results in a minimal output on the horizontal axis. The output is not big enough to move the cursor (internal deadzone?) but allows the vertical axis to move. I would highly appriciate if someone, effected by this issue, could test my workaround and give a short feedback, so we could push RAZBAM in the right direction on how to solve this.

Same Situation here, any news in this topic?

You can start DCS in an "non-vr Mode" With the following startpatameter: Create a copy of DCS shortcut, and change its target to: "C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" --force_disable_VR Thus was you don't have ti Change your Settings.

Hi, I noticed a weired behavior with the key bindings, while using the two rotary switches for RSBN and PRMG channel switching. By default these switches are mapped to the keyboard letters "U" (increase) and "LSHIFT + U" (decrease) for PRMG channels as well as "Y" (increase) and "LSHIFT + Y" (decrease) for RSBN channels. However, hitting "U" or "Y" once, doesn't change the channel. I have to do it multiple (4-6) times to increase/decrease one channel by 1. Furthermore I noticed that pressing and holding one of these buttons increases/decreases the channels constantly ... one channel each ~1 second. I'm guessing there's some kind of internal timer, kicking in each "X" ms and watching for a key/button press? The same behaviour seems to be true when using jostick buttons mapped to these functions. Using the mouse let's me click through the individual channels just instantly. I double checked the behaviour with the radio channel rotary switch and there, it reacts as expected: One keypress /joystickbutton press changes the radio channel by 1. I would highly appreciate seening this fixed cause I'd love to use two physical rotary switches in my home-pit for the RSBN/PRMG channel switching.

My framerate droped down to ~15 fps when i jumped Into the mossie for the first time today in Normandy. After a reboot i got steady 40-45fps again. Maybe there was some prerendering going in when i started the bird for the first time? As said, at the Moment everything looks fine ( pimax 5k, rtx 3070)

For sure it is . As my wingman an I both own your campaign I thought it should be possible to fly the Coop Missions together on a dedicated server. Initially i thought maybe only the .crypt File was Missing on the Server that didn't work either. Meanwhile i found out, it's possible to start a standard dcs Installation with the Parameters "--server --webgui" . This way the Coop Mission seams to start fine while the server ist still remote controllable.

Hi, Is it possible to Host the Coop Missions on a dedicated Server? I tried to, but ended up with error Message : " mission not authorized". Even on a standard DCS Installation startet with Options "--server --norender" the mission would not load. Only by starting a server from within the gui menu I was able to load it.