I am back to LFS since years with the game left and unfortunately the game closes when I select VR. I use Pimax 5k+ and I think I do everything right. I can configurate everything but when I choose VR/OpenVR/solo configuration in VIEWS I see (only in monitor, not in the HMD) for a pair of seconds the next configuration window but then the game closes. I have the latests U patch, latest SteamVR and latest Pitools (1.01.197)
Thanks for the help and sorry if I did not see the solution in another thread (I have tried to find at least)
Thanks for the report. That is strange because I have not heard of that happening before.
It would be good to have more information. I wonder if there is any message in the deb.log file. That could be the case if LFS decided to close for some reason. Or can you find anything in the Windows event viewer - this would be the case if there was a crash. Do let us know if you need any help finding that information.
Here what log files have (sorry if I am not looking for the correct files):
LFS OpenVR 2019_03_08 LFSVR_Open ProductName: Pimax 5K Plus Manufacturer: Pimax VR, Inc. LFSVR_QueryHMD RT size: 6072 x 2496 Left eye: GetProjectionRaw___: Left -1.742 Right 1.346 Top -1.270 Bottom 1.270 GetProjectionMatrix: Left -1.742 Right 1.346 Top -1.270 Bottom 1.270 GetEyeToHeadTransform: 0.985 0.000 0.174 -0.031 0.000 1.000 0.000 0.000 -0.174 0.000 0.985 0.000 Right eye: GetProjectionRaw___: Left -1.346 Right 1.742 Top -1.270 Bottom 1.270 GetProjectionMatrix: Left -1.346 Right 1.742 Top -1.270 Bottom 1.270 GetEyeToHeadTransform: 0.985 -0.000 -0.174 0.031 0.000 1.000 -0.000 0.000 0.174 0.000 0.985 0.000 IPD: 0.063 LFSVR_AcceptSharedTexture(NULL) LFSVR_AcceptSharedTexture size: 6072 x 2496 LFSVR_CreateTextures size: 6072 x 2496
LFSOpenVR Mar 20 2019 ProductName: Pimax 5K Plus Manufacturer: Pimax VR, Inc. LFSVR_QueryHMD RT size: 6072 x 2496 Left eye: GetProjectionRaw___: Left -1.742 Right 1.346 Top -1.270 Bottom 1.270 GetProjectionMatrix: Left -1.742 Right 1.346 Top -1.270 Bottom 1.270 GetEyeToHeadTransform: 0.985 0.000 0.174 -0.031 0.000 1.000 0.000 0.000 -0.174 0.000 0.985 0.000 Right eye: GetProjectionRaw___: Left -1.346 Right 1.742 Top -1.270 Bottom 1.270 GetProjectionMatrix: Left -1.346 Right 1.742 Top -1.270 Bottom 1.270 GetEyeToHeadTransform: 0.985 -0.000 -0.174 0.031 0.000 1.000 -0.000 0.000 0.174 0.000 0.985 0.000 IPD: 0.063 LFSVR_AcceptSharedTexture size: 6072 x 2496
Nov 01 21:24:40 LFS : 0.6U7 Nov 01 21:24:40 timer resolution 1 ms Nov 01 21:24:40 read config Nov 01 21:24:40 get command line Nov 01 21:24:40 preinit d3d Nov 01 21:24:41 started Direct3D 9Ex Nov 01 21:24:41 number of adapters : 1 Nov 01 21:24:41 adapter 0 - valid modes : 32 Nov 01 21:24:41 load font Nov 01 21:24:41 ----- Nov 01 21:24:41 max texture size 16384 Nov 01 21:24:41 can do shadows Nov 01 21:24:41 can do multi tex Nov 01 21:24:41 load language Nov 01 21:24:41 initialisations Nov 01 21:24:41 human system Nov 01 21:24:41 tables Nov 01 21:24:41 helmet Nov 01 21:24:41 controllers Nov 01 21:24:41 load objects Nov 01 21:24:41 start intro Nov 01 21:24:41 end of initialisation Nov 01 21:24:41 Controller 1 (Thrustmaster T500 RS Racing wheel) : Nov 01 21:24:41 Added 5 axes Nov 01 21:24:41 Controller 2 (vJoy Device) : Nov 01 21:24:41 Added 8 axes Nov 01 21:24:41 Controller 3 (Xinmotek Controller) : Nov 01 21:24:41 Added 4 axes Nov 01 21:24:42 init sound Nov 01 21:32:17 Next LOD Nov 01 21:32:17 Next LOD Nov 01 21:32:17 Next LOD Nov 01 21:32:17 Meshes : 40 Nov 01 21:32:53 shutting down Nov 01 21:32:53 free objects Nov 01 21:32:53 free languages Nov 01 21:32:53 free controllers Nov 01 21:32:53 clear light map Nov 01 21:32:53 close sound Nov 01 21:32:53 close rift Nov 01 21:32:53 free humans Nov 01 21:32:53 free font Nov 01 21:32:53 free helmet Nov 01 21:32:53 kill graphics Nov 01 21:32:53 save controls Nov 01 21:32:53 save views Nov 01 21:32:53 save config Nov 01 21:32:53 free mouse Nov 01 21:32:53 EXIT
Thanks for the reports. It seems from deb.log that LFS closed itself. I see that from "shutting down" and going all the way to "EXIT". So it didn't crash, but decided to close for some reason. So I don't think you'll find anything in the event viewer (it stores a log of program crashes, and other events). I don't know what do say at this point but let's see if anything comes to mind.
It's not .197 at least since I just tried out LFS with the 120hz mode.
I've had this issue once before, but I can't remember how I fixed it. I think I may have restarted everything including pc, but I'm not sure.
I have tried today, everything restarted obviously, and same result. The difference could be that I was able to see the next menu options a little bit longer. It is something related with the position, left/right and things like these.
Did you adjust the FPS limitation, reduced the supersampling, any graphic configuration, etc? I did not, everything full since my pc should be able to move the game easily. Maybe I am too optimistic?
I have tried with lower graphic configuration, testing one on one, and the same closing. I have tested with and without FPS limitation, shaders on/off, everything which could be related. I have even tried to click on "ok" red button but once the this last VR configuration window opens I lose the mouse cursor and enter key does not work either, it is a matter of 5 seconds the game closing.
No changes with -vr parameter, same closing
DEB files does not help much I think (attached both game starting ways)
EDIT: Watch the screenshot I have time to take. The auricular position appears red but HMD position stuf seems correct. Plus, the game closes when the sound init line has been created in DEB file when the game is started using the vr parameter. Audio problem? Let me how to test it
It only gets as far as "open VR". There is no closing sequence visible in the log files. I think this is related to something you said before, that the LFS process is still running? Does that mean you need to close LFS with the task manager?
I think auricular is the translation for 'headset' but I guess from what you are saying it's not a good choice because really the Spanish word refers to something more specific like 'headphones'.
So it seems like:
It enters VR mode, draws a distorted image on screen as if you are in VR mode, then you say it 'closes' after a few seconds. But as I understand it, LFS is then still running in the background and you can see it in task manager? So what actually happens... does the LFS window disappear? Is LFS still visible in the windows taskbar?
I think you should use task manager to close any LFS instances that are still in memory but are not visible, before starting a new one. They are taking up memory and it's possible they could affect Steam VR.
A couple of things you could try:
1) Try setting LFS to English before trying to enter VR mode. It is really unlikely this could help, but it's worth testing in case there is a text buffer I made too small, and the Spanish translation uses a long line.
2) The Pimax software has a mode "Parallel projections" or something like that. LFS should not need to use parallel projection. It may be worth trying in both modes.
No, sorry for the misunderstanding. LFS does not appear in task manager after it closes, it happened once and with older U version (just U). With U8/9 it never has appeared in task manager or at least I am not able to see it. Is it called LFS.EXE right? (All processes are viewed)
Ok, I will test in english and with a fresh installation, without the wheel and everything else configured (I doubt they are a problem because I can play in monitor mode)
Parallel projections always has been disabled, I will try with it on.
OK, if LFS.exe is no longer running but there is no shutdown sequence in the deb.log then that says to me it must have crashed. So there should be a crash log somewhere. Can you try the 'reliability monitor' in Windows? If you click on the start button and type 'reliability' you may be able to see some crash reports there (critical events) and you can double-click an event to see some more information.
EDIT: Alternatively, Event Viewer -> Windows Logs -> Application - maybe some info there.
A crash address (or offset) and an exception code can sometimes help.
I can't find that "reliability" or at least the spanish translation is not correct, there is not any windows program which could be the one you tell me to execute.
Here the error log in Windows logs (attached the screenshot but in Spanish):
"Failed application name: LFS.exe, version: 0.0.0.0, timestamp: 0x5dbda5bf
Module name with errors: unknown, version: 0.0.0.0, timestamp: 0x00000000
Exception code: 0xc0000005
Error offset: 0x0df04367
Process identifier with errors: 0x5bb4
Application start time with errors: 0x01d591b67aaa6f92
Failed application path: E: \ LFS \ LFS.exe
Module path with errors: unknown
Report ID: a469f8f3-c650-49aa-bcae-4b63c258f099
Full package name with errors:
Relative application identifier of the package with errors:"
PCH_DB_FROM_ntdll + 0x0006AE8C
\\? \ C: \ ProgramData \ Microsoft \ Windows \ WER \ Temp \ WER6C07.tmp.dmp \\? \ C: \ ProgramData \ Microsoft \ Windows \ WER \ Temp \ WER6D60.tmp.WERInternalMetadata.xml \\? \ C: \ ProgramData \ Microsoft \ Windows \ WER \ Temp \ WER6D90.tmp.xml \\? \ C: \ ProgramData \ Microsoft \ Windows \ WER \ Temp \ WER6D92.tmp.csv \\? \ C: \ ProgramData \ Microsoft \ Windows \ WER \ Temp \ WER6DB2.tmp.txt
C: \ ProgramData \ Microsoft \ Windows \ WER \ ReportArchive \ AppCrash_LFS.exe_9a5287748b83a52d5f12c675c7b753b16141_d41fbd6c_5ee272ce
The first one seemed to be the most useful, because it has the "Error offset".
Error offset: 0x0df04367
Unfortunately this offset is not within the LFS.exe code, although I guess it was called by LFS. I don't know if it could be within the LFSOpenVR.dll or in the OpenVR code or in the Pimax drivers. In any of those cases it may or may not be an actual LFS bug. The trouble is I can't identify the line of code because it's not in the LFS.exe.
Yes, not a single problem with Steam games and iRacing at least.
Found the problem!!
The problem is the "FIXED FOVETEAD RENDERING", it can not be activated in LFS
Sorry for all this wasting time. Maybe you could warn pimax users somehow and let them know that we cannot use "FFR". It is a very good tool because it helps a lot with the FPS
by TRM.13 : Problem fixed
What max resolution is allowed in LFS? Do you know how large the pimax FOV is?
by Scawen : no longer needed
I don't know the Pimax FOV but it is big and LFS can handle it fine. I did all the research back when we first supported the Pimax. It was different because of the angle of the displays. But that is sorted and everyone else I have heard of who has tried it with the Pimax, finds it works fine. At the moment this is only a problem with your computer + Pimax + LFS. Until this point, LFS can run well with all known headsets and really doesn't crash. At this point, I don't really think it's a bug in LFS. I did a search yesterday and found there have been crashes in recent drivers. So I wouldn't be surprised if it's something in the Pimax drivers. Although emiljensen2 said the same drivers you are using work find on his computer. Is it a possibility to try some older drivers that were known to be stable?