PDA

View Full Version : TEST Patch W41


Pages : [1] 2

Scawen
31st May 2007, 01:29
WARNING 1 : THIS IS A TEST

WARNING 2 : THE PATCH CAN TAKE A FEW MINUTES TO CONVERT SOME SKINS THE FIRST TIME YOU RUN IT

Hello Racers.

Here is a new test patch W41.

Please read the list of changes below.

Here is some information about the major changes in this series of test patches :

- Preload added to clutch pack differentials improving handling
- The number of cars that can join a race has been increased to 32
- False starts are now possible (LFS does not hold you at the start line)
- Skin improvements including high resolution premium skin download service
- Global class balancing system (currently applied to GTR and TBO classes)
- A new version of InSim including many improvements and a button interface

There are various improvements related to skins including the option to download high resolution skins while online, for a small charge of £1 for 2000 downloads. The low resolution downloads are still free. We have to charge for the downloading of high resolution skins because of the increased bandwidth and the need to buy and maintain more internet servers for LFS online usage which is always increasing. Please note, we are not selling skins. The skins remain the property of their owners. Your copy is a high resolution compressed version of the original. This is a charge purely for the downloading service which allows you to see other cars' skins in higher resolution.

Downloaded skins are now always saved and shown in compressed form. The original jpg is not saved on other computers. This allows the best use of memory and the quickest load from disk.

To use your own jpg skins, or to view skins that you manually download, save them into your skins folder - you will then find them selectable in game, just as before. You can see your manually downloaded skins compressed or not compressed according to the option for local skins. There are now 4 skins folders but you can ignore them all, just forget about them and just use the skins folder as usual.

skins : you save jpg skins that you want to select in game
skins_dds : lfs uses this to store dds (compressed) versions of your local skins
skins_x : lfs stores automatically downloaded low res skins
skins_y : lfs stores automatically downloaded high res skins

If you want to use this service, you can make a payment at www.lfsworld.net or at the main site http://www.lfs.net/?page=shop

To deal with the increased memory usage, there is also a skin purging system which removes unneeded skins from your graphics card memory, some time after they were last used. You can see the list of skins in use in the Misc Options screen. White means the skin is actually in use. Black means it was recently used and is hanging around a while in case it is used again (to avoid a disc access). In the past, LFS just left all skins in memory until you changed track or weather.

Changes in TEST PATCH W41 :

Queue can be up to 48 (Queue + In Game can be up to Max Conns)
Hopefully reduced the possibiliy of "Did not receive guest info"
FIX : Bug that could cause host to stop responding after /reinit
FIX : Admin slots and Max Connections did not work properly

Changes in TEST PATCH W40 :

Improvements / fixes to deal with connect / disconnect issues
More "keep alive" packets while loading track and skins
Number in queue should now never increase
Disconnection reason is now shown in MPR

Changes in TEST PATCH W39 :

A new connection queuing system to keep it clean
Some other small fixes in the multiplayer code

Changes in TEST PATCH W38 :

Too many players could join when limited by starting grid size
Attempting to fix another bug where joining player never joins

Changes in TEST PATCH W37 :

Dedicated host now has a grey screen so you can read black text
BLUE FLAG works in practice (priority to racers not on first lap)
Start time added to MPR file @ offset 36 (seconds since 1/1/1970)
Current race position added to CompCar structure (InSim IS_MCI)
FIX : In practice, second lap on reverse track was not counted
FIX : W36 could wrongly count first lap of hotlap as valid
FIX : Safer code when changing windowed to full screen

Changes in TEST PATCH W36 :

InSim buttons can now be seen during a replay
FIX : List of connections was invisible in the game setup screen
FIX : First lap in practice or qualifying was shown as 1 hour
FIX : Second lap in practice on reverse track was not counted

Changes in TEST PATCH W35 :

Admin penalties, pitlane commands and rcm are now recorded in SP Replays
Code page names are now translatable (for switching keyboard layouts)
InSim : Added "always on" option and better control of the clear area

FIX : Dedicated host could stop responding to typed messages and commands
FIX : Occasionally you could not start a race with AI after practicing
FIX : Penalty given during pit stop would make the pit stop never end
FIX : Overtaking lesson could sometimes give an invalid lesson result
FIX : In lesson 81 you needed to park 5 times to complete the lesson
FIX : AI drivers left pit speed limiter on after leaving pit lane
FIX : AI drivers ignored the pit lane speed limit

Changes from W to W34 :

Multiplayer :

Up to 47 guests can connect to a host
Max cars in multiplayer race increased to 32
Kick and ban votes are held open a little longer
In demo still only 12 racing but up to 15 can connect
Can now save MPR from dedicated host (auto or manual)
Removed "unknown finisher" and its stats / insim issues
Car is no longer held at start line - false starts possible
Start lights time between red and green is changed each race
Avoided most of the "Can't x - a player is connecting" messages
Implemented a new "canreset" option while leaving hotlaps valid
Automatic spectate on driving out of bounds when reset not allowed
Global handicaps for class balancing (set by master server)
Remote car's handicap shown in F11 menu, tyres in F12 menu
Grid reordering is now done on end race as well as restart
Improved connection - less likely to fail to join a host
FIX : Pit instructions were wrong when taking over a car

Racing :

Start and pit fuel loads range from 1% to 100%
Qualifying and practice now start from the pit lane
Qualifying out lap is no longer counted as a valid lap
Single player now allows up to 20 ai cars (powerful pc)
Pit instructions and live settings work in single player
SHIFT+G gear shift selection no longer stops SP recording
New voluntary handicap system in pits (part of setup)
Added preload setting to clutch pack differentials

Display :

Small map colours can be changed : Options-Display-Interface
Small map cars more than one lap ahead are a different colour
Automatic show results - leaves small map visible when driving
Hide / show results removed from options - now available on CTRL+TAB
Timing info is show in yellow after winner crosses line or time over
Yellow finished message is no longer duplicated in central text
Connection bars are not drawn if they would obscure tyre info
Qualifying cars on out lap are drawn orange (others yellow)
Qualifying position is shown in yellow like race position
Added text on screen showing the reason for a penalty
Display option : Virtual steering gauge
Display option : Rotate small map

Interface :

Added button to spectate directly from pits
Supporting TrackIR with 6 degrees of freedom
Scroll though autocross results with PgUp / PgDn
SHIFT+P now enters garage from game setup screen
SHIFT+O now enters options when watching a SP replay
New keys SHIFT+S (spectate) and SHIFT+P (go to pits)
Button look is now added to the yaw output of TrackIR
Automatic unpause when starting or restarting a replay
Ignition key "I" is now assignable to any key or button
Removed the sound effect of a racer pitting or spectating
Pit instructions fuel load can now be adjusted in 1% steps
Escape menu improvements : can use keys (listed on screen)
Race control message now has priority over wrong way message
Wider FOV and more view pitch available (for extreme settings)
Filter added to list of games to avoid hosts which allow reset
Place objects is now switched off when entering race or qualifying
FIX : Start restriction countdown was missing from OK button in pits
FIX : Q / X / ESC / ENTER keys did not exit from pits if player in race

Skins :

Replay skins download screen new "always" and "never" options
High res premium skin download system (£1 for 2000 downloads)
System to purge skins from graphics card memory when not used
Skin download and preload during connection after loading track
Improved the "new colours" system - combined with skin selection
Skins in skins folder are not converted to dds if using full skins

InSim :

New version of InSim allows up to eight TCP or UDP connections
New buttons system allowing better interface in InSim programs
More race tracking info and many packets added (see InSim.txt)
More commands now work on AI drivers : /spec /pitlane /p_xxx
More commands work even if player joining e.g. /spec /laps
New /i command to send a message to a race control program
Race penalty can now be removed with /p_clear command
Send all players to their pits with /pit_all command
Admins can now use the IS_REO (race reorder) packet
New packet IS_MSX - allows typing of longer messages
New packet IS_MSL - output a message on local computer

System :

Removed the option not to use HVS if it is available
Better messages showing the reason for disconnection
Admins can now edit and /axsave layouts while online
Admin ban dialog now asks for a number of days to ban
Admins can now see other admins in list of connections
Added short track name to SPR, MPR and RAF file formats
Command /mprdir to specify mpr folder on dedicated host
MPR file format : result times now saved in milliseconds
Added handicap mass and restriction to hotlap file header
Increased maximum physics objects due to more cars on track
Start grid remains when track or config changes (if possible)
Command line command /player (start LFS with specified player name)
Startup skin conversion now shows progress and skin being converted
New command /wait (like /exec but LFS hangs until the program exits)
FIX : Removed the need to pass a split after receiving admin penalty
FIX : The TAB key did not work with /press /ctrl and /shift commands
FIX : Autocross checkpoints in line could cause rapid lap count bug
FIX : Path followers were reset when an object was added or removed
FIX : Path follower reset caused a glitch or an out of bounds reset
FIX : Some objects were not drawn after exiting pits while paused
FIX : Start lights were not shown in some of the training lessons
FIX : Autocross layout number of laps sometimes did not load
FIX : Message "NETWORK FATAL : NOTSOCK" when joining a host
FIX : /end command in single player did not exit correctly
FIX : Find user in S2 mode looking for racer on S1 host
FIX : Occasional crash when exiting from List of Games
FIX : Long messages could sometimes get cut short

DOWNLOAD :

PATCH (Version W must already be installed) :
www.liveforspeed.net/file_lfs.php?name=LFS_TEST_W41.exe

ZIP VERSION (If you prefer a zip file) :
www.liveforspeed.net/file_lfs.php?name=LFS_TEST_W41.zip

DEDICATED HOST (for hosting only) :
www.liveforspeed.net/file_lfs.php?name=LFS_S2_DEDI_W41.zip

Scawen
1st June 2007, 17:44
Updated correctly to W39 now.

It includes a new connection queuing system.

Lible
1st June 2007, 17:45
Hope I'm not too late - the updated commands in Estonian.

HogaMan
1st June 2007, 17:46
Dedicated Host still W38?

Scawen
1st June 2007, 17:49
Hope I'm not too late - the updated commands in Estonian.Thanks but you only posted the Autocross instructions -0 is that what you intended?

Dedicated Host still W38?That was probably my wrong upload - it should work now. Sorry about that.

Riders Motion
1st June 2007, 17:51
So, when is X coming? I tought I'd have it today when I got back from school but unfortunelately, I haven't :(

A M R
1st June 2007, 17:52
in the queuing system we trust...

jjones
1st June 2007, 17:55
So, when is X coming? I tought I'd have it today when I got back from school but unfortunelately, I haven't :(

Be gratefull for what you already have, Dont you understand that a lot of work goes into this game. And things in life dont allways come on time, it will come when its ready. :thumb:

Bean0
1st June 2007, 18:00
I do like the sounds of the queueing system.

Would this make it possible to have a Counter-Strike style 'Server full, wait for next free slot?' option when joining full servers ?

niall09
1st June 2007, 18:01
So, when is X coming? I tought I'd have it today when I got back from school but unfortunelately, I haven't :(

Scawen said earlier that it needs more testing and that it could be out tomorrow :)

GeForz
1st June 2007, 18:09
- Queue position jumped from 4 to 6 and then 5,4,3,2,1,0
- A lot of "New player could not connect" messages (translated ger->eng ^^)
- Scawen dropped!!1
- Emergency restart :(

alxf1
1st June 2007, 18:09
stress test server went down...

a lot of "BLANK : OVERFLOW - Name" messages......

three_jump
1st June 2007, 18:10
just got than "blank: overflow" message again.
I guess it was related to a massive lag and several people got d/c ed at once.

strange thing was that even the host had that message (blank: overflow - host)

mantvisrep
1st June 2007, 18:11
TO MUCH changes=bugs i cant play :(

pauliaK
1st June 2007, 18:11
Is there still a chance for X release this evening? :juggle:

EDIT: I guess not... :sorry:

alxf1
1st June 2007, 18:12
connection queue is full :)

Krane
1st June 2007, 18:15
TO MUCH changes=bugs i cant play :(

Read this post carefully: http://www.lfsforum.net/showthread.php?t=9866

Especially the part where it says: That means it's very likely that you will find bugs or problems. You install them at your own risk! Be warned that in some cases it will be hard to revert to your original LFS, you may lose settings or encounter any kind of problems that we can't predict. If you don't want to take the risk, please wait until the OFFICIAL patch comes out, or make a separate installation of LFS for testing purposes.
(Emphasis mine)

mantvisrep
1st June 2007, 18:20
ok...

HogaMan
1st June 2007, 18:25
Cant connect says username is all ready online.

mikey_G
1st June 2007, 18:26
Apparently the stress test servers died, or it was something on my end, but when I wanted a new server list after restarting lfs I got this error:
Could not find host (2)

it still loaded the list though :S

DanneDA
1st June 2007, 18:27
Is this a bug?

If more than 1 car type is allowed on the server, it will not be shown if I filter by a specific car type (ie all cars allowed on server, filter set to GTRs, server won't show up).

hammer it
1st June 2007, 18:27
Cant connect says username is all ready online.

Me too

alxf1
1st June 2007, 18:28
Apparently the stress test servers died, or it was something on my end, but when I wanted a new server list after restarting lfs I got this error:
Could not find host (2)

it still loaded the list though :S
same here

three_jump
1st June 2007, 18:30
Apparently the stress test servers died, or it was something on my end, but when I wanted a new server list after restarting lfs I got this error:
Could not find host (2)

it still loaded the list though :S

- similar here: but I didn't had to restart LFS for that message.

- before that I was (but after getting disconnected from the server) I had the message "closing 1 connect" which wouldn't disappear ( although I could enter the chat and talk there). The message only disappeared after pressing ESC.

GeForz
1st June 2007, 18:32
Is this a bug?

If more than 1 car type is allowed on the server, it will not be shown if I filter by a specific car type (ie all cars allowed on server, filter set to GTRs, server won't show up).

Not a bug.

If you click on GTR is sets MRT and the formulas to red so not showing servers which allow those cars. If you want all server on which you can drive the three gtr cars, click each of them one to set their names to blue.

mikey_G
1st June 2007, 18:37
Btw, I also saw the connection queue integer going 1 up. Did an admin join and do they have priority in the queue system, or was something weird going on?

DanneDA
1st June 2007, 18:38
Not a bug.

If you click on GTR is sets MRT and the formulas to red so not showing servers which allow those cars. If you want all server on which you can drive the three gtr cars, click each of them one to set their names to blue.



Ok, thanks. Never really thought about it until now. Haven't really raced for several weeks either.

Renku
1st June 2007, 18:43
Just got black screen in Bug test server. Queued from 20, entered server, did nothing while being on the server for 2-3 minutes, SHIFT+F4 to go to windowed mode and screen went black. I don't think there is anything in the error message, but I'll add it anyway.

Lible
1st June 2007, 18:45
Thanks but you only posted the Autocross instructions -0 is that what you intended?

Haha, silly me, the autocross one is not anything new at all :). Sorry.
Here's the right one.

three_jump
1st June 2007, 18:47
Btw, I also saw the connection queue integer going 1 up. Did an admin join and do they have priority in the queue system, or was something weird going on?

according to the man himself that comes from people who joined the server before you but where loading the track

ussbeethoven
1st June 2007, 18:50
I lost connection to the stress server two times because of LFS preloading skins while joining the server ("waiting for first messages", that means after preloading task). Shortly after disconnect a single "skin loaded:" was shown.

Scawen
1st June 2007, 19:00
Haha, silly me, the autocross one is not anything new at all :). Sorry.
Here's the right one.Thanks, got it.

J.B.
1st June 2007, 19:14
Just got another shift-f4 black screen of death. This time without using ATT.

anbiddulph
1st June 2007, 19:28
connection queues:
2,4,3,2,3,2,1
1,2,3,2,1

audimasta
1st June 2007, 19:33
connection queues:
2,4,3,2,3,2,1
1,2,3,2,1

Had the same problem..5-6-5-7-6-7 etc. It went ok in the end though :shy:

troy
1st June 2007, 19:34
i guess thats admin slots getting taken, could be at least :)

CharlieP
1st June 2007, 19:39
It all seems to be working fine here..... apart from a lot of lag, but I guess you will get that with this many connections :D

I wonder when we'll get the 'X' files ;)

SladiVadi
1st June 2007, 19:40
I lost connection to the stress two times because of LFS preloading skins while joining the server ("waiting for first messages", that means after preloading task). Shortly after disconnect a single "skin loaded:" was shown.

I think I got the same error. While loading skins it said "lost connection to host" and something else I think. I reconnected using the list and it loaded one skin I think and I could join the server (bug test).

I downloaded stuff via FTP while doing this.

The General Lee
1st June 2007, 20:12
I missed the mass test. Can anyone update me, is the problem fixed or is it prosponed again. - Not to worry if it is, I know all the Devs work their butts off.:thumb:

GeForz
1st June 2007, 20:12
What I observed while on test server 2 was that the vote system needs some rework...

Because every time someone joins the vote is canceled and it's hart to vote for anything if there are lots of ppl joining :/

SpikeyMarcoD
1st June 2007, 20:19
What I observed while on test server 2 was that the vote system needs some rework...

Because every time someone joins the vote is canceled and it's hart to vote for anything if there are lots of ppl joining :/


This is annoying but has always been the case though

imthebestracerthereis
1st June 2007, 20:20
Can someone tell me what the "new connection queuing system" is exactly? :scratchch

spiderbait90
1st June 2007, 20:23
lol, its pretty self explanitery. Its a Queue, when you are connecting, if someone else is already connecting. So a line of people waiting to get in. Im sure someone else will have a more complex post including the meanings of the words "connection" "queuing" and "system".

beefyman666
1st June 2007, 20:23
You queue to connect if too many people are trying to connect at once.

E: beaten.

Krane
1st June 2007, 20:33
You queue to connect if too many people are trying to connect at once.

E: beaten.

IMO it should* also put you on queue if the host is full... The Bug Test Server seemed not to do that, got "server full" :shrug:


*And that's how from the changelog I understood how the system would be...

GeForz
1st June 2007, 20:35
This is annoying but has always been the case though
But it's even more annoying with twice as much people on the server ;)

beefyman666
1st June 2007, 20:39
IMO it should* also put you on queue if the host is full... The Bug Test Server seemed not to do that, got "server full" :shrug:


*And that's how from the changelog I understood how the system would be...

Would be a bit more logical. But you could be waiting hours if you desperately want to get on that oh so busy server.

SpikeyMarcoD
1st June 2007, 20:40
But it's even more annoying with twice as much people on the server ;)

if server is full its not a problem. We had more joiners and leavers now, but you are right the more people on server the more have to agree with you. Dont get why its needed to restart the vote.

ussbeethoven
1st June 2007, 20:44
I think I got the same error. While loading skins it said "lost connection to host" and something else I think. I reconnected using the list and it loaded one skin I think and I could join the server (bug test).

I downloaded stuff via FTP while doing this.
There was no background download in my case.

GeForz
1st June 2007, 20:59
if server is full its not a problem. We had more joiners and leavers now, but you are right the more people on server the more have to agree with you. Dont get why its needed to restart the vote.

well the situation i war referring to was the following:
someone (admin?) wanted to end the race and the countdown race ends in 3...2...1 cam up but it was ~4 times interrupted because a new player joined ^^

Mike85
1st June 2007, 21:12
I think I found a minor bug not related to servers or anything.

When you drive, if you hold the throttle and press the "windows" key simultaneously, then when you return, the throttle is still pressed. You have to press the throttle again to depress it. Im using keyboard.

Basically, when you exit with the "windows" key, it still keeps the button pressed.

Also, it would be good to make a better spectate mode. Like an ability to go freely around the track in mouse view. No-clip. But thats another topic:)

Basically look at rFactor and Counter-Strike Source to see what is missing in LFS:)

RudolfR
1st June 2007, 21:14
Im just wondering , will the WR's be deleted , example .. FZR is more slower etc.

kiss me
1st June 2007, 21:16
I think I found a minor bug not related to servers or anything.

When you drive, if you hold the throttle and press the "windows" key simultaneously, then when you return, the throttle is still pressed. You have to press the throttle again to depress it. Im using keyboard.

Basically, when you exit with the "windows" key, it still keeps the button pressed.


i know, this is olso with the steering wheel :shrug:
meh, i dont mind, i never go windowed, unless its for insim/outsim :D

Mike85
1st June 2007, 21:18
Yes, but its in case if you accidentally press the key. Im sure it can be fixed, but its not the main thing to fix in W39.

510N3D
1st June 2007, 21:23
having big fps problems (like <10 fps) while using shift+U mode, maybe anyone else has the same problem? Been tested on 3 servers now.

dmwright
1st June 2007, 21:27
Hi,

Ive just started getting problems with my computer trying to connect to a 47 connection Host. Yesterday i was doing the same thing but wasnt getting any problems im getting now. What seems to happen is i get between the guest info and the screen showing people (there is a black screen) i get stuck there and my computer freezes. I havent expirenced this problem along time ago when i was trying to connect to a full server with a layout. I did a virus/Spyware scan and Disk Defrag aswell and a disk clean up. Is it my pc again or is there something wrong where people are expriencing these problems?

Thanks,

Matt

RudolfR
1st June 2007, 21:29
Yes , when Shift+U , FPS is dropping down alot

Maybe there is possible something to not freeze my lfs ? my friends have same problem , thankyou.

DEVIL 007
1st June 2007, 21:31
Hi Scawen,

I have noticed strange behaviour of the servers after you raise the number of players(connections).

Just saw it on W39 test server full of people as well.When I see message "new guest connecting" after a short time all lag bars getting really high and it goes down after the player get connected.Sometimes is same happening when player left pits.

I dont know how this can affect other players,for example by dropping someone, on the server
but I guess something might not be correct.I really dont know if this can have some neggative effect but I dont rememer I saw this behaviour before.

If this doesnt cause any issue,then sorry to bother you with that.

I can also confirm the issue with SHIFT+U.FPS now drop sorry for that word but like hell.I have like 80-160 FPS and with SHIFT+U it drops even to 17FPS or even less.I am pretty sure it wasnt like that before and its not my computer.(Just qucik spec A64 3200+,2x512MB ram,7900GT 256MB ram).

EDIT:attached picture.Just 1 car on screen and 22FPS?Also it dropped suddenly few times to like 6 FPS:really: :really: There is really something wrong with SHIFT+U now.With TV cameras there is non drop from the usual behaviour.

SpikeyMarcoD
1st June 2007, 21:36
Think behaviour is not new just more noticable on a 47 server that is full.
However how many of them will be that full and with that many joiners and leavers.

It is a good test though and definetly something to improve. Dont hope its a patch stopper though.

EDIT: confirming the shift U drop in FPS. Dont know if its new since i rarely use it.

FL!P
1st June 2007, 21:44
I was on the test server with about 35 other people, and it was quite a pain between each race to get enough of us to vote to restart in the same "window". I think votes to restart should remain valid at least twice as long.

Also is it indispensable to reset all the votes each time someone connects? Because it really doesn't help in these situations.

ussbeethoven
1st June 2007, 21:50
My FPS also getting very low when using shift + u, but that's maybe because of small VRAM (128MB) and high-res texture mods and AA/AF.

Yisc[NL]
1st June 2007, 21:50
I was on the test server with about 35 other people, and it was quite a pain between each race to get enough of us to vote to restart in the same "window". I think votes to restart should remain valid at least twice as long.

Also is it indispensable to reset all the votes each time someone connects? Because it really doesn't help in these situations.

+1 on your suggestions. It's already a hell of a job to get a race restarted sometimes. With more people on a server and a constant connect/disconnect, restarting is almost impossible.

Lotesdelere
1st June 2007, 21:57
I was on the test server with about 35 other people, and it was quite a pain between each race to get enough of us to vote to restart in the same "window". I think votes to restart should remain valid at least twice as long.
+1

DEVIL 007
1st June 2007, 21:57
Got message when connecting to Bug Test server:

"Did not receive message from all players
Lost connection to host "

Also when I am on the host and I see message that new skins get downloaded,then there is small yellow text which just blink quickly(i dont see what is says as its showed like few ms) and at that time there is small freeze like 1/2 sec maybe less.Can be very bad at race(btw my connection is 5Mbit).

Yaamboo
1st June 2007, 22:40
There is really some wrong with SHIFT+U now.With TV cameras there is non drop from the usual behaviour.

I can confirm that as on the test server I tried to use it, but I couldn't - the fps dropped to 0-2.

PMD9409
1st June 2007, 23:25
I can confirm that as on the test server I tried to use it, but I couldn't - the fps dropped to 0-2.

Same here, I tried it last night when all the x/ufr's were on the test server. I went to shift+u for a nice camera angle but the fps was so low I couldnt really get where I wanted to.

russraine
1st June 2007, 23:58
Couple of similar issues.

When logging onto a server with hires skins enables but you have no credit and there is a lot of cars on track and new skins to download, lots of messages about no credit, this caused big lag for me and others on server. Now obviously people with no credit shouldn't have hi res skins enabled, but, say they only have enough credit for two skins and don't realise when they log on, they get the first two skins but then it gets laggy while it's checking if you can afford each skin or not.

Also it's possible that someone doesn't know they have it enabled until they log on, causes uneeded lag.

My ideal solution would be that if you can't afford the first skin it doesn't keep checking if you can with every skin, but to not check for any more until the next time you run LFS.

Now after switching hi res skins off I get this.

Second problem was that the general time it takes to check for skins seems to have increased, the usual pause when someone leaves the pits and the game checks to see if you have their skin or not is longer than before and in my opinon causes problem.

FL!P
2nd June 2007, 00:38
I got the black screen thing triggered by Shift+F4 a couple of times in single player mode (in W39). Unfortunately it seems to occur randomly and I can't reproduce it at will. Is there some way to get info for Scawen, in this case? Had it happen in Mac OS X I would have run Sample against LFS, but in Windows I don't know what to do.

faster111
2nd June 2007, 00:43
I got the black screen thing triggered by Shift+F4 a couple of times in single player mode (in W39). Unfortunately it seems to occur randomly and I can't reproduce it at will. Is there some way to get info for Scawen, in this case? Had it happen in Mac OS X I would have run Sample against LFS, but in Windows I don't know what to do. i will try.


Update i pressed the shift F4 30 times and no black screen.

ninja469
2nd June 2007, 01:21
I got the black screen thing triggered by Shift+F4 a couple of times in single player mode (in W39). Unfortunately it seems to occur randomly and I can't reproduce it at will. Is there some way to get info for Scawen, in this case? Had it happen in Mac OS X I would have run Sample against LFS, but in Windows I don't know what to do.

I only got about 1 second of black screen when changing from full screen to windowed in about 50 attemps.
What version of windows are you useing and are your graphics drivers upto date. I run xp pro without any problems.

FL!P
2nd June 2007, 01:36
What version of windows are you useing and are your graphics drivers upto date. I run xp pro without any problems.

XP Pro SP2, ATI Radeon X1900 XT, drivers up-to-date. I tried to reproduce it again, but I couldn't.

J.B.
2nd June 2007, 01:45
I've already had it twice but I can't reproduce it by hitting shift-f4 50 times in a row.

Radeon x1950 Pro XP SP2 7.5 and 7.4 drivers.

DasBoeseC
2nd June 2007, 02:04
I also got the black screen in W39 tonight.

Can't reproduce it :shrug:

Seems to me it's not only got to do with Shift+F4 but also with additional applications that are running at the same time, as it only happened to me when I had something like Firefox or Media Player running parallel to LFS.
Some kind of gfx initialization that fails or something, as I see the black screen often when I Shift-F4, but usually I only see it for half a second max.

CU, Sebastian

Misko
2nd June 2007, 04:33
Also when I am on the host and I see message that new skins get downloaded,then there is small yellow text which just blink quickly(i dont see what is says as its showed like few ms) and at that time there is small freeze like 1/2 sec maybe less.Can be very bad at race(btw my connection is 5Mbit).
I think thats "Saving Skin" message, converting and saving as dds to disk.


Just another thing which I didn't see mentioned so far: in MPRs messages like disconnects and timeouts are no longer recorded, is that intended or a bug? MPR message block is 0 in cfg, and pitting messages are still there. I'm not sure in which test patch it started (probably W9) but it was there in W, and no longer there in W25 and later (those replays I just checked). Its maybe not a big thing, just it would make reviewing league races easier like before.

DeKo
2nd June 2007, 08:44
XP Pro SP2, ATI Radeon X1900 XT, drivers up-to-date. I tried to reproduce it again, but I couldn't.

I've already had it twice but I can't reproduce it by hitting shift-f4 50 times in a row.

Radeon x1950 Pro XP SP2 7.5 and 7.4 drivers.

Yeah, ive got an x1900XT. really seems to be a ATI thing, dont think its much to do with LFS.

Shotglass
2nd June 2007, 09:00
its not just an ati thing
i have a 78gtx and sometime during the u test cycle it started to happen (never had it before or if i did it was very very rare like once every 6 months) very often the first time i ran lfs it went black with shift f4 (iirc closing lfs and starting it again completely solved it for that windows bootup)
now with w39 it appears to be gone or at least hasnt happened yet

Scawen
2nd June 2007, 09:13
Does it make any difference if you started LFS in full screen or windowed?

In one old version the black screen on SHIFT+F4 was reproducable if LFS originally started in full screen or windowed (can't remember which).

DeKo
2nd June 2007, 09:29
Does it make any difference if you started LFS in full screen or windowed?

In one old version the black screen on SHIFT+F4 was reproducable if LFS originally started in full screen or windowed (can't remember which).

I always start LFS in full-screen so it probably would have been that.

Ill try starting LFS in windowed for a while and see if it happens again though, might aswell.

niall09
2nd June 2007, 09:31
i know, its a bit late to be saying, but i sometimes get that blackscreen occasionally in W

AndroidXP
2nd June 2007, 09:37
Scawen!
I think I can reproduce the black screen bug - it has to do with losing focus during window mode change.

The steps are relatively simple
Start LFS, windowed or not is irrelevant
Just stay in the main menu, it's not necessary to have anything happen in LFS
(Maybe set up the LFS fullscreen resolution to the desktop one, so Shift+F4 works faster)
Press and hold Shift+F4 - the LFS window should start switching between full and windowed mode quite fast. You can keep this up infinitely, that's not the problem.
Now, click on the half visible task bar or somewhere outside so LFS loses focus. At first I thought it happened by launching any application, but it's actually the lost focus that makes LFS screw up.
Continue holding Shift+F4. It might happen that LFS still shows as full screen but doesn't actually have focus, so you have to Alt+Tab back in and start pressing Shift+F4 again. I can quite reliably get a black screen at that point.

It seems the problem occurs if LFS loses focus during screenmode change, which would explain why I got my first black screen shortly after joining a server - I guess it was going back to full screen (from the multiplayer windowed mode) shortly after I clicked outside to look at the forums.

As a note, I also managed a few times to get LFS into a state where it wouldn't close by itself anymore. Usually Alt+F4 works, or clicking the X of the window, but sometimes it just froze and I had to kill it with the task manager.

Shotglass
2nd June 2007, 09:46
I can quite reliably get a black screen at that point.

i cant reproduce that on my machine
78gtx
fw 91.47

DeKo
2nd June 2007, 09:47
android it works, just tried to reproduce it and i can. That could explain it.

Jakg
2nd June 2007, 09:49
I think I found a minor bug not related to servers or anything.

When you drive, if you hold the throttle and press the "windows" key simultaneously, then when you return, the throttle is still pressed. You have to press the throttle again to depress it. Im using keyboard.

Basically, when you exit with the "windows" key, it still keeps the button pressed.

Also, it would be good to make a better spectate mode. Like an ability to go freely around the track in mouse view. No-clip. But thats another topic:)

Basically look at rFactor and Counter-Strike Source to see what is missing in LFS:)iirc thats something to do with hooking into windows ans disabling the Win key temporarily is it not? imo it's not that importantIm just wondering , will the WR's be deleted , example .. FZR is more slower etc.No - try offline and all the ballast goes and the cars get faster :tilt:

AndroidXP
2nd June 2007, 10:00
i cant reproduce that on my machine
78gtx
fw 91.47
After LFS lost focus, did you make sure to start pressing Shift+F4 again? The lost focus can interrupt the keyboard input and you have to press it again.

You don't even have to be fast. In one case LFS is fullscreen and still has focus after clicking outside, but I see "good race" pop up at LFS now, as the shift key press was lost. At that point I can take my time to start again and switch to windowed mode, and as soon as I switch back to fullscreen it goes black. Every time.

Actually it seems the black screen only comes up when switching from windowed to full mode. When clicking outside it usually leaves LFS in fullscreen mode (which is logical, the click "outside" only counts when you're currently in windowed mode, and the most likely thing that will happen then is going to full as you're still pressing Shift+F4). Then it could be that LFS has focus or not - if not you first have to Alt+Tab back in, but it doesn't influence the outcome. As soon as I start going to windowed and back to full it's black.

Just for the record, I have a 6600GT with 92.91 drivers.

Shotglass
2nd June 2007, 10:05
After LFS lost focus, did you make sure to start pressing Shift+F4 again? The lost focus can interrupt the keyboard input and you have to press it again.

You don't even have to be fast. In one case LFS is fullscreen and still has focus after clicking outside, but I see "good race" pop up at LFS now, as the shift key press was lost. At that point I can take my time and switch to windowed mode, and as soon as I switch back to fullscreen it goes black. Every time.

Just for the record, I have a 6600GT with 92.91 drivers.

as long as its not in any way time critical yes
i can resume keeping shift-f4 pressed after losing focus for as long as i like and make it lose focus during that as often as i want and it never goes black

CharlieP
2nd June 2007, 10:13
I was doing nothing, so I thought I'd try the black screen routine above.....

holding shift-F4 and as it was super fast switching I managed to click something else.....

Black screen...... both in FS mode and Windowed !!!

The menu music is still playing, but I cannot get anything on the screen now, and I can't seem to click anything either!

alt-F4 stops the music...... screen still there...

Can't close on the 'X' or from taskbar.

Closed it from the task manager.

I've never had any problems with any patch regarding a blackscreen, so this is obviously a very rare occurrence unless you do this routine.

For info - GF7900GTO driver 93.71

Scawen
2nd June 2007, 10:35
Scawen!
I think I can reproduce the black screen bug - it has to do with losing focus during window mode change.

The steps are relatively simpleThanks for that - making progress now! I have two questions :

1) Does this explain why this might happen when LFS auto windows? Is it because you are clicking on another program while connecting to a server? Sorry if that's a dumb question but my slightly tired mind is focussed on network connection / disconnection issues and that's very complicated.

2) If you can work out an even more simple way to reproduce it that would be great (with minimum number of clicks and keypresses). I mean, a way to guarantee it happens, that way I can for sure catch it in the debugger. If it's "hit and miss" then I can't necessarily catch it.

niall09
2nd June 2007, 10:46
can i ask you a question scawen? Why does LFS go windowed when you search for a list of games? is there any reason behind it?

11SuLLy11
2nd June 2007, 10:46
can i ask you a question scawen? Why does LFS go windowed when you search for a list of games? is there any reason behind it?
Click connecting to windows "NO" it's in the same box as search games:thumb:

Sven Menkhoff
2nd June 2007, 10:50
Same here, that "Black-Screen" Problem i had twice. 1 Time long time ago, and 1 time at W39. I can´t reproduce it, but at W39 i had Mediaplayer running. That´s all i can say about it.

I also never use the Window-mode at joining a server. It always sets to window after i install a LFS-Patch. Then i turn it off again. :)

SpikeyMarcoD
2nd June 2007, 10:51
can i ask you a question scawen? Why does LFS go windowed when you search for a list of games? is there any reason behind it?


It is to make it more noticeable that your firewall wants input is my guess. To prevent comments like i get no servers :) But its a bit missplaced as in my case that little norton screen hides after the LFS windows anyway.

niall09
2nd June 2007, 10:52
i know that, but i was just wondering why :)

AndroidXP
2nd June 2007, 10:53
can i ask you a question scawen? Why does LFS go windowed when you search for a list of games? is there any reason behind it?
It goes to windowed mode because often there are firewalls that will block LFS at the exact point you display the list of games (as you do the first query to the master server then). If that happens in full screen mode, many firewalls simply freeze LFS, without the chance to even Alt+Tab out, forcing you to do a hard reset (or do some task manager trickery). So it is much safer to go to windowed mode first and then try to access the net, as you can easily allow LFS' connection in the firewall popup window then.

niall09
2nd June 2007, 10:55
ahh, thank you Android :)

Jakg
2nd June 2007, 10:58
can i ask you a question scawen? Why does LFS go windowed when you search for a list of games? is there any reason behind it?because a firewall may pop up and say "z0mg! LFS.exe is trying to connect to "t3h intertuubes!" - Do you want it to? Yes/No" and if LFS was full screen you wouldn't see it and would just think "Why isn't this motherfizzling program working!"

EDIT - Last time i waste time telling my Dad what kind of drugs i want, just bring me Morphine god-damnit and then i can beat Android!

MoonForce
2nd June 2007, 11:06
because a firewall may pop up and say "z0mg! LFS.exe is trying to connect to "t3h intertuubes!" - Do you want it to? Yes/No" and if LFS was full screen you wouldn't see it and would just think "Why isn't this motherfizzling program working!"

EDIT - Last time i waste time telling my Dad what kind of drugs i want, just bring me Morphine god-damnit and then i can beat Android!

no one can beat andriod, he is already fused with the forums lol, the matrix got him :D

AndroidXP
2nd June 2007, 11:19
@Scawen: I'm working on simplifying the process, and while I can reduce the steps, it's certainly *harder* to reproduce it without the screen flicker, but it makes it more clear what's triggering it.

The general gist is, that it happens when going from window to full screen, but you have to click outside LFS at the exact moment you hit Shift+F4. I think it's easiest to reproduce when LFS and desktop resolution are the same, so it doesn't take so long to change screen mode for trying again.

Basically

LFS in windowed mode, focused
Hit shift, ready your finger over F4
Get ready to click with your mouse on the taskbar
Hit F4 and immediately click the taskbar "after" that
By immediately I mean the click should be at the same time as shift+F4 as far as a human would be able to discern, but for the program it should first get the screen mode change command and in the next possible frame the focus change.

Possible results:

Nothing happend.
You clicked too fast and the Shift+F4 didn't reach LFS anymore.
.
LFS goes fullscreen and then minimizes.
You clicked too slow, LFS was already over the critical phase and handled the focus change properly (or Windows did?).
.
LFS changes to fullscreen, but it still works.
You clicked too slow, LFS was already maximised when you tried clicking the taskbar, so it didn't lose focus.
.
LFS takes a split second longer than usual to change to full screen mode.
Now it is in the correct state for that bug to happen. You probably have to click onto the now full screen LFS again so it gets the focus back. Switch back to windowed mode, everything still ok. Now get your debugger ready and switch back to full screen - which will remain black.
.
I hope from this point you'll be able to backtrack what happened during the first screen change that initiated the bug.

That's pretty much as simple as I could make it, hope it helps you :)

Edit:
It is easier to reproduce if you go to Options > Misc, enable "Limit frame rate in game" and set it to "10 fps". This should give you a longer time window in which you can click the task bar, compared to the usual 40 fps menu limitation. VSync has no influence on the outcome.

felplacerad
2nd June 2007, 11:27
Using androids guide I was able to reproduce the bug within 10 tries. Well done! Good luck Scawen.

CharlieP
2nd June 2007, 11:29
Reproduced with similar steps....

Make sure you have a few other programs running ..... winamp, explorer window, e-mail prog and firefox here!

run lfs - go windowed..... make it 1/2 screen so you have room

LFS focused - press shift-F4 and at same time click on one of the background programs.... explorer for me.....

works every time, as long as the timing is right :(

Edit: I can make it happen, 1 in 3 tries .... now..... practise makes perfect :) Maybe we could have a black screen ladder ? It would be nice to be the best at something :D

Edit,Edit: Not sure if anyone else tested...... happens in 'W' also!

GP4Flo
2nd June 2007, 11:40
I cannot reproduce it here. If I remembe correctly, I did never get a black screen while switching window/full screen.

What happens here is, that I can make LFS go fullscreen without having the focus. So LFS is on top, but I cannot click any buttons. If I click, I can make other programs (or desktop icons) popup over the LFS window, just for the time I click.

Maybe it depends on the graphic driver, if you get a black screen or only a LFS without focus as in my case. So I guess the problem is, that LFS can go full screen without actually having the focus. Is there a way, you can make it sure, that LFS always has the focus if being fullscreen?

Edit: ATI X1600 mobility with Mac drivers for Win XP (Bootcamp)

felplacerad
2nd June 2007, 11:43
Florian, I managed to get in that state as well (see above). Keep trying.

Renku
2nd June 2007, 11:43
The general gist is, that it happens when going from window to full screen, but you have to click outside LFS at the exact moment you hit Shift+F4.99,99% of the time it happens to me when I go from full screen to windowed mode; but then again, I can't reproduce it.

AndroidXP
2nd June 2007, 11:49
@Flo: What you described happens for me too - well, almost. LFS is fullscreen without having focus, but I can get it back by clicking into it, and that is pretty much the part where I will a get black screen as soon as I go > window > full again after that.

CharlieP
2nd June 2007, 11:49
I cannot reproduce it here. If I remembe correctly, I did never get a black screen while switching window/full screen.(Bootcamp)

You are not trying hard enough :D

I can reproduce it on two different machines with different cards and drivers ;)

and, for me, once it happens you cannot do anything apart from close LFS.... sometimes only with task manager.

GP4Flo
2nd June 2007, 11:51
Yes, but I've tried it several times now. Clicking LFS to bring the focus back, window, full-screen. No black screen, it just doesn't happen here. What graphic card / drivers are you using? Does it depend on the screen res / color / refresh rate settings of LFS / windows? I'm using the same (32bit, 1440 x 900, 60 Hz (built-in lcd)) for both.

Madman_CZ
2nd June 2007, 11:58
I cannot reproduce the bug here too, I've been clicking away for the last 35 minutes and it just doesn't happen.

Desktop and LFS resolution set at 1400x1050 85hz

It seems to minimize and maximize flawlessly. Saying that tough, few days ago with patch w34 i believe I did get a black screen, first time in ages but nothing since then.

mad

AndroidXP
2nd June 2007, 12:00
6600GT (not OC), 92.91 ForceWare, 1280x960x32bit @ 85Hz refresh rate. VSync off (also reproduceable when on). Z-Buffer depth 24 bit.

NV GFX options:
AA: 4x (also reproduceable when off)
AF: 8x (same)
Image settings: High quality
VSync: App controlled
Force mipmaps: none
Conformant texture clamp: On
Extension limit: Off
Trilinear opt.: Off
Anisotropic mip filter opt.: Off
Anisotropic sample opt.: Off
Transparency AA: Multisampling
Triple buffering: Off
Negative LOD bias: Clamp

Madman_CZ
2nd June 2007, 12:09
My radeon 9800pro settings:

AA: 4x
AF: 8x
Anisotropic filtering: Quality
Texture preferance: High Quality
Mipmap Detail Level: High quality
VSync: App controlled
dont have the rest in the options (its an old card)

I did forget to mention that I am using the Omega drivers which are quite a bit different from the official ati drivers...

mad

DeKo
2nd June 2007, 12:09
Ive got a Radeon X1900XT 512MB overclocked to XTX speeds, running 6x AA and 16x AF, although its reproducable with it off aswell. Running catalyst 7.4. If i get my timing right i can reproduce the black screen every time.

Shizzle
2nd June 2007, 12:14
There is still 'UniqueId' field in CompCar and NodeLap structs.
Is this a 'feature' or just forgotten? I figured it means PLID, but maybe it should be changed for clarity.

Struct field name changes are annoying for a programmer, but i guess its all for the better in the future. :thumb:

Yaamboo
2nd June 2007, 12:19
1) Does this explain why this might happen when LFS auto windows?

The firewall window might be "stealing" focus from LFS at the same time, so that would cause it.

AndroidXP
2nd June 2007, 12:32
I just updated to 160.02 ForceWare drivers, and it's still reproduceable for me.

MoonForce
2nd June 2007, 13:49
i also cannot reproduce it :(

1440x900 32bit

joen
2nd June 2007, 13:52
Ive tried several times, but so far I haven't been able to reproduce it :shrug:
1440*900, 32 bit, latest forceware, 4*AA, 16*AF

wien
2nd June 2007, 14:02
Took a few tries, but I was able to reproduce using Android's method too (Turning on the FPS limiter helped!). I've never seen it happen on it's own though.

- Windows XP SP2
- GeForce 7600GT AGP @ 1920x1200x32 - Forceware 93.71
(I can give more detailed specs if it's needed)

faster111
2nd June 2007, 14:05
anyone got the crash code?

wien
2nd June 2007, 14:07
anyone got the crash code?It doesn't crash, so there's no address to report. Hence the struggle to find a reproduction method.

faster111
2nd June 2007, 14:13
It doesn't crash, so there's no address to report. Hence the struggle to find a reproduction method.

ok well i just tried and its dam hard to get it to do it.

KMSpeed
2nd June 2007, 14:41
I can't reproduce it either, but then again I never had this "black screen" problem anyway :shrug:

hackerx
2nd June 2007, 14:48
Very likely this black screen problem is specific to some video cards/drivers. Never had it myself.

wien
2nd June 2007, 14:51
Okay, I've been experimenting a little in Spy++ and I was able to record a log of a black screen occuring using Android's method. (Attached, message 01084 and onwards) LFS was in windowed mode and I held down SHIFT before pressing F4 and clicking the task bar at the same time to send focus away from LFS. LFS goes to a black full screen, but is still out of focus (I can see the taskbar flicker through the window).

I'll look a bit closer to see if I can find out what messages exactly are causing the problem and see if I can write a program to make it happen Every Time™.

Ramses
2nd June 2007, 15:04
EDIT: In my case LFS doesn't go to full screen but stays windowed! But black nevertheless.

Worked for me the first time I tried

Never got this before but no firewall here so never have to go windowed when connecting to masterserver.

I just started LFS and did the test Android provided straight from the main menu screen (so I wasnt in race or anything) The area of the desktop used by LFS in windowed mode turns solid black. I can shut it down by pressing Shift-F4 again. Then the window returns and I can click the "x".

AMD A64 3200 2.4 Gig winchester
ASUS Nf4 (A8N32-SLI)
AA=8x
AF=16x
SCreensync off
No limit framerate
1xASUS Gf 7950GT (EN7950GT) Driver 93.71 Forceware
Crucial 3200 XMS (Dualchannel)
Windows XP SP2 (No further updates installed)

FL!P
2nd June 2007, 15:30
update: never mind, it was already answered.

Madman_CZ
2nd June 2007, 15:47
(I can see the taskbar flicker through the window).


This flicker I had as well, I could see the task bar and my winamp flashing through the screen while sitting on the lfs main menu. The screen wasn't black though...

GruntOfAction
2nd June 2007, 15:52
Heh I was right.

It will get to W40 before Patch X..or W40 will be patch X.....hmmmm

NjHarwood
2nd June 2007, 16:03
grunt, it better to have a fully working full patch than something that only works for a few people and the rest struggle

faster111
2nd June 2007, 16:05
grunt, it better to have a fully working full patch than something that only works for a few people and the rest struggle lest we know its a
Bug what is Reproducible.

AndroidXP
2nd June 2007, 16:08
This flicker I had as well, I could see the task bar and my winamp flashing through the screen while sitting on the lfs main menu. The screen wasn't black though...
Yes, but at that point, did you try clicking inside LFS to give it focus and switch screen mode *again* (several times)?

Gil07
2nd June 2007, 16:25
The only way i can get focus back in that situation is alt-tab in and out. Can't clik anywhere inside the LFS window...

wien
2nd June 2007, 16:34
Hmm, okay. I've experimented a lot now and I've been able to write a program that reproduces the black screen consistently here. I may just be abusing the API to do something Windows normally wouldn't do, but it may help you debug it. :shrug:

Anyway, the program sends a SHIFT+F4 keydown/keyup pair to the LFS window, but the crucial bit here is that I call SetForegroundWindow on the window in between the keydown/keyup pairs. If I remove that, or move it to after the key messages, LFS behaves normally. The interesting bit though is that it only happens the second time you go full screen after the program has been run. First time everything is fine, but the second time it goes black... every time.

So, to reproduce:
- Start LFS in windowed mode.
- Run the program and LFS will go full screen.
- Press SHIFT+F4 manually twice to return to windowed and back to fullscreen.
- Black screen hopefully. :)

geeman1
2nd June 2007, 16:38
Heh I was right.
It will get to W40 before Patch X..or W40 will be patch X.....hmmmmMy guess is that Scawen is mainly trying to fix the server going bonkers while lots of people try to get in at once bug. It's rather serious issue because it locks up the whole server and the server needs to be restarted to fix it. When it is sorted X can be released.
The black screen thing everyone is talking now isn't as serious because it's only a nuisance for the individual player so if that can't be fixed easily it will probably be left for later patches.
Disclaimer: That above is only a speculation.

AndroidXP
2nd June 2007, 16:51
Hmm, okay. I've experimented a lot now and I've been able to write a program that reproduces the black screen consistently here.
Yes, it works perfectly, and you only need to run it once. The first run already starts the bug, you just need to change screen mode twice after that yourself. Exactly like I described, if you think about it ;)

faster111
2nd June 2007, 16:57
Yes, it works perfectly, and you only need to run it once. The first run already starts the bug, you just need to change screen mode twice after that yourself. Exactly like I described, if you think about it ;) So now all they have to do is run that then it would be fixed.

Scawen
2nd June 2007, 17:01
Hmm, okay. I've experimented a lot now and I've been able to write a program that reproduces the black screen consistently here. I may just be abusing the API to do something Windows normally wouldn't do, but it may help you debug it. :shrug:

Anyway, the program sends a SHIFT+F4 keydown/keyup pair to the LFS window, but the crucial bit here is that I call SetForegroundWindow on the window in between the keydown/keyup pairs. If I remove that, or move it to after the key messages, LFS behaves normally. The interesting bit though is that it only happens the second time the program is run. First time everything is fine, but the second time it goes black... every time.

So, to reproduce:
- Start LFS in windowed mode.
- Run the program and LFS will go full screen.
- Press SHIFT+F4 manually to return to windowed.
- Run the program again.
- Black screen hopefully. :)Thanks! :) Now we have a way to reproduce it every time.

You program didn't run on my windows for some reason, so I've compiled again with your source code and attached it here.

I'll do some remote debugging and try to catch this later. Remote debugging, for anyone who doesn't know, means : running the program on a different computer from the debugger, and that is needed when you are debugging things going full screen, because when it goes full screen you can't see the debugger. :D


My guess is that Scawen is mainly trying to fix the server going bonkers while lots of people try to get in at once bug. It's rather serious issue because it locks up the whole server and the server needs to be restarted to fix it. When it is sorted X can be released.
The black screen thing everyone is talking now isn't as serious because it's only a nuisance for the individual player so if that can't be fixed easily it will probably be left for later patches.
Disclaimer: That above is only a speculation.Yes, when too many people join and leave all at once, it can go wrong. I've already improved some things and will probably test this evening. Though I'm keen to make in-game votes and the game setup screen "ready" flags persistent because it's so hard to get in for a race or restart. So... patch X is already delayed and it's better to fix these known serious issues or it really isn't that good for 32 players.


wien's program, recompiled :

Arfman
2nd June 2007, 17:02
Thanks for the update, Scawen. Awesome job, and you're right: it's better to release bugfree than to rush things.

GeForz
2nd June 2007, 17:03
Hmm, okay. I've experimented a lot now and I've been able to write a program that reproduces the black screen consistently here.

I tried it several times and did not succeed in getting a black screen on my system. When switching from full screen to windowed mode the window is black for about 1 second but then everything is fine again.

ATI, same res on windows/lfs, AA AF on

Rocabiliz
2nd June 2007, 17:17
I tried it several times and did not succeed in getting a black screen on my system. When switching from full screen to windowed mode the window is black for about 1 second but then everything is fine again.

ATI, same res on windows/lfs, AA AF on
don't worry.. it happens to me everytime since i got the game (patch U) :)

GP4Flo
2nd June 2007, 18:18
I tried it several times and did not succeed in getting a black screen
Same here, not a single black screen yet. Neither with the provoke program nor with manual switching.

Shotglass
2nd June 2007, 18:23
same here i still cannot provoke a black screen of death

jayhawk
2nd June 2007, 18:36
Thanks!
Yes, when too many people join and leave all at once, it can go wrong. I've already improved some things and will probably test this evening. Though I'm keen to make in-game votes and the game setup screen "ready" flags persistent because it's so hard to get in for a race or restart. So... patch X is already delayed and it's better to fix these known serious issues or it really isn't that good for 32 players.


My question is: when will we see, over the next X amount of time, such a large amount of people joining all at once? I can only see this happening if S2 final comes out, or if you release the long anticipated RBR and Westhill Club circuit. ;) And then the fervor will die down in a matter of days, if not shorter.

Obviously, it is good to plan for the future, but are you sacrificing time and energy on a bug that for the most part will be a rare occurance? Or am I missing the point? I guess I am speaking for the common man who does not understand the reason for such extensive coding.

Just throwing my opinion out. :) Still...for me, the wait is worth it.

Madman_CZ
2nd June 2007, 18:39
Yes, but at that point, did you try clicking inside LFS to give it focus and switch screen mode *again* (several times)?

Yeah, I then clicked on the screen so LFS regained focus and then tried shift + f4 and nothing.. still came back to the game with normal picture..... try as i may I just cannot reproduce it :(

AndroidXP
2nd June 2007, 18:52
Guess it's not working on all configurations then... and maybe it's not even an LFS bug. I mean, in how many other games do you repeatedly switch between fullscreen and windowed mode? Normally that's not even possible, or ridiculously slow.

The only hope is that Scawen can reproduce it, so he can maybe rewrite the code a bit to, if not fix it, at least minimize the chance of it happening even further. Then again, it's not like the black screen thingy is a real problem anyway, especially now that I know how to reproduce it, I also know how to actively avoid it - the network issues are far more important :)

tristancliffe
2nd June 2007, 18:54
My question is: when will we see, over the next X amount of time, such a large amount of people joining all at once? I can only see this happening if S2 final comes out, or if you release the long anticipated RBR and Westhill Club circuit. ;) And then the fervor will die down in a matter of days, if not shorter.

Obviously, it is good to plan for the future, but are you sacrificing time and energy on a bug that for the most part will be a rare occurance? Or am I missing the point? I guess I am speaking for the common man who does not understand the reason for such extensive coding.

Just throwing my opinion out. :) Still...for me, the wait is worth it.


Very true, but imagine a scenario where we have a nearly full server or two attempting to restart. It's quite hard to get enough votes as it is, but when a 99% completed vote gets cancelled because of a new joiner it can be quite annoying. And it does happen even with 'only' 20 people.

Scawen
2nd June 2007, 19:06
Yeah, the issues are quite serious. There are just so many people joining and leaving all the time on a 48 connection / 32 players host, that these bugs come up too frequently - and when they do, 30 to 40 people are affected all at once. So... gotta fix them.

Anyway, I've tried to fix the server killer bug, updated to W40 now. Franky will soon be updating the bug test server and we can try another stress test on it. That involves basically everyone joining and racing, but we probably need to try all leaving and rejoining a few times.

AndroidXP
2nd June 2007, 19:13
:thumb: Count me in!

Mike85
2nd June 2007, 19:28
I think there should be more people involved in beta patch testing, so that bugs would be found faster. This testing has been the most interesting to me:)

dawesdust_12
2nd June 2007, 19:30
because a firewall may pop up and say "z0mg! LFS.exe is trying to connect to "t3h intertuubes!" - Do you want it to? Yes/No" and if LFS was full screen you wouldn't see it and would just think "Why isn't this motherfizzling program working!"


Sometimes I wish there was a .cfg switch to tell LFS to never do the window bit on new versions.

the_angry_angel
2nd June 2007, 19:33
Under the queueing system, if you reach #1 and then enter, it's possible for you to receive a "player is disconnecting" and your connection attempt becomes void. Technically not a bug I realise :)

I also received a JOOS on connection, in w40, yet managed to stay in server about 20 seconds before I was disconnected, perhaps not relevant, but I'd rather report it. It ws franky's bug testing server also, about 19:30-ish

gohfeld23
2nd June 2007, 19:48
the only change I can notice with 39 and 40 is that it twitches and laggs the game much more then it used to when people connect, leave pits and DL/loading skins.

Not sure if this is simply an issue on my side but it is much worse then it used to be (now I regularly lag off of the track during the above mentioned occurrences)

M1N1M4N
2nd June 2007, 19:52
How does the queing system work. I am trying to connect to a full server on W40 and its not coming up with any queue system?

wien
2nd June 2007, 19:56
How does the queing system work. I am trying to connect to a full server on W40 and its not coming up with any queue system?It's only meant to handle a lot of people connecting at the same time while there's still room in the server I think. If it's full, you get the normal message.

M1N1M4N
2nd June 2007, 19:57
Ahhh right, sorry i thought it meant it was more of a Steam style where if the servers full a queue to join forms :)

wien
2nd June 2007, 19:59
Hmm. LFS just crashed on me while waiting in the connection queue. I think it was at the first position and was getting ready to connect. Unfortunately I didn't have LFS in focus when it happened so I couldn't see exactly what it was doing.

Crash address: 0x0052b3d3.

duke_toaster
2nd June 2007, 20:02
Got black screen bug when shift-F4ing on bug test server 2.

_--NZ--_[HUN]
2nd June 2007, 20:04
I was spectating on Bug Test Server when I got this message: MP Replay:Out of stash space and Lost connection to host

Chaos
2nd June 2007, 20:08
I was trying to connect to the test server by pressing ENTER and got a message saying "too many CLICKS"!!! wtf I was not clicking my mouse button! this is a major bug!! :D

Pakalulu
2nd June 2007, 20:15
After some lagging from my side, I got a flying circus
Is this normal behaviour?

duke_toaster
2nd June 2007, 20:36
Any chance of a server 3? Races are full on 1 and 2 and it would help this bug squashing party :)

faster111
2nd June 2007, 20:43
After some lagging from my side, I got a flying circus
Is this normal behaviour? Never seen that before.

fireb0llch
2nd June 2007, 20:45
After some lagging from my side, I got a flying circus
Is this normal behaviour?

Just change the view and U will see the street again :)

Pakalulu
2nd June 2007, 20:49
Also when trying to connect again and again, I get 'too many clicks, wait xx seconds', which is ok.

But when I then try to connect to another server I immediately get the same message again, so I can't connect to any server during the 'time out'

Is this normal behaviour?

Chaos
2nd June 2007, 20:50
Also when trying to connect again and again, I get 'too many clicks, wait xx seconds', which is ok.

But when I then try to connect to another server I immediately get the same message again, so I can't connect to any server during the 'time out'

Is this normal behaviour?
yup, i think its there to protect the master server from flood clicking...

DeKo
2nd June 2007, 21:02
woah, just got booted off the bug testing server, when i try to join any other server or the meeting room i get user name allready online, and the server doesnt appear on the list. server crash?

Okay maybe not, just restarted LFS and it appears fine.

Pakalulu
2nd June 2007, 21:03
yup, i think its there to protect the master server from flood clicking...

Yeah, maybe I better stop to want it NOW

DEVIL 007
2nd June 2007, 21:13
soory Scawen but I have bad news...
I never ever got black screen with SHIFT+F4 in LFS so many years and now 1st it time happend to me with LFS(please see attached picture).

I still hear the LFS sounds but with SHIFT+F4 going back to fulscreen I have still black screen.As I said never had that bug before but now with W40 yes:(

I was on the Bug test server and tried to type after i got black screen.Not sure if some saw that.

Now host not found on the master server???

Jakg
2nd June 2007, 21:21
Same here on the host status :(

We all saw your text, but didn't know how to tell you

Yaamboo
2nd June 2007, 21:29
I had the black screen bug also after tinkering with Netlimiter's settings.

DEVIL 007
2nd June 2007, 21:30
at least seesm LFS works fine.As I said I never got black screen in LFS with SHIFT+F4 since I played the first demos years back and now happend 1st time to me with W40.seems worst.

Also as reported some posts back shift+U is now completly unusable.Got 4 FPS !!!! (see attached picture again). Thats ridiculous.Its either bug or there must be done some huge optimization.Its not my graphic card being slow.Dunno whats the problem. Got thzat on Bug test 2 server.

EDITED:still on Bug test 2 server and 18FPS with almost nothing drawed???I really dont get it.Attached 2nd picture.

EDITED 2:7 FPS after the end of race and again almost nothing drawed.

I know the SHIFT+U is not so importtant but still something doesnt look fine with LFS.

franky500
2nd June 2007, 21:38
i must admit i also get rediculously low FPS on Shift U.

Iron
2nd June 2007, 21:48
I sometimes (not always) got some heavy stutter just before race restart, while it counted down.

RedRiver
2nd June 2007, 21:48
I tried shift-u and i didnt have any fps loss.


Intel C2D 6600
Asus P5N32-SLI
Geforce 8800GTX
Corsair Dominator 2x1024mb

Pakalulu
2nd June 2007, 21:50
I also got the black screen when changing from windowed to full screen, but after 3-5 seconds normal full screen re-appeared with the message 'preloading'.
Everything fine after that..

wien
2nd June 2007, 21:50
i must admit i also get rediculously low FPS on Shift U.I think LFS turns off any LOD and multiplayer draw optimizations when in SHIFT+U mode (For screenshots presumably). When you have 32 cars running about, that can take quite it's toll on the FPS (unless your computer is fast enough to handle LFS with everything on anyway, like RedRiver up there).

DeKo
2nd June 2007, 21:52
I sometimes (not always) got some heavy stutter just before race restart, while it counted down.

yeah i can confirm that, starts when the text appears on screen, but the stutter only lasts a couple of seconds, shouldnt be something that is a high priority atm.

Shotglass
2nd June 2007, 21:53
shift u problem occurs on my machine as well

and after a lot of shift f4ing tonight im still free from black screens ... driver issue maybe ?

Iron
2nd June 2007, 21:57
yeah i can confirm that, starts when the text appears on screen, but the stutter only lasts a couple of seconds, shouldnt be something that is a high priority atm.

I agree, I forgot to mention that by the time the cars are on the grid, everything is all right. I just thought I would mention it.

wien
2nd June 2007, 21:58
and after a lot of shift f4ing tonight im still free from black screens ... driver issue maybe ?I think that's very likely. It's either the drivers, or something LFS is doing wrong that only manifests itself on certain drivers/graphics cards. It is 100% reproducible here, so it isn't just some freak thing that happens once in a while.

Lateralus
2nd June 2007, 22:06
Just installed W40 and got a 'could not connect to master server' error. Is this just unfortunate timing (i.e. the server is actually down) or did something mess up with the install?

ninja469
2nd June 2007, 22:09
EDITED:still on Bug test 2 server and 18FPS with almost nothing drawed???I really dont get it.Attached 2nd picture.

EDITED 2:7 FPS after the end of race and again almost nothing drawed.

I know the SHIFT+U is not so importtant but still something doesnt look fine with LFS.

Shift U works fine for me, looking at the pics the ping meter is fairly high maybe that's half the problem of low frame rates.

On a different note, the car reset would be better with a 3rd option Imo.

0 = no, car reset not allowed
1 = reset, car reset allowed with no damage repair
2 = yes, car reset allowed with damage fixed

That's because we run enduros and now if you flip your car it's unfair to have your car fully repaired without making a pitstop, or worse that's the end of your race if resets turned off.

And finally, with W39 I had damage then made a pit stop it said was repaired but after leaving the pits the car still had a lot of damage to the suspension.
I've had this happen a few times in the past too but it's not a regular thing.

DEVIL 007
2nd June 2007, 22:19
I think LFS turns off any LOD and multiplayer draw optimizations when in SHIFT+U mode (For screenshots presumably). When you have 32 cars running about, that can take quite it's toll on the FPS (unless your computer is fast enough to handle LFS with everything on anyway, like RedRiver up there).
But do we need all such a machine(You almost cant have better one) to run LFS in all aspects fine?The SHIFT U is normal in W version which I have as well.

I dont think its connected to the lag which occured on server.When it dropped it was the same.I dont know whats the issue.I have with full server around 60-100 FPS with wheel view+virtual mirror and its fine as well in TV camera views.

It really doesnt concern me so mucch but I wanted to reported with as much evidence as possible.There are ofcourse much more important bugs to fix.

The General Lee
2nd June 2007, 22:21
Sorry if it has been mentioned....

...but if your roll, your speed stays the same when you are on your roof and it doesnt go down unless you brake.

Derfrager
2nd June 2007, 22:22
Come the Patch today or when he coming?

Beenom
2nd June 2007, 22:24
Come the Patch today or when he coming?

It's coming soon, Scawen originally wanted it out for Friday but a few bugs were found particularly the "mass join/leave bug". This has been fixed, i think, with the queuing system. It could be later tonight or tomorrow... just wait.:D

AndroidXP
2nd June 2007, 22:27
@Shift+U fps, I can confirm that the reason for this is the completely turned off LOD reduction in that mode, which does indeed make sense for screenshots. Though, I guess an extra option in the shift+U menu to toggle that would make everyone happy.

Misko
2nd June 2007, 22:28
About shift+u, I tried todays replay with about 40+ connections and 31 cars in race, and another (W25) with 26 connections and 24 in race, same combo bl1 gti, same place of the camera. fps is always about half in the first replay regardles of whats in view, 25 as opposed to 55 fps right before start viewing empty road, but drops quite a lot as cars start to move, even to about 4-5 in busier replay, and about 18 in replay with less cars/connections. Number of cars in view is almost the same, maybe few more, but number of connections is double. It does seem like it matters, but maybe Im wrong.

Btw, my normal driving fps is about 40 on starts and 70 later with some lod reduction, dynamic too.

wien
2nd June 2007, 22:32
The SHIFT U is normal in W version which I have as well.But you'll never have as many cars around with W. I think the problem is just amplified because there's so many cars on the track in W40. If you try it with only a few players in the server, I think you'll get FPS similar to what you had in W (I do).

Iron
2nd June 2007, 22:34
Sorry if it has been mentioned....

...but if your roll, your speed stays the same when you are on your roof and it doesnt go down unless you brake.
Erm, that's because your wheels are still rotating and the speedometer measures speed based upon the wheels' rotation... :)

May I have a question: i checked through quickly the changelog in the first post, but didn't see anything regarding the absence of the "best lap" display in the upper right corner which used to be there in W along with your last lap and split time. Where did it go? Note that I'm not talking about the results table which appears after the race is finished, of course you can see everyone's best lap there.

duke_toaster
2nd June 2007, 22:34
Sorry if it has been mentioned....

...but if your roll, your speed stays the same when you are on your roof and it doesnt go down unless you brake.

That's a feature, not a bug.

It's done off wheel speed, like a real speedo :)

EDIT : Or is it skidding on the roof without friction. That would be a bad bug.

The General Lee
2nd June 2007, 22:35
The wheels were slowing down, but the needle was staying put.

I am not a noob you know :razz:

E: Haha, Duke got beatened :razz:

DEVIL 007
2nd June 2007, 22:49
@Shift+U fps, I can confirm that the reason for this is the completely turned off LOD reduction in that mode, which does indeed make sense for screenshots. Though, I guess an extra option in the shift+U menu to toggle that would make everyone happy.
Andriod,look at my screenshots above,especially with these where I am looking just at track.Are there any cars around.No.This doesnt explain what you said above.Seems the number of connections now affect FPS a lot in SHIFT+U.Its fine in other views when there is more drawed.Its really weird.

As you said LFS doesnt use reduction LOD in shift+U but it seems like from my picture LFS would still send these invisible cars to be drawed on the graphic card.This not correct in my eyes.Just my observation..maybe oits not like that.Dunno.

What bother me more is that SHIFT+F4 bug with black screen.

DeKo
2nd June 2007, 23:01
shift u problem occurs on my machine as well

and after a lot of shift f4ing tonight im still free from black screens ... driver issue maybe ?

I dunno how though, its been reproducable on 2 sets of Nvidia drivers and 2 sets of ATI drivers, at least.

Shotglass
2nd June 2007, 23:12
maybe those who have the issue on nvidia hardware could try the 91.47 drivers and see if those fix it

HeerBommel
2nd June 2007, 23:24
Scawen can you explain this to me ?

FIX : AI drivers left pit speed limiter on after leaving pit lane
FIX : AI drivers ignored the pit lane speed limit


when I start a qualify or practice in singleplayer mode I see the following message:
S2 Alpha: AI drivers can't yet qualify or practice because they don't know how to drive through the pitlane

How can they leave the pitlane as they don't know how to drive through the pitlane ????

KMSpeed
2nd June 2007, 23:28
See this thread http://www.lfsforum.net/showthread.php?t=25140

Scawen's answer http://www.lfsforum.net/showthread.php?p=438237#post438237

DasBoeseC
3rd June 2007, 00:29
I can confirm that I could reproduce the black screen bug using Wien's tools that you compiled.

Win XP Pro SP2 / GeForce 7800GTX (Driver 93.71)

[TDRT] Spøgelset
3rd June 2007, 04:23
Not sure if this matter is of any importance or if it has been mentioned already.

Tonight ( June 3th ) i was racing on the test bug 2 server and did a couple of races there. As I´m able to see other player results i raced on this server my own results are not in lfsworld.net stats. . Not even that I have joined the server. Send me a PM if interested in my S2 account name.
I have a lapper version W server running from my IP. Is this the reason why mayby? I have no explanation

BTW: It was great fun racing about 30 XFG´s at Blackwood. My framerate dropped from normally 120 to 30, still fun and playable.
Pls. enable the XRG´s as well.
I´m aware of it´s primary for testing, still .... ;-) :)

RudolfR
3rd June 2007, 09:05
I think I found another bug :)

when I restarted the race , then I started quali , he specticated me for wrong way :)

Iron
3rd June 2007, 09:32
Spøgelset;442000']Not sure if this matter is of any importance or if it has been mentioned already.

Tonight ( June 3th ) i was racing on the test bug 2 server and did a couple of races there. As I´m able to see other player results i raced on this server my own results are not in lfsworld.net stats. . Not even that I have joined the server. Send me a PM if interested in my S2 account name.
I have a lapper version W server running from my IP. Is this the reason why mayby? I have no explanation

BTW: It was great fun racing about 30 XFG´s at Blackwood. My framerate dropped from normally 120 to 30, still fun and playable.
Pls. enable the XRG´s as well.
I´m aware of it´s primary for testing, still .... ;-) :)
I had a similar problem. LFSW didn't record my pb (and perhaps other stats) that I did before bug test server 2 crashed.

DEVIL 007
3rd June 2007, 09:36
Please could be possible to have total lap time visible all the time.
Its confusing not to see how much better or worst I did in next lap.

three_jump
3rd June 2007, 09:39
I think I found another bug :)

when I restarted the race , then I started quali , he specticated me for wrong way :)

I tried to reproduce this, can you give more informations please?

like track, did you finish the race before or didn't you move at all etc.

RudolfR
3rd June 2007, 09:51
It was westhill
I left pits , then I restarted race , then while he counted "Race restarts in.."
I hitted quali , and after he specitated me for wrong way :)

three_jump
3rd June 2007, 11:21
It was westhill
I left pits , then I restarted race , then while he counted "Race restarts in.."
I hitted quali , and after he specitated me for wrong way :)

tried it about 15 times now, but couldn't reproduce it :(

DEVIL 007
3rd June 2007, 13:20
I tried to reproduce it several times as well but no luck.

alxf1
3rd June 2007, 13:24
Scawen, can you please check the attached mpr, got this problem when joining the race on "bug test server". when joining into the race, the car was just thrown into the wall just because it was joining in the garage of another player.

PS. something more, when watching a replay, if you press pause button and then press F3, "paused" message will blink faster :)

word.
3rd June 2007, 13:48
when joining into the race, the car was just thrown into the wall just because it was joining in the garage of another player.

I have had this happen even in the demo with patch W, in the blackwood carpark. The chance of it happening is just much higher when more players are in the server.

AttaHorse
3rd June 2007, 15:29
I installed W40 above W17(unlocked, as far as I remember), and it locked. I tried to unlock it several times, but LFS says "Unknown command". I tryed incorrect game password, but lfs says "Incorrect game password", so game recognizes it.
I checked f*.xxx files: f1 is new, but others are not.
I have just copied f*.xxx files from my W installation and it's ok now.

W can be unlocked ok.

three_jump
3rd June 2007, 15:33
I installed W40 above W17(unlocked, as far as I remember), and it locked. I tried to unlock it several times, but LFS says "Unknown command". I tryed incorrect game password, but lfs says "Incorrect game password", so game recognizes it.
I checked f*.xxx files: f1 is new, but others are not.
I have just copied f*.xxx files from my W installation and it's ok now.

It's a "common" :D thing that Scawen forgets to update the master server to allow unlocking for new versions... see also here: http://www.lfsforum.net/showthread.php?t=25332 So I it's not a real patch connected problem.

robt
3rd June 2007, 15:57
ok, so not a bug BUT an idea to help with the vote problem with all the disconnects etc. would it be possible to maybe put a button in the connections menu (like the send setup button) to toggle on/off that will then automatically vote to restart after a votes been canceled once the person has connected/disconnected? probably wouldn't work, but just an idea that popped into my head. would just have to be careful it doesn't automatically vote when the race restarts :schwitz:

ste_
3rd June 2007, 16:24
Scawen, would you consider putting some logic in wrt what garage people appear in if they join mid-race? A couple of times i've being doing a pit-stop and someone has joined the race and started from the garage that I'm currently doing my pitstop in. But they've driven straight out of the garage and knocked me out of my pitbox and messed me up. If someone joins midrace, could you put them in a garage who's pitbox isn't currently being used?

Mike85
3rd June 2007, 16:59
Or how about have numbered pit stops, so you have your own pitstop. It could be optional atleast. But I guess thats for future.

faster111
3rd June 2007, 17:04
BUG?

Network fatal connreset did not receive ok that message popped up when i was have way trough downloading skins.

joshm1989
3rd June 2007, 17:06
wat about the people that come out of the pits and jack the car up and you feel the feedback and cange the pit lane to how ever many people can join say 46 theres 46 spots are racing thats how many spots in pit lane there are and everyone has there own pit spot

robt
3rd June 2007, 17:08
wow u have large capacity lungs there josh!

wheel4hummer
3rd June 2007, 17:16
wat about the people that come out of the pits and jack the car up and you feel the feedback and cange the pit lane to how ever many people can join say 46 theres 46 spots are racing thats how many spots in pit lane there are and everyone has there own pit spot

I cannot even say that with one breath!

Scawen
3rd June 2007, 17:19
W41 : http://www.lfsforum.net/showthread.php?t=25134

I'll join one of Franky's bug test hosts at about 18:30 uk time / 19:30 europe for some testing.

Gil07
3rd June 2007, 17:34
Scawen, got some JOOS when trying to go to the garage on the Bug test server. Don't remember the exact text as I had to leasve the server, but someone may remember it... It could have something to do with the race being full.

Milanche
3rd June 2007, 17:46
Hi Scawen few of my friends and me were racing today on AutoPlus S2 server. And all the sadden everybody disappeared I could only some my self and also they couldn't see me and I couldn't see them no one could see no one by them self xD.

is this a bug or what????

Now I can't even log onto the server it says "Did not receive guest info Lost connection to the host".

I'll keep u informed!

RGDS


Milanche


10 minutes after still can't connect :(


edit: patch was w39

danowat
3rd June 2007, 18:12
Haven't read through everything, but I can't reach the master server with the latest patch

SpikeyMarcoD
3rd June 2007, 18:19
Haven't read through everything, but I can't reach the master server with the latest patch

can only be that you forgot the firewall

spiderbait90
3rd June 2007, 18:28
Took 3 attempts to connect, First time, Lost connection / Did not recieve track info.
2nd. NETWORK FATAL :CONABORT (or similar)
3rd time got through in a queue of 5.

danowat
3rd June 2007, 18:29
nm, fixed

Madman_CZ
3rd June 2007, 18:41
Out of 3 connections to the test servers 2 connections were successful and once i received "did not receive guest info" after waiting in a queue of 2.

I am also suffering with bad stutters when people join the server, is anyone experiencing the same thing?

Pakalulu
3rd June 2007, 18:44
18.40h GMT left bug server2, on reconnect I get 'username already online'

A few minutes later all was fine (I updated to W41 in the mean time)

Termi
3rd June 2007, 18:47
18.40h GMT left bug server2, on reconnect I get 'username already online'

A few minutes later all was fine (I updated to W41 in the mean time)

For me the same at #1

Doorman
3rd June 2007, 19:03
Thank God that it's just a stress test. That many people on a server just raises the DH level. Still I bet no-one punts Scawen up the backside! :)

Seemed to work pretty smoothly for me though.

niall09
3rd June 2007, 19:14
Still I bet no-one punts Scawen up the backside! :)

Seemed to work pretty smoothly for me though.

I done it to Vic on the first night of the stress testing :tilt:

duke_toaster
3rd June 2007, 19:20
Still I bet no-one punts Scawen up the backside! :)

He is of the LX pursuasion, I couldn't clock which one but LX at South city is good (if you can actually drive it well)

traxxion
3rd June 2007, 19:21
Still I bet no-one punts Scawen up the backside! :)
You'd think that (http://www.meuksite.nl/1ST/patchXdelay.wmv) ;)

AndroidXP
3rd June 2007, 19:32
Guess the /reinit failed?

DratsaB
3rd June 2007, 19:33
I was 26 in queue, then got "did not receive OK", Then Host Not Found On Master Server

J.B.
3rd June 2007, 19:34
Looks like we just killed test server 2.

We all disconnected and reconnected at once, I got the queue counting down, then "OK not recieved", then host not found. Now it's not on the server list.

EDIT: oops, I meant server 1

Quietus
3rd June 2007, 19:34
Same, queued, then the host vanished...

wien
3rd June 2007, 19:35
Looks like we just killed test server 2.Server one went down too. Maybe another ill-timed network outage? Some coincidence if it is though.

Scawen
3rd June 2007, 19:44
You'd think that
hehe :D


About the crash ... Android that was server 1.

Most people left and were rejoining - then half way through that I did /reinit - and server died.

Server 2 is still running fine.

tristancliffe
3rd June 2007, 19:56
Lol. You'd think the FM team would be good at the BF1 by now :)

Shotglass
3rd June 2007, 19:57
You'd think that (http://www.meuksite.nl/1ST/patchXdelay.wmv) ;)

ive got an even better one with some cp guy wrecking him ... gotta fraps that soon

other than the reinit serverkiller ive had no problems thus far tonight
highest queue slot war ~16 so sry for not being able to give any valuable input at this time


just had an error during connect

Lost connection to host
Can't remove - Unknown!

didnt have shift-f8 on at the time

PMD9409
3rd June 2007, 20:39
The Test Bug 2 Server just took a dump on some drivers. Just before the dump, the lag meter seem to grow quite a bit. Don't know what else to add, see the pic below, maybe it can tell you more.




31757

speedykev
3rd June 2007, 20:56
I done it to Vic on the first night of the stress testing :tilt:

I would keep that to your self.:nod:

Venus
3rd June 2007, 21:11
Question about the patches: I want to install the latest patch. But I'm concerned about whether the I'll still be able to join all the same servers using 0.5W. Someone know the answer to this? Also, does the latest patch include all the previous ones?

Venus

Jakg
3rd June 2007, 21:13
1. No, W and W41 are not compatible.
2. Yes, download W41 and your away (i would fancy downloading W41 + the other 24 patches just to play!)

Storm_Cloud
3rd June 2007, 21:18
Question about the patches: I want to install the latest patch. But I'm concerned about whether the I'll still be able to join all the same servers using 0.5W. Someone know the answer to this? Also, does the latest patch include all the previous ones?

Venus

Make a copy of the LFS folder and patch the copy to W41. Then you can go back to W whenever you want.

Doorman
3rd June 2007, 22:08
You'd think that (http://www.meuksite.nl/1ST/patchXdelay.wmv);)
Damn me! :)

mcintyrej
3rd June 2007, 23:26
I think these Test patches are a VERY good demonstration on how an officially supported race schedule could work.

How about officially hosted events by the dev's each week, the server would EASILY fill within minutes and some great racing would be there.

This would really bring the community together and stop people complaining about the cruise servers taking away racers. - I know this is kinda O/T, but I think I shuold make this point rather than not.

wark
4th June 2007, 02:18
Sorry if this has been found and mentioned before, but:

If you start a practice or qual (i.e. from pits) and get on the gas right away in a faster car, with the limiter off, you can break the speed limit with no penalty--even upon reentering the pit lane--the speed limit is effectively removed for the remainder of the session.

I've been able to reproduce this in the last few versions, on any track, but it only happens if you accelerate past the speed limit in the first couple seconds of play (most of the cars aren't even fast enough).

This only works in practice/qual.

Misko
4th June 2007, 02:32
Hi Scawen few of my friends and me were racing today on AutoPlus S2 server. And all the sadden everybody disappeared I could only some my self and also they couldn't see me and I couldn't see them no one could see no one by them self xD.

is this a bug or what????

Now I can't even log onto the server it says "Did not receive guest info Lost connection to the host".

edit: patch was w39That had probably something to do with Wine, server PC is totally new and maybe something wasn't configured right in Linux yet. Dedi host is actually W40, and its been running for about 18 hours before that problem happened. One restart fixed it. We don't think it's about test patches.

Scawen
4th June 2007, 13:00
Scawen, can you please check the attached mpr, got this problem when joining the race on "bug test server". when joining into the race, the car was just thrown into the wall just because it was joining in the garage of another player.

PS. something more, when watching a replay, if you press pause button and then press F3, "paused" message will blink faster :)

Thing is, that shouldn't happen. Two drivers should not start in the same pit square. It is possible to happen if the other driver drives into your pit box and parks there, then you can spawn intersecting that car. That's easy to reproduce and not actually a bug, it's just a situation that LFS doesn't yet deal with. I don't know what happened in that replay, did he park there before you joined (not a bug) or did he spawn there (bug). If it's reproducable then I can fix it, if we don't know how it happened then I can't really look into it.

Hi Scawen few of my friends and me were racing today on AutoPlus S2 server. And all the sadden everybody disappeared I could only some my self and also they couldn't see me and I couldn't see them no one could see no one by them self xD.

is this a bug or what????

Now I can't even log onto the server it says "Did not receive guest info Lost connection to the host".

I'll keep u informed!

RGDS


Milanche


10 minutes after still can't connect :(


edit: patch was w39

That had probably something to do with Wine, server PC is totally new and maybe something wasn't configured right in Linux yet. Dedi host is actually W40, and its been running for about 18 hours before that problem happened. One restart fixed it. We don't think it's about test patches.

Yes that is a typical Wine issue, and it's something to do with UDP packets, I think the host stops receiving UDP packets. I've heard it can be fixed by using a different version of Wine. Better discuss in technical assistance if you want to know more. That's all I know, I don't know Wine so cannot help.

ksa_land
4th June 2007, 13:04
Hi Scawen,

I was yesturday and the day before at the bugtest server which was Blackwood running. I noticed there that the green light came EVERYTIME (10-15 races) in the same rhythm.

I did a bit testing. Went on a empty server. Had NO WIND. Blackwood.
Everytime there was the same as at Bugtest server. Same rhythm. No variation in greenlight delay. After 3 seconds first red light and after six seconds green light.

Then I turned on wind (low). Now I had a variation in the greenlight delay.
Time to first redlight varied. Sometimes 1 or 2 lights where already on after shift+R.

Another guy in the german forum noticed this lack of variation on the bugtest server too.


regards

Land

Doorman
4th June 2007, 13:25
Maybe that's for the benefit of the "if there's wind I'm outta here", "pfft, no resetting?" and "Bah, no predictable start lights" brigade. I'm sometimes tempted to enable strong wind but I fear that would cause an uproar! :shrug: Ho hell with it I WILL enable /wind 2 just to see what happens. :D

AndroidXP
4th June 2007, 13:34
I guess the random start light generator is powered by the rotating wind power stations, explaining the lack of randomness on "no wind" servers :p

GeForz
4th June 2007, 13:45
Well I have noticed some pattern in startlights ^^
- no ai, no wind: the time between no lights and red and between the last res and the green is always the same
- with ai, no wind: the time between no lights and the first red is a bit longer; the time between the last red and the green a bit shorter but still everytime the same ^^
- with wind: random

But I would suggest to make the time when the first red switches on a fixed time and to just vary the time between red and green. As atm it's always the same time between "showing the lights" and "green".