In-flight refuelling tanker chutes only visible on server.

[tribbin]

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

Edited March 7, 2024 by tribbin

[tribbin]

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

Edited March 18, 2024 by tribbin

[Dangerzone]

On 3/7/2024 at 7:33 AM, tribbin said:

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 4.41 MB · 5 downloads jeroen_tanken-20240306-200451.trk 5.37 MB · 4 downloads tanken.miz 10.14 kB · 4 downloads

 

I have no idea, but I do have one suggestion for you to try for debugging.

In your user\saved games directory you will find a DCS (or DCS.BETA) folder. Can you please try renaming that to DCS.OLD (to make a backup) on both computers.

Then perform a DCS Repair on the main install.

Once done, please start up DCS and see if the problem persists.

If this has fixed it:

This will confirm that it's either a setting or a MOD, or similar that is causing the issue. You can reverse your changes (see below) to get your original settings back and try and debug further knowing that it's a setting or a mod issue, or otherwise just reconfigure the new settings to your liking noting the changes you make until either the problem occurs again (thus telling you what the issue is), or until you get DCS configured to how you want it again without the issue, in which case - fixed.

 

If it doesn't help:

Close DCS. You will find that DCS created a new DCS (or DCS.BETA) directory there. Rename it to DCS.DELME. Then rename DCS.OLD back to DCS (or DCS.BETA - whichever it was originally). This will return your settings back to what you had. 

Once you confirm you're back to what you had originally you can delete the DCS.DELME directory (as this is just the new one DCS automatically created). 

 

Important Note:

Renaming the DCS folder to DCS.OLD will remove your key bindings. You will need to rebind the basics back to do your testing (or after starting DCS, you can close, and copy the controller INPUT directory across from DCS.OLD to the new DCS directory to copy your conrol bindings only).

 

Hope this helps. I'm unsure of what the issue may be, but since you didn't get any other replies, maybe this may help to diagnose.

[tribbin]

11 hours ago, Dangerzone said:

I have no idea, but I do have one suggestion for you to try for debugging.

In your user\saved games directory you will find a DCS (or DCS.BETA) folder. Can you please try renaming that to DCS.OLD (to make a backup) on both computers.

Then perform a DCS Repair on the main install.

Once done, please start up DCS and see if the problem persists.

If this has fixed it:

This will confirm that it's either a setting or a MOD, or similar that is causing the issue. You can reverse your changes (see below) to get your original settings back and try and debug further knowing that it's a setting or a mod issue, or otherwise just reconfigure the new settings to your liking noting the changes you make until either the problem occurs again (thus telling you what the issue is), or until you get DCS configured to how you want it again without the issue, in which case - fixed.

 

If it doesn't help:

Close DCS. You will find that DCS created a new DCS (or DCS.BETA) directory there. Rename it to DCS.DELME. Then rename DCS.OLD back to DCS (or DCS.BETA - whichever it was originally). This will return your settings back to what you had. 

Once you confirm you're back to what you had originally you can delete the DCS.DELME directory (as this is just the new one DCS automatically created). 

 

Important Note:

Renaming the DCS folder to DCS.OLD will remove your key bindings. You will need to rebind the basics back to do your testing (or after starting DCS, you can close, and copy the controller INPUT directory across from DCS.OLD to the new DCS directory to copy your conrol bindings only).

 

Hope this helps. I'm unsure of what the issue may be, but since you didn't get any other replies, maybe this may help to diagnose.

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)

[tribbin]

On 3/19/2024 at 11:55 AM, tribbin said:

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)

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.

Edited March 20, 2024 by tribbin

[tribbin]

59 minutes ago, tribbin said:

We played again today. There as a glitch of me seeing the chutes and he not seeing them. After I aborted and re-requested he saw them too.

I asked him to send his track to me so I can capture and compare in more detail.

 

 

[Dangerzone]

2 hours ago, tribbin said:

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.

 

Definitely sounds like a bug. I'd suggest posting the tracks here and maybe tagging in Bignewy or nineline to make them aware of this bug, and your reproducable track files. 

[tribbin]

10 hours ago, Dangerzone said:

Definitely sounds like a bug. I'd suggest posting the tracks here and maybe tagging in Bignewy or nineline to make them aware of this bug, and your reproducable track files. 

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

[BIGNEWY]

Hi, 

we will take a look at this to try and reproduce

thanks 

[tribbin]

36 minutes ago, BIGNEWY said:

Hi, 

we will take a look at this to try and reproduce

thanks 

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).

[Dangerzone]

@tribbin - while you wait for ED to investigate and potentially patch this issue, a workaround may be to run a stand-alone server instance of DCS on one of your computers.

(This could also potentially give performance benefits to you as well, as your client DCS would be focusing only on you, and the server instance and threads would be serving the 'server' side). 

[tribbin]

17 hours ago, Dangerzone said:

@tribbin - while you wait for ED to investigate and potentially patch this issue, a workaround may be to run a stand-alone server instance of DCS on one of your computers.

(This could also potentially give performance benefits to you as well, as your client DCS would be focusing only on you, and the server instance and threads would be serving the 'server' side). 

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.

Edited March 22, 2024 by tribbin

[tribbin]

Will test this tonight.

[tribbin]

The problem is solved with today's patch, tank you very much!

[tribbin]

@BIGNEWY Tried air refueling again today with my colleague (to test my new flightstick base) and there are still sync issues.

Colleague requested contact on the right side many times and did not get a clear contact and also never saw the right chute. (for me both were extended)

When I aborted fueling and requested fueling again, the left chute retracted for my colleague but not for me.

We were both using MT version and I was the server.

[Swanny]

Any update on this? I'm hosting a server, my friend joins and we both approach the tanker. If we have AI refueling before us we can both see the baskets. When they finish we both see the baskets go back in.

If I request a refuel all works ok, if he requests a refuel I see the baskets but he doesn't. Both on steam version. Exactly as the OP has reported.