Game seemed to install fine but when after running it the FMV scenes show up only as blackness right from the start.

And the only way I can find to exit the game is to use the task manager. The exit commands just freeze the game until I hit escape.

I'm using 64-bit Windows 7 with an nVidia GeForce 7600 GT. Any help would be appreciated.

Actually it seems I was just being silly, my graphics cards been acting up and I just updated it. The game seems to work now.

Have a brand new Windows 7 64 bit laptop with a Intel Family Graphics Card or one with dual graphics cards like a Intel Family Graphics card and like a Geforce 540M and can't see no intro movie at the start up (black screen / but sound) but in game the graphics are fine ?.

A possible solution can found here:

http://strike-team.net/forums/index.php/topic/172813-black-screen-no-menus-showing-in-red-alert-2/.

It works for the longest Journey as well as for Red Alert 2 !.
Hope I helped someone with this information.

AAIJETOOI !

I have a Windows 7 64 bit laptop too but my problem is the transition between the videos and game play. When the video gets to the spot where it has to switch over to game play, it shuts down the game. I tried the screen change thing from the link and it worked. I tested it several times, with and without the change, and that screen thing was the fix. Now, a few weeks later, I tried the exact same thing, with all the same settings, and it is crashing just before the game play exactly as before. I am so confused. Anyone have an idea as to why it's not working now? It's a Dell with Intel HD Graphics 4000 or something like that (I don't know much about computers).

... I was about to post this and then decided to try one more time. I tried to update some drivers but it said they were up to date. Then I got on the game and it worked fine. So strange. I'm sure this will happen again, but I don't know why.

Edit: And the next day it's not working again.

I'm having the exact same problem, but haven't tried anything to fix it as of yet. It goes to the cutscenes just fine, and plays them, but when it gets to the moment where the game would transition from the video back to regular gameplay, CRASH. Since you tried one solution and it wasn't a complete fix, and you haven't posted since... did you ever get the problem fixed completely? Any advice? (Hopefully someone has some simple advice?)

Another note - after I installed the game, the font on my computer changed for some reason. It's weird, and a little alarming - like installation downgraded the appearance of system fonts or something strange. I'm far from a computer expert, so maybe it's nothing, but it's odd.

EDIT: That text problem was fixed - apparently the installation turned off "clear text" or at least checking that setting made it right somehow. Huh.

This game, while I think is great, is the only game in the GOG catalog that I have that gave me the biggest headache. The font thing happens to me also, but only after exiting the game.

This game really needs to be fixed, but I don't know how much of that is in GOG's hands or Funcom's.

As far as crashes are concerned, mine runs pretty stable, only crashing at the police station (Win 8.1, Nvidia GeForce GTX 670). It crashed endlessly when I played around with the graphic settings via Nvidia control panel until I found a setting that would work (Antialiasing - FXAA On).

I don't know if it any help, but check out this forum (if you already haven't found it):

http://forums.longestjourney.com/forumdisplay.php?f=13

You might find some useful information.

Dreamfall has its own forum hosted at the same site, but if the explainations go over your head then it doesn't matter anyway. I'm not a computer genius myself and mostly discover things by messing around, sometimes making things worse, forcing me to reinstall programs :). Like I said, this is the one game that has given me a headache (I'm sure there are others, but it is rare from what I gather from reading the forums - most issues are minor and have more to do with configurations and hardware than software). Contacting support certainly wouldn't hurt, and don't let this one experience dissuade you from coming back.

That's exactly my fear -- don't want to mess around too much for fear of messing up my computer somehow. I have contacted support, but I'm still waiting for a response.

For what it's worth (if anyone else is reading this or comes across this thread in the future), I did find and try the following solution that I've seen mentioned in a few places, but unfortunately it didn't fix anything for me:
___________________________
1. Right click on Desktop
2. Select Screen Resolution
3. Click Detect (with no additional monitor connected)
4. Next to your first display, you'll see a grey square with the text "Another display not detected" Click on the grey square
5. Next to "Multiple displays" it will say "No display detected"
6. Click on "No display detected"
7. A drop-down menu will appear
8. Select "Try to connect anyway on: VGA"
9. Click on your primary display (the square with the big "1" in it)
10. Next to "Multiple displays" select "Extend these displays"
___________________________

Thanks for your support!

i'm using win7 64 ultimate.
solved CTD at least for one scene using the canvas at the academy the first time with setting my games compatibility to windows 2000, ticking last three options, scaling, desktop stuff, visual desgins, and of course run as admin.
will see if CTDs even more appear. but as said, solved for this time so long.

Hi,

I keep having the same problem - I'm in Chapter 3 now and it's crashing right after an FMV once getting back to Arcadia.

What can I do? I tried jedcooper's suggestion but it still crashes. Man this is annoying!

Btw I'm running Win 7 64-bit.

If you're experiencing a crash right after a video is played (for example in the end of the long intro film when the Guardian wakes up and April lies in her bed) then the solution has been posted in the forum thread called "Fix for binkw32.dll crashing in Win7 after some FMVs" written by R33D3M33R. Just wanted to share that since it worked flawlessly and even though it's a VERY strange fix, it's super simple.