The campaign loaded fine. I gathered all the data and it prompted me to "press F to end the mission." Of course I'm pissed because ME2 doesn't show the actual button I had bound (which is actually on my mouse). But I bound it to F before the mission just to make sure.
Nothing happens when I "press and hold F." Kind of paid for this expansion so I'm hoping for some answers... any suggestions here?
Mass effect 2 firewalker issues (PC version)
Débuté par
spatnatz
, janv. 22 2011 07:30
Retour en haut
#2
Posté 22 janvier 2011 - 08:02
Bogsnot1
-
- Members
- 7 997 messages
#3
Posté 23 janvier 2011 - 01:12
spatnatz
-
- Members
- 7 messages
1. What version of the game are you playing: physical disc or digital download (along with which vendor)?
v1.02, Digital download from Steam
2. System Details
Details about your problem.
1. What is the nature of the problem you are seeing?
Nothing happens when I "press and hold F" at the end of the initial research collection of the Firewalker campaign.
2. When did the problem start occurring?
At the end of the initial research collection of the Firewalker campaign.
3. Where does your problem occur?
The planet where the research data is collected.
4. What are the steps in replicating the problem?
Collect all the data in the first mission of the Firewalker campaign.
5. Have you modified your game in any way?
I have not used any save game editors.
v1.02, Digital download from Steam
2. System Details
Details about your problem.
1. What is the nature of the problem you are seeing?
Nothing happens when I "press and hold F" at the end of the initial research collection of the Firewalker campaign.
2. When did the problem start occurring?
At the end of the initial research collection of the Firewalker campaign.
3. Where does your problem occur?
The planet where the research data is collected.
4. What are the steps in replicating the problem?
Collect all the data in the first mission of the Firewalker campaign.
5. Have you modified your game in any way?
I have not used any save game editors.
#4
Posté 23 janvier 2011 - 02:19
Bogsnot1
-
- Members
- 7 997 messages
ME2 will only give the default keys in the hints, and wont read your new mappings and change the hinit to suit.
The Geforce 700 Go references I found all relate to notebook video cards. Notebook or "Mobility" video chipsets normally dont have the grunt that their desktop counterparts have, and as such arent really supported. This often translates into dropped frames per second, which would cause the F key, or your new binding, not to work when pressed.
I also found a forum on nVidias page about the weknesses of these cards, in both design, and imlpementation into notebooks.
http://forums.nvidia...howtopic=155176
Another thing is your very much outdated video drivers. While I cant guarantee it will fix the problem, update them to a more recent version, but not the very latest. 258.96 is a stable release known to be working with ME2.
http://www.nvidia.co...aspx?lang=en-us
Last thing I noticed, is that even though the T7200 is listed as Core2 Duo, the config utility isnt recognising it as such. This could be that as a mobile CPU, something has been modified in the chipset.
End prognosis is, unfortunately, you dont have the hardware to support the game. The fact that you have been able to up until now means you have been very lucky. If the newer driver revision works, your luck will continue for just that little bit longer.
The Geforce 700 Go references I found all relate to notebook video cards. Notebook or "Mobility" video chipsets normally dont have the grunt that their desktop counterparts have, and as such arent really supported. This often translates into dropped frames per second, which would cause the F key, or your new binding, not to work when pressed.
I also found a forum on nVidias page about the weknesses of these cards, in both design, and imlpementation into notebooks.
http://forums.nvidia...howtopic=155176
Another thing is your very much outdated video drivers. While I cant guarantee it will fix the problem, update them to a more recent version, but not the very latest. 258.96 is a stable release known to be working with ME2.
http://www.nvidia.co...aspx?lang=en-us
Last thing I noticed, is that even though the T7200 is listed as Core2 Duo, the config utility isnt recognising it as such. This could be that as a mobile CPU, something has been modified in the chipset.
End prognosis is, unfortunately, you dont have the hardware to support the game. The fact that you have been able to up until now means you have been very lucky. If the newer driver revision works, your luck will continue for just that little bit longer.
#5
Posté 23 janvier 2011 - 08:12
spatnatz
-
- Members
- 7 messages
Hmm. Let me just say, I am by no means a hardware idiot 
I do understand that it only displays the default mappings, I made that distinction in the original post. That doesn't change the fact that it's a bit annoying, since ME1 was perfectly capable of detecting your actual key mappings.
I get 20-30 fps in ME2 with that hardware configuration. It's very playable. I would like to doubt that the FPS would be the reason for this issue, that just sounds fishy. The performance in ME1 is even slower, and I had no issues like this one.
These mobile drivers aren't updated nearly as often as their desktop counterparts. So updating those isn't much of an option. I've already tried their beta 179.48 drivers from about a year ago, they didn't work very well at all. The fact that the most "up to date" driver is from a year ago should give you an idea of what I'm talking about.
I'm fairly certain that the omission of the "Duo" in the detection isn't much of an issue. A simple CPU-Z diagnostic clearly shows that it's a Core 2 Duo, just a mobile version.
Also, I found a plethory of mobile GPU names in the Coalesced.ini file... so if these cards aren't "supported" then why would those be put there...?
I do understand that it only displays the default mappings, I made that distinction in the original post. That doesn't change the fact that it's a bit annoying, since ME1 was perfectly capable of detecting your actual key mappings.
I get 20-30 fps in ME2 with that hardware configuration. It's very playable. I would like to doubt that the FPS would be the reason for this issue, that just sounds fishy. The performance in ME1 is even slower, and I had no issues like this one.
These mobile drivers aren't updated nearly as often as their desktop counterparts. So updating those isn't much of an option. I've already tried their beta 179.48 drivers from about a year ago, they didn't work very well at all. The fact that the most "up to date" driver is from a year ago should give you an idea of what I'm talking about.
I'm fairly certain that the omission of the "Duo" in the detection isn't much of an issue. A simple CPU-Z diagnostic clearly shows that it's a Core 2 Duo, just a mobile version.
Also, I found a plethory of mobile GPU names in the Coalesced.ini file... so if these cards aren't "supported" then why would those be put there...?
Modifié par spatnatz, 23 janvier 2011 - 06:29 .
#6
Posté 24 janvier 2011 - 02:57
Bogsnot1
-
- Members
- 7 997 messages
Did you also notice that yours wasnt listed?
#7
Posté 27 janvier 2011 - 01:40
spatnatz
-
- Members
- 7 messages
Bogsnot1 wrote...
Did you also notice that yours wasnt listed?
I didn't, because the 7900GS Go is listed.
I've noticed you're posting on a lot of tech topics... best to learn your stuff first.
Modifié par spatnatz, 27 janvier 2011 - 01:41 .
#8
Posté 27 janvier 2011 - 04:44
Bogsnot1
-
- Members
- 7 997 messages
OK, my initial search was for the 7900 GS Go, not Go 7900 GS. I was wrong in that respect.
If I didnt know my stuff, then why do I have a decent success rate in dealing with other issues that crop up? And dont go along and say "google search", I only rely no that to find out about substandard products such as yours. If you know more than me, by all means take over and outshine me in providing support on these forums. The fact that you cant even get yourown version of the game working sorta points that you would be unable to.
That still does not change the fact that mobility chipsets do not meet any form of stanadrd across the board the same way that the full fledged cards do. Laptop manufacturers do not liase with each other to come up with any form of standard across the board as to which features they will enable or disable in the mobility chipsets they incorporate on their mainboards. Given that the computer industry is self certifying (which means they only have to meet the specifications on paper, there is no 3rd party testing facility they have to submit to in order to ensure they physically meet the requirements), there is no way of guaranteeing any form of success.
I have already pointed out that the card you are using has well known and well established weaknesses, but you are unwilling to accept it.
That said, these are user to user support forums, with official support being performed by EA. I invite you to deal with them to sort out the issue.
If I didnt know my stuff, then why do I have a decent success rate in dealing with other issues that crop up? And dont go along and say "google search", I only rely no that to find out about substandard products such as yours. If you know more than me, by all means take over and outshine me in providing support on these forums. The fact that you cant even get yourown version of the game working sorta points that you would be unable to.
That still does not change the fact that mobility chipsets do not meet any form of stanadrd across the board the same way that the full fledged cards do. Laptop manufacturers do not liase with each other to come up with any form of standard across the board as to which features they will enable or disable in the mobility chipsets they incorporate on their mainboards. Given that the computer industry is self certifying (which means they only have to meet the specifications on paper, there is no 3rd party testing facility they have to submit to in order to ensure they physically meet the requirements), there is no way of guaranteeing any form of success.
I have already pointed out that the card you are using has well known and well established weaknesses, but you are unwilling to accept it.
That said, these are user to user support forums, with official support being performed by EA. I invite you to deal with them to sort out the issue.
#9
Posté 27 janvier 2011 - 05:07
IBPROFEN
-
- Members
- 370 messages
Try using the the key that controls your "melee" that was my fix, somehow it switched to that key.
#10
Guest_NewMessageN00b_*
Posté 27 janvier 2011 - 09:42
Guest_NewMessageN00b_*
Guest_NewMessageN00b_*
-
- Guests
Sometimes turning the keyboard over and pushing it helps.
Really, no. It doesn't. But it can't hurt to try all keys in these situations.
I also think that all that notebook argument has gotten old.
Really, no. It doesn't. But it can't hurt to try all keys in these situations.
I also think that all that notebook argument has gotten old.
Modifié par NewMessageN00b, 27 janvier 2011 - 01:53 .
#11
Posté 27 janvier 2011 - 11:59
Moondoggie
-
- Members
- 3 742 messages
This is an old bug that crops up every now and again. It's usually solved by one of two ways. Reloading to the last save and replaying the bit. F to end mission should eventually just work on it's own. Or press whatever button you binded for a melee attack.
I doubt arguing the toss about gaming on notebooks will do anything to solve this issue lol.
I doubt arguing the toss about gaming on notebooks will do anything to solve this issue lol.
