Battlefront II Server Software Reports

[RaTix]

Just wanted to post the bugs and setup glitches found with the server software. Plz feel free to add and post any new findings.

• - Server will not start with 70+ maps selected. *may be due to command line character limit
  - More then 16 AI will result in not being able to see AI blaster fire or nades.
  - Keeping the AI and actual players in server near 24 Total, will lessen the frequency of server crashes.
  - Autoboot enable will cause the server to not startup. *May be due to command line character limit
  - Direct Voice seems to work the best
  - The lower the Throttle the shittier the gfx. Throttle works ideal at 1M (1024)
  - Mos Eisley assult (Jedi Battle) Should be kept to low AI and players. The crashing occurs more often on this map, Probally due to heavy jedi gfx and effects.
  - Mic flodding may also be the caus of server crashes.
  - Reinforcements cant be changed on space assaults, Jedi Assault, or hunts

On another Note, If your CD sounds like its skipping or your ps2 making clicking sounds, It is the game itself and not your PS2 or copy. A patch shoul fix this problem. It seems the game is looking in the wrong area of the disk for gfx and sound files.

[RaTix]

Well I think I'm closer to figuring out the the AI no blaster issue. some reaosn when Its only 1 person in the server (well when I'm the only one int he server) There is no AI blaster fire. But as soon as there are 2 ppl in the server it seems to fix itself.

This might be a combination of AI Max limit and player count. Its all very Confusing and frustrating. But I think as long as the AI are below 24, and there are 2 ppl in the server, the blaster fire is fine.

[fromunda]

Thats good to know cause that tickin sound was pissin me off, and about the blasters I cant defend my self if I cant see it comeing. Hopefully they hurry up w/ a patch.

[Nordagh]

I have a question also, besides all the normal crap thats been wreaking havok with servers, when are the leaderboards suppose to start working??? Last game recorded for anyone was like 11/4, did gamespy take a nap?

[Lady_Death]

I gave up on the leaderboards long ago.

[RaTix]

Leaderboards were always crap, im sur ethey always will be.

Anothe rnote on the AI blaster fire issue. If your alone in a server and someone jumps in, they will be able to see the blaster fire. you on the othe rhand may have to Jump out and back into the Server for the Blaster fire issue to fix itself for you.

[RaTix]

Hero Settings

If you set heroes on, and have teh unlock as Always on Random Assignment, Some map the Jedi Will just not apear. Perhaps its randomlly assigning to an AI, who knows.

[RaTix]

Server Ports

These are the ports I have found the server to use. If you are having issues with not seeing your server online, you will need to open these.

These Ports should be set to both UDP and TCP
3658, 13658, 3659, 13659, 3660, 13660

Each are set to one of the sessions in the Server GUI. The 1**** ports are the secondary ports the server uses for the session.

Also UDP and TCP
27900, 27901 (Port for the Gamespy servers)

29920 (Gamespy stat tracking server port)

The server also seems to use ICMP on port 3. This will also have to be opened.

** Side Note **
Even with these ports open, some ppl may have difficulties conencting to your server. It appears that sometimes Battlefront connects on random ports. 3 out of 12 ppl were able to connect with these settings.

Of course if you disable all Hardware/Software firewalls, or DMZ the PC you are hosting on, you will eliminate most issues. Although even fully DMZ'd with no firewalls, I still had a few ppl that could not connect. This was ONLY on a home hosted PC. On our Remote Dedicated PC no one has issues connecting.

[LordYggdrasill]

Re: Battlefront II Server Software Reports

Just wanted to post the bugs and setup glitches found with the server software. Plz feel free to add and post any new findings.

• - Server will not start with 70+ maps selected. *may be due to command line character limit
  - More then 16 AI will result in not being able to see AI blaster fire or nades.
  - Keeping the AI and actual players in server near 24 Total, will lessen the frequency of server crashes.
  - Autoboot enable will cause the server to not startup. *May be due to command line character limit
  - Direct Voice seems to work the best
  - The lower the Throttle the shittier the gfx. Throttle works ideal at 1M (1024)
  - Mos Eisley assult (Jedi Battle) Should be kept to low AI and players. The crashing occurs more often on this map, Probally due to heavy jedi gfx and effects.
  - Mic flodding may also be the caus of server crashes.
  - Reinforcements cant be changed on space assaults, Jedi Assault, or hunts

On another Note, If your CD sounds like its skipping or your ps2 making clicking sounds, It is the game itself and not your PS2 or copy. A patch shoul fix this problem. It seems the game is looking in the wrong area of the disk for gfx and sound files.

About the Clicking sound on the PS2 , u sure it's not the game cuz , when i play other games it doesn't make that clicking noise .

[RaTix]

Again,

If your CD sounds like its skipping or your ps2 making clicking sounds, It is the game itself and not your PS2 or copy.

So yes.. It IS the game. Wether it be poor coding, or just cheap disks they used. It most deff is the game itself. But this is a problem EVERYONE is having. so its not just your copy.

[LordYggdrasill]

Sry Ratix i missed read the post u made . My Bad .

[CRABcrap]

Music skipping

the clicking and music skippng are both very annoying but, i just found out that it not only online but single player too. but hell at least its better than the glitchs and over heating power supplies on the XBOX 360 i've been reading about on news.com.

[Darkcide]

I am a Information Technology student at University of Phoenix Online. I am no genius in the field but I have met a few while in school. It seems that the industry is pushing for release dates and turning a blind eye toward fixing problems with software until later after they get profits flowing. Everyone wanted a copy of SWBF2 and they got one...regardless of actual quality the money changed hands. Dont blame those that create the games, blame the greed of the industry. And it doesnt just end at the gaming end of the stick either. Pity those in the medical field...

[Lady_Death]

Hmmm, ever since ive been playing bf2 my ps2 has been going mad with the clicking and grinding noises. Then it stopped reading disks altogether. IT wouldnt read any other disks either.
I then adjusted the 2 white cogs inside the drive that control the angle of the laser, and it worked again.
If you have this problem, try adjusting the cogs with a star screwdriver a few clicks each time and trying a game inbetween until it stops making noises.
I have the old sort of ps2, but i think on the new slimline one its basically the same inside.

[SHOOTORDIE]

really? i have never had that problem or any of my friends. Then again our ps2s are barely 1 1/2 - 2 years old.