Why player can't see the network prop entity

FiveM Server Development Server Discussion
1

I found that when I start the server.Firstly I can see the phone props ,the police cad and so on.
when the server start after some time,the player can’t see the newtwork prop each others.
And the LBphone has given the warning:

[   1464985] [b3095_GTAProce]             MainThrd/ ^3Warning: [entity] NETWORK_GET_NETWORK_ID_FROM_ENTITY: no net object for entity (script id 3522306)^7
[   1469453] [b3095_GTAProce]             MainThrd/ ^3Warning: [entity] NETWORK_GET_NETWORK_ID_FROM_ENTITY: no net object for entity (script id 3526402)^7

I am using the ESX 1.10.2
And OneSync Legacy

how can I solve the problems?Thank you read this!I will appreacitae it that you can help me!

2

I also find that i remove some networkds props,it works.
if i can change the network entity more?

3

There is a limit to the number of networked props in any given area. You have likely reached the max in the area where this was happening. One or some of your scripts are creating networked props and are not cleaning them up so they are probably just sitting there spawned until server restart. When you reach the networked prop limit like this then the prop is not given a network ID which what the error is referring to, there is no network ID for the phone prop.

4

Thank you for answering my question.
i havd found that there are some limit amount for the network props.And it s about 80.
i search it on the forum.And it has existed.
It seems nobody konw how to increase the limit amount.
So i try to clear the props when server start 30min
and it can solve the question temporality.
I really want to konw if the player is up to more than 80 or 800.How the network props spawn in the world.If we can’t change the 80 limit?
Thank you for reading my question.

5

If you try to spawn a prop in an area where the networked prop limited has been reached the prop will still spawn for the player that spawned it, but it wont be networked, so no other player will see it. You should also be careful clearing all props as some scripts may rely on the existence of props that they spawned. It is best to investigate what scripts are causing the excess props and fix those rather than apply a bandaid fix which will likely break other scripts.

6

Ideally you should never use networked props. A limit of 80 is more than enough to not cause any problems.

Example of non-networked props:

  • Prop is directly attached to another entity (e.g. props from animations)
  • If it’s a static prop that doesn’t need to move

(these of course need to be manually synced/placed for each client in range)

Example of networked props:

  • Sport scripts that include an additional physics prop (e.g. the ball in soccer or basketball) where everyone needs to see exactly the same thing
7

I see. Thank you very much for your answer. I will try to treat other unnecessary items as non-network entities. It is very sad that things such as roadblocks in origen-police can only be online items, and I can’t change their logic without open source. But thank you for your answer.

8

It’s basically also the reason why nearly all vanilla objects (bin bags, signs, traffic lights etc) are client side (non networked). It simply would cost way too much performance to sync those things :slight_smile: