Quote from Keling :

Isn't socket.close() sufficient for freeing the socket? I tried this

if keyboard.getKeyDown(exitKey):
sockOS.shutdown(0)
sockOS.close()
sys.exit(0)

at the beginning of the loop but rerunning the script still fail.

I thought it would be. I actually never tried to use the close() method properly and I thought that was the reason I could not create new sockets within the Python interpreter in FreePIE.

You could ask the FreePIE guy, I'm not very familiar with neither FreePIE nor Python in general. There might be some other trick to it.

I figured that FreePIE can receive OutGauge and OutSim packets, so you can read realtime data about the car and the game into your PIE scripts. Really cool.

Simple example to monitor the car speed and gear with a none-blocking socket. Note the exception handling when there was no UDP packet available for the given loop iteration.
Another thing to note is that to my knowledge, FreePIE does not have a "stopping" bool like the "starting" bool, so you cannot properly close the socket when you stop the script. To re-run it, you need to restart FreePIE in order to free up the socket.

It can be used, for instance, to reduce the max braking power when the speed goes below a threshold to help prevent flatspotting. Or if you're really pro, you can make your PIE script be aware of oversteer and understeer in realtime. Lots of ideas springs to mind.

Last edited by Skagen, Tue 2 Sep 2014, 22:32.

I made the same argument 2 years ago, but back then to no prevail: https://www.lfsforum.net/showthread.php?t=80366

Gah, makes me want to get a DK2 now.

Quote from Scawen :

...and we could do with the cash!

1. Give people additional options to fund the development outside just purchasing licenses.
2. More updates and openness about the development.

A.k.a the Star Citizen and Elite: Dangerous model. It seems to work, and I'm sure this community would be equally enthusiastic about helping you fund the continued development of LFS.

Here's my FreePIE + vJoy script for mouse steering. It was initially made to mimic the LFS style of mouse steering in other racing games, and the axes are therefor mapped to the axes which the default G27 profile had in the games I tested.

It isn't very elegant because I ran into scoping problems as soon as I tried to solve this using functions and classes/objects.

The script features:

• Easy axis inversion controls
  
• LFS style sensitivity center reduction for mouse steering
  
• Timer based ignition cut so you don't manually cut the ignition for longer than necessary by holding down the shift up key
  
• Throttle blip that can be controlled by how long you hold down the shift down key
  
• Independent rate controls for increasing and decreasing throttle, brakes and clutch
  
• Addition rate controls for increasing and decreasing throttle and clutch during ignition cut and throttle blip events
  

Last edited by Skagen, Fri 18 Jul 2014, 18:47.

Quote from Scawen :

Just remember the resolution is still going to be a bit low. This will be a problem in a racing simulator when you are looking far down the road. Maybe the consumer version (developed with facebook money) will have a higher resolution. Just reminding people, with all the hype, it's still just a developer kit and it might be disappointing if you expect too much.

The horizontal resolution in each eye will be 960 pixels, spread over move than 90 degrees, so you can easily see each pixel individually.

But at those resolutions, even older grade hardware should be able to handle supersampling AA to help out the resolution. On my 4 year old laptop, I ran LFS with 4x SSAA, and not only did it help with the annoying flickering from vegetation and fences with alpha channels, but it is also far superior with correcting texture mooshing than anisotropic filtering which is very nice when you're looking really far down the road.

Whatever you plan on doing with the new possibilities with DX9, I hope you will make it possible for people to disable any expensive effects. There is no doubt in my mind that I would take supersampling AA over any eye-candy effects in LFS if I had to make choice between them.

Depends how the limit is set. If it is just an integer threshold value, the amount of layout objects your processor is actually capable of handling makes no difference.

TCP is also slower and can cause big hickups with other cars, since the flow of position data between you and the server can queue up if there is just one tiny bit of information that is taking a very long time to transmit.

With UDP, if one bit of information is lost in transmission, you just get a minor hickup, if not unoticable hickup in many cases.

Quote from DANIEL-CRO :

Just because it was always there doesn't mean its not a "bug".
Is it limitation of LFS or graphics limitation...?

Most likekly, Scawen has set a limit in LFS as to how many physic interactions the game will compute for layout objects at any given time. For each layout object that is moving, LFS will have to compute its physics. If there are too many moving layout objects moving around at once, the processor cannot keep up with all the calculations required, and the game will start to lag and skip frames.

To avoid this, the limit is probably set with good margins, and the game will simply not calculate the physics for any additional layout object that is over the set limit. It's just a mechanism for prioritizing more important stuff (like the car physics) before the processor load goes too high. And the message is just verbose.

Last edited by Skagen, Mon 21 Jan 2013, 22:58.

In my experience with ENB, the result you get with any given setting isn't deterministic. Often I will have a quite different visual result compared to other people who have posted their settings and screenshots. In all these cases, the ENB library has been the same.

I'm no expert, but it could be ENB doing things which isn't supported by the DX API or drivers, which gives different results on different implementations.

You can check out the current world records here: http://www.lfsworld.net/rafa/

I think you can download and watch SPR (replays) of hotlaps for valid demo combos, i.e XFG@BL1.

Quote from Kyotee :

I know, but as you said, if you can't automatically supersample with ENB enabled, why not force it manually?

Quote from Skagen :

(...) for textures at the angles you often see the road ahead of you while driving. It just gives a much better degree of fine detail in the image, and the image is generally calmer since there is no pixelation from transparent textures, etc.

Quote from Kyotee :

I know how it works, silly. In that case, why not just render at a higher resolution, providing your PC can handle it? If not, then, oh well.

That is what supersampling is; rendering the frame at very high resolutions. With supersampling, my GPU is rendering LFS at 7680 x 4320, and averaging every 4 x 4 block down to 1920 x 1080 which is my laptops screen resolution.

http://www.gimp.org/
http://www.getpaint.net/

Are you sure there is no one else connected to your wireless point using bandwidth? You can log in and check the DHCP client list to see what units have been assigned an adresse on your network.

You can also use tools like insSIDer to check if there is any signal interference with other wireless networks and units in your area.

Sorry, I haven't tested the skins myself. But I'm guessing it's the sort when you have two overlapping surfaces? I don't see any reason for it to happen unless the geometry of the race track was changed.

The flickering has to do with lack of sufficient dithering when the game is trying to determine the color value for each pixel on your monitor. With the massive increase in texture resolution, the new textures will provide far more pixels with varying color information per pixel on your monitor. The flickering is just a sympton of crude metods in the graphics renderer for choosing the most representative color value for each pixel on your monitor. You might think of it as a lack of anti-aliasing for textures/surfaces, rather than edges.

For those of you who have powerful graphics card, you can turn on supersampling anti-aliasing. The screen will be drawn at 2, 4, or 8 times the resolution on your display (depending on drivers), and the overshooting pixels are used to determine the average (or representative if you like) color value for each pixel on your monitor. The result is a much "calmer" image since there is no dramatic changes in color values for neighbouring pixels (atleast when compared to a non-supersampled anti-aliased image).

You can also try adjusting the map bias for grass and road surfaces in options to reduce the flickering.

Last edited by Skagen, Mon 10 Dec 2012, 19:03.

Quote from jajp999 :

- Is there a dynamic track (grip different on and off the racing line) - does it build during a race?

Tyres have a life cycle. In longer races (~45 min or more) you will notice that as the tyres wear down, they get grippier and cooler, so you can push the car harder without loosing the grip or overheating the tyres.

Litt usikker på hvordan man aktiverer demo (jeg kjøpte S2 direkte). Men jeg tror du kan ha fått en epost med en voucher-kode. Når du logger inn på www.lfs.net kan du kopiere og lime inn koden for å aktivere S2-lisensen for LFS-kontoen din.
Merk at det er ett passord for å logge inn på www.lfs.net, www.lfsworld.net, osv (nettside-passordet ditt), og ett annet passord for å aktivere S2 i selve spillet (game-passordet ditt). Begge disse passordene kan du resette her hvis du må: https://www.lfs.net/?page=accountdetails

Etter du har logget inn på www.lfs.net kan du enten trykke på "License status", eller gå hit: https://www.lfs.net/?page=viewstatus
Der vil det stå øverst "Your current LFS license is: ..."

Hvis det står Demo, så har du ikke aktivert S2-lisensen. Hvis det står at du har S2, så trenger du bare å starte LFS, og trykke nederst til høyre hvor det står "Demo license: aleken1997".

Edit: Jeg er for treg...

Your laptop is fitted with the Intel Integrated Media Accelerator 900 (GMA900). According to notebookcheck.net, GMA900 doesn't support hardware T&L which is required for some older games: http://www.notebookcheck.net/I ... celerator-900.2178.0.html

Not sure if LFS requires it. But you can try downloading and installling the drivers of it (if you haven't allready): http://www.intel.com/products/chipsets/gma900/index.htm

But if you get LFS to run with GMA900, I really doubt it will run any smooth at all. Since the GMA900 doesn't have hardware vertex shaders, all the work will be done by the CPU via software - which isn't a fast CPU to begin with.

Last edited by Skagen, Tue 4 Dec 2012, 18:38.

Quote from ACCAkut :

pretty sure that is has been like this forever, and that Scawen explained it once, has something todo with problems of the deformation physics, setup changes can't be applied to a car with deformation.

If I understand you correctly, suspension damage and deformation is a direct manipulation of values, rather than damage beeing an addition to the initial value?

What you see on the Airio page is an error message which is so detailed it even tells you where in the source code the error appeared.

But I haven't seen EQ Worry around lately. Is Airio still beeing maintained? If not, is there any chance of official implementation of Airio-ish features? The popularity of Airio did after all demonstrate a demand for such features.

Last edited by Skagen, Mon 3 Dec 2012, 00:48.

As all ready suggested, if you turn on the virtual pedals in options, you will also see clutch and brake pedals.

Quote from Iginla :

GT2 FZR @ KY2R is pretty good tbh

I agree with that, FZ2 at KY2R is among my favorites.

FZ2 at KY3 would be my favorite if it wasn't for the oval-exit chicane. And AS4, AS5 and AS6 are allways nice.