dutchili

Thanks for the help. The ACQ settings helped for a target at my flight level, but not for a bogey at 7000 ft while i was at 30000ft, bogey was hot. Also still lost PDT on my wingman while he was constantly flying at 30000 ft.

In this track I loose the primary data link track to one of the targets for a reason I do not understand. Can somebody explain? I also fail to lock the Mig 29 that is right ahead of me. Can somebody explain? radar targets not shown.trk

I would like to bump this topic again as all new viper features are missing in the manual.

What happened here? I was tracking the IL-76 when all of a sudden i lost the radar track. When I re-acquired the lock the IL-76 was far more to the left compared to the moment where i lost the track. It appeared to me that the E3 data and my own radar track were inaccurate. Later in the mission I try to lock a MI-29S to shoot it with an AIM-120, but i cannot get the lock quickly with the radar so rely on the AIM120's own radar. Did i you do things wrong? ...tried to update the track but it was over 5 mb...

Oculus support wrote: Thank you for reaching out to Oculus Support. I understand that you are having issue with the graphic performance of your apps while connected via Oculus Link . Rest assured, I'll be here to assist you. I appreciate you providing details about your concern. In line with this issue, I would advise in following these troubleshooting steps: Temporarily disable the Airlink feature on your Quest 2 headset and computer then connect your cable. This 2 can normally cause conflict with each other. Check if the headset is connected to a USB 3.0 port. Re-seat the cable on the headset and computer. Please also inspect it for any damage. Make sure to update your GPU and USB to the latest version. For additional information, please click here. Opt to our Public Test Channel for the latest update and fix. You can click here for the instruction on how to opt in. The Oculus headset does use USB power and bandwidth from your PC. If your PC's USB is being worked to capacity, this can potentially cause the kind of issue that you've described. To help check if this is happening, please try the following: Unplug all USB devices from your computer except for your keyboard, mouse, and your headset. Plug your headset USB cable in to the back of your PC, not the front or anywhere else. Disable USB Selective Suspend Setting: right-click Start click Power Options click Additional Power Settings click Change plan settings click Change Advanced Power Settings find USB Settings make sure that Selective Suspend Setting is set to Disabled, not Enabled Ensure that USB power saving settings in Windows Device Manager are not enabled for your USB ports: right-click the Start button and open Device Manager find your USB ports right-click and select Properties go to Power Management make sure that options to save power are deselected (please note that it is normal that some of them will not have any checkbox for power saving settings). Once all that has been confirmed, please restart your computer. Meanwhile, if the issue persists, I would like to ask for a copy of your Oculus log file so we can review it for the possible cause of the issue. You can follow the steps below in order to do so: Open the Run window (Windows key + R). Enter and run: C:\Program Files\Oculus\Support\oculus-diagnostics\OculusLogGatherer.exe The above link is the default directory. Bear in mind that if you installed Oculus Home to another drive you will need to update the command with the correct file path. Select the checkbox next to ‘Full logs’. Select "1 day" from the "Collect last" drop down list. Wait for the log collection to finish. This can take some time to complete. The program will automatically generate a zip file containing your logs, which will be saved to your desktop automatically. Attach the newly created zip file to your next support response. Looking forward to hearing back from you with the results.

Ocuclus support send me a procedure to resolve the issue, which involved things like unplugging every USB device and resetting the computer. It did not sound like a solution, but it was. Back to normal 'no stutter' performance. +2 for Oculus Support, as this is the 2nd time they resolved an issue for within 24 hours.

Thanks @Flappie. I am using only the software from the manufacturers. When trying Virtual Desktop with SteamVR this particular issue seems gone, but general performance is worse. That's why I suspect it to be an Oculus/Win11 issue that occurred due to a Windows update. I have filed a support ticket with Oculus and will report back if then solved it for me.

Hi all, This is not an issue related to DCS (i think), but you guys must experience it too and might know a solution. Since about a week I have a lot of dropped frames (a few every second) as soon as I establish the Oculus LInk (wired or wireless). The issue is visible even before starting a game. The Oculus performance overlay reports dropped froms from the app and compositor. I did not have the issue before. Oculus software version 38 on windows and device NVIDIA driver 512.12 Windows 11 (i am afraid something change here through auto updates). Any help?

Just a question: should i give a radio command to my wingman if i want him to start bombing? (mission is configured as 'perform task'>bombing from a certain waypoint. The last time i tried the wingman did not start bombing after the command 'execute mission, then rejoin', or something like that.

Fps also drops when flying a f16 and looking at an Apache, even when it is not yet visible (Oculus 2) MP is a drama now, while non Apache single player mission improved.

Incorrect track in 17 march 2022 release of OB. Track shows the Viper (me) backs right before the merge in this head-on dogfight scenario. In reality i banked 'over' the SU-27. You can see me shooting and mark-pointing the crash location, but the SU is doing other stuff that 'never happened'. track not synched.trk

I can get direction, but not distance. Indeed broken.

It was unclear to me how the viper was responding to my commands. Previously it was just doing exactly what is explained in the video by Wags. Now it doesn't.

then there is a bug when switching from RWS to TWS

@BIGNEWY: - noted: one topic onluy - What is the normal behavior when switching from RWS to TWS? Should track remains visible or is scanning required?

Do you know if CCIP is also reported? I can't find the latest on that. I experience inaccuracy in both cluster and non-cluster bombs.

@frederf Thanks for your reply. I watched your track. I noticed you make a 45 degree bank instead of 90 degree bank. I tested this and it helps to maintain track in RWS. @moonshine I am afraid you are right, because: - an immediate switch form RWS to TWS does not make the target re-appear on the rader screen in this scenario - switchting from RWS to TWS with the nose pointing directly at the targets, range > 20 nm, does not show targets - in TWS with targets visible, TMS right, sometimes have no effect until seconds later (>3 seconds) It is either buggy, or the radar is not really supportive of the pilot.

1) 3 targets visible on RWS scan (1 left, 2 right) 2) turn right into 2 bandits 3) switch RWS to TWS with the intention to create sytems targets for the rights bandits - expect targets to remain visible / appear after 1 scan - reality: targets are not visible on radar screen when pressing TMS right to lock al system targets, they appear out of nowhere some time later as system targets with one bugged target. radar targets not shown.trk

it's not that i suspect a bug, more a question if the F16 turns into the wind at takeoff

I tried to replicate storm Eunice :), but ran into something unexpected. 10 m/s crosswind from the left at takeoff. On the runway the jet was turning left, where I was expecting it to drift right. is this normal?

Wow, this made a huge difference for me in multi-player, which is now without FPS drops compared to single player! Keep it up ED!

I don't know anything about the internals of DCS, but when my GPU suffers when more planes are 'in game' while i cannot see them, and the CPU has a bore out, i know our experience can be much better. Same thing with FPS being dependent on the network in multiplayer. Vulcan, multi-core, multi-threading, i don't care what is needed as long these 'issues' are addressed. Such a great game, such a pita sometimes

Amy news @Flappie?

@Flappie: thanks for confirming. Please have a look at the manual for comparison. Beside the blurryness, the aiming cross is also an issue. The manual states: "Use the TQS cursor to place the target within the crosshairs on the WPN format, then press TMS forward to designate the target. The crosshairs will close on the target. Confirm that the missile is tracking the correct target, the pointer cross is not flashing, and that the target is in range." It doesn't seem to work like that anymore. The aiming cross is not 'open' so i can't 'place the target within the crosshairs'. Even if i could see it. In previous version, i could acquire the target at about 7 to 10 miles, now it is 2 to 3.

Found the button to make the screenshots. Reproduction steps to create these visuals: start in flight select A-G select WPN on left MFD leave mode in VIS scroll marker on HUD to target area press TMS up ....see almost nothing ....many attempts with TMS up to lock the target. Pointing 'the middle of the screen' works best, but without the crosshairs it is very difficult. Image 'mav mfd' shows the initial situation. 3 horizontal lines. Image 'target not visible' shows how difficult it is to see the target (FOV was pressed) Image 'cross gone' is the result of TMS UP short (top horizontal line gone, no aiming cross, no lock) Image 'misaligned' shows what happens when lock is obtained after repeatedly trying to lock, knowing where the target should be. Track files shows it all mav issue.trk