Getting a lot of errors in the console

baseless research

I've been getting a lot of errors of the following type (I'm mostly interested in the PhysX errors, since it seems to coincide with a lag spike):

<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->Record Device: Logitech G330 Headset
Loading config://ConsoleBindings.json
Main Menu Initialized at Version: 221
Connecting to server 81.19.212.190:27015
Loading config://ConsoleBindings.json
Error: Couldn't open file 'cinematics/alien/cloak.cinematic'
Loading 'maps/ns2_veil.level'
Error: Couldn't open file ''
Error: Couldn't open file 'materials/refining/refining_decal_danger_01.material'
Error: Couldn't open file 'materials/refining/refining_decal_danger_01.material'
Error: Couldn't open file 'materials/refining/refining_decal_danger_01.material'
Error: Couldn't load 'materials/descent/descent_floor_01_a_normal.dds' (File not found)
Error: Couldn't open file 'materials/refining/refining_decal_danger_01.material'
Error: No shader specified for material 'materials/refining/refining_decal_danger_01.material'
Finished loading 'maps/ns2_veil.level'
Error: Couldn't open file 'materials/effects/halo_yellow.material'
Error: No shader specified for material 'materials/effects/halo_yellow.material'
#####*****some chat that has no business being here*****#####
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: Particle data read not allowed while simulation is running.
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().
Error: PhysX: PxParticleReadData access through PxScene::fetchResults() while its still locked by last call of PxParticleBase::lockParticleReadData().<!--c2--></div><!--ec2-->


any idea how to fix this?

Runteh

Yup, wait for the next patch. Or the patch after that one. :)

Davil

<!--quoteo(post=1989421:date=Oct 10 2012, 02:31 PM:name=baseless research)--><div class='quotetop'>QUOTE (baseless research @ Oct 10 2012, 02:31 PM) <a href="index.php?act=findpost&pid=1989421"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->I've been getting a lot of errors of the following type (I'm mostly interested in the PhysX errors, since it seems to coincide with a lag spike):

any idea how to fix this?<!--QuoteEnd--></div><!--QuoteEEnd-->

Yea those are all procedure calls, in short it's a problem with the hard code in the game. The reason why it's giving you a lag spike is likely cause physx is a sort of physics engine that nvidia acquired a while back. It uses the gpu to take the load off the cpu in calculating physics information. From the looks of it, some particles are having problems and since it's probably some sort of a loop the program has to wait until the loop is finished before it can process anything else. And that would cause a good bit of lag.

The ones near the top look like the game is searching for what you would traditionally call a texture or skin that doesn't exist (eg.'materials/refining/refining_decal_danger_01.material'). It's likely from duplicate materials or just a file that wasn't included in the package.

The short answer though, is no nothing you can do other than wait til the devs notice it and fix it.

baseless research

<!--quoteo(post=1989494:date=Oct 10 2012, 04:48 PM:name=Davil)--><div class='quotetop'>QUOTE (Davil @ Oct 10 2012, 04:48 PM) <a href="index.php?act=findpost&pid=1989494"><{POST_SNAPBACK}></a></div><div class='quotemain'><!--quotec-->Yea those are all procedure calls, in short it's a problem with the hard code in the game. The reason why it's giving you a lag spike is likely cause physx is a sort of physics engine that nvidia acquired a while back. It uses the gpu to take the load off the cpu in calculating physics information. From the looks of it, some particles are having problems and since it's probably some sort of a loop the program has to wait until the loop is finished before it can process anything else. And that would cause a good bit of lag.

The ones near the top look like the game is searching for what you would traditionally call a texture or skin that doesn't exist (eg.'materials/refining/refining_decal_danger_01.material'). It's likely from duplicate materials or just a file that wasn't included in the package.

The short answer though, is no nothing you can do other than wait til the devs notice it and fix it.<!--QuoteEnd--></div><!--QuoteEEnd-->
Well that kinda sucks. Still, at least it's got nothing to do with my system. Was starting to get worried.