0.6F Oculus Toggle crash [FIXED in 0.6F2]
Tried some searches, didn't get any hits.

Latest version from lfs.net, autoupdated.

Latest Oculus SDK

Alt-F11 bound to a Thrustmaster T500RS button. Press the bound button for Oculus toggle and LFS.exe crash consistently.

Anything I can do to hunt that crash down, let me know.
Are you sure it's the latest? 0.6E isn't the most recent version.
Corrected.
I autoupdated yesterday from 0.6B.
Are you able to get the crash address from the crash report? That's what could tell the devs a bit more about what happened there.
Just get the "lfs.exe has crashed" dialog. Maybe there's a log?
Crash is easily reproducable by holding button with the bind "/rift toggle" (default ALT+F11). You don't even need rift to reproduce it.

Problem signature:
Problem Event Name: BEX
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 53a30b6e
Fault Module Name: MSVCR100.dll_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4df2be1e
Exception Offset: 720ab65a
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1050
Additional Information 1: 0f31
Additional Information 2: 0f3137665bbf0bb676c8a16f3fa76e52
Additional Information 3: 1d68
Additional Information 4: 1d686001bff90c6a00857de9c6b9d3fc

Quote from atledreier :Just get the "lfs.exe has crashed" dialog. Maybe there's a log?

Does this happen every time you press the assigned button?

Does it happen if you press ALT+F11?

I think the relevant crash info may be on your computer, stored as AppCrash events which are .WER files, as seen here:
https://www.lfsforum.net/showt ... php?p=1860400#post1860400

I think you might find the info quite easily as seen in this post:
https://www.lfsforum.net/showt ... php?p=1860409#post1860409

If you could attach a relevant WER file, we'll see if it contains any information different from Daniel's one. Problem is I am not able to reproduce this reliably, and not in the debug version at all, and the crash address Daniel shows is not within LFS.exe.
Tried same thing on laptop, and a bit different crash there

Problem signature:
Problem Event Name: APPCRASH
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 53a30b6e
Fault Module Name: [B]LFSORDLL.dll[/B]
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 527d1326
Exception Code: c0000005
Exception Offset: 0000b65a
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1050
Additional Information 1: a076
Additional Information 2: a07647fd22b60ec504255b34e373830b
Additional Information 3: 0243
Additional Information 4: 0243c3521b2ef187d28615651546247a

The toggle works fine in UI and menus, but in the car I get an immediate crash. Here's the most recent:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-07-06T08:30:27.000000000Z" />
<EventRecordID>57880</EventRecordID>
<Channel>Application</Channel>
<Computer>Atle-PC</Computer>
<Security />
</System>
- <EventData>
<Data>LFS.exe</Data>
<Data>0.0.0.0</Data>
<Data>53a30b6e</Data>
<Data>nvd3dum.dll</Data>
<Data>9.18.13.2049</Data>
<Data>51c40fa2</Data>
<Data>c0000005</Data>
<Data>005c7ed0</Data>
<Data>2110</Data>
<Data>01cf98f46ca77406</Data>
<Data>D:\spill\lfs\LFS.exe</Data>
<Data>C:\Windows\system32\nvd3dum.dll</Data>
<Data>c7aed478-04e7-11e4-89ad-f46d0403e2fc</Data>
</EventData>
</Event>

Pressing alt-F11 works fine.
I have a thrustmaster T500RS, latest official drivers and firmware.
Today I finished a race on cargame and stayed in the car after the race. Went to options and assigned /rift toggle (in the ALT+ menu) to one of the buttons on my wheel. Pressed it once, switched to the rift mode, pressed again, crash. I haven't got a Rift. Pressing ALT+F11 also works fine here.
Windows crash log (it's weird, it has the ATI/AMD driver named in it):
Problem signature:
Problem Event Name: APPCRASH
Application Name: LFS.exe
Application Version: 0.0.0.0
Application Timestamp: 53a30b6e
Fault Module Name: atiumdag.dll
Fault Module Version: 9.14.10.926
Fault Module Timestamp: 5064fef0
Exception Code: c0000005
Exception Offset: 0001730c
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1051
Additional Information 1: 4709
Additional Information 2: 4709938665fa84e3ff99c8cbe11223bb
Additional Information 3: 710f
Additional Information 4: 710fc537215186d2113af37ac1d885f4

Thank you, now I understand it is only when you use a wheel button, as described in the original post.

I got knocked off the trail when I read Daniel's post, and also did manage to reproduce a crash that way, not reliably, when holding down the keypress ALT+F11 (without wheel button assignment). Looking into that, I found that to be a mysterious bug and forgot to test the wheel button assignment, which turns out to be a different issue.

When using the wheel button assignment, it's reliable crash, when going from Rift mode back to normal mode, there is a crash. Should be easy enough to fix (tomorrow).
Excellent! Glad to help! :-)
** Best answer **
You can reproduce the "steering wheel button returning to non-rift mode" crash without a steering wheel:

- Press ALT+F11 to enter rift mode
- Press T to open a text entry dialog
- Press ALT+F11 in the text entry dialog... CRASH!

Also found a stack overflow, not really related:

- Assign e.g. ALT+F10 this text: /alt F10
- Press ALT+F10... CRASH!

FGED GREDG RDFGDR GSFDG