HoBGoBLiNzx3

Thanks for the info, I think more people are concerned with transparency than anything. The fact that I learned all of this from someone outside of their dev team speaks volumes. It's completely understandable that an immense task such as building a new engine from scratch takes time. It's also understandable from a developers perspective to not put themselves in a position where failure to deliver is met with a large communal scrutiny. That being said, being kept in the dark on progress will be met with even more. I don't think ED's work has ever really been questioned, or their intentions as a business. Transparency goes a long way, even when the outcome isn't favorable. I hope to see some sort of beta release soon, keeping the option to use the stable version we currently have. Is it safe to say that once open beta is released, they will likely have feedback much earlier from the plethora of programmers, developers, and modders that are a part of the community? Once it gets to that point, that is. While this all might seem like slight to them (if i'm projecting) the fact that people are antsy to use their work should be satisfying, and criticism welcome. As if there were none, people just wouldn't care enough to gripe about it.

Has anyone got the Quest2 companion toolkit menu working yet?

I apricate the information, just seemed very trolly and sumptuous. I agree, I think having the option for the briefing room would be cool too. In a lot of MP servers you don't wanna go though briefing and then start up just to get back in the air. However if they did something cool like setting up a preplan flight where a data cartridge would add everything so start up is quicker then I think that would be really interesting. Having a custom preplanned mission set that is easy on the fly and you can add groups/tasks for the mission. IE: a CAP/AG mission, assign waypoints, tasks, refueling points, starting time. Once it's finished, people can enter the brief and select one of the tasks for the mission until it's complete. All data will be loaded into those air craft that select the mission, including radio freqs, markpoints, target information, etc. Then you can arm, start, confirm weight and fuel for mission on deck, and boom you're off.

You don't know me or what I'd say.

lol did really just though all that trouble? All you had to do is say.. There are other threads about this topic.

Curious if there are plans for catapult weight confirmations to the green shirts to set the cat properly? Obviously failure to properly confirm weight will have concequences, also giving more deck hands animations and more direct interaction with the carrier crew. Any constructive thoughts on this are welcome!

Yeah, my initial log shows everything working. Loading up DCS etc. It only ran once though. I haven't had a log pushed out since. That's the thing, I can verify the install is done properly in multiple different ways but without knowing if the API is running in game. I think I should be able to check a console command or at least, run a log during a DCS session to find out.. so I'll wait for that info. Until then, business as usual. lol.

Haha thanks man, but I already have all that. I just need to know if there is a way to check the APi while DCS is running. I already know all the other stuff.. You don't need WMR though, it's not compatible with quest2 even though it's in part of the installation video,. Just openxr tools, toolkit, open composit, and I use skatezilla launcher to launch into in steam vr.. You can check in openxr tools what api is being used for openxr. It's quest2 with toolkit API layer. So we know all that of that is good. The issue of installation wasn't the hard part it's diagnosing if it's actually working when you can't pull up the actual toolkit menu... You're not sure if Openxr is actually running, even with all things active. There is no screen to tell you as such. For all I know, OC could be rejecting OCDSW.exe and booting into the quest2 api launcher and that is why the menu isn't working. Until I know how to actually check what api is running while in game, I can't be sure.

Thank you so much! I got it installed, changed the path to D for my install. Is there a way to check to see Openxr is actually loading? Currently I have the opencomposite ACC with ini file in bin, skatezilla set to launch steamvr. for some reason I had the opencomposite app working prior and DCS would come up and I could set it system wide but now I can't get it to pick up opencompositeDCS.exe So I just did it manually.. (I had the ini file in the bin, and even tried if it would pick it up with the manual files there but no luck) None of that will really matter as long as I can check the API and make sure it's loading. The only log from tool kit companion was when I initially ran it. It was successful and the openxr tools shows oculus with XR toolkit as API layer, demo works and all. Thanks for your help, I'm positive this will help LOADS of people as they are kind of left in the dust when they ask about the Quest2 install process. The structure makes sense however when features don't work it's hard to troubleshoot.

You're a golden god! Please do! I will definitely be doing this. This is huge for all amount of people who just can't get the display menu working! I currently only have 2 options besides the default key and module. Bypass and First run. I must be missing something...

I have mine active as per the log but can't get the menu to pop up. I never have been able to but apparently people have with it. Not sure how but... yeah.. I wish there was a .cfg file to configure out of headset but I'm guessing it's more complicated that that.

You do you SkateZilla you've contributed plenty to the community. I for one will be thrilled when you're able to finish it! Champagne will be on ice for first flight, with streamers and kazoos.

I don't know how to do a track, I have video but it's in vr mirror so it's hard to see. It happens for me every time. once you go into the submenu the text just disappears.. the button is still there and works..

I have everything installed.. Here is the thing.. is it launched this way? Quest2/standalone DCSlauncher (set to SteamVR) > Opencomposit runtime switcher (set to opencomposit) >>> SteamVR (steamvr runtime) or DCSlauncher (set to steamVR) > Opencomposit set to open composit>>> oculus (occulus runtime) <-- when I run this I get crashes and openxr tools wont stay open and crashes (conflict in runtime I'm guessing) It doesn't crash running though steamvr but steamvr actually launches it instead of on the oculus app.. if I set the oculus app to defualt I get crashes on game and tools. So i can't get it to launch out of steamvr without acutally loading steamvr, and if I do get i get crashes.. the closest I got was an openvr.dll error somehow. I've never been able to make it work.

Thanks for clarifying. It's a feature most DCS SRS users do not know about and the comms channels get flooded with jargon, didn't meant to post any wrong information, I must have misinterpreted it from the pilots that went over it on a tutorial.

Does anyone have a link or can they put up a link to share the F-22 Mod. https://fsoutlet.com/ is down and I'm not sure if it's coming up soon or not, but it would be nice if someone could host a secondary link that would be great

I gave up a while ago. I couldn't get the tools to open and the dev's didn't really care to help all that much. I don't understand why they can't make an OvGME version...

ahhh okay thanks! I was under the impression that all encryption ran through it. My apologies! VOCA/VOCB is a game changer in MP.... lol

Could you explain? I know the KY-58 is just a encryption device, I was unaware it didn't encrypt VOCA/VOCB channels. Granted it's not a UHF frequency but it should still also encrypt the Datalink channels no?

bumping this for people who are unaware of it. Make sure you have your KY 58 set to the on position the panel as well, and set to either P for Plain or C for encryption. I believe that if you are in C mode, and other are in P you will only get static as the channel needs to be encrypted in both ends.

This is still an issue. I recorded it last night. It's just not rendering the INV under the button, the actual button does work though.

That is so weird. If I install the toolkit and run the openxr dev tools it crashes once I change tabs and DCS wont start. It's only the openxr toolkit though... Everything else works.. So weird.

Thanks guys! Are any of you guys running OPENXR toolkit along side this? I can't get that to work it crashes DCS before even starting, likely cause I have openxr dev tools installed but right now openxr is running at least. lol

I'm on standalone beta. There is no guide for the quest and it doesn't work with WMR.. So using the DCS updater I have steamvr checked, opencomposite installed, I have devloper tools reading that quest is the set API and the demo works. Not running WMR portal either. If I download and install toolkit, it crashes my developer tools when I go click on any of the tabs, and DCS won't start. It crashes on start up. For Quest users do we need to delete Dev tools and install toolkit instead or? It would be nice to have a step by step install for the Quest2 as so many people use them and they have their own software. I ended up downloading 3dmigoto for OPENXR and it runs, and I can access everything, So I'm pretty sure OPENXR is running, I just can't use the toolkit, and it's what I want to use the most lol.

Openxr Toolkit crashes my MSOPENXR TOOLS (dev kit) if I uninstall toolkit, it works fine.. When I have toolkit installed, I can't pull up the HMD options regardless.... Any fix for this? I'm on a quest 2 with link, RTX2060, windows11, 32gbDDR4, i7-9700k I have opencomposite, I can load in to DCS even running the OPENXR version on 3dmigoto, use those in game options, I KNOW openxr is working, just can't get toolkit to run with it regardless (I've tried with and without mods)