That's because of the new unified objects system - the same object index is now the same for all tracks and no longer unique to each track.
Scawen made all objects available to all tracks, and as a result, some existing objects needed to either dropped or replaced. The advertising hoardings seem to have been the ones that had least impact, so yes they have been rationalised to some degree. I think someone noticed the Aston style posts are no longer available, but not confirmed that myself.
As I said earlier, it seems that the new regs will just stifle innovation. That is something that does filter down to us plebs at the end of the day. Yes they are only designed for a 200 odd mile lifetime, but designing to close tolerances does give tangible data for real world application. Why the regulations have to enforce the configuration is beyond me.
I'm having trouble passing command line parameters to LFS that I'm sure worked before. For example, I want to force windowed mode using
LFS.exe /windowed=yes
but I'm getting an error
What I actually want to do is to use another cfg.txt file by passing
LFS.exe /cfg=mycfg.txt
This throws
I'm sure I was able to use parameters in the past, and commands.txt still leads me to believe that the above command should be valid. The only parameters I can get to work are /insim=xxx and others after using /host=Host Name, but nothing else works for a single session.
Have I missed something like start in single player mode, if so what is it please?
Last edited by Squelch, .
Reason : Changed topic title
Event log to see if an app has crashed and left that port assigned.
On the last point, it is possible that an application that has used that port did not exit cleanly and left a child process open. Windows tries to clean up after exited programs, but cannot if there is another part of that app, or something else that it spawned still running.
The very last step is to try a reboot to see if it clears.
exit.lfs - A script that is run when LFS closes down. It can be used to initiate any clean up and resetting that the user may need from within LFS. It can also be used to signal external applications that LFS is closing.
entry.lfs - similar to autoexec.lfs, but is run every time the user goes to the entry screen. This can be used to set certain defaults, change controller mappings to enable program navigation for example.
The function of both of these scripts could be made via an external InSim application, however, a simple, connectionless and failsafe method using these scripts would be preferable.
is used when LFS Dedi starts. It means there will be no window to see. If this is the case, it is very easy to start LFS again and find TCP Socket : bind failed although it should also say another instance of LFS is running too.
I think you may have something else using that port. Try changing the port number if possible, or use a tool to display ports in use.
Sysinternals is a very good suite of programs and utilities created for and by MS.
To check if another program or service is already using that port. Get Sysinternals suite or just TCPView and run it. It will should all ports that are in use.
Part of the skill of racing is managing your tyres. It's all very well going off at tremendous pace for the first few laps, only to find that the tyres are overheated/worn out. Also cold tyres add that extra bit of danger to the beginning of a race. On the other hand, having warm tyres at the beginning of a race could remove the T1 blues. Tyre warmers are not used on track day performance tyres as used by the road going class cars, it really doesn't make sense. Even some race classes with slick tyres don't allow warmers (Ginetta cup for example)
There is also something else to consider. New tyre physics. We don't know what is in store for us yet on this level, and I would bet Scawen has a plan.
A direct method of accessing the pit adjustments that can also be mapped to a controller would be highly useful. The same goes for brake bias and ARB settings without having to open and look at the F11 menu or create a lengthy macro. Alternately, or in addition, these adjustments could be made available as options in the control options screen for direct mapping.
Last edited by Squelch, .
Reason : Moved my improvement suggestion to its own thread.
What does it matter if an unlock is required? Is it too much trouble to enter a password?
There have been no texture changes to my knowledge. If you know how to edit or change your textures, I'm sure you also know how to back them up. Why the negative attitude?
Edit:
You can change your password by going here Top right is your license. Login using the *same* password as this forum, and you can then edit your details and passwords.
This might be a worthy improvement request, but I wanted to be sure I hadn't overlooked some obvious way of detecting a return to entry screen and shut down from within LFS. I'm sure there are others that could use these signals for their scripts without having to resort to an InSim app too.
That's what I have been doing, but I don't always remember. Although I always try to start any app with known parameters to avoid odd behaviour, it's not always possible, and I do like to have things finish up properly on exit.
So, supplemental to autoexec.lfs, I'd like to see entry.lfs, and exit.lfs, to be run on returning to the entry screen and on LFS shutdown respectively.
The last round of patch testing made me think about having the associations point to a batch/CMD anyway so I could then pick which LFS install to start. That is still relevant for a dev/test install, so I might just do that anyway. It's much easier/safer to edit a text file than hack the registry to achieve the same ends.
I'm using LFS Script to set controller profiles plus some other LFS related settings for the different cars. It all works very well except for one minor annoyance. If I exit LFS or return to the entry screen, I would like to reset my controllers to a default setting. I've read all of the docs, searched the forums, and tried everything I can think of short of using an external program via InSim.
Here is a rough outline of what I'm doing.
I set some defaults using autoexec.lfs which is called at LFS start.
For every car that is used, the associated *.lfs script calls an external app to apply the controller settings.
The problem.
If LFS is exited using Alt+F4, or drilling down the menus to exit, the last cars settings are still in force. Returning to the entry screen does not re-invoke autoexec.lfs.
My current workaround is to call LFS via a CMD script that resets controllers on LFS exit. This is a bit messy and suboptimal. LFS started via a replay association for example, will bypass the loader script, and therefore miss resetting the controllers.
Does anyone have a suggestion on how to detect LFS entry screen, or signal LFS exit from within an LFS script?
This is a good initiative, but the test patch threads contain information why the following are not bugs in my opinion.
The open configs remove objects which are not shared between all original track configurations. This means that some walls, fences and barriers will be missing. Scawen fixed the worst offenders by putting a new barrier in its place, but really this requires a track edit which was not a planned part of this patch. If the holes bother you so much, they can be plugged with autocross objects, open configs give us a free canvass to work on after all.
I'm assuming that you would like to adjust the bite point on an analogue clutch?
It would be nice to have this same sort of feature that RBR has in regards to setting the controller axes profiles built into LFS where the axes are linear
The clutch axis (and others)can be tweaked somewhat by an external application to make it more realistic. Just remember that the axis are inverted in most case, so take this into consideration when making adjustments.
Each car would need its own profile, but this can be done via the LFS scripting functions to set each car differently. I might do a little howto if people are interested
Last edited by Squelch, .
Reason : Added bit about inverted axes
Congratulations on the new release. I'm sure we will all relish the new features/fixes and polish.
Thank you also for your hard work and tolerance over the last eight weeks - it really doesn't feel that long - The whole exercise has rekindled the LFS bug for many it seems. Long may it last...
Selecting a 16 bit mode in LFS will force aero off, and might help diagnose your full screen issue.
Edit:
No wait that's wrong. Selecting a screen resolution as Scawen suggested will force LFS full screen. You could also try disabling desktop composition under compatibility in LFS shortcut properties. This will disable Aero.
Stopping it might not fix things, but that process is the taskbar sound mixer control. Try right clicking the speaker to open properties, drill down to the enhanced effects under advanced tab and disable them. If you are sound editing, you want to do your own, and not let windows take over. You could even disable the windows mixer completely if you like.
Edit:
I just re-read the thread and you don't mention your soundcard make or even the lappy make/model. Are your drivers up to date? I'm surprised no-one has asked this already. Windows updates can sometimes kill what was a perfectly working system unless the system drivers are also updated. Not all manufacturers continue support on slightly older kit (they'd prefer you to buy new) but the reference drivers for most components can be used and are more likely current. Old or poorly performing drivers are a cause of this type of problem. This was exactly the case with my problem, and because my good drivers weren't Microsoft signed. the generic and older drivers were used in preference.
[caveat] Some manufacturers have special enhancements that depart from standard, some even just depart from standard to make you go to them for support. Installing the wrong drivers can make things worse in these cases. In other words check the Laptop manufacturers site first.
Last edited by Squelch, .
Reason : manufacturer details