1.3 Patch

Started by boomjohnson, July 16, 2014, 03:44:54 AM

Previous topic - Next topic
July 16, 2014, 03:44:54 AM Last Edit: July 16, 2014, 06:09:35 AM by Led
 :censored:, seems like the 1.3 patch wouldve fixed the  :censored: multiplayer game...

http://starwarsbattlefront.filefront.com/file/Battlefront_13_Patch_Beta;40940


Description:
This is a US only full client patch and you should have the 1.2 patch installed for it to work properly. The final 1.3 patch should be released in a few weeks but in the mean time, install this patch and give it a try. Post any bugs you encounter and I will let the developer know.

This is basically what is fixed,

CHANGES FROM 1.2
-------------------------------------------------------
Multiplayer

* Unlocked frame rate
* Better tolerance of latency spikes and frame rate spikes
* Fixed an end of game hang
* Better smoothing of predicted positions and orientations
* Allow more maps specified from dedicated server command line
* Better Droideka prediction
* Added remote admin support for those hosting dedicated servers
* Tighter clock synchronization under normal conditions
* Fixed joining servers behind most firewalls
* Allow more mod maps (was 50, now 512)

Global

* Fixed CIS Pilot shooting backwards


Pity it seems to never have been released/adopted by anyone at any stage #yolo

Quote from: boomjohnson on July 16, 2014, 03:44:54 AM
Pity it seems to never have been released/adopted by anyone at any stage #yolo

Many players have it ;)
And [FC]Rage has released a GameMaster 1.3 patch for all languages (although the german one was already created, he made it in the game 7 languages).
The only requirement is to have the CD, but as I don't have it, I'll wait for Wolf or Baron to make it no CD fixed
Anyder | Talent, Ops & Culture | SWBF & Player Engagement
Email: communityambassador@swbfgamers.com
SWBFSpy Discord: http://discord.swbfspy.com
SWBFSpy Info: http://info.swbfspy.com

i suspect that once the no cd patch for 1.3 is made and distributed more players will be there. i plan on hosting both 1.3 and 1.2 since i prefer 1.3 so far it is much nicer, but most players are used to 1.2 and will continue to play there. it will be easy to switch between both versions using batch files or maybe a new custom res launcher for 1.3
heres link to my comparison notes http://www.swbfgamers.com/index.php?topic=7975.msg86014#msg86014

Quote from: boomjohnson on July 16, 2014, 03:44:54 AM
:censored:, seems like the 1.3 patch wouldve fixed the  :censored: multiplayer game...


Pity it seems to never have been released/adopted by anyone at any stage #yolo

First, no cursing here.

Second, 1.3 was a beta release that has some issues that prevents it from wide-spread adoption by the community right now, unless it gets fixed.  These issues are documented on the site.  Select search on the menu above and type in 1.3 beta.
Quote from: Abraham Lincoln. on November 04, 1971, 12:34:40 PM
Don't believe everything you read on the internet

Quote from: Phobos on July 16, 2014, 05:26:15 AM
i suspect that once the no cd patch for 1.3 is made and distributed more players will be there. i plan on hosting both 1.3 and 1.2 since i prefer 1.3 so far it is much nicer, but most players are used to 1.2 and will continue to play there. it will be easy to switch between both versions using batch files or maybe a new custom res launcher for 1.3
heres link to my comparison notes http://www.swbfgamers.com/index.php?topic=7975.msg86014#msg86014

yeah just read this thread. seems pretty cool. I hope everyone will move once the nocd patch has been made, just seems like a much better multiplayer experience. Less sponge-ing/more shots registering... If you say it feels more like single player, than multiplayer then that should be enough of a motivator really (id hope)       

You should try the /noframelock command.  It is what makes 1.3 so smooth.  This command works in 1.2.
Quote from: Abraham Lincoln. on November 04, 1971, 12:34:40 PM
Don't believe everything you read on the internet

Quote from: Led on July 21, 2014, 06:03:59 AM
You should try the /noframelock command.  It is what makes 1.3 so smooth.  This command works in 1.2.

However with no frame lock command, you make that the enemy doesn't take 100% damage of your shots.
-={EvO}=- Sonny warned me of this when he first told me about this command, and proved it to me.
Anyder | Talent, Ops & Culture | SWBF & Player Engagement
Email: communityambassador@swbfgamers.com
SWBFSpy Discord: http://discord.swbfspy.com
SWBFSpy Info: http://info.swbfspy.com

Quote from: Hades on July 21, 2014, 06:18:53 AM
However with no frame lock command, you make that the enemy doesn't take 100% damage of your shots.
-={EvO}=- Sonny warned me of this when he first told me about this command, and proved it to me.

I am sure there are special conditions where that statement is and is not true.

There would be no difference in 1.3, except that you can not turn off the noframelock in 1.3.

Changing the tickrate may help, but you can do that in 1.2 or 1.3.

It goes back to no difference.

Anyway, he wanted 1.3 because it is visually smoother, and he can get that same experience in 1.2.
Quote from: Abraham Lincoln. on November 04, 1971, 12:34:40 PM
Don't believe everything you read on the internet

July 21, 2014, 02:56:58 PM #8 Last Edit: July 21, 2014, 03:08:36 PM by Phobos
a 1.3 server with /tps 60 that uses /waitlate is much smoother than /noframelock in 1.2 with /tps 60. i tried using /waitlate in 1.2 and it crashed the server so i dont think the command is supported but it really makes a difference for shots registering. i am starting to find that servers with only /tps 30 dont register shots very often at all now.

2 bugs worth mentioning in 1.2 and 1.3:
- you can throw mines in 30 tps servers but not 60 tps.
- escape button for opening pause menu doesn't work from the spawn screen when using /noframelock in 30 tps servers, it works in 60 tps servers though.