Okay thank you for clearing that up scawen

Quote from batya123 :

There are too many unnecessary mods. It would be great if we can block the author or mods. Too many unnecessary mods makes confusion.

Please keep this thread test patch related. There is a dedicated subforum for discussing the mod system: https://www.lfs.net/forum/498-Vehicle-Mods-Forum

Quote from batya123 :

Too many unnecessary mods makes confusion.

On the other hand i agree with an idea of having a blacklist to hide unwanted mods from the main mod list, that could be opened separately like the favourites list.

Many things may be good suggestions, but we have a special forum section for mod system suggestions:
https://www.lfs.net/forum/532-Mods-System-Suggestions

I do look there and in time I act on things I see. But random suggestions placed in this thread that is about a test patch, are kind of annoying. This thread is to discuss issues about the test patch or extremely on-topic suggestions related to something in the test patch.

Well,we are not getting closer to the big update whit dashboard editor

I would like to see average load consumption like in Lazy.

First I must say this is not a request thread. Second, your description doesn't mean anything to me. Maybe it's something to do with the fuel usage feature that has already been added? Options - Display - Extra status info?

Please only post here if it is something to do with the test patch. It's very difficult trying to stay on top of everything.

Yes, fuel consumption is available after setting things mentioned above and clicking F9 or F10 on second lap and above.

Can i ask when the update for 0.7E will come or whatever it will be called?

Aint no way u just did PDF presentation or whatever that is about AI UPDATE....

You have too much free time and waste it on something like this

Singleplayer racing under 1 month had more updates than multiplayer since 2002

I think scawen try for traveller Al drivers.

Today my Windows Defender deleted LFS.exe during gamplay because of finding in it "Behavior:Win32/DefenseEvasion.A!ml" (serious danger). I thought I actually had a virus problem, but immediately after downloading the package from the official link, ie:

https://www.lfs.net/file_lfs.php?name=LFS_PATCH_7D_TO_7D26.exe

Windows defender detects the virus again. Could anyone confirm that this is the same for you? Win 10, everything up-to-date.

File ist clear

Fałszywy alarm

Quote from limac92 :

Today my Windows Defender deleted LFS.exe during gamplay because of finding in it "Behavior:Win32/DefenseEvasion.A!ml" (serious danger). I thought I actually had a virus problem, but immediately after downloading the package from the official link, ie:

https://www.lfs.net/file_lfs.php?name=LFS_PATCH_7D_TO_7D26.exe

Windows defender detects the virus again. Could anyone confirm that this is the same for you? Win 10, everything up-to-date.

Ididint have anything like this bud u can try virus total or smth.

I don't know if it's just me, but I'm getting a consistent crash when trying to race on Blackwood BL1 on patch D46, where D45 was working fine. I can drive on BL1X though.
I'm playing on Linux through wine, but was having no problems at all before D46 and now it keeps crashing (just happened as I was changing cars too).
On the bike handling side, I now understand what people said about D45, it's true that D46 makes bikes much more agile at lower speeds.

As you say the crash is consistent, please can you explain how to recreate it? Which vehicle are you using, which game mode (single player / multiplayer / hot lapping)? Exactly when does the crash happen, what do you do to make it happen, etc...

Also, if possible can you give us a crash address or crash offset?

Crash address reporting described here: https://www.lfs.net/forum/thread/96121-Please-do-report-crashes

It actually seems less consistent than I thought - I still get a crash 100% of the time, but not always at the exact same time.
- First scenario where it always happened: previous track was Fern Bay Green, I changed that to Blackwood BL1. Vehicle was Reaper bike (stock), with a grid of 20 AI which I cleared to ride alone. Race was set to 20 laps. The game crashed after pressing the Go button, while loading (towards the end, just before displaying the game).
- Second scenario: BL1X, alone on the Reaper bike (stock), 20 laps (no checkpoints). Crash happens after the hairpin, before the chicane.
- Third scenario (somewhat different): from scenario 1 or 2, changing the vehicle (to XRR or BF1, only tried those 2), crash happens while confirming car choice or even before that, while moving the mouse.
- Fourth scenario: I went back to Fern Bay to avoid the car selection crash, switched to XRR, then went back to BL1X, practice. The game crashes as soon as I'm done turning after exiting the garage (I tried going the wrong way as well, same result). It's almost as if something in the field of view causes it.

As for the crash address/offset, I'll have a look if I can get that, running from wine I'm not sure how to open the Windows event viewer. I do have 2 crash dumps from wine itself, but nothing in there looks like the address/offset you want. As a side note, I'm on an old PC right now, not my main PC, not sure how relevant it could be, but I had D45 on that same old PC working with no issue.
I will try and downgrade to D45 and check that none of this happens, just to be sure.

Below is part of one of the crash dumps:
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code (0x6ab275f5).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
EIP:6ab275f5 ESP:054cf7e4 EBP:054cf808 EFLAGS:00010206( R- -- I - -P- )
EAX:00000000 EBX:1e62ef00 ECX:0016850c EDX:00000000
ESI:1fe00030 EDI:00000000
Stack dump:
0x054cf7e4: 1e5f4b88 054cf8b8 6ab2f0be 00000000
0x054cf7f4: 1fe00030 0016850c 1e62ef00 054cf8b8
0x054cf804: 1e5f4b88 1e62ee08 03424875 00000000
0x054cf814: 1fe00030 0016850c 40002000 00008892
0x054cf824: 1e5f4b88 012d7884 034425cf 012d7884
0x054cf834: 012a0f30 00000002 00000001 012c73cc
Backtrace:
=>0 0x6ab275f5 in ucrtbase (+0x675f5) (0x054cf808)
1 0x6ab2f0be memcpy+0x4e(dst=0x000000000, src=1FE00030, n=0x16850c) [Z:\usr\src\packages\BUILD\dlls\msvcrt\string.c:3063] in ucrtbase (0x054cf808)
2 0x03424875 wined3d_context_gl_unmap_bo_address(context_gl=012A0F30, dst=054CF8B8, src=054CF8B0, range_count=0x1, ranges=1E62EF00) [Z:\usr\src\packages\BUILD\dlls\wined3d\context_gl.c:3125] in wined3d (0x1e62ee08)
3 0x03424875 wined3d_context_gl_copy_bo_address+0x1a5(context_gl=012A0F30, dst=054CF8B8, src=054CF8B0, range_count=0x1, ranges=1E62EF00) [Z:\usr\src\packages\BUILD\dlls\wined3d\context_gl.c:3124] in wined3d (0x1e62ee08)
4 0x0341710f wined3d_context_copy_bo_address+0x47(ranges=<internal error>, range_count=<internal error>, src=<internal error>, dst=<internal error>, context=<internal error>) [Z:\usr\src\packages\BUILD\dlls\wined3d\wined3d_private.h:6589] in wined3d (0x1e62ee08)
5 0x0341710f wined3d_buffer_load_location+0x38f(buffer=1E62EE08, context=012A0F30, location=0x8) [Z:\usr\src\packages\BUILD\dlls\wined3d\buffer.c:666] in wined3d (0x1e62ee08)
6 0x0341866a wined3d_buffer_load+0x19a(buffer=1E62EE08, context=012A0F30, state=04AC002C) [Z:\usr\src\packages\BUILD\dlls\wined3d\buffer.c:902] in wined3d (0x012a0f30)
7 0x0341aa68 context_update_stream_info+0x148(context=012A0F30, state=<is not available>) [Z:\usr\src\packages\BUILD\dlls\wined3d\context.c:306] in wined3d (0x00000000)
8 0x034271ba context_apply_draw_state+0x20c(indexed=<internal error>, state=<internal error>, device=<internal error>, context=<internal error>) [Z:\usr\src\packages\BUILD\dlls\wined3d\context_gl.c:4244] in wined3d (0x012a0f30)
9 0x034271ba draw_primitive+0x43a(device=<is not available>, state=<is not available>, parameters=<is not available>) [Z:\usr\src\packages\BUILD\dlls\wined3d\context_gl.c:5151] in wined3d (0x012a0f30)
10 0x03437ab6 wined3d_cs_exec_draw+0xe6(cs=04AC0020, data=04DA6B00) [Z:\usr\src\packages\BUILD\dlls\wined3d\cs.c:1006] in wined3d (0x00000000)
11 0x0343b4bb wined3d_cs_command_unlock(queue=<internal error>, cs=<internal error>) [Z:\usr\src\packages\BUILD\dlls\wined3d\cs.c:3308] in wined3d (0x054cff28)
12 0x0343b4bb wined3d_cs_execute_next+0x53(ctx=<couldn't compute location>) [Z:\usr\src\packages\BUILD\dlls\wined3d\cs.c:3307] in wined3d (0x054cff28)
13 0x0343b4bb wined3d_cs_run+0x13b(ctx=<couldn't compute location>) [Z:\usr\src\packages\BUILD\dlls\wined3d\cs.c:3374] in wined3d (0x054cff28)
14 0x7b629ee0 in kernel32 (+0x29ee0) (0x054cff48)
15 0x7bc5c6e7 in ntdll (+0x5c6e7) (0x054cff5c)
16 0x7bc5cef0 RtlCreateUserThread(entry=0343B380, arg=04AC0020) [Z:\usr\src\packages\BUILD\dlls\ntdll\thread.c:306] in ntdll (0x054cffec)
0x6ab275f5 ucrtbase+0x675f5: movq %mm0,0x0(%edi)

And some thread info regarding LFS:
00000158 (D) C:\LFS\LFS.exe
0000015c 0
00000160 0 <== wined3d_cs
00000164 0
00000168 15 winepulse_mainloop
0000016c 15 winepulse_timer_loop
00000170 15 wine_dsound_mixer
00000180 0

The backtrace seems to point to something in the graphics system and doesn't seem to directly involve LFS at the time of the crash. I will not claim that LFS couldn't cause the problem, but I will say that I can't think of anything changed in D46 to create a new graphical issue. Could there have been a coincidental graphics driver update or something like that? It will be interesting to see if D45 has the same issue now. And at this point I'd suggested restarting the computer if you haven't already.

Would you happen to have a link to D45 somewhere? I just realized I deleted it after upgrading to D46...
I also restarted my computer and I still have those crashes (I guess Linux is more consistent than Windows here )

Quote from Bokujishin :

Would you happen to have a link to D45 somewhere?

Just edit the link from opening post to 45: https://www.lfs.net/file_lfs.php?name=LFS_PATCH_7D_TO_7D45.exe

Thanks Eclipsed, got it.
I'll have to assume my issues are on my side, as a fresh install updated to D45 crashes just as often now, though I'm really not sure why... I was planning to try out another Linux distribution on this PC, I'll update if/when I do that or when I get back to my usual PC if anything is still broken.

Quote from Bokujishin :

Thanks Eclipsed, got it.
I'll have to assume my issues are on my side, as a fresh install updated to D45 crashes just as often now, though I'm really not sure why... I was planning to try out another Linux distribution on this PC, I'll update if/when I do that or when I get back to my usual PC if anything is still broken.

Are you using straight WINE or using Proton? Proton may work better as it should be using Vulkan for D3D rather than the Wine D3D system?

Anyone experiencing issues with Mouse X Y driving since last patch?

Since update (tried with old 0.7D, same issue, same folder only EXE different) the mouse X Y for throttle/brake and steering stopped working.

If I revert to mouse/keyboard configuration, the inputs are recognized and the vehicle turns. If i change to wheel/joystick and configure Mouse X and Y for steering and throttle/brake, no input is recognized except mouse buttons (shifting up and down).

Was this a coincidence or is it something related with the new patch ?

Additionally, I remember updating to D50 and driving normally (with XY). Only after closing and opening later LFS (without any change from my side) I noticed this problem.
-------

• configuring on the wheel/joystick menu to accelerate and brake with mouse buttons also is not recognized.
  
• The look function with mouse XY is working
  
• A new installation on a separate folder of LFS 0.7D does not fix the issue
  
• Cross-checking with FreePie and Vjoy is also not recognized ( I only use FreePie for games that does not support mouse steering)
  

Somehow with new patch there was a conflict with Vjoy drivers, uninstalled it all OK now

Quote from cuni :

Anyone experiencing issues with Mouse X Y driving since last patch?

Since update (tried with old 0.7D, same issue, same folder only EXE different) the mouse X Y for throttle/brake and steering stopped working.

If I revert to mouse/keyboard configuration, the inputs are recognized and the vehicle turns. If i change to wheel/joystick and configure Mouse X and Y for steering and throttle/brake, no input is recognized except mouse buttons (shifting up and down).

Was this a coincidence or is it something related with the new patch ?

Additionally, I remember updating to D50 and driving normally (with XY). Only after closing and opening later LFS (without any change from my side) I noticed this problem.
-------

• configuring on the wheel/joystick menu to accelerate and brake with mouse buttons also is not recognized.
  
• The look function with mouse XY is working
  
• A new installation on a separate folder of LFS 0.7D does not fix the issue
  

Had an issue like that, turned out to be the number of buttons used by Vjoy, which i use for mouse steering in other sims.

Hello, first of all, thank you for the beta of the next update and we look forward to the update! I wanted to ask if there is an idea of implementing the day/night system and weather like rain and it would be great to have circuit mods that players can create in the asseto corsa style thanks in advance for keeping live for speed alive