Ahdidaas

I don't want to muddy this discord w/ these n00b questions - I'll bullet point them.. Context: I like flying the A10CII, and will usually play whichever socal server has the most players - the radios are still mostly silent still - and if I see another A10 flying, I'll join that server. I'll go to a target location, the ground target status will tell me there's like 6-8 things for me to destroy, and I'll fly, fly, fly around, sometimes find someone hiding under a tree, yet sometimes I'll circle and circle -- or fly down super low for a better look -- and still not find anything. My n00b question - is it supposed to be that hard? I understand that the reaper circling high above can help me target (or maybe its the AWACS that's controlling it)? Is that true? How would I interact with them to find my targets? I'll go to an easy ground strike target location, flying 40 min to get there, only for it to be completed by someone else, and then I wait for another easy mission to spawn, and then that's 30min to the new one (which may cause me to backtrack). My n00b question - is there only one easy ground mission at a time? Can I go out and find my own mission? Or a different one even - for example I may spawn in Sochi yet have to fly south of Sokhumi for the mission - is it possible for me to go east and do something there? Thanks in advance!

I got the Wacom Intuos S for exactly this reason, and it works exactly how I hoped it would. I don't recall how much it was, it was cheap - I even when and picked it up at Staples. I recommend.

You can add the F1-F12 comm commands into the control *.lua profiles. This should be part of the default, in my opinion, yet if you add the below, you can then map those commands to any of your inputs: {down = ICommandMenuItem1, name = _('Command menu item 1'), category = _('General')}, {down = ICommandMenuItem2, name = _('Command menu item 2'), category = _('General')}, {down = ICommandMenuItem3, name = _('Command menu item 3'), category = _('General')}, {down = ICommandMenuItem4, name = _('Command menu item 4'), category = _('General')}, {down = ICommandMenuItem5, name = _('Command menu item 5'), category = _('General')}, {down = ICommandMenuItem6, name = _('Command menu item 6'), category = _('General')}, {down = ICommandMenuItem7, name = _('Command menu item 7'), category = _('General')}, {down = ICommandMenuItem8, name = _('Command menu item 8'), category = _('General')}, {down = ICommandMenuItem9, name = _('Command menu item 9'), category = _('General')}, {down = ICommandMenuItem10, name = _('Command menu item 10'), category = _('General')}, {down = ICommandMenuItem11, name = _('Command menu item 11'), category = _('General')}, {down = ICommandMenuItem12, name = _('Command menu item 12'), category = _('General')},

Exactly the same for me. I've yet to figure out a solid way for dealing with the controllers, using them to control my cockpit is real nice. they also control the external camera views nicely too.

+1 the pro is fantastic for exactly this.

Hi Friends, So I fly the A-10CII with a quest pro. I use the quest pro controllers around the cockpit to turn things on, etc.. Those that do this are familiar - there's a technique to using the controllers in DCS. You use the trigger as a mouse click, and you twist your wrist and it becomes right click. After plenty of hours playing, its quite easy for me to use that, and I don't have to use a keyboard/mouse combo. My problem is that when I arm the gun, the left controller's trigger button fires the gun. I've gone through the controls and have the oculus column completely empty for everything, yet it still fires. I'm at a loss as to why. Has anyone else had this situation and know a solution? Ty!

ty. turns out the defaults are perfect for me. 65 fps+, fully fidelity, on the TTI Socal MP servers. I love this!!!! VR ftw.. I can't imagine playing this game w/out it.

This is an amazing addition to DCS! It makes my immersion so fantastic to have so many settings ramped so high up! I do wonder if there are settings within Quad-Views-Fov that I should be changing? Out of the box support is terrific, so I don't mean to be asking for more, just trying to understand all the ins-n-outs of this awesome tool. Thanks again!

Over the last month to six weeks I’ve spent pretty much all my time in DCS messing with my settings. I watched numerous videos and ended up figuring out my pain points and solved them all. I’ve got a beefy gaming laptop, a RTX3080ti, and have a nice 40+ fps with no juddering. It took a while but I’m thrilled with what I got. I do love watching replays of my sessions, and recording bits, in 2D cause I can max everything. The immersion you get in VR, where everything is life sized, is amazing. I’ve dreamt flying these planes as a kid, and this feels real damn close to actually doing so. I do not regret the time and expense. feel free to hit me up for vr tips. I’ve tried most everything, so I know what works for me. razer blade 15, i9, RTX3080ti, 32gb, quest 2, now quest pro

I may have found it - I recently started running the Q2 on 90hz, getting a steady 45fps w/ aws. I changed it to 72hz (still getting 45+ fps), and played a 3 hr session with no issues. even taking it off to goto the bathroom. Not sure it applies to folks here, it worked for me (so far).

I may have found it - I recently started running the Q2 on 90hz, getting a steady 45fps w/ aws. I changed it to 72hz (still getting 45+ fps), and played a 3 hr session with no issues. even taking it off to goto the bathroom. Not sure it applies to folks here, it worked for me (so far).

I'm getting something similar. I'm using Airlink, and I used the meta quest developer hub to turn off guardian and proximity. mine crashes while playing, i'm not taking the headset off even. I'd love some advice here. Never had this problem before, seems to have started about two weeks ago. I even factory reset my gaming laptop to start fresh, nothing changed, I always crash around 10-15 min in the game. 2023-08-31 05:45:26.687 INFO LUA (Main): Lua CPU usage: metric: average game loading: 40.0621 % 2023-08-31 05:46:46.287 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1380, 1380] 2023-08-31 05:46:46.414 INFO VISUALIZER (Main): OpenXR: request restart 2023-08-31 05:46:46.414 INFO VISUALIZER (Main): OpenXR: request exit 2023-08-31 05:46:46.414 INFO EDCORE (Main): (dDispatcher)enterToState_:5 2023-08-31 05:46:46.414 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST 2023-08-31 05:46:46.416 WARNING LOG (18268): 1 duplicate message(s) skipped. 2023-08-31 05:46:46.416 INFO APP (Main): application shutdown 2023-08-31 05:46:46.687 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 0 2023-08-31 05:46:46.689 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 1 2023-08-31 05:46:46.689 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 2 2023-08-31 05:46:46.771 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 3 2023-08-31 05:46:46.835 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 4 2023-08-31 05:46:46.845 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 5 2023-08-31 05:46:46.847 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 6 2023-08-31 05:46:46.848 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 7 2023-08-31 05:46:46.848 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 8 2023-08-31 05:46:46.849 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 9 2023-08-31 05:46:46.849 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 10 2023-08-31 05:46:46.849 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 11

Yea, I tried two, and then airlink -- the log you see above is from the airlink'd one. This is the log from the airlink'd one. I was surprised how good airlink is, I always assumed... anyway, the airlink one has this? Haven't a clue what's happening here: 2023-08-31 05:45:26.687 INFO LUA (Main): Lua CPU usage: metric: average game loading: 40.0621 % 2023-08-31 05:46:46.287 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [1380, 1380] 2023-08-31 05:46:46.414 INFO VISUALIZER (Main): OpenXR: request restart 2023-08-31 05:46:46.414 INFO VISUALIZER (Main): OpenXR: request exit 2023-08-31 05:46:46.414 INFO EDCORE (Main): (dDispatcher)enterToState_:5 2023-08-31 05:46:46.414 ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST 2023-08-31 05:46:46.416 WARNING LOG (18268): 1 duplicate message(s) skipped. 2023-08-31 05:46:46.416 INFO APP (Main): application shutdown 2023-08-31 05:46:46.687 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 0 2023-08-31 05:46:46.689 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 1 2023-08-31 05:46:46.689 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 2 2023-08-31 05:46:46.771 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 3 2023-08-31 05:46:46.835 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 4 2023-08-31 05:46:46.845 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 5 2023-08-31 05:46:46.847 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 6 2023-08-31 05:46:46.848 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 7 2023-08-31 05:46:46.848 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 8 2023-08-31 05:46:46.849 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 9 2023-08-31 05:46:46.849 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 10 2023-08-31 05:46:46.849 INFO EDOBJECTS (Main): lTypeObjectManagerImpl::clear 11

I've been having the same issue as well - frequent crashing after ~10min in the game. I'm very concerned.. Razer 15, 3080Ti, 32GB, Quest 2 2023-08-31 05:18:24.512 WARNING LOG (5636): 4 duplicate message(s) skipped. 2023-08-31 05:18:24.512 INFO APP (Main): Device unplugged: \\?\USB#VID_2833&PID_0183&MI_00#6&12958148&0&0000#{f33fdc04-d1ac-4e8e-9a30-19bbd4b108ae} 2023-08-31 05:18:24.795 INFO APP (Main): Device unplugged: \\?\USB#VID_2833&PID_0183&MI_00#6&12958148&0&0000#{6bdd1fc6-810f-11d0-bec7-08002be2092f} 2023-08-31 05:18:24.869 INFO ASYNCNET (Main): Current ping: 13.2ms 2023-08-31 05:18:25.023 INFO APP (Main): Device unplugged: \\?\USB#VID_2833&PID_0183&MI_00#6&12958148&0&0000#{6ac27878-a6fa-4155-ba85-f98f491d4f33} 2023-08-31 05:18:25.087 INFO APP (Main): Device unplugged: \\?\USB#VID_2833&PID_0183&MI_01#6&12958148&0&0001#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b} 2023-08-31 05:18:25.154 INFO VISUALIZER (Main): OpenXR: request restart 2023-08-31 05:18:25.154 INFO VISUALIZER (Main): OpenXR: request exit 2023-08-31 05:18:25.207 INFO APP (Main): Device unplugged: \\?\USB#VID_2833&PID_0183&MI_01#6&12958148&0&0001#{dee824ef-729b-4a0e-9c14-b7117d33a817} 2023-08-31 05:18:25.295 INFO APP (Main): Device unplugged: \\?\USB#VID_2833&PID_0183&MI_02#6&12958148&0&0002#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b} 2023-08-31 05:18:25.416 INFO APP (Main): Device unplugged: \\?\USB#VID_2833&PID_0183&MI_02#6&12958148&0&0002#{dee824ef-729b-4a0e-9c14-b7117d33a817} 2023-08-31 05:18:25.516 INFO APP (Main): Device unplugged: \\?\USB#VID_2833&PID_0183#1WMHHB669T2096#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 2023-08-31 05:18:25.617 INFO Dispatcher (Main): Stop 2023-08-31 05:18:29.080 INFO TACVIEW.DLL (Main): End of flight data recorder. 2023-08-31 05:18:29.096 WARNING SCENE (14812): Scene was removed with 7 alive objects 2023-08-31 05:18:29.097 WARNING SCENE (14812): Scene was removed with 27 alive lights 2023-08-31 05:18:29.356 INFO TERRAIN (Main): lSystem::CleanScenes() 2023-08-31 05:18:29.366 INFO ASYNCNET (Main): messages tracked: 808166 2023-08-31 05:18:29.376 INFO VISUALIZER (14812): Stopped collection of statistic. 2023-08-31 05:18:29.376 WARNING SCENE (Main): Scene was removed with 4910 alive objects 2023-08-31 05:18:29.395 WARNING SCENE (Main): Scene was removed with 545 alive lights 2023-08-31 05:18:29.396 INFO VISUALIZER (Main): DCSScene initialized 2023-08-31 04:58:19.000 ERROR_ONCE (): 2023-08-31 05:18:29.782 INFO VISUALIZER (14812): DCSSceneRenderer initialized 2023-08-31 05:18:29.782 INFO EDCORE (Main): Create boot pool. 2023-08-31 05:18:29.804 INFO EDCORE (Main): Created boot pool: n:20 2023-08-31 05:18:29.941 INFO EDCORE (Main): (dDispatcher)enterToState_:3 2023-08-31 05:18:30.302 INFO APP (Main): Device plugged: \\?\USB#VID_2833&PID_0183#1WMHHB669T2096#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 2023-08-31 05:18:30.361 INFO APP (Main): Device plugged: \\?\USB#VID_2833&PID_0183&MI_01#6&12958148&0&0001#{f72fe0d4-cbcb-407d-8814-9ed673d0dd6b} 2023-08-31 05:18:30.419 INFO EDCORE (Main): (dDispatcher)enterToState_:5 2023-08-31 05:18:30.420 INFO APP (Main): Device plugged: \\?\USB#VID_2833&PID_0183&MI_01#6&12958148&0&0001#{dee824ef-729b-4a0e-9c14-b7117d33a817} 2023-08-31 05:18:30.649 ERROR_ONCE DX11BACKEND (14812): render target 'mainDepthBuffer' not found 2023-08-31 05:18:30.686 ERROR VISUALIZER (14812): xrEndFrame failed with error: XR_ERROR_RUNTIME_FAILURE 2023-08-31 05:18:30.687 ERROR VISUALIZER (14812): xrBeginFrame 14540.467561 failed with error: XR_ERROR_CALL_ORDER_INVALID 2023-08-31 05:18:30.687 INFO APP (Main): application shutdown 2023-08-31 05:18:30.692 ERROR VISUALIZER (14812): xrBeginFrame 14540.467561 failed with error: XR_ERROR_CALL_ORDER_INVALID 2023-08-31 05:18:31.764 INFO ASYNCNET (Main): disconnected: 0 2023-08-31 05:18:31.764 INFO ASYNCNET (Main): disconnected from server 2023-08-31 05:18:31.764 INFO ASYNCNET (Main): client has stopped I'd love any help or advice on what to do here. Just a month or so ago, I could play for hours and everything would be totally fine. ¯\_(ツ)_/

Are we all aligned that reducing the resolution for the desktop works? I tired this w/ both 800x600 and my native 2160x1440 and didn't see any diff in FPS. Where I did get an amazing increase in framerate (up to 90fps) was changing the FOV Multipliers (set to 0.71 for both horz and vert). I'm now able to run at max settings with a steady 45fps AWS - its completely changed my enjoyment!! So I'd like to confirm, does this actually make a diff?

Yea, I'm using the controllers to click around the cockpit. I like that I can use either hand this way. I'm trying solutions for where to put them so they're easy to grab when needed, and won't roll off to the floor.

I wanted to thank y'all for this post and thread. I was struggling with understanding the intercom panel, as I wanted to be able to talk to my crew w/ the canopy closed, and I felt the manuals were vague. Ty!

yes they are. and I'm not too proud to admit, it took me a way long time before I realized that's why I wasn't moving! fail one for me not reading the change log prior to playing the latest update. ¯\_(ツ)_/¯

Hi friends, So I use a Quest 2 w/ a TM-Warthog HOTAS. Its fantastic, I'm having a great time! One issue I have though is where to put the quest controllers when my hands are flying? I'd often just leave them in my lap, yet they will fall off eventually, dropping out of the chair onto the floor. I've tried leaving them tucked in between the hip and the chair, yet I have to be careful about the triggers on the controller. I've flipped the seat-eject-active button accidentally doing this. I've got a great cockpit setup, just can't decide what to do with these controllers. I've thought about just keeping one in my lap and using that exclusively, yet I do switch the hand I'm using around the cockpit, so that won't work. I'm curious what others do with their controllers while flying? -Jim (Guymn)

Is your squadron still running?