Server: Object info 21:2 not found / Can't change owner from 0 to 170090558

[He-Man]

Already talked with another Admin and our rpt-logs are full with the following messages:

Spoiler

17:21:09 Server: Object info 21:2 not found.
17:21:09 Can't change owner from 0 to 170090558
17:21:09 Server: Object info 2:6742 not found.
17:21:09 Can't change owner from 0 to 2
17:21:09 Server: Object 2:7274 not found (message Type_91)
17:21:09 Server: Object info 21:2 not found.
17:21:09 Can't change owner from 0 to 170090558
17:21:09 Server: Object info 2:6742 not found.
17:21:09 Can't change owner from 0 to 2
17:21:09 Server: Object info 21:2 not found.
17:21:09 Can't change owner from 0 to 170090558
17:21:09 Server: Object info 2:6742 not found.
17:21:09 Can't change owner from 0 to 2
17:21:09 Server: Object info 21:2 not found.
17:21:09 Can't change owner from 0 to 170090558
17:21:09 Server: Object info 2:6742 not found.
17:21:09 Can't change owner from 0 to 2
17:21:09 Server: Object info 21:2 not found.
17:21:09 Can't change owner from 0 to 170090558
17:21:09 Server: Object info 2:6742 not found.
17:21:09 Can't change owner from 0 to 2
17:21:10 Server: Object info 21:2 not found.
17:21:10 Can't change owner from 0 to 170090558
17:21:10 Server: Object info 2:6742 not found.
17:21:10 Can't change owner from 0 to 2
17:21:10 Server: Object info 21:2 not found.
17:21:10 Can't change owner from 0 to 170090558
17:21:10 Server: Object info 2:6742 not found.
17:21:10 Can't change owner from 0 to 2
17:21:10 Server: Object info 21:2 not found.
17:21:10 Can't change owner from 0 to 170090558
17:21:10 Server: Object info 2:4823 not found.
17:21:10 Can't change owner from 0 to 412568192

 

[vbawol]

Hey He-Man,  We don't currently use setOwner command in Epoch. A function made by Axeman does exists in our code that does use setowner. However I checked and it is unused.

I would recheck any custom scripts that do make use of the setOwner command. Also, based on that 412568192 number (Can't change owner from 0 to 412568192) I don't think that is the netid of the player but some other number. 

The "Server: Object info * not found" messages happen anytime you have a reference to an object that does not exist and continue to try to pass commands at it. In most cases you can prevent the object not found errors by conditioning the code to always check that the object not null !(isNull _object) before running any command that takes an object as input. 

[He-Man]

Okay thanks!

I will recheck it.

But because we are atm not running any AI missions or something else, I think I will found nothing.

But I also will check all codes.

Edit:

Okay, I have checked and we also have not setowner in our codes.

I also checked again the Epoch files and there can find setowner in a script, that is not used (as you said).

!(isNull _object) I will check in my codes, where I can use this.

 

Thanks!

[Demellion]

13 hours ago, He-Man said:

Okay thanks!

I will recheck it.

But because we are atm not running any AI missions or something else, I think I will found nothing.

But I also will check all codes.

Edit:

Okay, I have checked and we also have not setowner in our codes.

I also checked again the Epoch files and there can find setowner in a script, that is not used (as you said).

!(isNull _object) I will check in my codes, where I can use this.

 

Thanks!

Just for info: Type_91, Type_90, Type_119 object not found errors are totally harmless, unless it burns your eyes with spam in rpt. If you are using some missions with AI dead body cleanup - you will anyways encounter that in rpt simply because of cleanup scripts not being perfectly written. Cleanup may loose some object reference in the loop and try to delete it to the end of times. Why? Tons of reasons. Some even related to Arma engine.

[Demellion]

On 01.02.2016 at 7:28 PM, He-Man said:

Okay thanks!

I will recheck it.

But because we are atm not running any AI missions or something else, I think I will found nothing.

But I also will check all codes.

Edit:

Okay, I have checked and we also have not setowner in our codes.

I also checked again the Epoch files and there can find setowner in a script, that is not used (as you said).

!(isNull _object) I will check in my codes, where I can use this.

 

Thanks!

UPDATE: Got struck with your problem.

"Can't change owner" exactly not harmless. They kill server FPS for some reason. I did check all Epoch repository and found nothing with used setOwner, so its true. If you solved this - please tell me where and how, as for me it appeared from nowhere and dont happen exact time, floating. 

Thanks much. 

 

UPDATE: Seek for {setGroupOwner} in AI missions, where they transfer locality.Stupid idea.

[He-Man]

I'm not sure, what it was, but I have no more "can't set owner" messages in my logs. Only Object x:xxx not found (message Type_xx) still persists a lot.

What I have done:

- Added !(isNull _whatever) in every code of my AI-Mission (as vbwol advised)

- Added removefromremainscollector [_whatever] to the cleanup script of the AI's

 

My next step will be checking all my codes for "deletevehicle " and check, if these "vehicles" are in the remainscollector. If so, I will add:

if (isInRemainsCollector [_whatever]) then {

removefromremainscollector [_whatever];

};

deletevehicle _whatever;

[He-Man]

can't set owner came back.

No idea, what's the problem :(