Kiwegapa

We need your system specs. Either the contents of swinfo.txt (you get that bt running the program swconfig in your SWKotor2 directory and running a hardware scan), or type out what you have. The contents of your swkotor2.ini file would also help. Your system may not be able to run KOTOR 2 perfectly. But we'll help if we can.

Both of those are pretty high-end laptops. Most people who have been posting have laptops with older graphics chipsets. And KOTOR 2 runs very unstable on chipsets without the right OpenGL support, if at all. I wish they'd code some fallback paths into the graphics engine, but I doubt it will happen for KOTOR 2. Maybe in KOTOR 3.

Can you post your swkotor2.ini and swinfo.txt files? The main things I can think of are that you might have CD backup software installed, might have an older video or sound card, or that your system drivers aren't up to date(video, sound, motherboard).

If you're using a radeon 7500, a patch won't help you... the engine just won't run on that card... Actually, if they change the way the game engine works to have a fallback path like Half-Life 2 or Doom 3, then it'd work fine, just with uglier effects. However, I doubt they're going to do that sort of major revamp. KOTOR 2 might be the first major game to fail to support a 7500, but it won't be the last. as the card continues to get older.

Verrry interesting. My game won't permit that. I wonder which one of us has a bug. Likely me, since she has a normal body shape. Go ahead and screenshot if you like. I'm interested.

They do have extensions..they would be .dl_ and the reason you don't see the extension is likely because you have the option 'hide extensions for known file types' turned on. With the folder open, go to the Tools menu, select Folder Options. Go to the View tab. Make sure you have both 'Hide extensions for known file types' and 'Hide protected operating system files' turned off.

I see what you mean. I appreciate that functionality too. I was thinking of the 'left mouse button not being mappable' issue. I really need to double check my posts if I'm posting at 3AM. Sorry, folks. :"> As far as the shift key issue goes, it can't easily be fixed because the shift key is special, and another key will not allow you to hold it and hit 1 or another such combination. I think the best possible solution, if they MUST fix it, would be to break apart left and right shift keys. Leave one for the fixed functions and let the other be freely mappable.

whoa..freaky. Can you post the contents of your swkotor2.ini file and maybe a small screenshot?

This is also why Visas cannot wear anything and have it show, and why Bao-dur cannot wear robes(Robes cover the arms). Mira and Atton are normal characters and thus they can wear anything. So it's not really a case of being cheap (Although Visas could probably wear normal clothes on her body if you kept the same head, should you care enough to make tweaks), but more one of being careful of the character's models and unique features.

I didn't have much trouble. Make sure you search every droid you kill for command codes or programs. Then go to a Command Console, not a Security console, to input the codes/programs. I didn't overload the cells, I shut them down with the ShutDown program, which should be the first you find on the T3-style droid in the first room. Once you have access to the cells, you can get two more important items. Shutting down turrets, mines, or droids wasn't really important on the console. Do it for experience after you've run through and destroyed them all. After the cells, rescue the Exile, then go to the bridge. The bridge on the left side of the map is where you need to finish your quest, and then escape back to the room you started in and out the airlock. Hope I haven't been too vague or too spoily.

Oh ok, Doesn't make sense to me, But I'll try that. It works fine. I modded several characters earlier today with sharper textures. When I find the time, I'll probably put out a texture pack, but it's nowhere near ready yet.

Good tips, folks. Quite a few people have discovered that their KOTOR 2 'bugs' were actually hardware problems. I've tried to address the basics in my KOTOR 2 Guide without getting into too much detail and turning it into a 'how to buy the right computer' guide. If you have any suggestions for additions, pass them on.

Nar Shaddaa is a bit wonky as far as the quests go. Make sure you meet with Vogga as late as possible. Visit the Pazaak den and the bar before you go see him, too. (Hint: visit the bar in stealth mode for a hard-to-find bit of info) It's really easy to miss a quest because you didn't talk to the right person, or talked to them at the wrong time.

Oddly enough, I find that racing with the mouse is a lot easier. In KOTOR 1 I liked using the A and D keys, but steering via the mouse seems better to me. (Hate those obstacles on Nar Shaddaa though! )

I read the readme but the games have the same engine and I think people with supported cards have the same problem. so... Unfortunately, they updated something in KOTOR 2 and now the game needs OpenGL 1.4 hardware support on ATI cards. The game might run, but until we find a better solution, it won't run well. Sorry.

I highly suggest you download the smaller seperate packages. I've had MUCH better luck with driver stability installing them. Grab the driver and the CCC or the Control Panel if you prefer. Smaller download, better install.

The game is buggy, yes. But the quality of the story and the actual game play is wonderful. Obsidian worked hard on this game, and they're working on a patch now. Give them a chance to fix their mistake before casting blame their way. Lucasarts forced the game out before it was done for a holiday release. If we never get a proper patch, I'll raise a torch and pitchfork with the rest, but until then we should have a little patience and a little faith.

Bad news, Skydude. KOTOR 2 was designed using OpenGL 1.3 (nVidia and OpenGL 1.4 (ATI) functions. This means you need hardware support of that OpenGL version, and most Radeon Mobility cards only support OpenGL 1.3 in hardware. Perhaps there's a way around this, but no one's posted a way yet. Some have apparently gotten the game to run on their laptops, but I don't know what their specs are or how they did it. I haven't talked to a successful laptop user yet. Keep trying though. Cat 5.2 is a good start. Make sure you have no CD backup or copy programs installed. Try setting the game to force software sound or disable sound completely. If there's a way to get Mobility chips to run the game, I'd love to hear it. I've got a laptop myself that would be nice to have the game on. What version of the Mobility Radeon do you have?

ATI has been notified of some of the problems we're having. No word yet on whether they'll be able to do anything, but they're taking an interest.

What he means is that you must have a semi-recent video card, one that can display the Frame Buffer Effects properly. If you hit G for Stealth Mode and your character disappears, leaving only a wavery outline, you can display Frame Buffer Effects. If your character looks like they're covered in lightning then you cannot display those effects or have Frame Buffer Effects disabled. Frame Buffer Effects are required for Force Sight, viewing cameras through computer consoles, the wavery stealth effect, the heat haze behind engines during a swoop race, and the glow cast by a lightsaber.

Right now you can't change the shift key, unfortunately. In the readme.txt it mentions the issue, meaning that it almost certainly will be fixed as soon as the upcoming patch is out.

Agreed. I don't have finely tuned ears, but I can hear that something's off and it bothers me, especially when the music loops frequently or when it swells in volume, drowning out the spoken dialog.

Yes, I realize now that I didn't have enough influence when I talked to her. I lost my chance. I'll try again next time I play.

Mira isn't a bug, check her armor she has damage immunity. If a critical is landed or damage over 'so much' it will hit. Didn't happen to me. The kath hounds kept slaughtering me unless I ran quick.

Some users report a problem with swoop racing where the swoop floats unusually high above the track, preventing a proper race. This can be fixed by holding down both mouse buttons before a race begins. Other reports say hitting space then left mouse button before the race begins fixes the issue. I don't know if this is your problem, but it's worth trying. Good luck!