58 réponses à ce sujet

[PieceMaker42]

nvm.......

Modifié par PieceMaker42, 28 janvier 2010 - 10:58 .

[MadChef -MoG-]

This is killing the game for me.... will someone from bioware please respond? I wish they would just develop all of their games the way they did with dragon age (developing for PC and console at the same time, rather than a strait port for PC). The controls and the mouse feel in dragon age were flawless.

The main thing I don't understand is why is the sensitivity in ME2 so much higher during combat rather than when you are just exploring? It should be the same.

Modifié par MadChef -MoG-, 30 janvier 2010 - 05:50 .

[Baby Ninja Jesus]

i bet you it was EA

"lets save money, make it a direct port, no additional work, 100% additional cash!"

"But but, mouse sensitivity...?"

"**** em, there just PC gamers, the PC is crap for games, consoles are the way of the future!"

i have uninstalled until it gets fixed, utter ****en disappointment.

Modifié par Baby Ninja Jesus, 01 février 2010 - 05:11 .

[Lucky12345]

This is really shockingly bad. Bioware needs to patch the mouse sensitivity problem ASAP. Or, start offering refunds. ME1 worked just fine and, being a non-programmer, I dont wish to f**k around with .ini files or whatever. Quality control anyone? Playtesting? Refund?

[Iron Spine]

Went ahead and read the entire thread. Saw plenty of entries about crashing and noone explaining why (unless I just missed it) so I'll chime in quickly. The file contains structures that define the length of the data in the embedded files. The game parses these structures so it can read the data correctly. These structures contain precise data length details.

When you make a change that increases or decreases the character count (total bytes) in the file, such as changing True to False (+1 bytes), the structures that define the data no longer have the correct byte length associated with the data. It's off by 1 byte (-1) in this example.

This is why the community created automation tools to rebuild the file so folks can edit it and not have to manually calculate the changes. This also prevents the need to have to remove (or add) bytes somewhere else to compensate for you adding (or removing) bytes related to the changes you've made, such as the True to False situation.

For the mouse or anything else related to Coalesced.ini give this a spin:
social.bioware.com/forum/1/topic/106/index/834703

In the Quick Jump Panel tree, BIOInput->Mouse Tweaking

EDIT:
Btw we all agree there should be in game options to do this. But until that happens, this is the way to do it.

Modifié par Iron Spine, 12 février 2010 - 06:07 .

[TessaRahr]

Thanks so much for all the help! I know I'm, like, a year late and all, but the notepad++ thing works. Of course you should always have a copy of the original, just in case.I find 0.2 would be perfect if it had accel, but it doesn't seem to. I currently use 0.4 - and it is a little fast, but much better than 0.3.

[masume]

apparently Bioware believes PC gamers are second class citizens.

[Bogsnot1]

Bioware's bread and butter were PC gamers, right up until the bloated scum at EA bought them out.

I have plenty of good things to say about Bioware, as they used to make solid, dependable games. EA coporate overlordship has ruined that aspect of Bioware, as they now get pushed to get their games out by quarterly deadlines to satisfy shareholders, instead of getting their games out relatively bug free, and satisfying their customers.

Game owners are quite happy to wait an extra month if it means the game will be more polished, smooth, and bug free. EA seems to think shareholders will dump their stock if they dont get a huge return every quarter. Wonder how EA will feel when shareholders start dumping their stock because people stop buying the crap that EA forces out before its ready.

[sepp0o]

mR.Waffles wrote...

I tried to change the .ini file to make the mouse sensitivity managable, but the game crashed on boot. When I re-edited the file the game still crashed. I had to reinstall. If anyone finds out how to fix the sensitivity let us know. I've been using the logtech set point drivers to drop my mouse to 400 DPI. It's a crude fix but it makes the game playable.

The total number of characters in the .ini file must not be changed either.

You have the values
MouseSensitivity=1.0DoubleClickTime=0.250000

If you want to change it to 0.09 (like I did) you have added a character. A fix would be to remove the last 0 from DoubleClickTime

MouseSensitivity=0.09DoubleClickTime=0.25000

if you add more charachters, you have to remove more of the 0's

MouseSensitivity=0.0009DoubleClickTime=0.250