The online racing simulator
Test Patch U9: Fixes / VR updates
(167 posts, started , go to first unread)
Btw...

The stand alone Oculus Quest (over Pc-Link) also works perfectly with LFS....Thumbs up
Quote from Whiskey :That sounds a lot like your computer is messing up a socket.
Did you try to switch between UDP and TCP packets in LFS? That should work even without leaving the server.

Can confirm after testing stuff out once it happened again, it is a strange sort of packet loss indeed. Eventhough it is on my locally hosted server, swapping from UDP to TCP packets solved the issue. Swapping back to UDP instantly caused it again.
Quote from rockclan :Can confirm after testing stuff out once it happened again, it is a strange sort of packet loss indeed. Eventhough it is on my locally hosted server, swapping from UDP to TCP packets solved the issue. Swapping back to UDP instantly caused it again.

I'm glad you were able to verify my diagnostic. But now, I'm afraid my networking knowledge is not enough to propose any further test or solution...
FFB at the placebo level. But it feels better. I will test in more detail and write later.
What settings should I set for Thrustmaster F430, 400 and 50Hz?
Scawen what about translate Rockingham tracks? it's still untranslated
iirc the release of blackwood industrial was 2018
i believe releasing all these graphics and time etc updates is better than losing the fans
Quote from Yazan0Alothman :iirc the release of blackwood industrial was 2018
i believe releasing all these graphics and time etc updates is better than losing the fans

I believe that's the plan, it is just not finished yet, updating South City is still ongoing and Fern Bay still to be done. Updating the tracks takes time when there is only one person doing the job. All we can do is to wait and hope Eric to progress in his work without any extra surprises in the development process. The day night transition is an extra feature which I think is mainly looked into by Scawen and as such does not affect Eric's progress on tracks. Then there will be the tyre physics update which we don't know how much effort that will still need to have it included in test patch releases along with grachics update for tracks.
Hi guys, i keep getting this message "CreateRenderTarget failed (MS4) : GARAGE~T" and lots more. pls help
Quote from nxggera :Hi guys, i keep getting this message "CreateRenderTarget failed (MS4) : GARAGE~T" and lots more. pls help

Your game install by me corrupted, try reinstalling the game. Or if that doesn't do it, it might be your GPU drivers. Try cleaning them with DDU and installing fresh drivers from Intel, NVIDIA or AMD. Wink
thank you for this Smile

now I am going to go back to slaving feverishly over this neutral fzr set. no idea how many years I've been taking advantage of these amazing physics but I'm faster today than I was a few days ago. ok maybe only a little bit, but still.

hopefully I can release something soon! it might even be before the day/night update, it's that close now
Pimax 8K
I can't start LFS anymore. LFS close after display view calibration.

The openvr.log contains following information

LFSOpenVR Mar 20 2019
ProductName: Vive MV
Manufacturer: HTC
LFSVR_QueryHMD
RT size: 5512 x 2332
Left eye:
GetProjectionRaw___: Left -1.742 Right 1.346 Top -1.306 Bottom 1.306
GetProjectionMatrix: Left -1.742 Right 1.346 Top -1.306 Bottom 1.306
GetEyeToHeadTransform:
0.985 0.000 0.174 -0.032
0.000 1.000 0.000 0.000
-0.174 0.000 0.985 0.000
Right eye:
GetProjectionRaw___: Left -1.346 Right 1.742 Top -1.306 Bottom 1.306
GetProjectionMatrix: Left -1.346 Right 1.742 Top -1.306 Bottom 1.306
GetEyeToHeadTransform:
0.985 -0.000 -0.174 0.032
0.000 1.000 -0.000 0.000
0.174 0.000 0.985 0.000
IPD: 0.064
LFSVR_AcceptSharedTexture
size: 5512 x 2332

The deb.log contains this data

Mar 15 15:38:05 LFS : 0.6U9
Mar 15 15:38:05 timer resolution 1 ms
Mar 15 15:38:05 read config
Mar 15 15:38:05 get command line
Mar 15 15:38:05 preinit d3d
Mar 15 15:38:05 started Direct3D 9Ex
Mar 15 15:38:05 number of adapters : 1
Mar 15 15:38:05 adapter 0 - valid modes : 57
Mar 15 15:38:05 load font
Mar 15 15:38:05 -----
Mar 15 15:38:05 max texture size 16384
Mar 15 15:38:05 can do shadows
Mar 15 15:38:05 can do multi tex
Mar 15 15:38:06 load language
Mar 15 15:38:06 initialisations
Mar 15 15:38:06 human system
Mar 15 15:38:06 tables
Mar 15 15:38:06 helmet
Mar 15 15:38:06 controllers
Mar 15 15:38:06 load objects
Mar 15 15:38:06 start intro
Mar 15 15:38:06 end of initialisation
Mar 15 15:38:06 Blackwood
Mar 15 15:38:13 Next LOD
Mar 15 15:38:13 Next LOD
Mar 15 15:38:13 Next LOD
Mar 15 15:38:13 Meshes : 40
Mar 15 15:38:13 init sound
Mar 15 15:38:20 Garage : data\veh\XF GTI.veh
Mar 15 15:39:05 open VR

Today I updated the PiTool. Afterwards the firmware of the headset was updated automatically, too. By the way, SteamVR home works without any problems. I haven't tested any other games yet.

I already rename the cfg.txt. After that I can start LFS. But when I configure 3D again, I got the same issue.

Does anyone else use the pimax 8k and have updated the pitool?
Thanks for the information.

At exactly which point does LFS close? You said "LFS close after display view calibration." Do you mean after you press the space bar when looking straight ahead?

In that case have you tried the other button?
What I am talking about, there are two different methods to centre the view:

"OK - reset headset position"
"OK - use relative position"

You could try the one you don't normally use.

Also, how does LFS close? Is there any information about a crash? If so, maybe there is an entry in the Windows Event logs.
@Scawen: LFS crash before I can press any key. I only see for a short time that the headset position menu is displayed. I have no chance to confirm with any key press.

I will check the windows event log asap.
I have found following entry:

Name der fehlerhaften Anwendung: LFS.exe, Version: 0.0.0.0, Zeitstempel: 0x5dbda5bf
Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x24cbb2a2
ID des fehlerhaften Prozesses: 0x274c
Startzeit der fehlerhaften Anwendung: 0x01d5fb812d89a4b4
Pfad der fehlerhaften Anwendung: D:\LFS\LFS.exe
Pfad des fehlerhaften Moduls: unknown
Berichtskennung: 858b8aad-d6cf-45a4-a560-251929a6543d
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Thanks for the information. That crash (0xc0000005) is a memory access violation.

Unfortunately the offset of the instruction that caused the crash is not within the LFS exe. It might be in D3D or the Pimax drivers (or the graphics card drivers). That doesn't prove that LFS is not at fault but it doesn't prove it is at fault and certainly does mean I can't locate the problem.

I don't really know what to do at this point. Would it be possible to ask the Pimax developers to run LFS using a debug version of their drivers to see where the crash is, as it seems to be caused by the new update.
Thanks you for verifying the data. In the meantime I have installed the latest NVIDIA drivers. Looks like something was wrong before. The installer was not aible to detect the driver version installed before. Very strange

But now everything works again. Thank you for the fast support.
Good to know - thanks.

Test Patch U9: Fixes / VR updates
(167 posts, started )
FGED GREDG RDFGDR GSFDG