Black Forest - Ulm

[Dekent]

Ick, a bioware fanboy ;p

Ahem...

The pentium 4 was offically released Nov 20, 2000, next years chip you say?

And the FSB issue occurs on a wide range, it appears to be linked to a chipset that was commonly used in such range. If they did any decent amount of QA this would surely of been revealed.

Even Gamespot (or gamespy...always get em confused) wrote in it's review of the game that it was unable to get the game going on TWO of its test systems, and experinced frequent crashes on the third.

There is also a well known error of the game not running right on Radeon Cards, although as I am a nvidia whore, I am not famliar with this one.

This is not however, the board to discuss such things. I suggest you take a look at the technical help forums at bioware to rest my case.

As for Dom2, from reading through those threads it seems to be software issues that are stopping Dom 2 in its tracks, where KOTOR was gapping hardware one.

[Graeme Dice]

Originally posted by Dekent:
This is not however, the board to discuss such things. I suggest you take a look at the technical help forums at bioware to rest my case.

That hardly shows you what percentage of the people have problems though, does it. It also seems that you don't quite understand what a hardware compatibility issue is.

[Dekent]

Bioware has admitted this problem and is working on it, it is a compatibliy issue.

Also it is true I do not know for a fact if the hardware or the drivers were responsible, but considering that neither mid range p4 or high end radeon cards are exactally rare, this issue should of never made it through QA.

While it's true you can not determine a % from a webforum, I can honestally say in the 15 years I have been playing games have I ever seen a tech board erupt like Kotors did the day of release. It was even worse then pool of radience and its happy fun time windows killing error. There were 100s of Users reporting major errors the first day. Ultimely it was split between people who were found to be using pentiums in the range of 2-2.8ghz and people who were using radeon cards. Many people reinstalled windows, formated their HD, and other such nonsense to no avail. QA missed something major, it has been admitted by them, I do not see what yall are trying to defend.

[Osium]

I think many of the issues with Kotor can be attributed to the fact while it is NOT a direct Xbox port, it was co-developed for both platforms and alot of code etc was cannibalized between the two.

I personally had zero problems aside from sound related slowdowns, which I fixed by turning off sound in a couple key locations.

I was using a Radeon 9600pro I even had hardware mouse on which crashed apparently every other Radeon user alive ;p I used a P4 as well. My system should have fallen under the unable to play, but I experienced one crash the entire game in an autosave loading the Last level of the Indictor cruiser level. I got around the crash by loading the autosave it generated and then crashed while making ;p

Bioware has a large QA department as I understand it, I think companies need to stay away from ports and co-developed stuff, ive yet to see an xbox port/co-developed game that didnt crash on many system configs or simply ran horribly.

[Dekent]

I still think its a port no matter what they say ;p


Controls that just don't feel right on a computer? Check

Lots of random crashes and general weirdness? Check

Came out 7 months after Xbox Version? Check

It is kinda funny if its a port or not to piss bioware off about it ;p

The levithan crash bug your refering too is also interesting...I still don't think anyone figured that one out other then it stops about half the people who have it in their tracks, who will crash then save (corrupt save) while the other half get lucky where it saves then crash (auto save on the other side of the door of doom you can progress from).