gagi2 50 Posted July 21, 2015 hi&hello... since the last update i get this line (more or less) spammed in my rpt logfile... its already 2gig where it should be less than 2mb atm... 19:30:16 Wrong player index passed to NetworkObjectInfo::GetPlayerObjectInfo - max=47, received=51 Share this post Link to post Share on other sites
cyruz 103 Posted July 22, 2015 I was going to create a new thread for this but I think this will suffice, in the recent Sitrep you asked that modders tidy up their RPT spam, this something I commend as we try not to adopt anything that spams the RPT (or open it and fix it ourselves as is more often the case). Error: Object(4 : 6) not found Server: Object 3:11 not found (message Type_324) (6200 [receivedMagazine]): Network sync error - NMTFireWeapon Again these might be useful, but they've been appearing in RPT logs since A2 (bar the last one) and no-one 100% seems to know what they mean (some suspect it's debug from setPos). I think if you're aware that logging things to the RPT can hurt client/server performance you should really look to review how logging is handled engine-side. I propose a tiered logging system like, TRACE DEBUG INFO WARN ERROR OFF and allow the client/server to specify which values they log, I understand this causes issues in regarding to collecting logs as people might be running various levels of trace, should default to something with minimal impact (ERROR). Using -nologs (or OFF) if using the above system should be an option but really shouldn't be recommended as a solution to bugs/RPT spam. Share this post Link to post Share on other sites
fn_Quiksilver 1633 Posted July 22, 2015 I was going to create a new thread for this but I think this will suffice, in the recent Sitrep you asked that modders tidy up their RPT spam, this something I commend as we try not to adopt anything that spams the RPT (or open it and fix it ourselves as is more often the case). Error: Object(4 : 6) not found Server: Object 3:11 not found (message Type_324) (6200 [receivedMagazine]): Network sync error - NMTFireWeapon Again these might be useful, but they've been appearing in RPT logs since A2 (bar the last one) and no-one 100% seems to know what they mean (some suspect it's debug from setPos). I think if you're aware that logging things to the RPT can hurt client/server performance you should really look to review how logging is handled engine-side. I propose a tiered logging system like, TRACE DEBUG INFO WARN ERROR OFF and allow the client/server to specify which values they log, I understand this causes issues in regarding to collecting logs as people might be running various levels of trace, should default to something with minimal impact (ERROR). Using -nologs (or OFF) if using the above system should be an option but really shouldn't be recommended as a solution to bugs/RPT spam. Upvote http://feedback.arma3.com/view.php?id=24573 Share this post Link to post Share on other sites
Vasily.B 529 Posted March 2, 2016 18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (89,91).18:22:49 found in (86,92).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (86,92).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (86,91).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (90,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (88,93).18:22:49 found in (88,93).18:22:49 found in (88,93).18:22:49 found in (88,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (88,93).18:22:49 found in (88,93).18:22:49 found in (88,93).18:22:49 found in (88,93).18:22:49 found in (88,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (89,93).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (94,87).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (91,91).18:22:49 found in (91,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (90,91).18:22:49 found in (91,91).18:22:49 found in (91,91).18:22:49 found in (91,91).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (89,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,88).18:22:49 found in (88,92).18:22:49 Bad muzzle direction in rhs_tr8_periscope:'usti hlavne'-'konec hlavne'18:22:49 Bad muzzle direction in rhs_tr8_periscope:'usti hlavne'-'konec hlavne'18:22:49 Bad muzzle direction in rhs_tr8_periscope_pip:'usti hlavne'-'konec hlavne'18:22:49 Bad muzzle direction in rhs_tr8_periscope_pip:'usti hlavne'-'konec hlavne'18:22:49 Bad muzzle direction in rhs_weap_tr8:'usti hlavne'-'konec hlavne'18:22:49 Bad muzzle direction in rhs_weap_tr8:'usti hlavne'-'konec hlavne'18:22:49 found in (88,92).18:22:49 found in (89,92).18:22:49 found in (89,92).Multiple it by 100 and you will imagine my rpt. Share this post Link to post Share on other sites
twakkie 57 Posted March 9, 2016 hi&hello... since the last update i get this line (more or less) spammed in my rpt logfile... its already 2gig where it should be less than 2mb atm... 19:30:16 Wrong player index passed to NetworkObjectInfo::GetPlayerObjectInfo - max=47, received=51 I apologise for bumping this old thread but did you find a solution or reason for this error? We have been having the same error, and for the life of me I cant figure out the reason. Share this post Link to post Share on other sites
Vasily.B 529 Posted March 9, 2016 It seems there is no solution for those spams. I need to delete all logs once per week, or my HDD get kill :P Share this post Link to post Share on other sites