[BUG] 4.35 MP Tanker
-
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
-
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.
We’ll be sure to let everyone know when there’s a filter value that could help with an issue - like in this case.
Not all the values would make sense to put in there for players – many of them are really only sensible for developers and wouldn’t tell you anything useful plus some of them actually make the game barely run at all (think: slide show) so you probably don’t want to mess with those since you don’t have the ability to work with the debugger on the code Oh and the other concern is that some of these values generate output that is years old and no longer reflects what the code actually does – it’s something that might only get fixed up if we need the messages to look at a current problem perhaps…with the current state you’d have to be able to look at code to know what is really going on while such a message is delivering “fake news” as it were. Having to explain details in such cases would take time that we’d rather be spending on fixing issues for you all at the moment
-
Here is 2 human logs after we enabled -MONO setting.
TE with 4 human pilots and only Host was able to get fuel.
link is to 2 humans that were not able to get fuel. Tanker only gave 3 humans a copy when requesting AAR.
-
We are confident we found the bug already
Thanks for the heads up
Unfortunately no workaround
-
As an insurance measure so we are sure that we’re right it would still be useful to see a COMPLETE (see post #14 above) set of logs from a refueling attempt that didn’t go as expected. That means not just logs from jets that didn’t get fuel but logs from all players connected to the game at the time the problem occurred. If someone can provide those we can cross check to make sure the proposed fix will do the trick.
-
Hello
Yesterday same trouble.
On a TE. 6 humains. 2 flights.
Only the host have refuel.
The tanker always reply copy to others humans.Merry Christmas
-
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
The main difference I might think of is FL is a dedicated server with the host flight not part of the package. I assume the reported issues that the host itself is flying within the package
-
The main difference I might think of is FL is a dedicated server with the host flight not part of the package. I assume the reported issues that the host itself is flying within the package
The main difference is likely that the bug comes from an unitinalized local variable for remote players
Therefore this is a “random” bug
But this needs to be confirmed -
Version
4.35.0 (x64)Build
22548Detailed Description
Tanker refuels lead/host in a human multi-ship flight and returns to station after Y-3 (done refueling) command instead of clearing next flight member to the boom.Video
- Not of the logged flight but same behavior
Example files
TE: https://drive.google.com/file/d/1nF7hbZcJWgJse6XvJ4WQ_m4n4FOcvkUn/view?usp=sharing
Logs (Lead calls Y-1 at 22:52:14): https://drive.google.com/file/d/1ULEa0RuhB8Zr5I31rM7sRt239HcQQe83/view?usp=sharingCrash logs
No game crash occurs. Wingman and Element may flameout and crash on RTBReproducibility Procedure (4 out of 5 probability of reoccurrence from my 5 samples)
1. Host multiplayer with at least 1 connected client
2. Load provided TE and have client join
3. Host takes seat 1 and clients take remaining seats of PKG 1984
4. Takeoff (Bug encountered in both Ramp and Taxi commits, if saving time)
5. Lead aborts any non-human seats
6. Follow all normal comm flow and procedures and depart Kunsan
7. Head towards steerpoint 4 and join the tanker
8. Once rejoined with tanker and all members are on tanker preset UHF 13, lead calls for fuel (Y-1)
8. Lead takes fuel and disconnects and calls done refueling (Y-3)
9. Tanker will not call subsequent flight members to boom
10. Lead can repeat from step 8 and tanker will only service leadExpected Behavior
For tanker boom operator to pass gas for all members of the flight -
Version
4.35.0 (x64)Build
22548Detailed Description
Tanker refuels lead/host in a human multi-ship flight and returns to station after Y-3 (done refueling) command instead of clearing next flight member to the boom.Video
- Not of the logged flight but same behavior
Example files
TE: https://drive.google.com/file/d/1nF7hbZcJWgJse6XvJ4WQ_m4n4FOcvkUn/view?usp=sharing
Logs (Lead calls Y-1 at 22:52:14): https://drive.google.com/file/d/1ULEa0RuhB8Zr5I31rM7sRt239HcQQe83/view?usp=sharingCrash logs
No game crash occurs. Wingman and Element may flameout and crash on RTBReproducibility Procedure (4 out of 5 probability of reoccurrence from my 5 samples)
1. Host multiplayer with at least 1 connected client
2. Load provided TE and have client join
3. Host takes seat 1 and clients take remaining seats of PKG 1984
4. Takeoff (Bug encountered in both Ramp and Taxi commits, if saving time)
5. Lead aborts any non-human seats
6. Follow all normal comm flow and procedures and depart Kunsan
7. Head towards steerpoint 4 and join the tanker
8. Once rejoined with tanker and all members are on tanker preset UHF 13, lead calls for fuel (Y-1)
8. Lead takes fuel and disconnects and calls done refueling (Y-3)
9. Tanker will not call subsequent flight members to boom
10. Lead can repeat from step 8 and tanker will only service leadExpected Behavior
For tanker boom operator to pass gas for all members of the flightSame behaviour here. After leader refueling tanker dismiss as if only one ship were in the flight. If other wingman request fuel Y1, tanker talks to the other ships as individual flights and doesn’t clear from pre-contact to contact. I can provide a TE if needed.
Also APP instructed each member to contact tower separately even at close formation after the tanker event. Not sure if related.
-
I’ve created an issue in the BMS bug tracker:
https://bmsbugs.blu3wolf.com/view.php?id=5
I’ve copied some info verbatim from this thread, hope that’s ok.
All the best,
Uwe