talking about corners, i've come to the conclusion that it comes down to straighten out every corner.
that's done by wide-in, hit the apex, wide-out.
the small differences that give you extra controlled speed during these corners are mostly unknown to me yet.
interesting piece of work...
found this myself believe or not, problem was to assign the mouseX to steering, since it is just grey (not clickable no nothing)...
so how did you accomplish that?
or am i just to impatient?
Forget it... guess what just happened
Ok, got them together, (a bit fiddling thou but this will get better in time) now all i need is some device that makes my ass shake (for knowing when the rear is on an overtake-attempt)
or sth else FF capable...
now i can understand all you wheel fanatics, controlled throttle and brake is a "must-have" for besttimes
i have a copy, but it's not fun running it with winNT 5.1 since the sound is crippled and crackels all trough the game.
this happend on all kinds of audio A/D converters. onboard/plug-in cards.
it's around 30MB zip file now, i can mail it in 5MB pieces...
pm me if you want it...
IF he's referring to post #6 then i don't get it...
take a look around there are many "crackers" with rev-engineering abillities.
it's THE abillity to understand code from other people.
you can't rebuild/recreate what you don't understand in the first place.
and therefore you can program your own "track-layouter" if you understand the concept of data organization in these *.lyt files.
to think that you actually need lfs for creating your layouts is just d***.
well ok i see it's quite pointless to change the mesh, as it's really easier to apply the dirt or raindrops via a meterial layer.
So this leads me to the question how to define that mat. since cinema has no V-ray plug-in, or i didn't found it yet.
so please help me XCNuse.
me uses 2mbit/s for dvd archival since i'm too lazy to switch discs for watching a movie.
1,2Mbit/s for quarter-sized (384*288 -black bars) analog tv recordings (due to very little picture snow)
combined with v-dubs internal "temporal smooth" filter @ level2
well then how about using longer names filled with "spaces" and a "*" at both sides since the names are usually shown earlier as the car model?
as an aditional hint next to honk and engine sound of other cars...
in comparsion with others (flac, wavpak, shorten, etc...) best compression achieved at "high" theres an "insane" level wich makes your files even a bit smaller but decoding takes twice as long then.
monkey's audio is a math-correct-reversible-enocoder.
Means what u put in, comes out 100% exactly the same. (try md5 hashes)
before, and after encoding/decoding cycle.
has error detection (wav hasn't).
Only reasonable if a certain music addiction was detected
otherwise use vbr mp3 encoding from 160 to 192 kbp/s
but it uses way to much bitrate due to outdated encoding tech.
imagine a bouquet of 4 diff channels sharing 18Mbp/s, when 2 of them show footballgames, racings and the other two a fast movie (many scene changes, rushed cam movements/zooming).
besides dvb-t/s/c looks AWFUL in direkt compare to dvd encoding wich is actually slightly different, thats why you can't easily dismantle the recorded-TS.
The bitrate is nearly the same but looks bad.
i've seen digital broadcast from other countrys and some are doing a way better job...
mx-5 miata mk II
tank leopard II (against park-fines) [hrhr try to hook that one up]
tank t-90
some stretch
s-ton (merc) (for mid-range travelling)
rx-8 (drift attempts)
supra (the one from nfs-u II)
some old army jeep (camping)
a taxi+driver (for lazyness)
some nice 650cc motobike (for trafficjams)
well, yes...
(i know tanks aren't cars, but i want them)