Perhaps the AntVR manufacturer publish some drivers so LFS devs can "easy" integrate native head tracking support (like for Oculus) in Live for Speed.
Currently the AntVR head tracking does only emulate mouse movements (which is also supported by LFS) but the (big) range of movements of AntVR headset is useless for LFS (if you look to much left or right you "lose" the center view to the track). Because of mouse emulation tracking of side movements (example: lean through the drivers window) is not supported.
However the 3D view (side-by-side mode) is much better then Oculus DK2, because I can see more details of the track (example: break points) with the same technical resolution (1920x1080 means 960x1080 each eye).
Looks like mumble makes the same checks. If any other overlay application is already running (in this case LFSLazy), mumble don't use/start its own overlay.
I'm sorry but I have still problems with the radar.
Today a friend was trying LFS at my home. In single player mode it was working fine. After some hours (now) I started LFS again... but radar won't work.
Now I do not receive a mesage like "LFSLazy Overlay". Some hours before I have seen this message after start/connect of LFSLazy.
In the single and multiplayer screen some buttons are not highlighted as a button but text informations are hightlighted. That looks very strange and confusing newbies and me.
local/UTC: Is simple text. Why they have a button background?
At the other side "Driver", "Garage" and "Track" are not highlighted like a button.
Very strange - Now it works again. Yesterday I have restarted LFS/Lazy some times - no effect. Today I have tried again, and it works. Foolishly I have reset the RadarY to 100 before trying again without changes. So I'm not sure, if it works again, because I have changed the value or not.
A team mate do have the same problem. I ask him, if the radar works now without changes.
Today I'm trying the latest version (in your last post), but the car radar does not work (can't see the car on screen). All other gadgets works fine. The options is active of course.
Any idea, why I can't see it? Is it possible that the radar is out of my view? How I can reset the position of the radar? I can't find any related entry in the LFSLazy.config.txt.
I have reduced the LOD and have disabled AA and also texture filtering.
I've got around ~23 fps in cockpit view of the last car (10.).
The GPU already supports SM4 but does not have enough power anyway to display a "simple" resolution of 1680x1050 without any image enhancement.
Btw. I have tried with nouveau and also proprietary driver of NVIDIA itself. The result with NVIDIA drivers was only around 10% better (2-3 fps).
With this GPU I don't think the result will be much better under Windows.
Software installation after core installation of Linux (KDE desktop):
- Installation of wine
- Installation of DirectX 9.0c
- Installation of LFS with the update to 0.6F2
I do not get any errors after LFS start. With a better GPU LFS work fine under linux.
The new installer (0.6F) ends with a screen with a link to create a new account. The german phrase is not complete and contains also a typo.
Current phrase is:
"Klicke hier, um einen LFS Account zu erstellen, falls cu noch"
"cu" = "du"
I think the complete phase should be like:
"Klicke hier, um einen LFS Account zu erstellen, falls du noch keinen hast."
or
"Klicke hier, um einen LFS Account zu erstellen, falls du noch keinen besitzt."
The link points to the english registration form. Perhaps the installer language could be used to redirect the user to the form in the same language?
Please implement a version number in your tool. It's hard to find out, which one is the newest. also if you publish new download links as a comment in this threat instead in the first one. thanks
Looks like the Kickstarter target ($200'000) will be reach soon (currently >$74'000).
FAQ from Kickstarter
[3D Experience] Does the ANTVR KIT support existing stereoscopic 3D?
YES, it supports the HSBS stereoscopic 3D mode. For PC, almost all 3D games can be played with stereoscopic 3D. Some have stereoscopic 3D options, which the headset can use directly. But for those that don't, you can use some software to convert to stereoscopic 3D, and it will work with the headset. On PS or Xbox, some games also have stereoscopic 3D options.
But I think the LFS native support for head tracking of AntVR is needed?
Workaround for wrong PBs: Clear your current PB with the command !clear (twice; second command confirm first one)
But I found an other bug:
Charset encoding for string clpb_2 is wrong (see screenshot -> red circle). The other strings clpb_1 and clpb_3 contain also "umlaute ä" but are correctly encoded in LFS.
Today I was racing a new track PB (2:27...). LFSState shows this time too. I only jump in the box and came back (same track, same car, without LFSState restart and without LFS restart), LFSState shows me now the old PB of 2:28... HLVC is disabled/off btw.
Is this a known issue?
Is it a limitation of LFS UI that it's impossible to move some tables e.g. "Standings" to the left or right screen in a multi-screen configuration?
By the way/feature request:
A own log directory will be usefull (for the UpdateWR logs).