Search the Community
Showing results for tags 'logs'.
Found 4 results
-
Are there any plans of including ingame logs for console servers? The same way as it was done for DayZ Console Version (Xbox, Playstation). A simple .ADM file with actions who killed who, connections and similarly. if possible maybe even a setting for log output frequency. Should help server owners with tracking actions on the server, help moderation and add support for action feeds. Thanks in forward.
-
[Crash log] Status application hang, access violation and more
Inna Woods posted a topic in ARMA 3 - TROUBLESHOOTING
My game has been constantly crashing for weeks at random, with these 2 errors happening every single time. Dont know how to read these logs so I cant find the issue. where can I upload the logs? I dont see a way to do it here -
Simple BeLog reader Hi again, I used to help moderate a not so small dedicated arma server. Occasionally I needed to look through server logs to see who was connected to the server when. What always bothered me is those server logs are in plain boring text and not in a nice structured table like the ones you have when using something like EPM RCON. So I decide to write a program that transforms that plain boring text into a nice structured table. I've also added a simple search function and some advanced options. Features: In a few clicks you'll transform your BeLog-file from a dedi server into a nice structured table All the basic features of a table Search function for name, id, ip, guid, connect time, disconnect time, connect date, disconnect date Filters for: empty IP, empty GUID, empty name, empty (dis)connect time/date, bad names, ... Able to filter for players online between 2 given hours Open multiple log-files in the same table Dark theme Note that almost all these features are still work in progress. They're usable but don't be surprised if something doesn't entire work as you'd expect it to. Future plans: Make a tutorial video on how to use it Fix all known bugs Expand documentation Pack into a .exe (Items higher up the list have a higher priority for me) If you have any suggestions for what else I could do, let me know. Usage: Download SimpleBeLogReader.jar from the gitlab linked below. A .jar is an executable like a .exe is with the only difference that you need java installed to be able to use it. Once you double clicked it the welcome window will appear with one button on it. Click on that button, browse to the BeLog file you want to look at. Select it and press OK. You'll now see your BeLog file in a nice table. I plan on making a small video explain how to use it in the future. Known bugs: Spelling mistakes (I mean, I'm sure I made at least one :)) No others at this time If you find any other bugs feel free to post them here or on my gitlab. Changelog: Requirements: Java SE Runtime Environment 8 or later. License: Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International https://creativecommons.org/licenses/by-nc-sa/4.0/ For the full license and copyright look at the readme on the gitlab. Download: https://gitlab.com/stanhope/SimpleBeLogReader If you simply want to use the tool download "SimpleBeLogReader.jar" from that gitlab, the source code is also provided on that gitlab. Lastly I'd like to kindly ask everyone to not host my work in other places if no major changes have been made to it. Instead please simply link to my gitlab, this is merely a request. If you made a significant change to my script I have no problem with anyone hosting it anywhere as long as it's in accordance with the license.
-
Forgive me if anyone else has suggested it, i didn't see anything in the forums about it, and my error messages aren't easily sent. I too have been suffering from the 3fps 'bug', and i'd like to make the following suggestion regarding submitting feedback. Is it possible to add 'send' buttons on the error messages so those could be sent directly to BIS? (I guess you'd need a dedicated SMTP mail server like JangoMail or similar to handle the log traffic, but this would likely generate more feedback for you guys.) I have no idea if this would help the DEVS to examine logs to see if any of the crashes share a common trigger, or if even the logs reveal such things. What i do know is that many users have short attention spans and probably won't take the time to share their crash data in the forums or feedback tracker, especially if they aren't yet Arma addicts. Here's my suggestion for sending error logs directly to you guys (in green) : Cheers and keep up the good work friends!
