Quote from speed1230 :

I'll give the Midget a break, since I went on the internet and I found this [merc]

Well, considering that'll all peel off at comparatively low speeds, it's not that bad.

Quote from speed1230 :

tbh I've seen a lot worse

You have NO IDEA, midgets are brilliant little boxes!

Quote from dawesdust_12 :

Rebuilding engine should restore that, no?

Quote from CoolColJ :

Have you rebuilt and reoiled? I read that there is some mileage loss over time.

Yes of course it's rebuilt, after 20000km it certainly wouldn't still produce 924bhp without a rebuild & new oil I ran it down quite a bit the past few days without rebuilding / oil changes, went down to about 866bhp before the oil warning light finally went on.

No need to replace it though, still kills just about anything you'll encounter in A&B-Spec, even at 866bhp.

Is there some sort of permanent engine degradation? My 787B Stealth used to produce 927 bhp fully built, now it won't do better than 924. Could be mileage related, it's got almost 20.000km on the clock

As filur raised before, there is no reason for this to be part of PRISM's core, it could be a plugin... or a module... or an addon, I'm not quite clear where the distinction lies with PRISM

Quote from Osco :

Why? She's probably legal by now

Aye, she's cute but still doesn't look legal if you ask me.

I don't understand what you're all on about? He's clearly performing the Heimlich maneuver to save her!

Quote from BlueFlame :

To me, a stoppie is a brakestand. As to define a brakestand as the word it is, would be, for one to stand on the brakes. You can only stand on something when you are upright. Therefore a stoppie is more fitting to the term 'brakestand'.

While that certainly makes more sense, the internet disagrees. Personally I find "brake stand" to be somewhat redundant and nondescript, so I won't use it to describe either a burnout or a stoppie, quite frankly I won't use it at all.

Quote from BlueFlame :

http://www.youtube.com/watch?v=k2D6G1zkceA&NR=1
this is a brakestand.

That's a stoppie. A "brake stand" is a burnout, although I don't see why anyone would call it brake stand

I still have my first mobile somewhere, Nokia 5110, got it in 1999.

Current one is this:


EDIT:

Quote from Boris Lozac :

Still using 6230i, almost 5 years now..

Yeah had one since 2004 until I got the Mozart for Christmas, was a very trusty companion. Bits and pieces fell off and I had to solder the power button back on once but that's no biggie.

Last edited by morpha, Mon 3 Jan 2011, 20:29.

Crush: Pontiac Firebird Flag Car
Drive: Ueli Anliker SLR Mclaren (although it really is an abomination, no argument there)
Live: Gembella MIG-U1


----
Toyo Supra MKIV
Mitsu 3000GT
Nissan 300ZX

Some of these mods, instead of modifying existing values, inject foreign code, allocate additional memory, etc. I figure that's what the AVs react to

Quote from Boris Lozac :

The hell is that?

It's a Tauntaun.

Can't quite believe someone actually recorded a video of this, but here you go.

Just for the record, if you'd bothered for a minute or so, you would have found out yourself. There are many ways to do it and most of them are painfully obvious.

E: Not to mention you could have googled for it.

A unique identifier is one thing, but I think what Dygear has in mind is an abstract button class with, among others, an update method. You wouldn't identify the button by a string or integer, but by the reference to the associated object.

Get WinRAR, or better yet, 7zip and extract the archive. It probably contains a complete "User Files" directory, which you're supposed to put in CSR's directory, i.e. where the CSR.exe resides.

Definitely, but PRISM should never send BTNs with invalid dimensions to the InSim host. It should keep a list of buttons with all their parameters and always send the complete BTN, the packet size remains the same so it really doesn't matter.

The added advantage is that PRISM can determine if it's actually necessary to send a button at all, which is particularly useful with high frequency triggers like MCI/CompCar at 50ms/20Hz. For example, if the application is to send the yaw angle as integer, it's likely to remain identical for several packets in succession, so sending the button again would be a complete waste of bandwidth and CPU cycles.

A sendButton() function/method would therefore check the provided BTN against the list of stored BTNs, compare BStyle, dimensions and Text and only send the new BTN if something's changed. It could also allow for a simple text update, like sendButton(ClickID, newText);

Quote from CrAZySkyPimp :

Actually the average age according to LFSWorld is 25.38.

Based on the (potentially incorrect) birth dates provided by the users themselves, besides, very few actually provided a date at all.

ws2_32.lib (WinSock2)

this would have been a good place, it must have shown up when you entered the thread title.

docs/InSim.txt

Read it and solve these simple issues yourself. Surely you must be able to, your signature reads "Insim Developer" after all.

These "Hoodrides" enjoy increasing popularity for their distinct visual appearance... I fail to see the appeal, I'd hate to get rust on my hands everytime I touch just about any part of the car, not to mention the damage to the surface, and eventually substance.

Quote from E.Reiljans :

How wind could be random on every replay load, considering it affects car physics? Wouldn't that cause OOS?

Perhaps it's not the wind itself but the animation of affected objects. I don't know what's behind it, I just know that I ran a pass, closed LFS and did something else for a while, launched LFS and ran a second pass of the exact same replay file, the shots were perfectly identical except for the flags.

Quote from wheel4hummer :

The Mazda K-series engine (The V6 in the MX6, and some other vehicles) is non-interference. But aside from that I don't know of any others.

I know that all Supra engines, 4M through 2JZ, are non-interference, except for the VVT-i versions of the 2JZ. I've also read that the entire Toyota VZ engine family are non-interference designs.