The online racing simulator
Searching in All forums
(602 results)
Scawen
Developer
Hi Tim, I noticed this error in the live stream start time. It displays LIVE although the event has not started.

I think when the event was rescheduled, the live stream start time was not updated.
Scawen
Developer
Well maybe you have misunderstood me. I didn't explain very well, but can't do without diagrams.

Anyway another method could be this:

Down in the crack at the point where you want the break in smoothing, set that to two rows of points (as you created anyway, but then they are combined automatically) but separate them by 1mm. Connect these with a very thin surface of triangles which are in a separate smoothing group.
Scawen
Developer
Quote from Snoop.DriftEra :For example, I need 2-sided windshield. I have two copys of same windshield with triangles faced different sides. But when I delete some cutouts in Editor, it merges all the points when i exit [Model Edit] mode and I get a mess with Normals.

As in your case you don't want to use the double sided triangles, you must use a different smoothing group for the inside and outside surfaces.

Quote from Snoop.DriftEra :Here's another example on screenshot: I need my fender to have a cut (see normals coming out of "one" point at the body line?; in fact there's two points in same place that each belongs to their own surfaces. But the whole fender can not be divided by smoothing groups. This screenshot made before I made a cleanup. After cleanup Editor screws everything up and make surface solid with no cut. How do I bypass it?

As the points in the same location will be merged at some point, you do have to use a different smoothing group for the top and bottom surface.

I understand, you have found a rare case where the smoothing groups are hard to use, because you want the top and bottom triangles to have a different smoothing group at the seam, but the same smoothing group rearward of the seam.

I think the only solution is to use different smoothing groups for the top section and the bottom section, and use extra triangles at the rear where the top and bottom section meet. By making the extra triangles co-planar where they meet, they will end up with the same normal.
Scawen
Developer
I believe this is no problem. After all, it's just a bit of free advertising for these companies. I think if good representation of different versions of a logo are used with respect it should be OK.
Scawen
Developer
Quote from akubosaan :Is there anyway to set single-adjustment suspension damping like in xrg, xfg, and uf1 (just like single-adjustment differential)?

That is not possible, because that system has been removed in the later version of physics. As the editor is built in the new development version, that option has already gone.

Quote from Snoop.DriftEra :I tried to search forums, but no luck. Excuse me if this question answered before:

When i try to delete points it says "Points in use". What do i do wrong?

I think it must be that the points are used by a triangle.

You can use "select connected triangles" to find the triangles. Note that the triangles may be in a different LOD, because points are shared between levels of detail. So you may need to "select connected triangles" again in each LOD.
Scawen
Developer
It seems quite strange that the audio device is shown as a display device.

LFS doesn't really know about separate physical monitors. It renders to a single surface that spans multiple monitors. When you press SHIFT+F12 I think it tries to go for a full screen borderless window at the desktop resolution.

So it seems to me you need to examine the actual desktop resolution when the device is enabled. It seems to me that Windows is reporting to LFS a larger desktop than you can actually see (a desktop spanning 4 screens although you only really have 3 physical screens).

When your audio device is connected, and you go into Windows display (or screen resolution) settings, do you have an option to only use the first 3 screens and leave the '4th screen' unused?
Scawen
Developer
Thanks for the report. Only one other user reported a similar issue with version 0.7C.

The crash report showed the crash was in the D3D9 module so we have not been able to track down the problem so far.
https://www.lfs.net/forum/post/1998089#post1998089

Please could you try something - somehow start LFS without a crash (maybe as you suggested, using an SPR). Then try to use a text entry dialog to type /eventlist=no so it does not try to load the list of events. If this seems to stop the problem then we can suppose it may be related to the list of events. I'd like to know if that is the case.

If that doesn't prevent the problem then it could be good to try using the LFS.exe from version 0.7B as suggested in this post:
https://www.lfs.net/forum/post/1998282#post1998282
Scawen
Developer
Thank you all for the feedback.

Version 0.7D is now available!

https://www.lfs.net/forum/thread/98364
Scawen
Developer
Thank you all for the feedback.

Official version 0.7D is now available!

https://www.lfs.net/forum/thread/98364
Scawen
Developer
Thank you all for the feedback.

The new official version is now available!

https://www.lfs.net/forum/thread/98364
New Version 0.7D
Scawen
Developer
Hello Racers,

Today we move on to a new version with some updates for the list of events on the entry screen.

The list of events now shows a countdown to a live stream if it will start within an hour. The number of racers on an event's host is now displayed, either during the event or when it is open for practice. A lock icon is shown if you will need a password to join.

The other changes are mainly fixes for a few issues that were found in the recently released version C, and some user interface improvements.

Please read the full list of changes on the Live for Speed version 0.7D page.

Scawen
Developer
Thank you for the tests.

I've uploaded a last chance test patch C6 as we plan to release the full version this afternoon.

Changes from C5 to C6:

Interface:

FIX: Virtual keyboard full of question marks in Greek or Cyrillic

List of events:

Lock icon reduces width of Join button to share the usual width
Generic 'play' character added for other live streaming services
Scawen
Developer
That is now available in Test Patch C5:
https://www.lfs.net/forum/thread/98309
Scawen
Developer
Changes in test patch C5:

List of events:

YouTube and Twitch links are now shown as icons instead of names
A lock icon is displayed beside Join button if password required

Mods screen:

Mod name was not always shown as selected when entering mods screen

Misc:

FIX: Corrected width of characters in text dialog code page view
Scawen
Developer
Quote from Eclipsed :... and hope to start some brainstorming how to improve this.

Quote from MicroSpecV :Perhaps for each event listing, if the event is passworded, there can be a sentence saying "Read forum for attending" or something like that? Or "Event is Private - read forum for details"

I asked Victor about this, the situation when:

- Host is private (has a password)
- That password is not supplied with the event list

He suggested a padlock symbol. I've implemented that as seen in the attached image. If you then click Join, it will stop on the "Join Specific Host" screen if you don't already have a password entered for that host.

If instead you click the padlock button, it takes you straight to the event page, as if you had clicked the event name.

I've also added YouTube and Twitch icons as you can see in the image.
Scawen
Developer
Thanks for the report. I've now fixed this so it will be in the next test patch (after C4).
Scawen
Developer
Thanks for the report. This is fixed in Test Patch C2:
https://www.lfs.net/forum/thread/98309
Scawen
Developer
I've gone with the cyan version in test patch C4.

It's not implemented on the web side so you won't see anything yet.
Scawen
Developer
The fix is available for testing in Test Patch C4: https://www.lfs.net/forum/thread/98309
Scawen
Developer
Quote from MandulAA :Or, another way, put the word "in" between the blob and the livestream countdown. Not sure how it would look with char "i" next to the blob.

Best solution!

Quote from MandulAA :Brackets for the numbers would be great! Whichever looks best Smile

When I realised the numbers should be coloured, I thought it looked better without brackets. Which do you prefer in the attachment? Other suggestions welcome.
Scawen
Developer
OK I think I have a solution. Luckily I have an old FF joystick to test.

I tried your proposed fast fix: abs(nXForce) -> nXForce

But that doesn't work properly - it resulted in reverse force when steering left.

So I tried keeping the change you suggested but also set the direction to 'right' always. This seems to work.

CODE:

old:
rglDirection[0] = nXForce;
rglDirection[1] = nYForce;
cf.lMagnitude = abs(nXForce);

new:
rglDirection[0] = 1;
rglDirection[1] = 0;
cf.lMagnitude = nXForce;

This seems to have the same result on the FF joystick and I guess it would work on your wheel.
Scawen
Developer
I think I agree about the space. My family members pushed me to add the extra space as they thought the blob was too close to the other text. Although I felt as you do, I went with the majority. Looking

I've removed that extra space now in the attached image. What do you think? When the next character is a 1, I can see what my family were worried about. Schwitz


About the racers online, would it matter that the number isn't live, and only updates when you refresh the page? It would be easy to add a static display but much harder to make it check in with the website or master server for regular updates.

If so, what about a 3rd possible notation using brackets:

Rony's Tuesday Fun Race (45/47)
Scawen
Developer
Thank you for this. I am trying to get my head around it but I'm not quite there yet!

I have the following code, which is copied from example code and edited a bit. I can't find any mention of axisEnable.

Here is a link where I've found a version of the original example code, posted by Chuck Walbourn:
https://github.com/walbourn/directx-sdk-samples/blob/main/DirectInput/FFConst/ffconst.cpp

See the function at the bottom "SetDeviceForcesXY" - when setting cf.lMagnitude it results in the same as my abs(nXForce).

So I'm a bit torn here as I'm reluctant to diverge from the proper way of doing things, to try to somehow make LFS compatible with bugged wheel drivers. It seems that something could go wrong. But I realise my understanding is incomplete.

LFS code:

INT nYForce = 0;

// modifying an effect is basically the same as creating a new one, except you need only specify the parameters you are modifying

LONG rglDirection[2];

DICONSTANTFORCE cf;

if (g_dwNumFFAxis==1) // if only one force feedback axis, then apply only one direction and keep the direction at zero
{
rglDirection[0] = 0;
rglDirection[1] = 0;
cf.lMagnitude = nXForce;
}
else // if two force feedback axis, then apply magnitude from both directions
{
rglDirection[0] = nXForce;
rglDirection[1] = nYForce;
cf.lMagnitude = abs(nXForce);
}

DIEFFECT eff;
memset(&eff, 0, sizeof(eff));

eff.dwSize = sizeof(DIEFFECT);
eff.dwFlags = DIEFF_CARTESIAN | DIEFF_OBJECTOFFSETS;
eff.cAxes = g_dwNumFFAxis;
eff.rglDirection = rglDirection;
eff.lpEnvelope = 0;
eff.cbTypeSpecificParams = sizeof(DICONSTANTFORCE);
eff.lpvTypeSpecificParams = &cf;
eff.dwStartDelay = 0;

// Now set the new parameters and start the effect immediately.

HRESULT hr = g_pEffect->SetParameters(&eff, DIEP_DIRECTION | DIEP_TYPESPECIFICPARAMS | DIEP_START);


Scawen
Developer
That is fixed in Test Patch C3: https://www.lfs.net/forum/thread/98309
Scawen
Developer
A crash fix and a few minor updates in Test Patch C3
FGED GREDG RDFGDR GSFDG