Star Wars Battlefront 2

[DPI Wizard]

Updated with hipfire and zoomed sensitivity for the release version.

View full update

[DPI Wizard]

Zoom sensitivity etc cannot be added until they fix the mouse input.

[noaimBoii]

Can you explain what the mouse input problem is?

[DPI Wizard]

I'm not exactly sure what happens, but when I send counts to do a 360, it ends up at a different spot every time. Kind of like acceleration, but it's all over the place.

Even if I just send one small packet of for instance 10 counts, it moves a different distance every time also. So it's quite obviously major issues with how the mouse input is interpreted. 

[harrspen]

FOV can be changed in the CFG by adding "GstRender.FieldOfView 1.00000" to the ProfileOptions_profile.cfg located in C:\Documents\STAR WARS Battlefront II Multiplayer Beta\settings. Can the calculator be updated to support FOV changes. Thanks!

[DPI Wizard]

15 hours ago, harrspen said:

FOV can be changed in the CFG by adding "GstRender.FieldOfView 1.00000" to the ProfileOptions_profile.cfg located in C:\Documents\STAR WARS Battlefront II Multiplayer Beta\settings. Can the calculator be updated to support FOV changes. Thanks!

Done!

[devilish]

So does zoom work because the option is there

[DPI Wizard]

4 hours ago, devilish said:

So does zoom work because the option is there

Sorry about that, it is not finished yet. It was a zoom sensitivity based on how it works in BF1, but this game seem to work differently. Removed it now until I can analyze it properly.

[TheNoobPolice]

It seems to use a fixed multiplier for ADS rather than a screen space system for the FOV change  (of any monitor distance %), because as soon as you press the ADS button the sensitivity drops instantly to the new turn-rate  even before you've fully zoomed in, which is something I really hate.

[kawaiikate9000]

it could be the post process or other graphics setting in the game thats causing weird mouse delay and inconsistencies. Maybe you can try turning off those settings and running the on lowest graphics setting? 

[CaptaPraelium]

Guys just don't buy this game please. It's pretty obvious that PC gaming is an afterthought to the devs when the MOUSE doesn't work. Unbelievable. We as gamers cannot support this kind of behaviour.

[Mixthat]

6 hours ago, CaptaPraelium said:

Guys just don't buy this game please. It's pretty obvious that PC gaming is an afterthought to the devs when the MOUSE doesn't work. Unbelievable. We as gamers cannot support this kind of behaviour.

I played a few hours and the game completely broke my muscle memory.

[Bikkboii]

Isn't this a pretty simple fix on the developer's behalf, though?

[DPI Wizard]

1 minute ago, Bikkboii said:

Isn't this a pretty simple fix on the developer's behalf, though?

It definitely should be. This engine has proven to be one of the best in terms of sensitivity and options, so I'm not sure how they'd manage to mess it up.

[CaptaPraelium]

On 09/10/2017 at 4:19 AM, Bikkboii said:

Isn't this a pretty simple fix on the developer's behalf, though?

Which is exactly why it should never have gotten this far. Clearly, as has been the case increasingly over the past few years, EA/DICE don't really care about the PC players.
...but we can hardly blame them if we are encouraging their behaviour with our wallets....

Edited October 10, 2017 by CaptaPraelium

[Mixthat]

9 hours ago, CaptaPraelium said:

Which is exactly why it should never have gotten this far. Clearly, as has been the case increasingly over the past few years, EA/DICE don't really care about the PC players.
...but we can hardly blame them if we are encouraging their behaviour with our wallets....

Can't remember problems with BF1 on PC. Probably Dice is pushed by EA since consoles are the main market for their games. Maybe if they would add some competitive aspects PC would gain more attention.

[CaptaPraelium]

BF1 had more problems by far than any BF before it. BF4 was famous for it's poor launch because it had a few major problems which effected a few large groups (eg netcode/hitreg was broken). BF1 on the other hand, spread those problems out, more problems spread among smaller groups (eg keybindings not working, plane-specific bugs, issues with only some GPUs, etc etc etc). This way, they gave the false impression that it wasn't a terribly buggy launch, because rather than having 10000 people complaining about one bug, you had 100 people each complaining about 100 bugs.

I don't know how you can miss the major issues with BF1 right now. To use the most obvious example, try like....looking at your screen. The lighting has been broken for months and will never be fixed, because it had to be broken on every platform so that the game would even run on PS4pro, and fixing it is too big of a job.... And you're right, this is really about EA and not DICE. Dice know what the problem is and they know how to fix it. If EA would give them the resources they need, it could be fixed.

But, supply and demand rules - and that's why I'm encouraging gamers to seriously consider their continued support for the actions of the companies involved.

Edit: I really don't want to get into an indepth political discussion here though, I feel it would detract from the nature of this forum. I've said my piece. If you think that EA/DICE are doing the right thing, please continue to support them.

Edited October 10, 2017 by CaptaPraelium

[DPI Wizard]

The sensitivity is still acting weird, will do some more in-depth analysis this weekend.

[kawaiikate9000]

I dont think the current calculator is accurate for the full version of the game, but it was accurate during the beta.

Im using a tape ruler to measure my 360 mouse movement right now, and it seems I have to roughly double the value that your current calculator gets. Looking forward to using your calculator again so i can stop using my ghetto tape ruler lol

[Pukas]

On calculator it says I have to use 14% for 38 cm 360 at 103 FOV but it's too low, had to set it at 22% to make it feel somewhat the same as in OW and BF1.

Hope you figure it out soon so we can enjoy perfect calculation

[DPI Wizard]

I'll remove the calculations until release, hopefully things will be stable then.

[nwf]

Found this thread from google while trying to troubleshoot a problem, so thanks for this very useful resource

The issue is that there is some wacky shit happening in-game where different classes have different sensitivity scaling. Without changing any of my settings, I can go from a 9 inch 360 (800dpi, 23% soldier, 83% zoomed) to a ~2 inch 360 just by spawning as a wookie warrior and ADSing. Try it in the arcade mode. Nuking the settings folder under my documents doesn't seem to fix it either. This might be what's throwing your calculations off?

 

edit: live game, not beta. wookie warrior aimed sens is ~3x higher than the regular classes, using default settings

Edited November 15, 2017 by nwf

[DPI Wizard]

Added hipfire for assault now, but needs more testing. I suspect it might behave differently of various systems. Any feedback appreciated!

[wooddwarf]

Thx for the hard work!! Tested the new sensitivity settings in game and the measurements with a ruler were spot on. So far so good! 

Edited November 17, 2017 by wooddwarf

[noaimBoii]

Hi. Will the zoomed sensitivity, vehicle sensitivity, starfighter sensitivity, star fighter mouse response, etc be added?