I'm very new to pc gaming, so I don't even have to vocabulary to describe what is happening, so I took a quick video with my cell phone


BUT I CAN'T POST ANY LINKS AT THE MOMENT???



Logo screens look fine, but when the game gets to the main menu, the screen flickers terribly. I suspect those more experienced with pc gaming can identify what is happening easily, and I am concerned there is little I can do.

I am running on a Lenovo Thinkpad T410, Windows 10 Pro 64bit, Intel core i5 2.4 Ghz, 4GB RAM, but I expect the problem is this (from my DXdiag)

---------------
Display Devices
---------------
Card name: Intel(R) HD Graphics
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics (Core i5)
DAC type: Internal
Device Type: Full Device
Device Key: Enum\PCI\VEN_8086&DEV_0046&SUBSYS_215A17AA&REV_02
Display Memory: 1696 MB
Dedicated Memory: 64 MB
Shared Memory: 1632 MB
Current Mode: 1280 x 800 (32 bit) (60Hz)

I also snapped this report from the swconfig program that came with the KOTOR download (attached)

So it seems to me the hated Intel integrated graphics are the culprit. I know this old laptop won't play No Man's Sky when it releases, but I thought it would be able to handle a 13 year old game. Everything else I've download from GOG has worked flawlessly (with one minor adjustment for VTM:B).

Is there anything I can do to get KOTOR to run on this Thinkpad? Is there anything in the game description that should have tipped me off that this old game would not be compatible? If anyone can explain to me what is happening, and what I might try to resolve it, the information would be greatly appreciated.

Thanks so much.

I have a lenovo laptop,i3 with intel hd 4000 integrated graphics, and this game runs just fine for me.

That's good to hear. Gives me hope I will be able to get this working.

Is there some reason why I can't post links to the video? When I press post my message, I get an error that says "You can not post any links at this moment".

You need more rep. to post links. It's an anti-spam thing.

ok. understood.

Thanks for explaining.

Just cut and paste the url into your post. People can copy it to their browser to get to what you want to show them.

So I finally got KOTOR to open in windowed mode, and the graphic flickering is gone. Looks good, just slightly smaller. But it is playable.

Don't really understand what it means. My graphics hardware can';t fill the full resolution of the screen? But the window is less pixels, so it works?

Thanks for the suggestions.

How did you get it to run windowed? There isn't an option in settings, and though I've set fullscreen to 0 in the config file it's not taking.

I've also got an Intel HD Graphics 4000. Game crashes unless I turn movies off, and now the game crashes if I try to enter the Under City. Everything else runs flawlessly, for the 4 hours I've played thus far.

Gog support seems to be insinuating that it's because my card "didn't meet the minimal 128MB of video memory required to run this game properly"

Which is bull considering everything else worked perfectly (besides movies) for 4 hours of play, and that I can run stuff like Alice: Madness Returns on high settings or F.E.A.R. 2 on medium-low.....so anyone know of any work arounds or other things to try? I've done the ringer with drivers/compatibility settings/run as admin

Crashing in undercity is often caused by grass effects. Did you turn those off?

From a helpful person on NeoGAF

window mode:

Go to the installation folder
Open swkotor.ini
Set FullScreen to 0.
Add AllowWindowedMode=1 under [Graphics Options]
Use ALT + ENTER to switch to windowed mode in game.

Hope it helps you, too.

Thanks for the tip! Working fine now. Didn't expect grass there...or think it would crash the game.

Yeah I've got both of those set but it's still fullscreen for some reason. Oh well, not a big issue anymore since the game is no longer crashing.

There are two places in the .ini that have a "FullScreen=#" option. One just covers cutscenes, the other covers the gameplay. You need to change the gameplay one to get the working window toggle. You can actually change both, since the cutscene one is unnecessary and doesn't appear to actually do anything.