The game works perfectly on my main computer, with an Nvidia 250 GTS, Linux.

I was surprised, that TF also works relatively smooth on my laptop a Lenovo T420 (also running Linux, Ubuntu 15.10), i5 3,2GHz, 16GB RAM, Intel HD3000 (I thought these cards were not supported, however, the game works surprisingly fast and I can also load “big” save-games from my other computer without trouble!)

The only Problem:

All trees in the game seem to be rendered on a separate layer which “flows” in the air, when viewed from far away. When I zoom in, the trees appear normally. This phenomenon is independent from the geometric detail setting (low/medium/high).

See screenshots:
Far away

Near:

The trees appear only when you move very near:

My guess is that TF uses different layers for rendering near or far away objects for performance reasons. However, the layer for the far away trees (and only the trees!) seems to cause problems (probably OpenGL-related?). As the rest of the game works without problems, I would also be satisfied if there was a (hidden) option in a config-file to disable the “far-away” rendering for trees, as a workaround.

The rest of the game works fine, even with reflections enabled and complex tracks (Ok, without AA):

I really would like to be able to play the game also on my laptop, and because its such a great game I would also buy a second copy to be independent from the steam-account and to support the developers, if they could fix this problem.

The problem was observed with:

TF Build 6219 Linux 64-Bit

Another guess what could be the problem:

I heard from someone that the Linux-driver for the Intel integrated graphics cards “emulates” features which are not implemented in the hardware by software-rendering (don’t know if that’s true). Therefore it could be that the hardware does not meet exactly the OpenGL requirements, but the driver gets it to work anyway.

The toool glxinfo says (among others):
OpenGL version string: 3.0 Mesa 11.0.2
OpenGL shading language version string: 1.30

So it’s true that the OpenGL-Version mentioned here is < 3.2, however as I just said the rest of the game works fine. I would appreciate it very much if there could be some kind of fix/workaround (even to disable trees). Maybe the game could reach even more users, if there are only such small issues on Intel-graphics-cards…

For responses, I also speak German

I bought the game via Steam after checking with system requirements lab if my Laptop fullfills the min. requirements. There it stated that I fullfil all requirements. After installing I get a message that I should install my newest driver which I did.

I am currently running a GeForce GT555M driver with Intel Core i7 -2630 QM 2gHz. The latest version availiable at the Nvidia homepage was 340.52 which I installed. Also I am not using a virus scanner when starting (as stated in other posts) and yet Steam gives me the message “ogl_Load Function Failed”. I tried reinstalling Steam, the newest driver and the game and yet I have the same issue.

I am very frustrated that after buying the game and checking its compatibility with my rig that it won’t work. Also I tried googeling for some fixes and it seems that it has semething to do with Opengl. I do not know, however, how to go about this issue and I would like to ask for help from you guys. It there something I would need to install? Some sort of Patch coming up? Something wrong with my driver?

Regards

immer wen ich bei Steam das Spiel starte kommt der Fehler “OpenGL-Kontexterstellung”.

Mein Grafiktreiber ist auf dem Neusten Stand (Nvidia GeForce 340.52 Driver).

Meine Pc Daten:

Betriebssystem: Windows 7 64Bit

Prozessor: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz 2.50 GHz

Ram: 8,00 GB (7,85 GB verwendbar)

Grafikkarte: Nvidia Geforce GT 630M

Ich hoffe das mir jemand helfen kann.

MFG

Bestplayer155

The first hour I played TF I got the OpenGL error, I used the old BF3 fix but I did something slightly different.

I got an old Nvidia 9600GT with the latest 3.40 driver, and I’m using Windows 8.1 64-bit.

Because I’m using Windows 8.1 64-bit I made a different “64 bit” key: Instead of using the “DWORD (32 bit)” key. I used the “QWORD”(64-bit)” key with exactly the same description as below. After that I played for 6 hours in a row without any crash, So I think it helps to use the right key for the corresponding system you’re using. (32-bit or 64-bit). I hope this helps you fix this error.

This seems to be an old fix used for BF3.
1.Simply go to your registry: Start –> Run –> Type in “Regedit”
2.Go to “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers” and create a key of type “DWORD (32-bit)” or “QWORD (64-bit)” (depending on what system you’re using) and name “TdrDelay” with a value of 10 as Decimal value.
3.Reboot and play

In a nutshell it gives the GPU 10 seconds to recover/respond vs. 2 seconds (default).

View post on imgur.com

This works for Windows 7, 8 and 8.1

This basically alleviates the “ Display driver stopped responding and has recovered” issue and/or “Display driver nvlddmkm stopped responding and has successfully recovered.” you will only see in the EventViewer.

If you want to learn more about this setting: Timeout Detection & Recovery (TDR)

Check this links:

http://http.developer.nvidia.com/NsightVisualStudio/2.2/Documentation/UserGuide/HTML/Content/Timeout_Detection_Recovery.htm http://msdn.microsoft.com/en-us/library/windows/hardware/ff570088(v=vs.85).aspx

TDR stands for Timeout Detection and Recovery. This is a feature of the Windows operating system which detects response problems from a graphics card, and recovers to a functional desktop by resetting the card. If the operating system does not receive a response from a graphics card within a certain amount of time (default is 2 seconds), the operating system resets the graphics card.

Before TDR existed, problems of this nature would have resulted in a system freeze and required a reboot of the operating system. If TDR is enabled and you see the TDR error message, “Display driver stopped responding and has recovered,” this means that the Windows operating system reset the display driver.