To avoid this kind of enjoyable threads on a forum for a game of which the channel seems to be manually (or maniacally to some) moderated, someone invented... EggDrop...
Rules are static and can be programmed... Problem solved... Close thread
Good point. It's not that it didn't look good on TV though. There was more overtaking in this race than in most of the F1 season combined, but that's not the point. The point is that overtaking on this track was overly risky, and that several potential overtaking spots were ruined by so-called speed-limiting chicanes. The first chicane reminded me of the Surfer's Paradise double chicane on the backstretch, but without a useful purpose. I can see how it was needed in Australia, but in South Africa the speeds at the point of the chicane were about 90mph slower. And that's the feeling I got from the track. Several good spots for overtaking ruined because the track was made single file at them. Which is a shame.
I love streetcircuits though. Including the concrete walls. Armco looks cheap in comparison. So I vote for more street circuits, but please... On bigger streets, and with less artificial chicanes/apex's.
Track sucked though...
It's a silly excuse for a circuit, even a street one.
The only wide spaces are completely useless because they give you no opportunity to overtake, and the places that allow overtaking end up in a bottleneck making every attempt at passing overly risky.
Sole exception being the hairpin at the end of the s/f straight.
The race was eventful, I'll give them that. But being held up by team Lebanon, because blocking here only takes about 10cm of deviating from your line, has to be something nobody likes very much.
Next season they should go to Kyalami or Welkom in SA, and add a different street circuit to the calendar. I've always been a fan of Long Beach for some reason.
Funny how in about an hour and a half, a driver can go from zero to hero...
He should never have stuck it on the outside in the sprint race, and I cursed him for that stupid move... Then in the feature, he did the same thing at the same spot at the same lap (the final one), and pulled it off, and guess what? It was a brilliant move now :P
Yes, but when the whole language patches thing came to an end Scawen mentioned starting work on a large (incompatible) patch to solve some of the bigger physics bugs... So that leads me to believe the initial release pattern of 0.3, 0.6, and 1.0 might be changed to 0.3, 0.7, 1.0... Basically that fits it better as well, because S1 was actually 33% of LFS, S2 66% (which rounds up to 0.7) and S3 100% done.
Either way, we're not at S3 stage yet, and I have a feeling that what we currently have will turn out to be only about 40% of what eventually will be S3.
SO we'll have plenty of room for patches once the final is out. It could even be that Alpha = 0.5 until the next incompatible physics patch, when it will be 0.6, and then S2 final which will be 0.7, so until S3 we'll have at least 3*26 patches left (if S3 alpha is released like S2 alpha).
On the other hand... WHY do you think Scawen released the language patches? Just so he could start using cyrillic characters for the versions of course
ajp's argument is exactly what you say... On stills (renders) the environment may look real, but the way we look at the screen and objects make them completely unreal because of the amount of detail we get... What you see on the screen, is not what you'd see in a real car on the same track... So he pleads for less detail to make it more realistic.
Hmmm... I've done that hundreds of times... Here's how to create a dual boot system the manual way:
So you've got 2 systems booting from different drives...
Make the W98 the primary master drive (the one it boots from)
Boot into W98 and create an Emergency Boot Disk...
Open Notepad and type in this (and exactly this):
L 100 2 0 1
N C:\BOOTSECT.DOS
R BX
0
R CX
200
W
Q
Save this file to the W98 system partition with an easy to type name (like Boots.dmp)
Reboot using the W98 EBD you created.
At the prompt type
DEBUG < C:\BOOTS.DMP
(use the name you just entired for the notepad file)
Check to see if there is a new file called bootsect.dos on the C-drive.
Next, boot up using the Windows XP install CD.
Once the setup loads, choose repair, and enter the recovery console for your Windows XP installation. It should detect it even if it's not on the bootable drive.
At the prompt, type FIXBOOT and press enter.
type Y and enter...
Remove the XP CD, reboot, and you'll have your options including W98 and XP...
The slave active partition will be disabled upon boot, so it should work fine.
If it's the comp it's probably hardware related. On the other hand, Windows should NEVER freeze because of a software problem that doesn't shut down hardware (that's why we have those blue screens).
I can only assume that there's something in your BIOS settings that turns off something it shouldn't turn off because of some threshold being reached. Usually this is temperature related. Even if it's not hardware related in the end, this is the best place to start experimenting, since there's only so much hardware in the comp.
Try the following:
Take out everything except the proc, and some memory (only one strip, not all if you have more)... Run the comp, and wait and see what happens. Then one by one start reinstalling hardware, until the beeping occurs again. (of course an old PCI videocard would be useful if you don't want the comp to seriously stress out because it wants to draw out the pictures in thin air.)
It's gonna take time, but at least you're ruling out hardware as the problem.
Also, check the proc for any bent pins (there's about 187 of them, so that should keep you busy)... Since you changed the MB, I'm assuming you inserted the proc. Could be you messed that part up just a tad. Or applying the cooling block might have slightly cracked the core (depending on what proc you got). <-- Yes, I've spent days looking for this very problem of a tiny crack in the core with my PC stopping dead in its tracks after about 20 minutes of uptime. Since this is a pretty dangerous operation when the cooling is already in place (you could crack the core by removing it again), I suggest you try this last.
If none of these solve your problem, get back to us, and we'll start examining your system.
(BTW, Windows not responding and the mouse still moving is not so strange... The way the mouse works on a computer is in many ways the stupidest design flaw ever... They made sure that the mouse's I/O will not interfere with anything else, so unless the processor itself is in a deadlock, and windows hasn't killed all its threads (which is basically when you get a bluescreen), the mousepointer WILL move.)
And to be quite honest... That's the only two words that should ever have been written in it... On the cover of a book "Don't PANIC" in large 'friendly' letters.
As for favorite font...
For large pieces of text, it's gonna have to be Century Schoolbook or Goudy Catalog... Only because it's just a pleasant typeface to read for long periods of time.
For the sheer looks of it, Lithograph and Mystical... Reads like sh*te, but looks awesome on posters and flyers.
Of course, there's hundreds more (I have several thousands installed) that are good, and as many that suck.
You know you can search the posts for keywords like DFP instead of just the thread titles, right? It will even highlight the keywords when you open a thread in the searchresults.
So by reading this topic, the skins started downloading again?
What worked? Deleting the helmet skins? If so, I'm going to try and recreate this problem so we get better insight into what makes it fail in the first place.
Victor, Scawen...
Seriously, it's not a BIG problem, but there seems to be a bug with the auto helmet skins download... Would you mind looking into this when you have a chance? My guess is it only happens when one or more of the helmet skins is corrupted on the local drive... I have NO clue how it could still happen when the entire skin_x folder is empty, but still that seems to be the case... It happened to me back in October, and it happened to other people as well... And Yugo wasn't entirely going crazy... I only remembered the helmet part because I looked for my own original post on this subject and someone mentioned helmets.
What conditions need to be met for a skin NOT to download? Must be on local drive, must have a timestamp newer or equal to the one on the server, and must have matching CRC?
I just found part of the original conversation about a looping problem like this on here...
Yugo, bud, can you do me a favor and try something for me?
You said you'd removed all the skins from the skin_x folder, right?
I'm assuming you tried connecting to the servers after that and start all fresh with no skins, so it would download ALL of them... (if not, hold on a bit, want you to try the next first)...
Try deleting ALL the HEL skins (helmets) from the skins_x folder. Turns out for someone that was the problem (I've tried millions of things, and found it worked again all of a sudden, so that may actually turn out to be what did it for me eventually). After you've done this, connect as usual and auto download the skins... See what happens, and report back.
If that doesn't work... Do me another favor (at least we're working on your problem now)... Delete everything from the skins_x folder (including hidden files, and stuff like that), and delete all skins except the default ones from your skins folder as well... I want everything to be clean so we can see what happens... Next, make a screenshot of when you join a server.
All white skins... And make one where you have the MISC options menu open (it shows the list of skins it downloads...)... When it's done downloading and starts looping (if ever), make another screenshot, just so we get to see the list of remaining skins. Then disconnect from the server, turn off auto downloading, and reconnect (you should see the skins, right?)
Screenshot of the skins, then turn autodownload on again, and make another screenshot of the disappearing skin...
I want to see what it is exactly that's happening... I also would like to know if the skins that disappear reappear in the MISC options window, so we can see if it redownloads them or leaves them alone.
Hide the .jpg files, or just the extensions?
This is getting weirder and weirder, but it COULD be that "hide extensions for known file types" is acting up. Uncheck that in "Folder options".
The weird part is that for some reason, the amount of skins LFS seems able to display changes when you use automatic skin downloading. I don't know how LFS handles changing that option, but it would seem to me that skins turning white has nothing to do with files on the harddrive at all UNLESS they are all reloaded when that option changes.
I remember a time when there were a lot of people complaining about skins not downloading... Maybe search RSC forums for "skins won't download" or "skin download loop" or something... It may turn up something useful...
@ Tweak: Actually it sounds as though the problem you are describing is the mirror image of this one... With you, this guy's skin wouldn't load on your PC, while here your skin won't load on his PC.
So... LFS says it's downloading the skins... And says its downloading some of those more than once in a loop...
While it is downloading those skins you don't see any of the downloaded skins, but when you disco and reconnect to the server, you see the previously downloaded ones, but not the ones it hasn't finished downloading yet?
If so... I've had that problem once... There's a list of skins it's downloading in the player options (I think)... See which skins are on there, and try to stop them downloading (you can cancel the downloads by clicking them or something, can't really remember... When you've done that, turn automatic skin downloading to off, and connect to the same server again... Then disconnect, turn automatic skin downloading back on, reconnect, and for some strange reason, from that moment forth, it would simply download all the available skins for me. There may be a small bug in the automatic download functions, causing the skins to become corrupted, or the wrong message received when downloads finish. Most common for me were helmet skins not downloading correctly.
Well we won't be able to help you if you don't tell us how it's set up...
We need to have at least some idea of what a packet of data has to pass on its merry way to and from your server to and from the clients...
So what IPs are you using on the server, how is the server itself configured, how is the router passing the packets needed (NAT config would be really nice to see), etc, etc..
You may want to scan anything you post here for passwords, so we don't get to see those, and you may change your external IP address to something else so we won't instantly know where to send spam mails, or virii (not that we'd do that, but this is still a public website). If you change the IP address, make sure you change it to the same one everywhere, or else we'll be yelling a lot of false positive errors in your configs
If any of this did not make perfect sense... Just say so.
LOL... You wouldn't happen to have one of those Genuine People Personality Prototype computers, would you? Because next it'll go off in a rant of how all the diodes down his left side hurt, but nobody ever cares to replace them, ooohhh no, it's god it's so depressed... Life, don't talk to it about life.
Just think about the possibilities, mate... stepping through a replay like that, having all the time in the world to position the camera just right before you hit Record, and the slideshow begins to fill your harddrive... Listen to the LFSMM write the frame, then seeing it advance one frame, adjust the camera, wait for the frame to be finished, and save it to disc, seeing it advance.... I'm ranting.