Quote from: Incognito on August 26, 2016, 08:04:30 AM
Hello ! Don't worry I haven't forgotten the project, I am proud to say I have found the engine I'll use, it is called the Daemon engine, and is an upgrade of the ID tech 3, that means it is still fully backwards compatible with all the materials created by Raven Software for Jedi Outcast and Jedi Academy, tons of high poly characters and textures to recycle ! 

It was used for a FPS named Unvanquished, which looks graphically like a mix of Quake III, DooM 3, Half-Life 2, and Halo CE, very neat.

For now I'm still gathering all the necessary materials to start it.

Just please don't make heroes have Jedi Academy or Outcast saber mechanics. Their system is too gated by movement which seriously detracts from the skill cap

Quote from: Darth Nyx on August 26, 2016, 02:06:12 AM
IMHO, someone should let AMD know so that they can fix this issue without people having to go through a lot to fix it themselves.

1. AMD probably wouldn't care about such an old game
2. It's really not that hard in the grand scheme of things

1. Go to https://mega.nz/#F!8tlAhDyQ!2AkAQukJKAYuIWEzDTGtFA!IslFkTSL
2. Click on Direct X 9.0
3. Right Click on 14.12.zip
4. Do a Standard Download
5. Extract Files to Same location as BattlefrontII.exe (locations for both Steam and disc versions will be provided below)

This will prevent you from having to do a driver "rollback" simply by using older AMD Driver Dlls.

Some people have reported crashes after appyling these changes. To fix this, use a different Driver Version under DirectX 9.0 for Step 3. Not all drivers may be supported by your AMD GPU which might cause your game to crash at launch.

Disc Directory: Windows (C:) > Program Files (x86) > LucusArts > Star Wars Battlefront II > GameData >

Steam Directory: Windows (C:) > Program Files (x86) > Steam > SteamApps > Common > Star Wars Battlefront II > GameData

Quote from: Anyder on August 24, 2016, 12:37:16 PM
I dont think there's a limit. When I got banned here and logged after i was unbanned (idk if it was 2 months) I had like 3 pages of unread topics.

Mine usually disappears after about 3 to 7 days and I never log in and out or delete cache or cookies

Quote from: Anyder on August 24, 2016, 02:22:00 AM
It does.
Personally I recommend 40 tps and /waitlate for matches up to 14 players. Anything above that would require 35-30 tps (but definitely nothing below 30)

There are a lot of ignorants who blame short registry on the masterserver, and they're wrong, obviously. It has to do with the server host, not the masterserver.

Oh, okay. Good to know. I've always felt ping was a bigger factor though

Quote from: Anyder on August 24, 2016, 02:17:31 AM
It's those u havent checked out (yet)

I know that but how recent? If I don't check lets say thread A for a certain amount of time it disappears and another list of threads appear if I forget to check this site

I've noticed the "Recent Unread Topics" button on the homepage and was wondering exactly what recent is in this case. a week? 3 days?

Do you get the message while other people are playing on your server?

Quote from: Auggie on August 23, 2016, 08:32:12 PM
Earlier today, I was playing on my 40tps GameRanger server (Don't worry, I haven't given up on SWBF2 SWBFSpy at all. Playing on GR has made me realize how horrible the software really is.) with about 20-30 players on it, and I noticed that the hit registry was HORRIBLE. At times, I could run up behind a guy and shoot him in the back with a shotgun at point blank range, and it wouldn't do any damage at all. Those were extreme cases though. Most of the time, I would shoot a guy with a shotgun and it'd only do maybe 0-25% of his health per shot. And no, it's not lag. I had an 80-85ms ping and very smooth-looking player movements the entire time. I know this is bad hit registry because earlier, I was 1v1ing a guy on my server (only 2 players on it) and even at medium ranges, I could 1-shot him with the shotgun. I could even 1-shot him in the air when he was using the Dark Trooper!

My theory is that past maybe 5-10 players, the hit registry of a 40tps server starts to become worse than 30tps, which is obviously what it was designed to run at. Sure, 40tps is STABLE at way past 5-10 players, but I think the hit registry starts to drop off.

Before I compare 40tps to 30tps, and subject my players to even worse hit registry, I wanted you guys' opinions. Does this even make sense? Can a higher than supported tick rate such as 40tps actually cause worse hit registry at higher player counts? Or is this just the result of SWBF2's poor net-code?

I believe simulation rate or tick rate only effects stuff like how fast you fall and some other stuff... I don't think it matters for hit detection, at least not for Hero Assault which should translate into guns the same way I would think

Quote from: Auggie on August 21, 2016, 05:48:12 PM
This is it. A guy with the in-game name of "Count of Sereno" was bragging about how he accidentally discovered a way to crash servers using a certain network configuration. I was told this by another player, so I checked the logs, and he was telling the truth. Apparently, he was IP banned on Ryza's server. He joined the server later just to play, and I IP banned him. I have his IP written down just in case anyone needs it. The unfortunate part is that he told a server of about 20 players how he did it.

He was told that by me.... He's reset his router completely since then though so he can't do it anymore. I saw him playing on UnityGaming server on GameRanger recently so I know for a fact he can't anymore. Most people who have this "certain network configuration", are usually doing it on accident and end up getting banned for no reason, but Serano should be kept banned regardless.

Quote from: Auggie on August 19, 2016, 06:47:59 PM
Okay, I installed the 1.5 patch, but people were still able to crash it. I know someone is crashing it because a bunch of other servers were crashed today as well.

Are they crashing the servers in a different way that the 1.5 patch doesn't prohibit? Does a new patch need to be made?  How long would it take to create such a patch? Does anyone even know what they're exploiting in order to create the patch?

I know it's possible certain network configurations can cause a crash on accident because I've seen it happen before to the Ryza server hosted by Ryza Sr. Not to mention a German that goes by Blokk has been using modified VA crash tools that send a massive packet to a specific server to crash it entirely. It could either be Blokk having fun, or a random crashing it on accident, or maybe both.

Quote from: TPRPrivate on August 07, 2016, 11:08:01 AM
what is hexediting?

Downlaod HxD (or any other hex editor works too) from the internet then open your original executable using HxD and then press ctrl r and replace all instances of "gamespy.com" with "swbfgamers.com" and you should be good to go

edit by led:   replace "gamespy" with "SWBFspy"   (caps not necessary)

Cool. The original was fun from time to time

Quote from: TheGangstarTY on August 04, 2016, 09:36:47 AM
There was lots in the summer last year but this year there hasn't been that many. Love your signature by the way Jean

Thanks! Anthony made it so I asked him if I could use it lol (don't mean to get off topic)

Make a shortcut for this game and put it on the desktop for convenience. Right click on the shortcut and select "Properties". Go under "shortcut" and then "target". Do /resolution "your resolution". For example, "/set resolution 1920 1080". This will override any resolution options in video settings. Hope this helps.

Edit by Led:   No.  This will not work for SWBF1.