7 réponses à ce sujet

[IAmDeathComeForThee]

This area is for a PW, and after it went live this started to happen.  The area runs fine when transitioned to at first, but after being in the area for roughly a half hour, the following occurs.  (see screen)  This is the most pussling thing about it, it only occurs after you've been in already for about a half hour, it doesn't make much sense.

 

I need to test further if it occurs in single player mode or not, but as you can see, many different icons suddenly turn into into the missing 2D texture and then conversations wont come up on NPCs, transitions stop working and usable objects like chemo chairs stop working.  Some have reported lag that basically makes the area come to a stop for them as well. 

 

I have several custom placeables Ive put into the area, but Ive used them in other areas as well and they've turned out fine.

Has ayone else ever experienced this?   

 

[Dann-J]

Could there a looping script that continuously spawns something over and over again? After a certain period of time it might exceed the maximum number of objects the game engine supports for any one area. If it's something invisible, like an ipoint or a trigger, you might not even notice it happening.

[IAmDeathComeForThee]

Hmm I don't think so.  I'll run that by our scriptors and see as I had them make a couple custom scripts for some triggers I laid down.   I'm no scriptor so I'm not even entirely sure what an ipoint is. ?   Never the less, there shouldn't be any scripts spawning anything aside form the MPWC spawner spawning the mobs for the area...  :/

[ColorsFade]

A slowdown like you're reporting, and the icon issue, makes me think it's a scripting issue. And since people are hitting a wall after X minutes, that would jive with a scripting loop. 

 

I accidentally spawned a creature indefinitely upon an area load once. The game eventually stopped spawning the creature, but it was pretty funny (I captured a screenshot). 

 

Definitely check with your scripters. Ten-to-one it's a scripting error. 

[IAmDeathComeForThee]

Awesome, thanks guys.  That's a load off my shoulder's as I thought it maybe had something to do with my custom placebles or just a corrupted area of some kind, which would suck bigtime.  We'll see if we can find it.

[Morbane]

Could there a looping script that continuously spawns something over and over again? After a certain period of time it might exceed the maximum number of objects the game engine supports for any one area. If it's something invisible, like an ipoint or a trigger, you might not even notice it happening.

 

Just to reiterate...

 

A slowdown like you're reporting, and the icon issue, makes me think it's a scripting issue. And since people are hitting a wall after X minutes, that would jive with a scripting loop. 

 

I accidentally spawned a creature indefinitely upon an area load once. The game eventually stopped spawning the creature, but it was pretty funny (I captured a screenshot). 

 

Definitely check with your scripters. Ten-to-one it's a scripting error. 

 

Definitely an infinite loop somewhere - or perhaps a script is looking for something that does not actually exist but the script thinks it does, with no way of stopping itself from checking.

 

I had a script which i posted in the scripting forum - it checks if the enemy has a silver weapon - but if the enemy had no weapon the game froze after the perception scripts completed.

 

can of worms on that area - tell the scripters to be aware of the virtually endless possibilities of something that is eating memory.

 

good luck.

[kevL]

ima gonna fix that.

 

I had a script which i posted in the scripting forum - it checks if the enemy has a silver weapon - but if the enemy had no weapon the game froze after the perception scripts completed.

[Dann-J]

I've created infinite loops by accidently commenting out too many lines in a script while testing it, which included the 'GetNext...' line at the end of a While(GetIsObjectValid()) loop. The game froze for about a minute, but eventually aborted the loop by itself. It took me ages to locate the source of the mystery pause.

 

Thankfully it was only checking for creatures in a radius, and not actually spawning anything. The first creature it found got well and truly scrutinised!