>Thanks for your patience!

Thanks for your time and a great game

dandealer,

awesome, this completely fixed my issue. many thanks for posting

game now works beautifully

Quote from Matrixi :

Those of you who have issues, is your DK2 on the left or right side of the main monitor in the windows display menu? Apparently it *HAS* to be on the left side for some things to work.

http://www.reddit.com/r/oculus ... culus_rift_wasnt_working/

I've always had mine on the right side of my main monitor and haven't had issues, but it might be worth a try moving your Rift to the left.

didn't fix the "could not open oculus dll" error.

would have been lovely if it did though

@HackMac

will do

thanks ctuchik.

The solution suggested in that link is to download the visual c runtime distributable. I've already done that and a few variations on that theme :/

thanks though

Quote from ctuchik :

No visual studio or SDKs on my gaming PC. I'd recommend doing a 'sfc /scannow', a full run of windows update and making sure you have up to date versions of directx and .net. Really weird issue...

sfc /scannow didn't find any issues and a full windows update including optional patches hasn't made any difference

dependency walker still reports MSVCR100.DLL as being problematic, but I have reason to believe maybe a limitation of dependency walker not understanding about win32/64 (see https://software.intel.com/en-us/forums/topic/393036)

In other news, I managed to get my venerable Logitech FFGP steering wheel out of the loft and working with LFS

Many thanks for the help and suggestions so far. Unless anyone has any other suggestions, I'll wait for the next patch and see if it's improved error reporting reveals anything.

Remembered about a tool I've read about elsewhere called "Dependency Walker" (http://support.microsoft.com/kb/256872)

Ran that on LFSORDLL.dll and it identified a problem with MSVCR100.dll.
I've run into similar issues on a few other applications / demos but I've installed various versions of the C++ runtime and in some cases this has resolved the issue.

see screenshot:

Anyway, this lead me to this page: http://stackoverflow.com/quest ... win-7-64-bit-dll-problems and installing the Win7 SDK from here http://www.microsoft.com/en-us ... confirmation.aspx?id=8279

One potential difference between my machine and most (all?) of yours is that I'm not an (active) Windows developer so my machine may be missing libraries (or something) that is installed with Visual Studio?

Anyway, I feel I'm getting somewhere, but having the Win7 SDK installed (and rebooting) hasn't made a difference. Also MSVCR100.dll still shows as missing in dependency walker :/

edit: MSVCR100.dll is present in both the System32 and SysWOW64 folders

Last edited by simg, Wed 13 Aug 2014, 11:13.

>which CPU

Intel Core-2 Quad Q6600.

Pretty sure this CPU is also affected by the "AMD" issue (which is in fact caused by a dependency on the SSE 4.1 extension also not present in older intel chips such as the Q6600).

I *was* getting around the "AMD" issue in other software by unplugging the position tracking camera. The update to the 0.4.1 Oculus runtime as fixed the "AMD" issue for me, so position tracking works fine.

>and maybe even do a full re-install of LFS with UAC off.

done. no luck

>EDIT : "FILE LOCKED WITH ONLY READERS" sounds a bit obscure, but have you tried restarting the computer?

only about 30 times

I've also enabled "Advanced mode" on process monitor which seems to give a fair bit more info (attached as a csv). Maybe this will help?

>Do you have user access control turned on in windows?

Yes

>Thanks for trying! For the next patch I'll try to add more information if "LoadLibrary" fails.

Sounds good, thanks for your help !

@TroutDeep: Good suggestion re: Process Monitor.

Attached a screenshot of the output related to LFSORDLL.dll which might provide some clues?



Also tried giving my user "Full Control" of the LFS folder but that didn't make any difference.

>Any screenshots of the 3rd person replay view?

I didn't think this was related to my issue? (still not sure ?)

Tried re-installing, tried re-installing as admin (including applying the patch as admin)

Files are in C:\LFS

I haven't tried to do anything "clever", just install LFS then copy over the 6F patch.

There are no other installations. The shortcut points to C:\LFS\LFS.exe (and the problem occurs even if I run the .exe directly)

'fraid not. just tried running as admin and same problem.

my "normal" user has read/execute permissions on the LFSORDLL.dll file anyway

thanks for the quick reply.

happy to be proved wrong, but I don't *think* it's as simple as not extracting the patch correctly. I've seen all the other posts where people have made this mistake and took care to ensure all the files were copied to the correct location.

I have a LFSORDLL.dll in the LFS folder and I also have data/shaders.

I initially used the "alternative zip" but just in case I've also tried the self-extracting archive version. No luck

I get the above error message when trying to enable Oculus mode in the view settings (and then no VR mode).

I've got the latest version of LFS (0.6F) along with the 0.6F6 patch (which show s on the start up screen). I've also tried the 0.6F5 patch which has the same problem.

I'm running a clean build of Windows 7 with the Oculus 0.4.1 Runtime. Graphics card is GTX650 if that makes a difference.

Any suggestions would be appreciated