Hi man, just tested this on CV1, great job! It does look like the "Automatic" FOV setting is wrong for CV1. I get a strong fisheye effect. The real value seems to be around 90, maybe slightly more.

Quote from cmorosco :

Just recorded a video but it is hard to see. Will have to wait for it to upload but I can post a picture from the video.

Do you have vsync on? Does it run at 75 fps? That's exactly what I saw in a demo when the refresh rate was locked at 60 hz instead of 75.

Quote from simg :

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.

Here is someone having issues with another dll, and someone suggesting a fix:
https://developer.oculusvr.com ... &t=8032&start=100

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...

Quote from simg :

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

Yes

Your procmon logs mention that the file has a DACL, maybe try turning off UAC completely, and maybe even do a full re-install of LFS with UAC off.

http://windows.microsoft.com/e ... trol-on-off#1TC=windows-7

Do you have user access control turned on in windows?

Works perfectly, absolutely amazing. So much better when looking at things in the periphery like passing cars. Makes a huge difference, you are a wizard!

Quote from hapklaar :

I have 'Wait for vertical refresh' set to on, but still no vsync and 90fps

Some people reported issues with having to turn it on in both the VIEW and MISC menus.

Otherwise you could just try turning off the FPS cap (since you are mentioning you are stuck at 90 fps I'm guessing you have this on). I've been playing with vsync off at 300ish fps and I think I prefer that to vsync on, as long as low persistence is also turned on.

**I'm running win 8.1. I had issues at first because I had set vsync to off in nvidia control panel, setting it to "application controlled" solved it.

Last edited by ctuchik, Mon, 11 Aug 2014 11:51.

Quote from museumsteve :

1 - Is there a reset VR button (to reset/re-centre view) or is tehre no need after initial centering when you start?

2 - Is there an option to moved the drivers seat position, up/down/in/out. If so can we map it

There is, it's in the normal control options. I bound it to a button on the wheel. You can actually use that to adjust your position in the car by using the position tracking. Just move a little in the opposite direction you want and press the button.

Quote from hapklaar :

For some reason vsync doesn't work. I have a constant framerate of 92 according to MSI Afterburner on the DK2, which is on 75Hz. Enabling or disabling vsync ingame doesn't seem to have any effect and the screen is very 'juddery'. I'm running the latest patch 0.6F4.

I'm using an i7-3770K with an AMD 7990 vidcard. Any idea how I can get vsync to properly work?

You can force vsync on/off in display drivers. Check catalyst control center.

Gotcha. However, when I do turn off the "Full screen vertical sync" option the "Low persistence" option is replaced by a Prediction setting in the View menu.


EDIT: Never mind, only on the initial rift selection screen.

So, this is a bit confusing. If I turn on low persistence that does make a huge difference. Much, much smoother. But if I turn off vsync (after enabling low persistence) I still get the effects from it even if it's running at 300 fps (screen is still dark, headtracking is smooth).

I though that was not supposed to be possible? Especially since you hide the low persistence button when vsync is off. I see no difference in headtracking smoothness between vsync on and off as long as low persistence is still on...

Just did 15 laps or so with and without vsync, headtracking is slightly smoother with vsync on. The game itself does feel smoother at 300 fps compared to 75 though (of course). Not sure which mode I prefer, need to do some more testing.

How is the chromatic correction coming along, difficult to implement?

Haha, the sweating is a serious issue. When I know I have a good lap and it's just a few corners left... I need to learn from the Iceman.

I've also developed a serious "just one more lap" problem.

Wow, that is some incredibly cool stuff.

I really only saw the flickering on things like curbs and billboards. Gonna experiment a bit more with it.

Changing the mip bias sliders to all zeroes does seem to make the world look a lot more solid. Removes some of the shimmering and flickering.

I don't see any reason for working on vsync or low persistence at this point. With vsync off and fps limiter off it runs at 300+ fps and the headtracking is extremely smooth. I see no screen tearing either.

The chromatic aberation is by far the biggest issue now.

Here's a good reaction.

https://www.youtube.com/watch?v=RLNO0Q7F0so

Quote from CodeLyoko1 :

https://www.lfs.net/?page=shop

put extra credit on your account

Awesome, I might just buy some S2 vouchers and give out to friends!

I spent quite a bit of time driving with DK2 yesterday and now I only have one major issue with this. How do I buy you a beer? Do you have a tip jar?

Holy shit, it's perfect. You are a genius. I run with vsync off now, averaging 90 fps with everything maxed. Very smooth and a ton of fun.

Quick test, seems to work flawlessly. Will get back in there and test more.

Quote from Matrixi :

That's interesting, for me it runs on my main monitor only unless I set the Rift as a primary "monitor". Are you on Nvidia/Win7?

Nvidia Win 8.1. Maybe you can actually pick display device in the menus? To make the text more readable you can mess around with the r_manual_stereo_buffer_scale setting. 1.4 or even 2.0 makes a big difference. Does affect FPS though, I already have problems getting consistent 75+ FPS and my PC is pretty beefy...

Quote from Matrixi :

Euro Truck Sim 2 is a good example of a horrible Rift implementation usability wise. First it requires you to set the Rift as a primary monitor... which moves the taskbar and all windows to the Rift by default (windows key + arrows are great for this) but once you manage to actually start the game, you're greeted by microscopic menus and fonts that are unreadable.

I did not have to set the rift as main screen for ETS! Having it extended and second monitor worked fine. I've only had one demo refuse to start on the rift as second monitor even with -adapter 1 and in that case I could just use windowed mode and drag it over.

The car moving and bumping around is not a problem unless it's extreme. Independent head shaking is better to turn off. Pretty sure that was done by default in LFS, correct me if I'm wrong.

The fov change is noticeable and definitely affects the experience. The improvements in latency and image quality from DK1 is just enormous though. Especially latency when rotating the head, should make driving much more comfortable.