Darkfire

I liked this one.... "BREJIK: Vulkars, to me! Kill the swoop rider! Kill the popcorn vendor! Kill them all!"

You should do well....I've got a 6600GT and it runs damn near everything at high settings. The only thing I can't do with it is run with 4xAA, though 2xAA is good enough for me (it hides the worst of the sawing and once your in motion you'll never see any). That said I have a 3200+ AMD and a Gb of RAM to back it up with. Still a good card though for the price. Wait a couple of weeks though...with nVidia's new card out now, the prices of the older stuff should drop a bit.

lucky bastard <_< <{POST_SNAPBACK}> Remember though that's six mother-in-laws as well...

Frankly I enjoyed using a single saber more than two, though yes two do move 'whaling' damage per ton. Ideally I'd use one for general use and then use two if I really meant it (like boss fighting or hacking your way into the palace near the end of KOTOR II). If they do a third game, I'd like to see them do something about the 'two sabers = best way' thing. Say only allow you use some force powers if you have a hand free like...

I get something similar recently (ever since the 1.0b patch in fact...interesting...). After combat I would get stuck...if I hold down a movement key I would start to move again after about 5 seconds or so. Not much help for you I'm afraid, though does anyone else have this problem? Notice it before the patch?

Careful you get shot just for asking al-la Star Wars Galaxies people...

KOTOR II doesn't need a huge amount of memory (you have enough really, just make sure your swap file is a good size, at least twice the size of your system RAM), and as far as driver settings go, just make sure that the AA and Filtering are set to application mode so the game sets them not the drivers. One thing I note however, is that the latest drivers from nVidia do seem to slow down both KOTOR and KOTOR II. I never had slow down issues before installing the 71.89 drivers, especially on Dantooine in the first game (which for me is even worse than in the second game). Oh and one last thing...defrag the drive you have the game installed on. I'm always installing and deleting stuff on mine, and after defrag the drive things started to fly again real quick...

No, I just don't like really bad console ports of FPS games...

6 hours to complete on hard. And the multiplayer is even worse than Battlefront.

Let me guess...the vibrate option. Always made me raise an eyebrow in KOTOR at the beginning when you find that vibration cell on that female Jedi's body.

It is the upgrade version of XP. <{POST_SNAPBACK}> There you go. Always do a clean install when changing OS. I know there is an upgrade option but as an IT Support guy I can say it causes a lot of problems...especially for games. Microsoft are very brave to try having an upgrade option, but frankly I wish they didn't...would make my life easier! :cool:

WHAT!?!?!?!?!?! SW:RC is one of the best FPS I've ever played. How can you call it rubbish!? Don't like the skill involved? Don't like the fact that there is no auto-aim? <{POST_SNAPBACK}> I didn't like it being so short...and boring...and sloooowwww...zzzzzzz

Don't make me frown at you.... For Bastila!!!

It could also be 'Star Wars: The Adventures of Jar Jar Binks'...

Well given that KOTOR was 4000 years before the Empire, and KOTOR II was 5 years after that, then if they follow the pattern then we can look forward to 800 or so more KOTOR games before we get too episode I. I'm sure Obsidian are up for that! :D

Well...not twice at least :D

I got the same type of card so I may be able to help. There are some slow down issues for me, mostly due to the Anti-Aliasing stuff. Run it at 2x and you should see some good speed. Other than that though I was running Frame Buffer and Soft Shadows OK. What other stuff you got on your system? Also when you upgraded you GFX card did you re-install the drivers (I assume version 71.89) or the whole OS?

Well that isn't really bad AI, just bad planning. As the player you are able to see what is coming and prepare for it, hencing buffing before a battle. Often the enemy doesn't know you are coming from a plot point of view and more especially from an AI point of view, so it doesn't prepare. One solution would be to have an 'alarm' like system where enemies on the level know you are there so turn on shields, apply buffs etc when an alarm near them goes off. This would give them a chance to react before you get to them and would also provide a nice tactical option of 'ghosting' enemies to avoid an alarm going off. That said though, the main reason they don't tear me apart is that I do it first. The damage levels in KOTOR II are massive compared to the number of hit points anyones got. The AI may have 'better' stats, but they don't have better equipment most of the time (lightsabers being a good example....they just have the saber, you have the crystals and upgrades), which gives you a damage advantage. Combined with the regeneration...poor AI hasn't a chance, and frankly even a good AI would have a bad day against that. It isn't hard to imagine I've played such games! :D. But the cause isn't just the bad AI, its the whole design of the battles. Damage is the key thing really. If I can do enough damage to kill something in one hit, then the only tactic that would make sense would be the 'great unholy massarce' approach. The enemy must do about the same damage to you as you can to it. That way you end up with a kind of 50/50 win lose result if you just leave it to the AI. Its then up to the player to do something 'tactical' to shift the odds in their favour, be it use of special items, knowing specific weaknesses of the enemy (not the AI itself), use of terrain etc.

Actually they are displaying a great deal of common sense. If you saw a man or woman with very grey features light up a red bladed lightsabers I bet you wouldn't say anything either...

It is a lot easier to be bad without being a petty bully in KOTOR II. And the game seems to draw you to it as well...

Those are good close quarter tactics, but there isn't the equipment for them to work well. Shields have about enough hit point to last two or three hits (if that, especially those useless melee shields), buffs don't provide that much help, work for only one person in the group and they are rare(ish and expensive to make). Helping each other out is difficult for AI to do, as it has to be aware of others around it (i.e. it more or less have to be specifically written AI). The most challenging battles in Baldurs Gate were fighting against other parties...everyone had a role. As for the force....well when did a battle last more than a few seconds. By the time most enemy Jedi cast anything you've already torn them to pieces. Making a generic AI is extremely hard to do since there are so many options. However having an AI that is strong enough to but up a good fight can be done if the game designers do it right. Part of the reason I like Baldurs Gate is that the set piece battles were well designed. At first appearence a battle can appear very difficult or nearly impossible...until you use tactics...then the battle becomes a lot easier.

The problem with the 'real-time' combat in KOTOR is the AI and the 'closeness' of everything. If you are going to use continous turn based system then you need to do one of two things for the AI: 1. Have a good AI for characters that are not currently being controlled by the player. To follow this route it has to be very good, otherwise you get the headless chicken behaviour in KOTOR. 2. Don't have an AI, but make it easier to control the party. Baldur's Gate is a good example. There was a number of scripts that could be used (and some were useful even), but the default behaviour was good enough to look after themselves for a few seconds before you gave them orders...and of course they would follow those bloody orders as well! More recent games have followed approach one, but failed because of combination of the tasks complexity and being more interested in the 'looks'. Frankly if you can't get it right, then DON'T do it...give back control or at least a way of turning of the AI. The closeness of the game make tactical options extremely limited, for both the player and the AI. Hence the 'rush em' approach...its about all it can do. Open things out a bit, make the terrain help (make you harder to hit that is, not just stop you from being shot at) and stop the AI from running at things to get line of sight (often I just want them to keep their distance but get line of sight...'move a bit to the left you fool...no, don't run through the door...ARRGGHH!!!' ). There is only one 'real-time' combat game that I've played were I could control the characters well enough and have the AI help and that was Fallout Tactics. Had some very simple controls for the AI, but was very powerful and more importantly they would follow the orders.

They did say they didn't want to use the same engine again...so you could be right there.

The ini file you have looks very strange...it's got a Display section and then a Graphics section. Mine doesn't... I note that the resolution is different in both of them. And you may want to change the refresh rate if you want your eyes to after playing...

This is a possibility, and if it was only the staff working on KOTOR III then I would agree, but from the article it was suggesting that Lucasarts had basically gutted itself to save money. I hope your right, I really do. I'd like to see a KOTOR III...a good KOTOR III, not a rushed 20 hour 'epic' because the publisher needs some quick money because of it's outrageously bad management. If I could decide who should make the game then I would have Obsidian do the story but Bioware the game engine and the like. Best of both worlds and it gets people doing what they are good at doing. Obsidian do have some of the best storytellers in the business (if given the chance that is), and Bioware, for all its faults, make some good RPG game engines (if they remember that the PC has graphics memory and use textures bigger than 16x16).