Anyone feels like doing some hillclimbing? We're on the "lfs at nkp" server trying to get up trento bondone with the abarth evo (rwd fiat500 abarth with more power)

Server: lfs at nkp
Password: lfs
Car: http://www.acracing.net/downloads/500AbarthEvo.rar (extract to /nkpro/cars/
Track: http://troy.freeunix.net/NKPro ... _patch_online_trc0.10.zip (extract to /nkpro/tracks/trento-bondone/server/

Quote from ACCAkut :

may I remind you to post links to streams if you find any

You may want to check some of your older pm's, there is a good chance you will find a working stream there.

http://78.111.71.32/BurnoutCrew/DoP/ this one I would think, at least I still got that in my history from previous years.

Out of this discussion: http://www.lfsforum.net/showthread.php?t=81867

So far only people with nvidia graphics cards seem to report the problem, could be driver related but why would it freeze with AA enabled through LFS ingame options and not with AA enabled via nvidia driver options directly? It also wont freeze in windowed mode, it's just fullscreen that is affected.

Quote from troy :

Tried this again on a clean lfs install. No matter the resolution and quality settings I always get some stutter when printscreen is pressed with enabled anti aliasing via the LFS in game settings, most noticeable in higher resolutions there it will stutter about 1 or 2 seconds, if I go back to 640x480 the stuttering is down to about 0.5s.

*stutter meaning the picture is freezing completely and the sound starts to loop

As soon as I turn off anti aliasing or force it via the nvidia control panel instead the stutter is gone, no other quality settings seem to make a noticeable difference. I would guess there is a problem with LFS' implementation of anti aliasing via the ingame menu? Could somebody test this on other affected machines so we can confirm this?

Just for completeness sake my rig:

Asrock Z77 Extreme4
Ivy Bridge I5 3570k
GF GTX 260 (896mb ram)
Win7 x64 (16gb ram)

Quote from pmw :

It's not about the hard disk, maybe if you are using computer from 90s.

I just tried that AA stuff:

Without AA, nothing happens when I hit print screen. No fps loss _at all_.
In windowed mode with AA, nothing happens, no fps loss at all.


BUT:
With _any_ AA mode, 2x, 4x, 8x etc in fullscreen, _always_ same pause, 2.5 seconds.
I tried many times, in many different MPRs, always same 2.5 seconds.

For me, it sounds definitely like fullscreen rendering with AA-enabled, something just bugs. It's not about HDD speed or caches, if stuck time is always same.

C - C - C - C combo breaker



Life is too short for the wrong job!

No rules on skins, apart from the usual lfs stance on no nudity and stuff

I could understand a very short stutter related to harddisk access times, but my system plate is an SSD and if I start to force AA via nvidia driver instead of lfs it's completely gone, not even a flicker on the fps when I press printscreen. So it has to be something lfs does differently when AA is done via in game settings.

Tried this again on a clean lfs install. No matter the resolution and quality settings I always get some stutter when printscreen is pressed with enabled anti aliasing via the LFS in game settings, most noticeable in higher resolutions there it will stutter about 1 or 2 seconds, if I go back to 640x480 the stuttering is down to about 0.5s.

*stutter meaning the picture is freezing completely and the sound starts to loop

As soon as I turn off anti aliasing or force it via the nvidia control panel instead the stutter is gone, no other quality settings seem to make a noticeable difference. I would guess there is a problem with LFS' implementation of anti aliasing via the ingame menu? Could somebody test this on other affected machines so we can confirm this?

Just for completeness sake my rig:

Asrock Z77 Extreme4
Ivy Bridge I5 3570k
GF GTX 260 (896mb ram)
Win7 x64 (16gb ram)

Last edited by troy, Thu 10 Jan 2013, 10:30. Reason : found another way to get rid of the stutter, updated.

You should probably go to the german lfs forum and ask flo or one of the other admins. I would imagine they know the internals better since 4players is just another reseller of s2 licences, there is not much the devs, or any other member of this forum can do about this.

Edit: Just to ask the obvious question, but why not buy it directly from lfs.net? They use a reasonable amount of payment methods so there should be something for everyone.

Quote from DavidTiger :

It does it only in fullscreen for me, fps drops but isn't noticable as its always above 60.

That is true indeed, just tested and I get about 1s of stuttering when I press print screen in fullscreen mode, as soon as I switch to windowed mode there is no stutter at all. I wouldn't consider my hardware weak either gtx260 and 3570k, that should be plenty to get this stutter free.

Maybe this should go into the program bugs section?

I got the same problem here, never investigated further though.

Nice, always hated that the radical was only on weekends for example, give me driver swaps and 50% on a year and I might even resub.

Run xbmc on it, and if you've got dvb-c/s/t use vdr as tvserver for example. And voila you've got yourself a low footprint mediacenter with pvr ability, that could serve the whole household with tv/media.

Tech demo probably out in a "couple" of weeks.

https://twitter.com/KunosStefano/status/286781328714784768

I'm not particularly fast in the fwd cars and it's the day after new years eve at 6 in the morning but I just felt like doing some laps.

Never mind the first few laps, took me a while to get used to the car/set, last 3 laps should be a reasonable benchmark to aim for. The default set got no camber and is generally outdated, so I would rather not try and go online with it but if you're just learning the car and track and got no real experience in simracing it's probably good to get yourself a set you feel comfortable with and just learn the track/brakepoints/lines until you are up to around 1 second of a good time. After that it may be worth checking out sets specially made for the track since they usually got a proper gearing and suspension to get the most out of a lap.

Sites/Places to get sets got linked already so I wont do that again, rule of thumb should always be "slow in fast out", don't overdrive the car be smooth with the throttle/steering input and everything else will come with more experience.

edit: great it looks like you can't save replays from the training lessons anymore, I thought that was possible at some point. Re-recorded the whole thing in single player with hardtrack setup (should be the same as the one in the testdrive)

Last edited by troy, Tue 1 Jan 2013, 05:33.

You will never get the RB4 competitive in any endurance race, he's using more fuel and has bigger tyre wear, so even if you do the same pace you will be staying in the pits longer. You could experiment with additional weight for the FXO/XRT of course but that only makes things complicated for everybody and the few teams who will chose RB4 should know by now that you wont be driving for the win with it.

concept skin (yes yes my photoshop skills are lousy, blame fuse for being in the army)

I quite liked the raw onboard feeds some of the lemans teams offered via the net, throw in a dedicated pitlane feed, live telemetry, some textbased updates and you've got a fan.

Quote from Scawen :

[from 6th December 2012]The crash seems to be in a part of the code that is used when the track is being generated, so it probably is something to do with the host changing track. I've had a go at reproducing it, changing tracks on the host while the guest is in a window, but could not find a problem.

Can you remember the exact time line of events, did you ALT+TAB from full screen, was LFS minimised at the time, did the host change tracks while LFS was minimised...

This is not really high priority as it is the only time I have heard of this crash. But if anyone does ever find a way to reproduce it, it will be good to fix it although it seems to be very rare.

• Finished race
  
• alt-tab from fullscreen
  
• lfs still running in the background
  
• checked mail
  
• lfs crash
  

I don't know what exactly happened on the server in the background, but usually they change track a few minutes after the race ended, so it could very well have crashed once the track changed, can't be sure though. Never happened again so far, had lfs alt-tabbed from full screen plenty of times, could've been a problem on my end too I guess.

Yep, getting Sat1 in HD but it was so horrible I switched to a low bitrate SD stream of motorstv to actually see some racing...

Quote from Squelch :

That's a good point, but it seems to happen whenever the skin isn't available from LFSW, so your suggestion probably doesn't help in this particular case.

....

I wonder what would happen if the skin was cached locally, and wasn't available from LFSW? (after a skin had been deleted for example)

Wouldn't lfs still access the disk while searching for it locally? I know demo users can't use skin downloads and get around that limitation by just putting the skins in their skins folder manually. So it could still be something with disk access? Not 100% sure of course, you only getting it on skins not available on lfsworld rules out dds loading when a new car joins I guess.

Could be the harddisk, I had some microstuttering too on skin loading so I made symlinks to the skins_x/y/dds folders on my ssd and kept the rest on the old hdd, since then it's not happening anymore.

Symlinks on windows with junction

Mh, I'm on a GTX260 and get flickering, also Full AA/AF plus super sampling. Can't test it with another card right now, GF is hogging her laptop.

Best I could come up with, zero flickering but not a very nice start line. Maybe somebody with more talent can get more out of it. For me thats enough to race on. (2048 version)

Quote from smove :

Could it possibly help moving the S/F line away from the edge of the texture, like in the picture attached? I know, it would still be a compromise, but surely better than removing the line completely.

I tried to fiddle around with all kinds of solutions, making it smaller, leaving more space on top or bottom but it seems to be chopped up in a really weird way, the start line is not what you think it would be judging from the picture of the texture, half of it is used on the fernbay green start the other half on the fernbay gold start both of those are then again used not in a single line but chopped in half again for the actual start line. At some point I just ran out of patience and decided that the line isn't that important after all.