Quote from dawesdust_12 :

I suppose you can also use any text editor to make C#, and then there's a command line compiler.

That's what I was thinking. They mightn't technically be "environments", but there are millions of text editors to write it in, and MS do a command line compiler too That's the problem with a MS developed language, but damn it's so quick and easy to use I'm not complaining

There's more than Mono and VS too, there's EdSharp, SharpDevelop, Turbo C#, QuickSharp to name but a few

Quote from VladasCerka :

but its old... only 1.0.2 version.... maybie there is newer version?

There is, but it's part of a different project, and isn't publicly released (and more than likely won't be, I've learnt my lesson). This one is open sourced, feel free to improve and re-upload, that's the idea.

Krammeh is right though, you should start your own from scratch. This one is very badly written, and you won't learn anything beneficial from it.

Quote from VladasCerka :

maybie... and last question.. whicj c# program i need to use? maybie microsoft visual c++?

There's plenty of C# environments to choose from, I used Visual C#

She's slowly but surely getting there. A bit of a setback a couple of weeks back (women drivers ), but nothing a few new panels and a lick of paint can't fix Went for a bit of a trip up the coast last week, I've had to take photos of the car from the back though, the front is now a mess

Quote from piggy501 :

A Mini.

I second this. It's a tad smaller than the Merc, but it makes up for it elsewhere.

Quote :

Power: Low down pulling power, yes. Top end speed, not so much, 90 is about as high as you can safely take it before it's making worrying noise levels. Given that you'll never need to slow down for a roundabout it balances out though. 0-60 is about 10 seconds depending on the car for the 1.3. They all seem to be different, but a well set-up model should have no bother hitting 10. They're very cheap and easy to modify if you wanted more power, but the car only weighs around 600kg so it's not essential.

Running costs: ~€1k insurance, so presumably less than £1k. Not all that bad for what you get.

Fuel: Anything between 25 and 35MPG I've found, not fantastic but those include fast motorway driving (you'll suffer here, with only 4 gears). With a light foot shouldn't be hard to get above 40MPG on a properly tuned 1.3.

Fuel Type: 1.3 carb'd FTW. There's also single and multi point injection on later models, but the carbs are far better if you're looking for performance.

Transmission: Choice of manual or auto, the slushboxes aren't too bad though from what I hear, and they can be put into manual select too without any of that sequential/DCG shite you get in a modern car.

Drivetrain: Gay wheel drive all the way, but that's a good thing. Unless you regularaly plan on chewing tyres diffing roundabouts, there's more fun to be had with the power at the front. You can still drift these if you go fast enough, the back tends to step out

Equipment: Umm...No. You (may) get a stereo, and possibly a speaker or two. No power steering, and no servo brakes on anything over ~15 years old. It's more fun without them anyway It's easy to add in anything electrical you fancy though, so it's not really a problem.

Body style: Saloon will hold 4 people, not that uncomfortably either unless they're all over 6' 7". You'll suffer in boot space though, I've filled mine with a spare tyre and a sub so I'm using the back seat as my boot. You might fare better with one of the long wheelbase models.

Age: You'll be looking at pre-2001 for sure, more than likely anything over 15 years old for your budget.

But compared to the S13 above, they're too expensive and too much hassle for what they're worth. An S13 would be cheaper and more fun to drive if you can afford the insurance

Hi Kamo,

I made an app to do what you're looking for. It randomly gets a track/car combo (I disabled rallyx tracks to avoid SS/GTR rallyx, but I can put them back in if you like), and switches to it after every 3 races, and then gets a new random combo (and so on).

There's a settings panel for admins ($settings), that shows you the next combo (which you can randomise again with the button), the races needed for a restart (editable), the length of a qualy session (editable too) and the current amount of races completed. The next race laps are calculated based on the length of the track. There's also a button to enable/disable the app.

PM me if you're still interested

Rob

Quote from aroX123 :

Went for a drive yesterday and hit 8-12 inches of snow on some of the local access roads through the Burren. But there's nothing in most places, just rain and cold

There's no need for the "(Connections[GetConnIdx(Players[GetPlyIdx(AXO.PLID)].UniqueID)].UniqueID)" part btw, it's the same story as with MSO.UCID vs. Connections[GetConnIdx(MSO.UCID)].UniqueID.

"Players[GetPlyIdx(AXO.PLID)].UniqueID" would be all you need to return the UCID, the rest is just pointless CPU cycles. It mightn't make much of a difference here, but if you were to put something similar in an MCI function on a busy server, that's up to 1,024 wasted CPU cycles every 500ms, just to find one ID. That could mean 32,768 wasted cycles to ID each player on the server, just for a single function. Sorry if it seems I'm nitpicking, but it all adds up...

But that isn't causing the issue. If InSim sniffer isn't finding any AXO packets, your program isn't at fault. It might be a setting in LFS, I'm not sure. See if you're getting 2 second penalties for hitting the objects. If not, then LFS wouldn't send an AXO. It might be that LFS doesn't count it as a "true" autocross layout, and doesn't count hitting an object as a fault.

"MSO.UCID" has the very same value as "Connections[GetConnIdx(MSO.UCID)].UniqueID" though. What the second one does is iterates through the connections list until it finds a connection with the ID MSO.UCID, and then returns the ID, which is going to be the same as MCO.UCID. I can't see any reason why the second one would work where the first one would fail, the second one is dependent on the first one really

When using a packet that contains the PlayerID rather than the UniqueID, you have to use something like this to get a UCID from a PLID:

Players[GetPlyIdx(!PLID HERE!)].UniqueID

Generally, if a packet can only be sent when a player is on track, a PLID is included (such as hitting an autocross object), or if the player can be either on track or spectating a UCID is sent (such as typing a message). IS_AXO only contains a PLID, so you'll have to use the code above. In InSim.txt, if you search for the packet you're looking for, it'll tell you exactly what's sent, a UCID, or a PLID.

A player is only assigned a PLID when on track (and it can and probably will be different each time they join from spectate), but a UCID stays with them for as long as they are connected to the server. So you can't rely on a PLID, it's always best to use a UCID where possible

Maybe if you want to do very zoomed enlargements it might come in handy. On a HD monitor running 1920x1080 you won't see any difference between any number above 2MP unless you start zooming (unless the camera is doing some funky interpolation or whatever they do to fool you into thinking you have more MPz).

For example, after a recent crash I was in (which wasn't my fault as the photo proves :razz, I took a photo with my 3MP camera phone. Yet on zooming in you can see the detail in my skidmarks, and even count the cars stopped in traffic 500 yards down the road. Maybe if I'd had an 8MP camera with me I could make out the facial expressions of those in the cars.

Look at it this way. Your standard TV cable comes in at a 520x576 res. That's just shy of 0.3MP. Yet it's still more than watchable on a 32" tele in your sitting room

Given the video res is 640x480, I'd imagine it'd be filming at 0.3MP, standard VGA Correct me if I'm wrong in anything here, I'm just using basic maths and my own experiences. I'm not a camera enthusiast of any kind

Looks like an LFS/InSim bug to me, that error is caused by sending MTC packets in single player mode. Since you're in a multiplayer host, an MTC should be fine

It seems to be Corsican, but yea, just a rant about the Scirocco

Roads are icy as hell (snow's melted and then frozen), and can't see more than 6 feet with the fog. The best driving conditions I've been in so far, the roads are literally deserted

Why is there a hoover in the background? Or are you trying to hold a microphone up to a speaker or something?

Nope, just plugged in my G25, traction control still stuck at 7

Quote from funRacer[83] :

TC is with the stock Nissan only active if you use a gamepad, if you play with a wheel TC is OFF. You can check it on the Ranking list.

You can see "Tuned" IN the picture *facepalm*

Quote from Vain :

I'm all open for criticism and I also think there's something not perfect about GT5, but do you realize that in the GT5 TimeTrial the traction control is activated?

Vain

This. And also LFS does have a rev limiter. It just doesn't go NING NING NING like a moped

No snow here, just ice and frost. Snow is hardly fun, but it's a damn sight better than driving on the icy roads in the dark with half a headlight working

Quote from Chrisuu01 :

Nice joke..

Ninja edit

It never says what year. Maybe they meant 18th December 2009 after all (if their week starts on a Sunday, as some people do)?

Quote from hyntty :

On a more serious note, always wear high visibility jackets.

According to the government road safety man on the radio, we're supposed to give hi-viz jackets for Christmas this year

Quote from Grigg94 :

nearly a year late till the vw scirocco was apparently ready to be released.

Quote from CoolColJ :

replay of the tuned Z
http://www.youtube.com/watch?v=5XvksBfIG8k

That looks amazing. Some of the exterior shots could easily be taken for actual photographs (The shots after 1:14 look particularly good). Whether it looks like that it in-game is another matter though, it's all well and good having shiny replays but it needs to look that good live

Quote from niall09 :

Stab City

Posting in an epic thread

You could use solid objects as the barriers, an AXO isn't sent when you hit one of those. The problem with doing a pacman style game is that the cones will respawn after you hit them, so you'd have to maybe have some sort of time limit?