[BUG] 4.35 MP Tanker
-
@Nick:
Kolbe,
Then you can do the bug report that is needed.Version
4.35.0 (x64)Build
The only one and only that is available right now.Detailed Description
In multiplayer scenarios only the flying host is able to refule.
All others do not get clearance but only a “Copy”.Pictures
NoneExample files
Crash logs
NoneReproducibility Procedure
1. Create a TE with a tanker and multiple AAR capable aircrafts.
2. Find a few pilots, who are willing to fly 4.35 online (could be challinging).
3. Go refueling.Expected Behavior
See BMS 4.34Good luck!
-
Version
4.35.0 (x64)Detailed Description
MP AAR is not working. Created Rolling Fire Campaign. Tanker Copper (created by Game).
Hosted Campaign on our Dedicated server.
Added 2 ship SEAD mission Plasma3 with 2 human pilots
Plasma 41 called for fuel at 3 miles.
Received “Copy” from Tanker
Then Plasma 42 was cleared to Pre-contact position.Tried this multiple times with same results. Plasma 41 could not get fuel.
Pictures
…Example files
https://1drv.ms/u/s!ApjPr59Y2kBii6EUngzHtE94Mv7-2Q?e=0kOjwPCrash logs
NONEReproducibility Procedure
1. Host camp on dedicated server
2. have 2 human files try and get fuel
3. Lead was not able to get fuel.Expected Behavior
-
Please do this if you can gather the people to reproduce your experience. The log files (we need the whole set, one from every player connected to the game even if they aren’t tanking) produced will almost certainly give us clarity on what is going on.
Note that this is a standard, best known method if you will, for reporting issues with the tanker…the code has extensive logging because the state machine that drives the whole thing is so darned complicated and debugging it otherwise is pretty hard, especially for MP issues.
-
Please do this if you can gather the people to reproduce your experience. The log files (we need the whole set, one from every player connected to the game even if they aren’t tanking) produced will almost certainly give us clarity on what is going on.
Note that this is a standard, best known method if you will, for reporting issues with the tanker…the code has extensive logging because the state machine that drives the whole thing is so darned complicated and debugging it otherwise is pretty hard, especially for MP issues.
And especially it is totally useless to try to debug 4.35 here since it has changed a lot since
So this should not be tested on 4.35 on our side …
There is 90% chance this is fixed already
Just saying -
We performed a TE and Camp test with 4 human pilots and 1 of the human pilots as the HOST with no issues.
So we will continue to perform more tests as we go along and will report back. -
I will have a look in 4.35 though if we have a good repro case ….
-
We just did ta test by jumping in a running campaign hosted on the Falcon Lounge:
- Jumping in a plane in flight (leader of a 2 KF-16) close to a tanker… I could ask tanker, pre-contact, refuel, all OK!
- Jumping in a flight of 2 KF-16 (2 humans) close to tanker… We coud ask, pre-contact, refuel, all OK!
Interested to understand what could be happening for you guys…
Cheers
-
So yes, please – xlog files will help zero in on the mystery.
-
We just did a flight of 4 in a TE and only the person hosting the TE was able to get fuel. All others the tanker ignored. We had 2 tankers in the same package on this mission. We will again test tomorrow but we will put the tankers in separate packages and see what happens. unfortunately their are no logs that i see that will help with this issue.
Report back tomorrow.
-
You can get xlog files after each flight by adding -mono to the end of the target line of the desktop icon.
Example:
“F:\Falcon BMS 4.35\Launcher.exe” -mono
-
Here’s the TE this bug has happened to me 4 times in. I’m sorry, I understood Mav as saying that the log for the config wasn’t useful, so i didn’t try that.
Video shows he ignores my #2:
TE files:
https://drive.google.com/file/d/1nF7hbZcJWgJse6XvJ4WQ_m4n4FOcvkUn/view?usp=sharing -
Again, xlog files will help. This is exactly the kind of issue for which those messages were put into the code. Sorry if that wasn’t clear between our responses.
-
Again, xlog files will help. This is exactly the kind of issue for which those messages were put into the code. Sorry if that wasn’t clear between our responses.
What’s the difference if we put just -mono to the shortcut command line or if we add the “set g_fXMonoprintFilter 512” to the “falcon bms.cfg” and then the -mono to the command line?
-
-mono alone does two things. It turns on the production of the log file and also gives you the basic default logged messages as output. The filter value of 512 in the cfg file is magic number that says: if -mono is on, then only put messages in the log file that are relevant to tanker operations. The filter value in the cfg file alone will not enable the log file generation. The -mono alone will not produce a log file with the tanker relevant messages in it since those are not part of the default set of messages. To get a file and a file that has the tanker messages you need both the command line -mono arg and the filter value in the cfg file. Hope that helps clarify.
-
Is there somewhere a list of the filter values? This would help a lot to provide helpful logs in such cases.
-
If I may, your expertise in picking that value may not be shared by other reporters, and yet values be used by them. I suppose that’s a downside to sharing it publicly?
-
I fully understand that. In the past we were told to rund the sim with -mono in order to have the xlogs generated. This would help to find the root cause of the issue. Now I i.e. tanker stuff is not included in the default filters. Understanding which filter setting would help to provide helpful logs for certain issues would help us alot.
-
Here’s the TE this bug has happened to me 4 times in. I’m sorry, I understood Mav as saying that the log for the config wasn’t useful, so i didn’t try that.
Video shows he ignores my #2:
TE files:
https://drive.google.com/file/d/1nF7hbZcJWgJse6XvJ4WQ_m4n4FOcvkUn/view?usp=sharingCould you describe EXACTLY what every player did and the configuration of the test
Please be as explicit and clear as possible
If we can have a reliable repro case that would be ideal
Monolog as boxer say is helpful as well
-
Certainly, I’ll capture it again for the log and make another post later today.
Edit: failed to coordinate with wingmen for today, will try again soon!
-
Certainly, I’ll capture it again for the log and make another post later today.
The exact description of the conditions of the bug is of the utmost importance.
Reading your bug report should allow us to reproduce