Koros

I found on the discord server that error -35 means the headset is not detected. In my case what it meant was Oculus was not set as the default openXR runtime. Just go to the oculus app on your PC and set it as default. In my case it's now working fine with beat saber, will try DCS when the update is complete. It also explains why DCS was launching in 2D windowed mode.

Hi guys, I am on DCS OB on Steam with an Oculus Quest 2. I followed the guide and everything was working fine until I encountered a crash with steamVR and I had to reinstall steam because it wasn't launching anymore basically. Now DCS is not working properly. Initially it was running steamVR. Now I did a reinstall of the WMRP and OpenComposite and it is now launching without steamVR but in windowed mode this time... It might be related or not idk but when I try to launch another VR game (e.g. beat saber) I get an error code -35 (see picture) Thanks for the help.

I figured it out. I'm sorry, the error was totally on my side . It appears the DCS forum and the DCS website are two separate things. I did not remember that. Still, thanks to you I realised this while trying to submit a support ticket.

Hi @silverdevil, you'll find attached my log file. Yes it is the same account and it is the correct credentials. I double checked by logging in on the forum. I also changed my password to be sure. I used the "save password" and "auto-login" before the update and it was working fine up until now. I tried to rename the DCS folder and let the game create a new one as you suggested but no luck... What is weird is I have a "Log out" option when I try to log in wether I use the correct or wrong credentials. dcs.log

Hi all, So as you can see from the title, I'm unable to connect to the DCS server after the last OB update on steam (2.7.14.23966). But there is something strange, it appears that I'm actually logged in. I have the "Log Out" option once I tried to sign in, even though it tells me "incorrect login or password" but I still cannot use the multiplayer. The "Log Out" restarts my game and allow me to try to reconnect again but then I'm at the same point again. I tried to check the files on steam, to go to stable, comeback on OB, with no success. My DCS install is around 170Go so I'd rather avoid downloading the whole thing again if possible. Am I the only one in that case ? I saw this problem already occured after some updates but nothing on the last one. Thanks for the help.

I think it only happens with the french 1995's faction.

Hi everyone, I recently changed my PC an made a clean install of DCS. I just installed the latest version of DCS liberation (5.1.0) but I have an error when launching the mission in DCS. Has anyone had this error before? What can I do? AFAIK, this error does not prevent the mission from running fine. I'm on the Steam OB version. Thanks, Edit: Liberation does not detect the end of the mission

Ok thanks for the info ! Btw i was on the 2.1.0 version and tried the 2.1.5. I'm not sure if it's a stable release but i found there were more bugs and instability but more importantly, it is detected as a Trojan and causes crashes so i'll stay away from this version and probably just Liberation 2.0 for now while hoping my pc is ok. I'm not saying this is a Trojan and dont think it really is but it is a "suspect behavior". I understand that it is probably linked to the way Liberation works but i didn't have this problem with the 2.1.0. Did it happen to anyone else here ? I'm using the zip version not the one with the installer btw. Edit: I don't want to scare anyone from using this great software but the 2.1.5 is unusable for me as i can't use anything on my pc when it's running, everything crashes. It is to note that this might have been caused by my antivirus to prevent any potential dammage and not by Liberation itself. Nonetheless there is a problem with this version (atleast for me). I hope you understand.

Hi guys, First, thanks for this mod i'm really enjoying it and the money management aspect is really cool. I see that someone already asked this but no answer sooo is it possible to add custom faction ? Thanks for your help.

Hi sublime, maybe that's the cause. What is the solution then ? I also tried TF-68-80 for the mig 21 and i have a problem with the GCI. The briefing says to tune to channel 0 but i can only hear my wingman, no GCI. Am i supposed to do something ? I didn't find anything but the awacs in the comm menu. I'm using the OB. Thanks for your help. Koros

Hey, i don't have this problem in TF-68-80s if i use the auto startup so i must be doing something wrong but since it's the first time i encounter this problem i don't know what lol With that said i don't think it's doing the TCN update position thing so that's not what i'm doing wrong. Does anyone have an idea of what the autostartup could be doing that i'm not and that could have and impact on alignment ? I noticed it uses the store heading but it doesn't work better for me. Edit: I followed the chuck guide and the Official early access guide but it didn't work I looked into the Macro_sequencies.lua and i don't see anything special. I don't understand

Check the installation PDF, it's probably because you made a mistake with the "saved game" folder location.

Yeah I did the same thing so i don't think it's related. Thanks anyway. There is also no GPS in TF-74 ? In TF-68-80s I was doing the position update with the WPDSG thing so if it's still the right procedure i don't think that's the problem but i'll double check this. Edit: I realise now that since the carrier is moving i should align with the Tacan procedure. Thanks for your help. Edit 2: I did the alignment with the TACAN but the problem persists. http://prntscr.com/ugfzzt

Hi guys, i'm playing on the stable release on steam (and also tried the OB version) and i have some trouble using CCIP and GBU/JDAM. The CCIP cross is always pointing toward the same heading. For example when i take off it's pointing heading 65 so if i go heading 135 the cross will be to the far left of the HUD so i will not be able to drop the bomb at the right spot. With the TPOD the target diamond on the HUD is to the right of where the TPOD is looking. I have the same problem with the ASL in CCRP. This happened in TF-74 and TF-68-80s in the Hornet. I don't know if anyone ever had this problem ? Thanks for your help