tribbin

Multiple people were successful with my instructions:

Re-installing now lets you end up with v63, since yesterday.

It seems it was presumed that people could just disable the updates as a workaround...

Meta is informed: https://communityforums.atmeta.com/t5/Get-Help/PTC-v63-DCS-crashes-on-Link/m-p/1160636

Done that, but there are no pictures. I already tried to search for common image-file magic-numbers in the files (to see if they are embedded) inside the track files but there are no images in there. It seems only the moment of the camera-shutter activations are recorded. Similarily to how it does not store the video of you flight, but only the data about nagivation.

OK guys... I got it working. 1. Download the folders on this guys Google Drive: https://www.reddit.com/r/dcsworld/comments/1blxiry/comment/kwkcbib/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button (and give this Redditor an upvote) 2. Stop the Oculus service in Windows. 3. Overwrite the -client and -runtime folders in C:\Program Files\Oculus\Support with his files. 4. Start Oculus app and then start DCS. If Oculus updates, repeat steps 2, 3 and 4.

Again; if anybody ( @YoYo ?) has the v62 install on their system, please share, as we are not able to get the v62 version from the installer anymore. Update: Adding @BIGNEWY to inform that Oculus now force-updates, making this a bigger problem. Also; v62 installer is not publicly available anymore.

Me too. Is there anybody that has v62 that can put the Oculus folder on some Google Drive or something?

Going by some file size comparison, it seems that only the moment of the camera-shutter triggers are recorded in the track file. Would be nice to have the ability to store the gun camera footage.

Is it possible to have gun camera footage in multiplayer? Is it possible to extract the images from the track file?

Did you manage to extract the images?

Tomorrow I will be hosting big training and I was wondering about performance, so this info comes in handy. Thanks! PS I'm afraid that my 32G will not be enough to also run a server instance.

Thank you. Further, for the last video we were 100% certain to both start the MT version. There is a chance that my colleague was not using the MT version in the first video (with track files).

As suggested by Dangerzone I tag @BIGNEWY and @NineLine. The mission file and track files are in te original post.

We played again today. There was again a bug, but this time me seeing both chutes and he only seeing one. After I aborted and re-requested he saw them both too. I asked him to send his track to me so I can capture and compare in more detail.

Thank you for your response! We will give it a try. (though I had a clean standalone install and my colleague uses Steam without mods)

Wednesday we have time to try any troubleshooting/root-cause-analysis suggestions, if anybody is interested in fixing this bug.

Kula66 posted a 1MB track file: https://forum.dcs.world/applications/core/interface/file/attachment.php?id=372740&key=32024898aea3b03c7bf7cc2fd0b900c3

How do we get the attention of the devs? How do we know they even know about this?

I have a replay track with this exact wobble. I watched the video from Grim Reapers and what I see is that we both had flaps set to half. I managed to extract and recompress the contents of the trackfile to make it fit. thegulf-20240306-220326.7z

In-flight refuelling tanker chutes are only visible for the player that is hosting the server. tanken.miz = used mission file robin_server-* = server hosting player track jeroen_server-* = connecting client player track We have switched roles (server/client) too; same result. Side-by-side recording: Update: tried other refuelling tanker (S-3B) too; same problem. robin_server-20240306-200438.trk jeroen_tanken-20240306-200451.trk tanken.miz

The repetitive propeller sound loop is why I don't fly this plane.

edit: Never mind... I opened the valve before closing the canopy.

The right TACAN channel knob is inconsistent with user expectations and different from the left TACAN channel knob. Most knobs work by using press+drag, so naturally one would use that for the TACAN channel knobs. Current behavior: Left knob: first digit changes Right knob: X/Y band changes As I could already change the X/Y band with a simple click, I see no reason to map press+drag differently on this knob. The intended way to change digits seems to be the mouse-wheel, but that seems to be inconsistent with all other knobs on the plane. Suggestion: Left-knob or right-knob click+drag = change channel Left-knob or right-knob mousewheel = change channel (for people that are already used to this, plus it works nicely) Right-knob mouse-clicks = change X/Y band