Hi!

Recently got my TH2G set up, and wanted to try it in LFS.

It works in other games, iRacing and FSX, along with ARMA2.

As soon as LFS tries to set the 5040x1050@57 the screens go blank and I get dumped to desktop, no errors.
I have no idea how to give any better info, please tell me ho I can help nail this.

My setup:
Q9550@ stock clock
Asus P5QL-Pro
Corsair HyperX PC6400 RAM, 4Gb
XFX 8800GTX, nvidia 182.50 drivers (latest that work properly with TH2G)
Win7 build 7100, all updates
Latest drivers for chipset and devices, latest firmware for TH2G.

I have TH2G digital edition worked in LFS straight off the bat for me, similar system specs to you but running WinXPPro SP3. Could be a Win7 thing

So it will fire up and run in single screen resolution?
Is it a new install of LFS or an old copied one?

On a quick search for "TH2G win7" and from the hits I'd has a guess that it would be a Win7 build and driver compatibility issue. Is it possible to try an XP compatibility mode? I've read about virtual XP under windows 7 but have no experience so can't help any further...

It could be an LFS bug or a drivers / DirectX bug. Although the other games work, it's possible there is a bug in the DirectX8 implementation.

I don't know how to find out exactly what is wrong but we could try a few things :

1) Does LFS work in a smaller 3 screen mode?
2) What about on a wide desktop? Try stretching or maximising an LFS window instead of going full screen.
3) What about a lower memory mode, like 16 bit instead of 32 - and try a 16 bit Z-buffer.
4) Does it crash in all screens, such as the entry screen, or only in-game?

Which LFS version are you using? Patch Z or Test Patch Z15?

I just read on another thread that on Windows 7 you have to search for error messages using a system tool :

http://www.lfsforum.net/showthread.php?p=1252445#post1252445

If that is the case then maybe there is an error report you can retrieve.

It works with any resolution as long as I don't apply any AA. AA can be applied to single screen resolutions, though. But any AA at any widescreen res and I get the 'LFS.exe has stopped working...' message.

I use a 8800GTX with the 182.50 nVidia drivers. Those are the only ones that work with Win7 and triplehead for me. All other drivers are up to date.

Edit:

I'll check the app for the crashlog. I'm not sure what patch version I'm at, it's one of the ones after Patch Z, I'll check it in a little while. Gotta get the kids to bed first.. You know how THAT goes...

Edit2: Running patch Z9, but I don't think there's ben any graphics changes since Z?


Edit3:
IS this something useful?

Thanks for providing a crash address, which is often useful information, when the crash address shows which line of code LFS crashed in. But unfortunately in this case, the crash was in the D3D8 dll. That does not necessarily mean that it is a bug in D3D, but it does mean that I can't look any further into what that crash address means, because I have no idea which part of LFS called that D3D function.

I don't know where to go from here - LFS doesn't really do anything different when using antialiasing. It just asks D3D to switch on AA.

What would be interesting to know is if any other programs that use D3D8 can go fullscreen with AA on a TH2G - if not then we'd know it's a problem with D3D8 or the drivers.

One question - can you go fullscreen with AA in a screen where there is no 3D? Just the main entry screen when you start LFS would be a good test, before any track is loaded so the texture usage is minimal.

Quote from Scawen :

One question - can you go fullscreen with AA in a screen where there is no 3D? Just the main entry screen when you start LFS would be a good test, before any track is loaded so the texture usage is minimal.

Just a note - he must have the Load track at startup option set to off, am I right?

Ok, some more testing...

The widescreen resolutions fail, the 4:3 resolutions are good even with AA.

I can run 2400x600, 3072x768 and 3840x1024 with 8x AA.
The widescreen res of 4320x900 and 5040x1050 fail.

Tried loading LFS and with the don't load track thing enabledwent direct to settings. Still failed as soon as LFS change the res.

The thing is, the new res get set, THEN fail, even if it is virtually instant. My screens switch to the new mode, then LFS fail and they switch back to the desktop res.

Possible fail with the refresh of monitors? so no all monitor accepts 57hz. At same time I don't know if LFS give you option to 57Hz, so the TH2GO don't accept 5040x1050@60, only 5040x1050@57

I use 3840x1024@60Hz 32bits maxium detail (AA,AF) on a 8800GT 512mb and never crash

PD: Scawen I can tell you some suggeriments/improvements/errors for TH2GO users?

They accept 57hz no problem, and the res is listed as 57Hz in the LFS settings. Like I said, most games work fine in this res. I am not sure I have any DX8 games that use that resolution, though, most are DX9.

I will try to force rFactor to DX8 mode and see if that works with AA.

It's also strange that the 4:3 (or rather 12:3) resolutions work with AA. Obviously the image is distorted beyond recognition, but they ARE triple screen, and the DO work. The 4380x900 use the same bandwidth (actually slightly less) as 3840x1024, only the aspect is different.

Quote from Napalm Candy :

PD: Scawen I can tell you some suggeriments/improvements/errors for TH2GO users?

I am busy on various things so cannot promise any extra TH2GO support, but I don't mind reading what you have to say.

By the way, I have fixed one thing - the autocross editor buttons appearing in the wrong place with any interface scaling or 3 screen mode.

Quote from atledreier :

I will try to force rFactor to DX8 mode and see if that works with AA.

I will be interested to hear about that, if we can see any other D3D8 program running at one of those resolutions with AA.

Did you try a 16 bit mode, or only 32 bit modes?

I'm not at home now so can't 100% confirm or rightly remember exactly, but moving the z-buffer down a notch solved this problem for me I do believe.

I have no idea or care what the z-buffer actually is or does, but I found that it worked just by trial and error and a determination to get it working.

Using XP, TH2go digital at 5040x1050@57. (Works with both GTX285 and 8800gtx). The frame rate loss, even with the 8800GTX, is almost non existent with LFS.

Not experienced any other problems at all with TH2go and LFS.

If anyone is thinking about Th2go, and you'd be crazy not to even think about it as it is the single best simming investment in my worthless opinion, be sure to check out http://www.widescreengamingforum.com for a list of monitors that are confirmed to work at 57Hz, not all do as I found out!

Dell 2408 wfp work ok.

I tried 16 bit modes, and I tried 16 bit z-buffer. Both fail.

Haven't got around to reinstalling rF yet, will do that as soon as I can.

Quote from Scawen :

By the way, I have fixed one thing - the autocross editor buttons appearing in the wrong place with any interface scaling or 3 screen mode.

That was 1 thing that I would say, thanks for fixing

The improvement is to make the feature that already has rFactor and iRacing is the "multiview", so every monitor render a diferent angle of view

http://www.damenmoden-hummler.de/rig/images/pic02.jpg

Other option is what in phothosp is called lens correction. (perfect for curved screens)

Without lens correction (normal mode)
http://www.lfsforum.net/attach ... id=53908&d=1208088375

And with lens correction (reduces a lot the sides distortion, see the yellow XFR on the left)
http://www.lfsforum.net/attach ... id=53909&d=1208088375

And the last thing that (i think) have iRacing, is not use the "Bezel management" from TH2GO drivers, this utility what does is cut the size of the borders of monitors to see the image in a good/correct proportion.

Without
http://www.matrox.com/graphics ... ucts/gxm/withoutBezel.jpg

With bezel correction http://www.matrox.com/graphics ... roducts/gxm/withBezel.jpg

So, the problem is the black borders on the side monitors because ever has the same resolution (3840x1024), to solve this problem need to render at higher resolution, for example 4040x1024, and use this 200 pixels to cut after in the place where are the monitor borders... I don't know if I explain so good.

Are secundary improvements, but I think will improve the LFS experience with TH2GO

PS: Sorry for offtopic

atledreier has you contacted with the Matrox guys? I remember that only compatible with these resolutions is the TH2GO Digital edition (analog don't work), and need to upgrade the firmware. But if it works in other games, it is not the case

The last thing that I don't remember yesterday, it is easy to fix

The replays are too much zoomed it will best if camera auto adjust by horizontal size of screen or window than the vertical like now

Napalm: It works in other games adn desktop, so it should work with LFS too. Could be a DX8 issue though, I don't have any other DX8 games installed at the moment.

Thanks for the suggestions, Napalm Candy.

I was inspired to do some updates and fixes for multiple screen setups. You can now try them in Z16.

http://www.lfsforum.net/showthread.php?t=61959

Thanks to you, you made it possible

Quote from Scawen :

It could be an LFS bug or a drivers / DirectX bug. Although the other games work, it's possible there is a bug in the DirectX8 implementation.

I don't know how to find out exactly what is wrong but we could try a few things :

1) Does LFS work in a smaller 3 screen mode?
2) What about on a wide desktop? Try stretching or maximising an LFS window instead of going full screen.
3) What about a lower memory mode, like 16 bit instead of 32 - and try a 16 bit Z-buffer.
4) Does it crash in all screens, such as the entry screen, or only in-game?

Which LFS version are you using? Patch Z or Test Patch Z15?

Just to add to this, as above everything worked fine with XP SP3. I have changed no hardware but have done a clean install of Windows 7 64bit and installed all the latest versions of drivers software for nvidia GTX260 (191.07) and TH2G (1.0.0.6) also installed a clean full version of LFS S2 Z25.

I get the exact same symptoms as atledreier in all circumstances he has described.

1) Does LFS work in a smaller 3 screen mode? (Yes AA works in all modes 3840x1024 32bit and below and works at 5040x1050 32 bit without AA)
2) What about on a wide desktop? Try stretching or maximising an LFS window instead of going full screen. (AA works at 5040x1050 32 bit when LFS is in windowed mode and stretched across three screens)
3) What about a lower memory mode, like 16 bit instead of 32 - and try a 16 bit Z-buffer. (Going 16 bit Z-buffer doesn't help, 16 bit 5040x1050 is not an available option to try)
4) Does it crash in all screens, such as the entry screen, or only in-game? (It crashes in all screens including the entry screen when enabling AA)

Note: I can enable AA manually from within the Nvidia control panel ok.

Quote :

Version=1
EventType=APPCRASH
EventTime=129030281304878501
ReportType=2
Consent=1
UploadTime=129030281306098571
ReportIdentifier=b019e61d-d44e-11de-8a00-00248c8581ba
IntegratorReportIdentifier=b019e61c-d44e-11de-8a00-00248c8581ba
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=LFS.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=4ae878e7
Sig[3].Name=Fault Module Name
Sig[3].Value=d3d8.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7600.16385
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4a5bd9a7
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0004bf62
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7600.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=3081
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=4709
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=4709938665fa84e3ff99c8cbe11223bb
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=05f4
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=05f442b71746d20c505b558ad13d7ce5
UI[2]=C:\Program Files (x86)\LFS\LFS.exe
UI[3]=LFS.exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\LFS\LFS.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\syswow64\USER32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\system32\WINMM.dll
LoadedModule[15]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[16]=C:\Windows\syswow64\NSI.dll
LoadedModule[17]=C:\Windows\system32\DINPUT8.dll
LoadedModule[18]=C:\Windows\system32\DSOUND.dll
LoadedModule[19]=C:\Windows\syswow64\ole32.dll
LoadedModule[20]=C:\Windows\system32\POWRPROF.dll
LoadedModule[21]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[22]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[25]=C:\Windows\syswow64\IMM32.dll
LoadedModule[26]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[27]=C:\Windows\system32\d3d8.dll
LoadedModule[28]=C:\Windows\system32\VERSION.dll
LoadedModule[29]=C:\Windows\system32\d3d8thk.dll
LoadedModule[30]=C:\Windows\system32\dwmapi.dll
LoadedModule[31]=C:\Windows\system32\uxtheme.dll
LoadedModule[32]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[33]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[34]=C:\Windows\system32\nvapi.dll
LoadedModule[35]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[36]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[37]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[38]=C:\Program Files (x86)\Matrox Graphics\PowerDesk\Matrox.PDesk.Hooks.dll
LoadedModule[39]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[40]=C:\Windows\system32\MSIMG32.dll
LoadedModule[41]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[42]=C:\Windows\system32\newdev.dll
LoadedModule[43]=C:\Windows\system32\devrtl.DLL
LoadedModule[44]=C:\Windows\system32\profapi.dll
LoadedModule[45]=C:\Windows\system32\nvd3dum.dll
LoadedModule[46]=C:\Windows\system32\HID.DLL
LoadedModule[47]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[48]=C:\Windows\System32\MMDevApi.dll
LoadedModule[49]=C:\Windows\System32\PROPSYS.dll
LoadedModule[50]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[51]=C:\Windows\system32\avrt.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=LFS.exe
AppPath=C:\Program Files (x86)\LFS\LFS.exe

Some more info to add (from another thread) which I think might be related.

Quote from Napalm Candy :

With no test patch forum I post here.

I have a problem/bug and is doing a full screen in Win7 some times only I see a black screen (I'm using 3 screens with TH2GO 3840x1024), if I press shift+F9 it go to full screen I see the main menu and instantly it go to windows desktop again, if I click on the LFS icon on the task bar, again go to LFS and return to windows desktop.

Is strange because I restart LFS 2 times and no changes in the problem, only I can saw LFS in windowed mode (with shift+F4) so I the cam to record, first I put on english language and then I put the 3840x1024 and.. all run fine again. So the problem it is not the language because when I was writing this I test again and I had the same problem when push shift+F9. The only way to restore it with Shift+F4 and the put the rigth resolution.

That's the video http://www.youtube.com/watch?v=DsOxPuKnuhc

What I made in the video was... I click on full screen TH2GO resolution, go to black screen, I press shift+F4, then another low resolution (1 monitor) show for a teenth LFS on screen an minimize automacaly to windows task bar, I click on the task bar icon, and again show for a teenth and minimize again, again I click on icon and speedy shift+F4, click on the full screen TH2GO resolution and works.

The problem is now I can't do fullscreen only works in windowed mode. I have a nVidia 8800GT with the lastest drivers and W7 32-bit. The problem was become after Z25~Z28 and it is randomize (like in the video), sometimes works sometimes no...

Quote from Glenn67 :

In graphics options set 'Full Scene Antialiasing' to none then try again.

If that fixes it it could be the same problem I and others are having at higher resolutions with TH2G and Win 7.

Quote from Napalm Candy :

Thanks, thats solved the problem I put AAx4 (I got AAx8) and run fine