thelusiv Wrote:Isn't the FMOD stuff intended to be distributed with the source and binary packages? I had to download it here and put the files in fmodapi374linux/api/inc/ in VDrift/include/ and fmodapi374linux/api/libfmod-3.74.so in /usr/lib/.
I'm not sure *how* it's intended to be distributed; I couldn't find any info on the site. I have gentoo and just emerge'd the FMOD package, and it put everything in my include and lib paths. I guess I'm supposed to include the library in the distribution, for people to copy over to their /usr/lib??poirus, your problem is probably due to me not packaging FMOD correctly. The "couldn't load sound" errors happen if the FMOD load function return an error.Also, chris, about the curb pieces looking like they're missing, can you send me a screenshot or two? I'm not seeing it.I'll look into the replay crash at 100%. There's no time limit, it's a data limit, arbitrarily set at 800 kb. Each time you move a control to a value that's different than what it was before (which is checked roughly every 2 ms) a 16 byte packet gets added to the replay file. The playback % is based on the time and not the data, however.Skew isn't actually implemented properly yet, I just have Vamos' old (buggy, incomplete) skew implementation. The xml file actually initially had that skew, and I complained to Sam about it and he said to take it out until he finishes skew. So, once I get around to adding skew into vdrift I'll put it back into the track file.