Widescreen Gaming Forum

as you can see the picture shows that im running a 16:10 resolution.

since i deleted all my cfg files the problem is solved -the files were recreated.
i think the caus was the first start up of the game: i had my secound (19") monitor running and it already made some errors in the game (videos wont play ie.).

The picture seems to show 1280x1024, which is not 16:10, fyi.

oh your right
must be because i just tested some resolutions back then.

i had 1680x1050 running

How do you even start the game? It goes straight to desktop for me?

How do you even start the game? It goes straight to desktop for me?

does it minimize? or crash?

_________________
System Core: | Intel Core i5-2500K + ASUS P8Z68-V + 16GB Corsair XMS3 DDR3 1333 MHz | Win7 x64 | MSI R7970 Lightning 3GB [1105/1400] |
Display: | 3 x Dell Ultrasharp 3007WFP-HC @ 7680x1600 | Dell u3011 |

Minimize, in the sense of what TH2G normally does when it doesn´t know what to do with the resolution, i click on the icon goes back to the game and minimizes again.

Ok i figured i need to set up matrox to use 1 screen in order to go in game and set a triple-screen-res and then come back out set matrox to use all 3 screens and bingo game launches, but the menu seems all zoomed-in :S

For those of us with the analog edition of TripleHead2Go... The FOV of 133 or 142 work fine at max resolution of 3840x1024 with the "Bindings" settings. However, the file that needed to be modified is engineconfigBaseInput.ini. There was no willowinput.ini. Not sure why. The menus still have the same problem and they need to be zoomed out.

When I tried as specified, the view did change when F11 was pressed, but no controls worked. I was completely frozen in game. I tried adding the Binding in the first section of WillowInput.ini, [Engine.PlayerInput] and that worked when placed at the bottom of that section.

When I tried as specified, the view did change when F11 was pressed, but no controls worked. I was completely frozen in game. I tried adding the Binding in the first section of WillowInput.ini, [Engine.PlayerInput] and that worked when placed at the bottom of that section.

You have to modify a control first to create the required parts of the ini I think.