[DocCorvid]

God, I hate posting a new topic for what is probably a simple problem, but I honestly couldn't find anything in the forums that sounded like what I'm experiencing.
Here are some specs, hope they're what you need:
OS: Windows XP
Mobile Intel ®
Celeron CPU 1.80GHz
704 MB RAM
Radeon IGP 340M
The main thing is when I commit to a mission I see the starfield but with no HUD and can’t move the ship or give any commands or anything at all. Sometimes I don't even get off the mission briefing screen. Then I get the old “has encountered a problem and needs to close” chestnut, and that’s it.
Also, when viewing ships in the tech room, some of the ships have chunks missing or weird stretching bits that seem to cling to the axis of rotation.
I ran the debug build and afterwards couldn’t find a .log file in the data folder, but I did find this text file called fs2_open that might be what you’re looking for. I've attached it to the post.

Thanks for any help. Really excited to get things sorted and play properly!

Oh, and I only downloaded the launcher and FSO, I haven't downloaded any of the media files yet.

[attachment deleted by Tolwyn]

[General Battuta]

Absolutely no problem, we like helping out. Nobody should feel ashamed of posting even simple questions. And you even got a log file posted, which is brilliant! Top of the class. 
 
It looks like you're running a 3.6.10 build. Is this 3.6.10 Final, the latest version?

Does retail FreeSpace 2 run fine, or is the problem occurring in both FreeSpace Open and Retail?

[FUBAR-BDHR]

Well I believe your OpenGL version (1.3.4276).is a little below spces.  Have you tried updating the drivers?  Also I'm wondering if that gog.com directory might be causing problems.

[The E]

Hello and welcome.

First of all, make sure you download the latest version of both the exe and its associated Launcher. Both can be found here. Go to features, and set the list type to "Troubleshooting". Mark the "Disable setting of Gamma" checkbox. That should take care of some of the graphical weirdness you're seeing. The directory should be OK, as should the OpenGL version (although I wouldn't want to run the advanced mediavps with that).

[Jeff Vader]

Theoretically, FSO requires OpenGL 1.2 or newer. In practice, it would be good to have at least 2.0.

If the latest drivers do not include any newer OpenGL, you can always try 3.6.9 and using Direct3D, though that would suck because
- 3.6.9 is old and a bit buggy
- Direct3D sucks
- Direct3D is no longer supported and 3.6.9 is the last build where it can be actually used.

[DocCorvid]

I downloaded the version listed under Windows Regular here: http://www.hard-light.net/forums/index.php/topic,64520.0.html

Retail FS2 WAS running fine but today I encountered a problem where the in-mission voices would cut out after only half a second as though they had ended. It doesn't seem related to my new problem really. The problem I related in my previous post has only happened in FSO. I just checked retail FS2 and it runs fine, although the text now appears a bit funny...?

UPDATE: I just tried what you recommended, but now I didn't even get to the mission briefing. It crashed when I tried to go to the tech (ie ship specs, mission sim etc) screen.

Here's the new log.

[attachment deleted by Tolwyn]

[Jeff Vader]

Also I'm wondering if that gog.com directory might be causing problems.

Hasn't caused so far, or as far as I know. Excessively long directory paths make FSO yelp, but this shouldn't.

Retail FS2 WAS running fine but today I encountered a problem where the in-mission voices would cut out after only half a second as though they had ended.

Ah, that fellow.

Did you get around to installing new graphics drivers yet?

[DocCorvid]

Hahahaha, yeah that's me. Honestly now I'm just curious what the original problem is! Let me install the new drivers and I'll get back to you.

Ah, I should have realised I was speaking to Jeff Vader on two forums at once...

[The E]

This is a long shot, but could you post the crash.log here?

[DocCorvid]

Sure. What's the crash.log?

[The E]

Sorry, got the filenames confused. Windows should have generated a file called errorlog.txt. Post that one.

[DocCorvid]

Sure. Where can I find it? Also, where can I get driver updates?

I'm going to bed now. I appreciate the help, and will get back to you in the morning if you tell me where I can update my driver. I'll try that and see if it helps.

[The E]

The errorlog should be in your FreeSpace folder, drivers can be found at http://ati.amd.com

[DocCorvid]

I've attached the log.

Maybe my machine is too old, but there were no results returned for "radeon igp 340m" anywhere on the site you linked to.

That being said, I am totally confused as to what I should be looking for. Should I download OpenGL driver updates or Radeon IGP 340M updates?

[Jeff Vader]

Maybe my machine is too old, but there were no results returned for "radeon igp 340m" anywhere on the site you linked to.

Maybe. But I just spotted a statement on the Internet saying that since IGP 340M is some integrated graphics solution, ATI doesn't release drivers for it; you'll have to search for drivers for your motherboard. And if you need help in it, we'd need to know what kind of a computer (laptop) you have.

That being said, I am totally confused as to what I should be looking for. Should I download OpenGL driver updates or Radeon IGP 340M updates?

You should download driver updates for your graphics card. Because since '95 or something OpenGL has been included in the graphics card drivers.

[DocCorvid]

I've got a Compaq Presario 2100. I just downloaded and installed what I think is the latest graphics driver according to my product number on the HP website. It all went fine, but then as soon as it finished, a window opened saying:

"Unable to fullfill your request at this time. Please try again later"

Sigh...today is not my day with updates. Also just updated windows media codecs, but still getting the message that the very codec I DLed and installed still needs to be DLed and installed.

Maybe I should just read a book?

UPDATE: I just tried running FSO again and still getting the same problem as before. Graphics glitches on the models in the spec room and crash to desktop at beginning of mission.