82 réponses à ce sujet

[Bogsnot1]

I may be barking up the wrong tree here, but after going through the various support threads, for various problems in ragrds to DLC, Weapons locker crashing, LotSB glitches and the like, it seems that most of the people having problems are running the 64bit versions of Win7 or Vista.
So, I need your help to either confirm or deny this theory by listing 4 things.

Windows Version: XP, Vista, or 7
Version format: Home, Professional, Home Basic, Ultimate etc
Bit Version: 32 or 64 bit. (If you dont know, look at the system summary in your control panel.)
Technical Competance Level (out of 10)

My theory is simple. ME and ME2 are 32bit coded software packages, designed to run on 32 bit operating systems. Windows is not the most stable OS to begin with, and trying to run a 32bit app on a 64 bit system could be all it takes for Windows to start crashing, with the blame being placed on the 32bit app, rather than Windows inability to "downshift" itself correctly.
I could be onto something, or I could just be blowing smoke out of my ass. I dont know, thats where you folks come in.

That said, before anyone starts jumping up and down demanding that Bioware/EA fix this oversight, just remember that you were the one who went out and bought the 64bit operating system, when there was a distinct lack of 64bit applications available on the market, especially when ME and ME2 werent coded in the 64bit architecture. If you were "suckered" into buying it by a smooth talking sales rep, then that too is your own fault for not being an informed consumer.

Now, please post away and let me know what versions you have, and what problems. Keep it short and sweet, as I dont plan to read any essay's.
Those of you who want to flame, send it as a PM, and I'll deal with you the same way I dealt with the others who take issue with my bluntness. With logic, reasoning, and ridicule.

Edit: Added one more requirement.
Edit2: Changed topic from "Windows 64bit to blame for the problems?" to "Windows UAC etc etc"

Modifié par Bogsnot1, 13 janvier 2011 - 11:23 .

[JamesMoriarty123]

Windows Version : Win 7

Format : Ultimate

Bit Version : 64bit



No problems at all. Ever. 3 full playthroughs totalling about 90 hours all together, last playthrough with pretty much all of the DLC, all missions, Overlord + LotSB, weapons packs etc, and have had maybe 2-3 random crashes in 90 hours.



In all fairness since I bought Win764 Ulti none of my games have crashes really, the odd random crash after like 40 hours of gaming but nothing you'd notice. And only 1 BSOD in about a year now. For me Win7 is the most stable OS I've ever had, but I think a lot of people might be experiencing problems with old hardware not ready for it.



For example, prior to 1 year ago I had an MSI motherboard, it REALLY didn't like Win7, at all. 3 BSOD's per day, sometimes 4, this was guaranteed, I had ZERO stability. Soon as I deduced the prob was the board from the error codes, replaced it with an ASUS Evo and as i stated above, had 1 random BSOD in a year, which is pretty freaking awesome.

[Stensig]

Win7 64bit Ultimate.



Sometimes the game randomly crashes, but its not often it happens. that's the only problem i can link to windows, of those "problems" im having in ME2. Same happens in DA:O, sometimes it just crashes without reason.

[Bogsnot1]

Out of curiosity, what level would you rate your technical expertise?

This could also be a contributing factor as to why some crash, and others dont.

[Stensig]

on a scale from 1-10 where 1 is best, i'd say around 4 or 3

[solowka]

windows 7 Home Premium 64bit



Problem - keyboard and mouse dont work in game but do in the menu.



a mate of mine has Windows Vista 64 bit and has had no problems

[Bogsnot1]

From the mouse keyboard thread....

solowka wrote...

interesting...got a response back from EA "Unfortunately the game is not tested on Windows 7 or 64 bit environment."

http://social.biowar...5646360#5698360

Food for thought.

[Stensig]

WTF!?

[JamesMoriarty123]

I build PC's regularly for friends and family and have been messing around with PC's for 15 years so I'd say around 8 for my tech expertise.

[Jack Lamden]

solowka wrote...



interesting...got a response back from EA "Unfortunately the game is not tested on Windows 7 or 64 bit environment."

What the representative stated is not completely accurate.

We tested on several flavors of windows XP, Vista and Win 7.



Much testing was on 32bit XP as that's what our development PCs used at the time, but we did have several test PCs that ran on various flavors of XP, Vista and Win7; one or two multi-OS pcs were set to use the 64 bit versions of the operating systems.

[Funkjoker]

Using Vista64 for almost one year and having no problems whatsoever.

Modifié par Jean-Funk Van Damme, 13 janvier 2011 - 06:56 .

[mad825]

....And 64 bit windows is backwards compatible (excluding old,old, games/programs as they don't contain x86 instruction sets for a 64x CPU and drivers)

The edition of windows is never going a factor due to the only difference is some nice finishing touches to the features that have been implemented for added security and day-to-day OS usage (back-up,customisation ect.)

I've had no problems and in fact I've ran them both on Visa 86x SP2 (just above min spec) and on Win7 x64 (above rec spec) however what would be of concern would the hardware and the background processes.

Modifié par mad825, 13 janvier 2011 - 08:56 .

[Bravenu3]

I had it running on Win7 Ultimate 64bit for a while and noticed no flaws with either the core game (Collector's Edition) or the DLCs published up till July. Since then, I'm on a weaker machine with different OS and can't check out LotSB.
EDIT: My tech-expertise *roll-eyes* I modded the coalesced.ini to my liking and I can build a PC from it's parts.

Modifié par Bravenu3, 13 janvier 2011 - 10:52 .

[Bogsnot1]

So, it doesn't look like 64bit versions of Windows is specifically the problem, but more than likely the individual installations of them, and no offence to those with problems, the technical competance of the owners of those systems.



1) Store bought PC's with Win preinstalled. Name brands often tend to include a horde of self promotional material, 3rd party add-ins and the like. Depending on supplier, they may even make the true admin account completely unavailable to you, the owner, but instead grant all your accounts "super user" rights rather than full admin.

2) Upgrade versions that just plaster the Win7 functionality & UAC on top of a pre-existing Windows build, either Vista or XP.

Call me paranoid, but Ive never trusted either of the above scenarios, and tend to build my rigs with full blown versions of the OS, with 3rd party software only being installed at my command.

I also do not see the point in buying 64bit versions of Windows until there is a decent complement of software out there to actually run on it. This is mainly because of MS's habit of releasing their API's to devs, only to then close some of them off later on due to security concerns, which the devs then have to patch around. Add in a 64-32 bit translation layer, and thats just another thing that can cause problems.



So its looknig more and more like UAC, and peoples unfamiliarity with it, than the actual Windows revision. Will edit topic to suit.



@mad285: Theoretically they are backwards compatible, the same way that theoretically Windows is a multi-tasking operating system, when it is more a time-division multiplexing OS. I'm not a dedicated penguin-head, but I believe MS are only just now starting to get their act together, with Win7 being equivalent in terms of security and stability of Linux builds released 10 years ago. They still have some way to go, but they are at least moving in the right direction.

[Bailyn242]

I'm having an issue that I'm wondering if it is Win 7 Pro 64-bit related.



We just added a new Mac Mini 2010 model to the office and since we're a web development shop we've installed Win 7 Pro 64-bit in a dual boot configuration. I installed ME2 and every DLC including LotSB but not Overlord just fine. After playing the game for a bit and getting back into it I decided to add Overlord. Overlord installed just fine on my personal Win XP Pro 32-bit at home but when I went to add it to the work Win 7 Pro install It does not appear to have installed at all.



When I originally downloaded it I got several errors and thought that might be the issue but I have since, days later, re-downloaded it and attempted the install again. Still nothing. I have managed to transfer my save games from the pokey old home system and using Gibbed Save Editor I've managed to delete references to the Overlord install from the home system so I could play them but I still cannot install Overlord.



I have a 2.4 Ghz Core2Duo, 8 GB Ram Nvidia Geforce 320M with 256MB and Win 7 Pro 64-bit

Game Version is the Gamestop Digital Deluxe Edition and updated to the latest patch.



Any suggestions to resolving this would be helpful.

[Bogsnot1]

@Bailyn: This is more of a discussion and fact-finding thread about Win7 & UAC. If you would care to start a new thread about your issue I'l happily respond in there. Dont want this to get too cluttered.

Fire up the game launcher, select configure, and then Summary under the System section. That should have a lot of the info we need to help troublshoot. (driver revisions and the like)



@NewMessageN00b: "Easy to Use" is what got Windows into all those security problems in the first place. Throwing UAC on top of Windows when people now expect Windows to automatically do and trust everything, seems to be leading us to this problem. Its not up to Bioware to write a logging system to compensate for the OS's shortcomings, not unless you want them to start charging even more for the game.

Windows has its own niternal logging system which you ca use, and it thats not specific enough, ther are 3rd party applications you can download and/or purchase.

[JamesMoriarty123]

Bogsnot1 wrote...

I also do not see the point in buying 64bit versions of Windows until there is a decent complement of software out there to actually run on it.

Well, the only reason most gamers SHOULD have a 64bit OS is the RAM limit. On 32bit you can only utilise 3.5GB of RAM. On 64bit its way higher.

Pretty elementary tbh...

[Bailyn242]

Bogsnot, thanks.... posted new topic regarding my issue.

[Bogsnot1]

Just thought of something else, as I mentioned in the help thread for Bailyn.



Some of the DLC isnt digitally signed. Depending on Windows UAC, AV and Firewall settings, permissions might not be granted for the files to run and/or install correctly.

If this is the case, then a small oversight in Bioware's QC regime could be whats causing so many headaches.

[AureateFlux]

Well, since the obvious test to this line of reasoning is to simply turn off UAC and try installing and running ME2 and its DLC on a Win7 x64 system that has encountered DLC-related crashes, I suppose I may as well volunteer.



So, to illustrate the issues I ran into: Went through entire game with one playthrough using only DLC available within the first month after release. A bit after Shadow Broker released, i returned to that save and played through all the content DLC that had been released in the interval. Everything worked fine.



So I decided to start a new game with my "evil" Shep. Having heard that people had been having trouble with Shadow Broker re. Samara's recruitment, I decided to uninstall the DLC and hold off on it until after a certain point in the game. When I did decide to reinstall the DLC, I found that I couldn't load into Omega: I consistently experienced a crash during the load-in. Removing the Zaeed DLC and reverting to a save from just before I installed the DLC got me playing again (I tried several discrete downloads of the DLC before giving up on ol' Zaeed--frustrating since he worked fine in the other save).



Later, I tried to go to Illium, which presented another crash. Some fiddling got me onto Illium (no shadow broker DLC, but i wasn't intending to use it anyhow) and I completed it only to discover that... now the Normandy was off-limits. At this point, enough was enough-- I gave up and decided to try again the next time I decided to format and do some other maintenance on my computer.



That, actually, I haven't gotten to yet, but since the ME2 itch came on the other day, I decided I may as well.



So. What I'm going to do tomorrow once Steam finishes reacquiring the game data: install the DLC required by my current save file (just in case, i downloaded discrete copies of the DLC and deleted older copies and the ME2 folder entirely tonight) and verify whether the crash has been resolved. If so, I'll let you know.



If not, I will delete the DLC installs again (any votes on completely wiping out the ME2 folder again and downloading from the cloud again?). Then I'll disable UAC, reinstall the DLC, and see if I encounter any crashes. To thoroughly test crashes, I will explore each area of the Normandy I have access to in my current save, then visit each of the worlds w/ priority for the worlds with DLC content.



Wish me luck

[Kronner]

Disable UAC, it is redundant unless you let idiots near your PC.

I have Windows 7 64bit and I have not had any problems with ME2 at all.

Modifié par Kronner, 14 janvier 2011 - 08:45 .

[Bogsnot1]

You sir, are a gentleman and a squire. I dont have WIn7 myself, so I am limited to merely coming up with the theories, and unable to test for myself.

My vote, if you can forgive me for asking you to spend the extra time, would be to purge the Steam cache, and get everything from the cloud again, purely to put yourself into the shoes of a recent purchaser of both game and DLC.



Good luck.

[AureateFlux]

A quick note: upon installing the Crash and Kasumi (the only ones the current save file apparently wants), the compatibility agent warned that the program may not have installed correctly and urged that I reinstall using recommended settings. I chose to reinstall, since I will likely have the same option with other DLC. This lends some credence to the UAC interference theory.



Unfortunately, it also means it will be hard to tell whether the clean install or the compatibility agent is responsible for avoiding the crashes. But since I've got plenty of DLC left to install and plan to visit as many locations as I can to test for crashes, I hope to be able to isolate these variables later. Obviously, I'm optimistic that the compatibility agent coming up on both the NormandyCrash install and the Kasumi install indicates a likely connection to the crashes.