orbir

I switched to Virtual Desktop too. I reported to Meta as well, but it was progressing slowly, my ticket is closed now, due to lack of time commitment to their requests on my part. They were quite responsive, but I didn't have time to do what they requested in a timely manner. If any one of you have any time to go through Meta customer support process, please do.

I am getting quite big memory leak in Meta Quest Link app (Quest 3) while playing DCS. After 30, 40mins more than 90% of 96GB gets used and eventually something gives up... The screen shot is taken while playing the "Intercept" mission on Caucuses in a F86. Happens with other planes too, tested with F-5E, A-10CII. Full (slow) repair didn't change anything. DCS Version 2.9.14.82222 Meta Quest Link App Version 74.0.0.675.347 (74.0.0.675.347)

Jan 16th is the preorder date. It will enter to early access in a couple hours/days/weeks/months. After 5+ years in early access, the video will still have lots of frames missing especially in the last minutes of it. The frames we have access to will have missing or wrong-colored pixels etc.

Yes it only affects clients. AI aircraft refuelling reported as expected.

When I select the "F-16C" filter in the "Campaign aircraft" @Reflected Simulations "F-16C Arctic Thunder Campaign" doesn't show up. i.e. "https://www.digitalcombatsimulator.com/en/shop/campaigns/filter/aircraft-is-f-16c/sort-is-date_desc/apply/" When F-16C is selected, Reflected Simulations count reported as 0 (see MissingF16-C-Reflected.png). Also, when "Reflected Simulations" is selected as the filter, the F-16C campaign shows up but "Campaign aircraft" filter F-16C is disabled and reported as 0 ((see MissingF16-C-Reflected-1.png)

Tested again with DCS 2.9.9.2280. Is there any other info required?

Here is a mission that replicates the issue for me. Tested with following 3 different runs: Single player => Everything seems normal. Event fire as expected, with correct initiator (i.e. F-14A) "Launch Multiplayer Server" => Events fire as expected but the tanker starts at ramp rather than on runway although set runway start in ME. Standalone server Refuel events fire with the wrong initiator (tanker vs F-14A) Only if I refuel to full a refuel stop event is triggered with a F-14A initiator. Tanker starts at ramp even though ME is set to start on runway Only one basket is extended when on pre-contact. I don't know whether it is a problem, just different than previous 2 runs. The correct messages should read "[REFUEL TEST] (Main): F-14A started refueling." or "[REFUEL TEST] (Main): F-14A stopped refueling." But as seen from the following partial log, standalone server reports the tanker as the initiator. 2024-09-27 02:40:00.803 INFO Scripting (Main): event:type=refuel,initiatorPilotName=KC135MPRS,t=1028.179,initiator_unit_type=KC135MPRS,initiator_object_id=16777473,linked_event_id=0,event_id=16,initiator_coalition=2,initiator_ws_type1=1,initiatorMissionID=1, 2024-09-27 02:40:00.803 INFO APP (Main): wcTanker::onEvent:6 2024-09-27 02:40:00.803 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:4 2024-09-27 02:40:00.803 INFO [REFUEL TEST] (Main): Shell 1-1 251 1Y started refueling. 2024-09-27 02:40:03.822 INFO APP (Main): wcTanker::onEvent:9 2024-09-27 02:40:03.822 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:5 2024-09-27 02:40:40.402 INFO APP (Main): wcTanker::onEvent:10 2024-09-27 02:40:40.402 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:4 2024-09-27 02:40:40.402 INFO Scripting (Main): event:type=refuel stop,initiatorPilotName=KC135MPRS,t=1067.778,initiator_unit_type=KC135MPRS,initiator_object_id=16777473,linked_event_id=0,event_id=17,initiator_coalition=2,initiator_ws_type1=1,initiatorMissionID=1, 2024-09-27 02:40:40.402 INFO APP (Main): wcTanker::onEvent:8 2024-09-27 02:40:40.402 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:3 2024-09-27 02:40:40.402 INFO [REFUEL TEST] (Main): Shell 1-1 251 1Y stopped refueling. 2024-09-27 02:42:11.139 INFO Scripting (Main): event:type=refuel,initiatorPilotName=KC135MPRS,t=1158.515,initiator_unit_type=KC135MPRS,initiator_object_id=16777473,linked_event_id=0,event_id=18,initiator_coalition=2,initiator_ws_type1=1,initiatorMissionID=1, 2024-09-27 02:42:11.139 INFO APP (Main): wcTanker::onEvent:6 2024-09-27 02:42:11.139 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:4 2024-09-27 02:42:11.140 INFO [REFUEL TEST] (Main): Shell 1-1 251 1Y started refueling. 2024-09-27 02:42:14.151 INFO APP (Main): wcTanker::onEvent:9 2024-09-27 02:42:14.151 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:5 2024-09-27 02:43:36.010 ERROR ASYNCNET (9332): HTTP request dcs:server:update failed with error 16: Error in the HTTP2 framing layer 2024-09-27 02:43:36.014 ERROR ASYNCNET (Main): Server update failed with code -16. The server will be unlisted. 2024-09-27 02:44:33.440 INFO APP (Main): wcTanker::onEvent:2 2024-09-27 02:44:33.440 INFO Scripting (Main): event:type=refuel stop,initiatorPilotName=Fluke,t=1300.816,initiator_unit_type=F-14A-135-GR,initiator_object_id=16777474,linked_event_id=0,event_id=19,initiator_coalition=2,initiator_ws_type1=1,initiatorMissionID=2, 2024-09-27 02:44:33.440 INFO EDCORE (Main): (wcTanker::Channel)enterToState_:1 2024-09-27 02:44:33.441 INFO [REFUEL TEST] (Main): F-14A stopped refueling. 2024-09-27 02:44:33.441 INFO EDCORE (Main): (wcTanker)enterToState_:1 nevada_refuel.miz

Would you consider renaming config zones, so they are grouped together in the Zone List to make them easier to find and identify? Below I just added "_" at the beginning, but something like "Config autoCSAR" would work too.