Jump to content

Constant Physics.PhysX errors

Closed 2.7.4



Searching all my plugins results with only one plugin that uses Mass
 

RaidableBases.cs
Line  9522:                     float d2 = body.mass * (vehicle is Tugboat ? 10f : 4f);

Included a screenshot.  Maybe there is nothing you can do or perhaps you know what I have done wrong?

image.png

RaidableBases.json

Edited by Merdynn
including config file

Share this comment


Link to comment

nah, you have everything disabled so no idea where that would be coming from. likely another plugin modifying the rigidbody, or potentially something wrong with the map itself.

the code you quoted wouldn't cause that error

Edited by nivex
  • Like 1

Share this comment


Link to comment

No, no pirates plugin.  It's ok...I've bothered you enough.  It might not even be anything to do with your plugin....just annoying to see a bunch of red text on the server output

Share this comment


Link to comment

ok, good luck. let me know if you figure it out.

you can respond even if the ticket is closed.

Edited by nivex
  • Like 1

Share this comment


Link to comment

I'm sorry to respond on this subject as it's been closed, but I recently updated the raidable bases plugin and I just got the errors as well. I did not have these errors before I performed the update.

 

  • 11/19 11:35:33 | [Physics.PhysX] computeMassAndInertia: Dynamic actor with illegal collision shapes
  • 11/19 11:35:33 | [Physics.PhysX] PxRigidBodyExt::setMassAndUpdateInertia: Mass and inertia computation failed, setting mass to 1 and inertia to (1,1,1)

Share this comment


Link to comment

no idea, never seen that before

delete this line from the .cs

TryPushMountable(vehicle, target);

if it still happens then it's not my plugin

 

Edited by nivex

Share this comment


Link to comment

actually it looks like you have a plugin modifying mass, so whenever my plugin tries to read that invalid mass the game throws a shit fit 😄

not sure though, but that's most likely what it is

I can just stop using the mass then and use a fix variable I suppose

Share this comment


Link to comment

After your update, I'm still getting the PhysX errors....which tells me it has nothing to do with your plugin and everything to do with something that one of my players is doing.  I'm going to start spectating him and watching my server output and it seems to only occur when a player is actually on my server

Share this comment


Link to comment

You assume I think he is doing something bad?  No, I just notice when he his on, whatever pve activity he is doing is what seems to cause it...but yes. I will share my list

 

𝐀𝐝𝐦𝐢𝐧 𝐑𝐞𝐥𝐚𝐭𝐞𝐝

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎

ᴀᴅᴍɪɴ ʀᴀᴅᴀʀ

ɴᴏ ɢɪᴠᴇ ɴᴏᴛɪᴄᴇꜱ

ᴘᴇʀᴍɪꜱꜱɪᴏɴꜱ ᴍᴀɴᴀɢᴇʀ

ᴘʟᴀʏᴇʀ ᴀᴅᴍɪɴɪꜱᴛʀᴀᴛɪᴏɴ

ᴠᴀɴɪꜱʜ

 

𝐒𝐞𝐫𝐯𝐞𝐫 𝐑𝐞𝐥𝐚𝐭𝐞𝐝

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎

ᴄᴏᴘʏ ᴘᴀꜱᴛᴇ

ᴅɪꜱᴄᴏʀᴅ ᴍᴇꜱꜱᴀɢᴇꜱ

ɪᴍᴀɢᴇ ʟɪʙʀᴀʀʏ

ɴᴏ ɪɴᴛᴇʀꜰᴇʀᴇɴᴄᴇ

ɴᴘᴄ ꜱᴘᴀᴡɴ

ꜱᴍᴏᴏᴛʜ ʀᴇꜱᴛᴀʀᴛᴇʀ

ᴛɪᴍᴇᴅ ᴇxᴇᴄᴜᴛᴇ

ᴛʀᴜᴇ ᴘᴠᴇ

ᴜᴘᴅᴀᴛᴇ ᴄʜᴇᴄᴋᴇʀ

 

𝐐𝐮𝐚𝐥𝐢𝐭𝐲 𝐨𝐟 𝐋𝐢𝐟𝐞

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎---͎-͎

ᴍᴏɴᴇʏ ᴛɪᴍᴇ

ʀᴇᴍᴏᴠᴇʀ ᴛᴏᴏʟ

ꜱᴇʀᴠᴇʀ ɪɴꜰᴏ

ꜱᴋɪᴘ ɴɪɢʜᴛ ᴠᴏᴛᴇ

ᴜɴʙᴜʀɴᴀʙʟᴇ ᴍᴇᴀᴛ

ᴡᴇʟᴄᴏᴍᴇʀ

 

𝐔𝐬𝐞𝐫 𝐑𝐞𝐥𝐚𝐭𝐞𝐝

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-

ʙᴇᴛᴛᴇʀ ᴄʜᴀᴛ

ᴄᴏᴏᴋɪɴɢ

ᴇᴄᴏɴᴏᴍɪᴄꜱ

ᴋɪᴛꜱ

ꜱᴇʀᴠᴇʀ ʀᴇᴡᴀʀᴅꜱ

ꜱɪɢɴ ᴀʀᴛɪꜱᴛ

ꜱᴋɪʟʟ ᴛʀᴇᴇ

ꜱᴋɪɴ ᴄᴏɴᴛʀᴏʟʟᴇʀ

 

𝐒𝐞𝐫𝐯𝐞𝐫 𝐄𝐯𝐞𝐧𝐭𝐬

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-

ᴀʀᴍᴏʀᴇᴅ ᴛʀᴀɪɴ

ᴄᴏɴᴠᴏʏ

ɴᴘᴄ ʀᴀɴᴅᴏᴍ ʀᴀɪᴅꜱ

ʀᴀɪᴅᴀʙʟᴇ ʙᴀꜱᴇꜱ

ᴡᴀᴛᴇʀ ᴇᴠᴇɴᴛ

Share this comment


Link to comment

I would unload other server events and see if the issue stops.

if you do not get results then disable them before a server restart and see if the issue stops. you can load them back if they are not the cause.

 

 

  • Like 1

Share this comment


Link to comment

i have a few plugins that you have as well, but none of them is showing such error.

 

I however do know that this could also be related to the hardware of your server. The error is also found in NVIDIA PhysX. (I just dmmed this to my hosting partners to look into it as I do have Nvidia stuff on the server. Will keep you posted )

 https://gameworksdocs.nvidia.com/PhysX/3.4/PhysXAPI/files/classPxMassProperties.html

  • Like 1

Share this comment


Link to comment

A followup due to a response

We can successfully rule out the fact that this is a hardware issue. Our partners are unable to dupe the issue on a freshly installed server as well. so, it must be one of the following plugins that could cause this error. Glad that we have a small list of potential plugins now, this makes it easier to find. Everything that's listed like this is what I do not have on my server.

𝐀𝐝𝐦𝐢𝐧 𝐑𝐞𝐥𝐚𝐭𝐞𝐝

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎

  • ᴀᴅᴍɪɴ ʀᴀᴅᴀʀ
  • ɴᴏ ɢɪᴠᴇ ɴᴏᴛɪᴄᴇꜱ
  • ᴘᴇʀᴍɪꜱꜱɪᴏɴꜱ ᴍᴀɴᴀɢᴇʀ
  • ᴘʟᴀʏᴇʀ ᴀᴅᴍɪɴɪꜱᴛʀᴀᴛɪᴏɴ
  • ᴠᴀɴɪꜱʜ

 

𝐒𝐞𝐫𝐯𝐞𝐫 𝐑𝐞𝐥𝐚𝐭𝐞𝐝

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎

  • ᴄᴏᴘʏ ᴘᴀꜱᴛᴇ ( possible that it could be an old raidable base paste by any chance @nivex? haven't looked into this yet, just popped up in my mind )
  • ᴅɪꜱᴄᴏʀᴅ ᴍᴇꜱꜱᴀɢᴇꜱ
  • ɪᴍᴀɢᴇ ʟɪʙʀᴀʀʏ
  • ɴᴏ ɪɴᴛᴇʀꜰᴇʀᴇɴᴄᴇ  ( FacePunch added this change in turrets for a good reason )
  • ɴᴘᴄ ꜱᴘᴀᴡɴ
  • ꜱᴍᴏᴏᴛʜ ʀᴇꜱᴛᴀʀᴛᴇʀ
  • ᴛɪᴍᴇᴅ ᴇxᴇᴄᴜᴛᴇ
  • ᴛʀᴜᴇ ᴘᴠᴇ
  • ᴜᴘᴅᴀᴛᴇ ᴄʜᴇᴄᴋᴇʀ

 

𝐐𝐮𝐚𝐥𝐢𝐭𝐲 𝐨𝐟 𝐋𝐢𝐟𝐞

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎---͎-͎

  • ᴍᴏɴᴇʏ ᴛɪᴍᴇ
  • ʀᴇᴍᴏᴠᴇʀ ᴛᴏᴏʟ ( i presume that one is from Mevent or the one that's listed on umod? ) 
  • ꜱᴇʀᴠᴇʀ ɪɴꜰᴏ ( doubt this has anything to do with it as the error is related to a rigid body )
  • ꜱᴋɪᴘ ɴɪɢʜᴛ ᴠᴏᴛᴇ
  • ᴜɴʙᴜʀɴᴀʙʟᴇ ᴍᴇᴀᴛ
  • ᴡᴇʟᴄᴏᴍᴇʀ

 

𝐔𝐬𝐞𝐫 𝐑𝐞𝐥𝐚𝐭𝐞𝐝

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-

  • ʙᴇᴛᴛᴇʀ ᴄʜᴀᴛ
  • ᴄᴏᴏᴋɪɴɢ
  • ᴇᴄᴏɴᴏᴍɪᴄꜱ
  • ᴋɪᴛꜱ
  • ꜱᴇʀᴠᴇʀ ʀᴇᴡᴀʀᴅꜱ
  • ꜱɪɢɴ ᴀʀᴛɪꜱᴛ
  • ꜱᴋɪʟʟ ᴛʀᴇᴇ
  • ꜱᴋɪɴ ᴄᴏɴᴛʀᴏʟʟᴇʀ

 

𝐒𝐞𝐫𝐯𝐞𝐫 𝐄𝐯𝐞𝐧𝐭𝐬

-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-͎-

  • ᴀʀᴍᴏʀᴇᴅ ᴛʀᴀɪɴ ( not active at the moment due to undersized map )
  • ᴄᴏɴᴠᴏʏ
  • ɴᴘᴄ ʀᴀɴᴅᴏᴍ ʀᴀɪᴅꜱ
  • ʀᴀɪᴅᴀʙʟᴇ ʙᴀꜱᴇꜱ
  • ᴡᴀᴛᴇʀ ᴇᴠᴇɴᴛ

Share this comment


Link to comment

I don't think it's copypaste files, but maybe

I see this in Convoy.cs

rigidbody.mass = 1;
rigidbody.mass = 1;
rigidbody.mass = 3500;

and this is your error

Quote

PxRigidBodyExt::setMassAndUpdateInertia: Mass and inertia computation failed, setting mass to 1 and inertia to (1,1,1)

Edited by nivex

Share this comment


Link to comment

I just added convoys. The crappy part of this is, I think its a combonation of 2 plugins causing a conflict and the errors didnt seem to start until sometime after I added cooking...I think. Also, I notice the error occurs after certain named pasted bases...like someone maybe made too goofy a base? I ha e over 200 raidable bases....I'll scour my logs this weekend and see what I can find.

Share this comment


Link to comment

I see nothing wrong with the base. errors spam when a base pastes and spam when no bases paste, too. it's seemingly random which makes it incredibly difficult to track down

I've been looking at logs trying to figure this out. I've seen days where there's no errors, and days where it's nonstop.

I have a server owner trying an experiment for me so maybe it'll turn up some results. we'll see. if not, i'll monitor entity spawns and parenting and see which is triggering it.

it could be that the problem originates from a different source, and raidablebases exacerbates the problem.

it could be an nvidia issue, too

I don't know yet 😕

 

Share this comment


Link to comment

Im a server owner as well, obviously, I also have a pro version of VMWare and my system is powerful enough to run about 8 seperate Systems...let me know if there is something you want me to try

 

 

Also, let me know if the other guy thats testing wants me to do anything.  I have a 3060Ti and a 2070 super I can run tests on

Edited by Merdynn

Share this comment


Link to comment

1.1m

Downloads

Total number of downloads.

5.7k

Customers

Total customers served.

82.2k

Files Sold

Total number of files sold.

1.6m

Payments Processed

Total payments processed.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.