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)

EDIT: I can play in monitor without any trouble

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.

Thanks for such fast replay.

Here what log files have (sorry if I am not looking for the correct files):

ovr_deb.log


openvr.log


deb.log

I can't understand anything I see in windows event viewer, let me know what to look for.

For the record: when the game "crashes" the task it is still opened. I realised that when I wanted to update from U to U7 (not letting me updating LFS.EXE file)

More: If the Pimax are not connected and if I go to VR, steamvr opens but then game says "not able to open vr device" (not exactly these words but something like that). The game does not crash.

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.

Quote from TRM.13 :

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)

EDIT: I can play in monitor without any trouble

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.

Maybe I need to add some logging in a test patch, so any reason for starting the exit process is logged as a line in deb.log.

For now, I just wondered what would happen if you start LFS in VR mode. You can do that by creating a shortcut to LFS.exe then add the command line /vr=openvr

So for example the Target line in shortcut properties might be:
C:\LFS\LFS.exe /vr=openvr

Quote from Scawen :

Test Patch U9 is now available.


- When LFS is set to close the reason is logged to deb.log file

TRM.13: please try to enter VR and then as soon as it goes wrong and LFS closes, please attach the deb.log file

- Live telemetry is available in a new customisable OutSim packet

Programmers: https://www.lfs.net/forum/thread/93701

- Yellow and blue flags now alternate with RCM or penalty message
- FIX: Stop-go penalty caused car to get stuck in custom pit stop


Download: https://www.lfs.net/forum/thread/93185

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

Quote from TRM.13 :

No changes with -vr parameter, same closing
DEB files does not help much I think (attached both game starting ways)

Ah, this is not what I was expecting.

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?

See me previous edited post, sorry for being slow editing it.

I did close the LFS in task manager, but only when I wanted to update from U to U8. Now I am doing the tests without closing it

I can see annoying blinks through HMD before the game closes (3/6 seconds after clicking the -vr shortcut), like an old TV but heavier

Forget about "auricular" and sound problem, somehow the spanish translation calls to the HMD "auricular" (which I would use for the earphones / sound hardware)

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.

Quote from Scawen :

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:"

"- System

- Provider

[Name] Application Error

- EventID 1000

[Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[SystemTime] 2019-11-02T19: 48: 22.498883100Z

EventRecordID 124549

Channel Application

Computer DESKTOP-8AA1RIM

Security


- EventData

LFS.exe
0.0.0.0
5dbda5bf
unknown
0.0.0.0
00000000
c0000005
0df04367
5bb4
01d591b67aaa6f92
E: \ LFS \ LFS.exe
unknown
a469f8f3-c650-49aa-bcae-4b63c258f099"

A second error log found, maybe it helps:

"- System

- Provider

[Name] Windows Error Reporting

- EventID 1001

[Qualifiers] 0

Level 4

Task 0

Keywords 0x80000000000000

- TimeCreated

[SystemTime] 2019-11-02T19: 48: 24.427505800Z

EventRecordID 124550

Channel Application

Computer DESKTOP-8AA1RIM

Security


- EventData

1314093422181352660
one
APPCRASH
Not available
0
LFS.exe
0.0.0.0
5dbda5bf
StackHash_90c9
0.0.0.0
00000000
c0000005
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

0
a469f8f3-c650-49aa-bcae-4b63c258f099
268435456
76f02b03e50ee22c923c99014ecc04d4
0"

Registration Name: Application
Source: Windows Error Reporting
Date: 02/11/2019 20:48:24
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: Not available
Equipment: DESKTOP-8AA1RIM
Description:
Deposit with errors 1314093422181352660, type 1
Event Name: APPCRASH
Answer: Not Available
.Cab file id: 0

Problem signature:
P1: LFS.exe
P2: 0.0.0.0
P3: 5dbda5bf
P4: StackHash_90c9
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: PCH_DB_FROM_ntdll + 0x0006AE8C
P9:
P10:

Attached files:
\\? \ 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

It is possible that these files are available here:
C: \ ProgramData \ Microsoft \ Windows \ WER \ ReportArchive \ AppCrash_LFS.exe_9a5287748b83a52d5f12c675c7b753b16141_d41fbd6c_5ee272ce

Analysis symbol:
New search for a solution: 0
Report ID: a469f8f3-c650-49aa-bcae-4b63c258f099
Report Status: 268435456
Deposit with hash algorithm: 76f02b03e50ee22c923c99014ecc04d4
.Cab file GUID: 0
Event XML:
<Event xmlns = "http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name = "Windows Error Reporting" />
<EventID Qualifiers = "0"> 1001 </EventID>
<Level> 4 </Level>
<Task> 0 </Task>
<Keywords> 0x80000000000000 </Keywords>
<TimeCreated SystemTime = "2019-11-02T19: 48: 24.427505800Z" />
<EventRecordID> 124550 </EventRecordID>
<Channel> Application </Channel>
<Computer> DESKTOP-8AA1RIM </Computer>
<Security />
</System>
<EventData>
<Data> 1314093422181352660 </Data>
<Data> 1 </Data>
<Data> APPCRASH </Data>
<Data> Not available </Data>
<Data> 0 </Data>
<Data> LFS.exe </Data>
<Data> 0.0.0.0 </Data>
<Data> 5dbda5bf </Data>
<Data> StackHash_90c9 </Data>
<Data> 0.0.0.0 </Data>
<Data> 00000000 </Data>
<Data> c0000005 </Data>
<Data> PCH_DB_FROM_ntdll + 0x0006AE8C </Data>
<Data>
</Data>
<Data>
</Data>
<Data>
\\? \ 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 </Data>
<Data> C: \ ProgramData \ Microsoft \ Windows \ WER \ ReportArchive \ AppCrash_LFS.exe_9a5287748b83a52d5f12c675c7b753b16141_d41fbd6c_5ee272ce </Data>
<Data>
</Data>
<Data> 0 </Data>
<Data> a469f8f3-c650-49aa-bcae-4b63c258f099 </Data>
<Data> 268435456 </Data>
<Data> 76f02b03e50ee22c923c99014ecc04d4 </Data>
<Data> 0 </Data>
</EventData>
</Event>

Thanks for the crash reports.

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.

Is your headset working well with other games?

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

SOrry Scawen, I found the REAL problem, see the previous post

OK, thanks for the info.

I'll look up this foveated rendering and see if there's anything we can do about it.

You mentioned supersampling before. I think you should be able to use it in LFS, where it is known as "Resolution adjustment".

Yes, sorry again... I did 2 changes in the same test and that is why I misunderstood the problem.

SS can be at least 1.5x without problem. The only thing that can not be activated is the FFR.

I need to play the game properly and I will test with higher SS and with LFS's resolution adjustments too before more posting

Thanks for your really good support