Jump to content

Psythrandir

Member
  • Content Count

    92
  • Joined

  • Last visited

About Psythrandir

  • Rank
    Survivor

Profile Information

  • Gender
    Not Telling
  • Location
    Hamburg, Germany

Recent Profile Visitors

681 profile views
  1. Hi! Das es am reviven liegt können wir so nicht bestätigen. Damit haben wir keinerlei Probleme. Wir nutzen auch kein Infistar z.Zt. sondern nur Epoch antihack.
  2. Du scheinst das gleiche Problem wie wir zu haben. Leider konnten wir den Fehler noch nicht lokalisieren. Wir konnten lediglich die Dauer der Lags durch das Entfernen einiger scrips erheblich reduzieren. Wir haben jetzt ein von Black Eagle modifiziertes VEMF, das A3AI 0.9.3 laufen und ein custom lootbox script laufen. Dadurch konnten wir die Dauer der lags auf wenige Sekunden reduzieren. Sofern wir beobachtet haben, tauchen diese Lags nur noch dann auf, wenn ein Spieler das spawnen der Bots aus dem VEMF script triggert. Google transaltion: You seem the same problem as we have. Unfortunately, we could not locate the fault. We were only able to significantly reduce the duration of the lag by removing some scrips. We now have a modified Black Eagle VEMF that run A3AI 0.9.3 and running a custom script lootbox. This allowed us to reduce the duration of the lag of a few seconds. Insofar as we have observed, these lags appear only when a player's spawn the bots from the VEMF script triggers.
  3. Since we've disabled the halojumps in the custom spawn script the lags are gone. In the last days we had one lag which was caused by a player trying to connect with our server. This guy is playing in our group so he is online more often. Usually no lags happen when he is connecting. Meanwhile he has serveral succsessfull connections to the server without producing any lag. I think/hope this one Lag was an exception. Other players (some of them were new) who have connected don't produced any lags. BTW: We have enabled the parachute drops by A3EAI but it didn't work. We have 80% chance of such droppings and a 50-60% chance for Chopper reinforcements but it seems that this isn't working too. Any other make such expiriences with 0.9.3.2??
  4. We've have disabled the halojump spawn and its seems the lags are gone. A3EAI can still jump out of choppers with parachute (for example when helis are shooted down) and produces not lags atm.
  5. Since we've disabled the halojump spawn it seems that the lags are gone.
  6. We just tested to jump out of a chopper with an equiped parachute and this time no lag happends.
  7. Now we've reduced the A3EAI spawns but that did not solved anything. We've got 3 very big lags today. ALL of these lags happend when a player tryed to connect to the server. At this Time I've found following in the RPT: 21:38:23 Server: Network message 2409ff is pending 21:38:23 Server: Network message 240a01 is pending 21:38:23 Server: Network message 240a01 is pending 21:38:23 Server: Network message 240a01 is pending 21:38:23 Server: Network message 240a03 is pending 21:38:23 Server: Network message 240a04 is pending 21:38:23 Server: Network message 240a05 is pending 21:38:23 Server: Network message 240a06 is pending 21:38:23 Server: Network message 240a07 is pending 21:38:23 Server: Network message 240a08 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a0a is pending 21:38:23 Server: Network message 240a0a is pending 21:38:23 Server: Network message 240a0a is pending 21:38:23 Server: Network message 240a0a is pending 21:38:23 Server: Network message 240a0b is pending 21:38:23 Server: Network message 240a0c is pending 21:38:23 Server: Network message 240a0c is pending 21:38:23 Server: Network message 240a0d is pending 21:38:23 Server: Network message 240a0d is pending 21:38:23 Server: Network message 240a0d is pending 21:38:23 Server: Network message 240a0e is pending 21:38:23 Server: Network message 240a0f is pending 21:38:23 Server: Network message 240a0f is pending 21:38:23 Server: Network message 240a10 is pending 21:38:23 Server: Network message 240a10 is pending 21:38:23 Server: Network message 240a11 is pending 21:38:23 Server: Network message 240a11 is pending 21:38:23 Server: Network message 240a13 is pending 21:38:23 Server: Network message 240a13 is pending 21:38:23 Server: Network message 240a13 is pending 21:38:23 Server: Network message 240a14 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a33 is pending 21:38:23 Server: Network message 240a3b is pending 21:38:23 Server: Network message 240a3b is pending 21:38:23 Server: Network message 240a3c is pending and.. 21:38:17 No player found for channel 1358753728 - message ignored 21:38:17 No player found for channel 1358753728 - message ignored 21:38:17 No player found for channel 1358753728 - message ignored ... (about 30 or more times) This kind of error messege I did't seen before I think. The custom spawn script we are using has the option to spawn with an halojump by using a parachute .... A3EAI has an option with parachutes too (Helicopter patrouls and helicopter reinforcements) which we have enabled. May be the lags have something to do with the parachutes?? (sorry for just copying my post from the A3EAI thread but this issue makes me mad und we want to figure out whats the reason for)
  8. Now we've reduced the A3EAI spawns but that did not solved anything. We've got 3 very big lags today. ALL of these lags happend when a player tryed to connect to the server. At this Time I've found following in the RPT: 21:38:23 Server: Network message 2409ff is pending 21:38:23 Server: Network message 240a01 is pending 21:38:23 Server: Network message 240a01 is pending 21:38:23 Server: Network message 240a01 is pending 21:38:23 Server: Network message 240a03 is pending 21:38:23 Server: Network message 240a04 is pending 21:38:23 Server: Network message 240a05 is pending 21:38:23 Server: Network message 240a06 is pending 21:38:23 Server: Network message 240a07 is pending 21:38:23 Server: Network message 240a08 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a09 is pending 21:38:23 Server: Network message 240a0a is pending 21:38:23 Server: Network message 240a0a is pending 21:38:23 Server: Network message 240a0a is pending 21:38:23 Server: Network message 240a0a is pending 21:38:23 Server: Network message 240a0b is pending 21:38:23 Server: Network message 240a0c is pending 21:38:23 Server: Network message 240a0c is pending 21:38:23 Server: Network message 240a0d is pending 21:38:23 Server: Network message 240a0d is pending 21:38:23 Server: Network message 240a0d is pending 21:38:23 Server: Network message 240a0e is pending 21:38:23 Server: Network message 240a0f is pending 21:38:23 Server: Network message 240a0f is pending 21:38:23 Server: Network message 240a10 is pending 21:38:23 Server: Network message 240a10 is pending 21:38:23 Server: Network message 240a11 is pending 21:38:23 Server: Network message 240a11 is pending 21:38:23 Server: Network message 240a13 is pending 21:38:23 Server: Network message 240a13 is pending 21:38:23 Server: Network message 240a13 is pending 21:38:23 Server: Network message 240a14 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a32 is pending 21:38:23 Server: Network message 240a33 is pending 21:38:23 Server: Network message 240a3b is pending 21:38:23 Server: Network message 240a3b is pending 21:38:23 Server: Network message 240a3c is pending and.. 21:38:17 No player found for channel 1358753728 - message ignored 21:38:17 No player found for channel 1358753728 - message ignored 21:38:17 No player found for channel 1358753728 - message ignored ... (about 30 or more times) This kind of error messege I did't seen before I think. The custom spawn script we are using has the option to spawn with an halojump by using a parachute .... A3EAI has an option with parachutes too (Helicopter patrouls and helicopter reinforcements) which we have enabled. May be the lags have something to do with the parachutes?? jaspoe ... do you have enabled parachutes on your server too?
  9. Today we've added a custom spawn script and A3EAI 0.9.3.2 too and the lags are back! Maybe the new custom spawn script is the reason, But I don't really think so. Seems to a problem with the AI.
  10. Today we've added a custom spawn script and A3EAI 0.9.3.2 too and the lags are back! Maybe the new custom spawn script is the reason, But I don't really think so. Seems to a problem with the AI.
  11. GTX has created a new server with a fresh DB for us (Using the same settings as the vanilla test server). We've added the earplug script, a status bar and an older release of VEMF for first and it seems all is running fine atm.
  12. No we don't using HC or something else. Our Support created a new Server with a fresh DB and the same settings like the vanilla testserver. ATM we don't have any lags. We've added an older release of VEMF and and it seems all is running fine atm.
  13. THX for your support! Our Provider has create us a new vanilla server on the same machine where our mainserver is running. We're testing it since Sunday evening and until now we can't recognize any lags. The support is trying to copy the settings of the testserver onto our mainserver. We hope this will fix the issue. BTW: Because we're not the only ones who have that kind of problem I'm in a discussion about this issue with others in this thread too: http://epochmod.com/forum/index.php?/topic/31551-a3eai-roamingvehicle-ai-patrols-discontinued/&page=47
  14. Guys... this is totaly off topic. Could you open an own thread for that discussion please?
  15. GTX has made us a server which is running on the same machine where our "real" server is hosted. This new test server is running on vanilla. We are testing it since Yesterday evening and don't had any lags yet. We will test it until tomorrow. If all is running fine than the GTX support wants to copy the settings of the test server to our main server in hope that this will solve the problem. I hope this is working.
×
×
  • Create New...