I've never ever been a cruiser, but the idea of a cruise control mod came up on the forums way too often for me not to try to make one. I'm indeed running Arch (nice job spotting the "A"). Using virtualized Windows as a development system is a bit of a pain in the ass, but I still consider it a better solution than dualbooting. I've got too accustomed to KDE4 desktop goodies that I can't really work effectively in Windows anymore. (plus there's no better LaTeX editor than Kile)

I intercept DirectInput calls using a proxy DLL and I run a "helper" InSim/OutGauge app which talks to the DLL through a shared memory. Wiki pointed me to a good looking article explaining the basic PID magic, I'll definitely share at least the throttle controller logic if I get it working reasonably enough.

I've been aching to give this a go for quite some time and today was the day The video below show a cruise control mod that works with any analog controller. The actual speed control algorithm is rather dumb and it the speed is oscillating quite a bit in powerful cars, especially in uphill sections. However, getting it right shouldn't be a problem once I get my hands on some info about PID controllers (by any chance, anyone of you guys wouldn't know about anything, would you? ).

Before someone asks, no, I'm not releasing it - at least not now. If I ever manage to get the throttle position maths right, I'll talk to the mods here to make sure there's no way somebody could use this to cheat. If all goes well, I'll make a public release eventually.

VIDEOS REMOVED, see the post #6

Last edited by MadCatX, Thu, 1 Mar 2012 19:16. Reason : Videos removed

Good, thank you.

I believe I fixed a rather tricky bug in the network code, everything should work fine now.

EDIT: Reuploaded to fix yet another possible issue
http://dl.dropbox.com/u/37342755/WinAmper3.7z

Last edited by MadCatX, Thu, 16 Feb 2012 17:44. Reason : Reuploaded

LOL'd at Yoda

I just realized something. If RawCap is returning an empty file, it's probably just not capturing anything. Make sure you're launching it like "RawCap.exe 127.0.0.1 dump.pcap" and try to run the cmd prompt as admin. Windows is unfortunately rather useless for network debugging...

CTRL+C usually works.

Wow.. apparently Wireshark cannot capture the loopback interface on Windows for technical reasons, the only other alternative that is said to work is RawCap (http://www.netresec.com/?page= ... ffer-for-Windows-released). I need the loopback capture because this is where all the InSim communication takes place.

I suggest you remove the previous log from the forum as it contains all your network communication, someone might use it to retrieve your login passwords and stuff from that.

Quote from S.E.T.H :

i am telling it once for last time. it kills realism and brings unfair advantage. simple as that.

How can it be an unfair advantage when everybody is free to use it?

Let's say I have a G27 racing wheel and I set my steering lock to 60 degrees, so I can countersteer ultraquickly and use nonlinear steering to compensate for the oversensitivity. It also kills realism and gives me a really unfair advantage (not everyone as a wheel with adjustable steering lock), should such racers be banned or something too?

Quote from S.E.T.H :

pfff kids around who calls the other ''stupid'' or ''idiot'' when run out of arguments. im sorry where did i say i cant have fun if i am not the fastest?

You indirectly implied it by this

Quote :

i'll not use unrealistic F mode and like i said i rather leave than to be forced to play with this mode.

and this

Quote :

i know i will be forced to use force mode when i am slower, or when if i do a fast lap, i will need to improve it force mode on.

for instance.

Quote :

nobody tells me why should not the developers remove it. if its only for setup building like all of you said, make it available on setup environment. and let people do hotlaps without force mode.

So far you haven't been able to come up with a reason why they should remove it (except that _you_ are faster with it).

Quote from S.E.T.H :

im just faster with it. but i still dont want to use it, i am not having fun.

Don't use it then. It's as simple as that.

OK, I'm outta here, it's become rather dull... I'd like to see this nominated for the thread of the 2K12 though (considering we're only half way through February, the nominations might get sorta though this year )

Last edited by MadCatX, Wed, 15 Feb 2012 13:17. Reason : Quote fail

Quote from S.E.T.H :

i'll not use unrealistic F mode and like i said i rather leave than to be forced to play with this mode.

I hate to say this, but do you realize what kind if idiot you are? You're acting like the force view was the only trick you could use to be faster. There are much more effective tricks and people regularly use them. You're also saying that if you can't be the greatest and the fastest, you can't enjoy the game... with this kind of attitude I guess you could apply to McLaren F1 as Hamilton's replacement.
Seriously, either get over yourself or leave.

Quote from S.E.T.H :

i know i will be forced to use force mode when i am slower, or when if i do a fast lap, i will need to improve it force mode on. because people always want more. there is nothing prevents you from using it and doing fast lap time if you are already using things like insim or outgauge or something. then it will become a necessity to me, then i'll swear to the new guy who says it must be removed and it kills reality.

So basically you're advocating the usage of cheats. There's nothing preventing from using other hacks which are much more effective than a different view mode, does it mean you will have to use them too to get a better laptimes?

Quote from S.E.T.H :

i was 0.2-0.3 sec faster each lap, and much better in races myself.

Which still puts you some 2 seconds behind the WR, how is that for an frikkin' aid?

I still fail to get it, if you think you're better off with the force view mode, then just use it and stop making a douche out of yourself. I've never heard anybody complaining about people who use like 90 deg steering lock to drive fast laps which is about as much unrealistic as non-cockpit views. In older patches there was a "high-nose" aero bug, etc. etc....

This is a video game, people _will_ always take shortcuts in video games, they _will_ even cheat and lie about it. I have yet to see a game where the real pro's aren't using all sorts of tricks which take a lot of fun out of the game but make you more competitive. Welcome to the universe of digital entertainment.

Oh come on now. There are much more legal-ish cheats people use to get insane hotlap times, the uberfast clutchbutton script, ridiculously low steering lock, setups that won't last for more than a lap, you name it...
Even online you can use InSim to write all sorts of "assistance" apps, the most die-hard cheaters can use info from OutSim and OutGauge to create traction control and ABS hacks and there is no way you can prevent that - should we remove InSim and OutGauge too?

Honestly, the force view mode is nothing compared to what can be done and what some people really do.

Just start logging on the loopback interface and apply "tcp.dstport == 29999 || tcp.srcport == 29999" as filter. When you get disconnected, you can save the log as pcap and upload it somewhere.

Quote from S.E.T.H :

... i was always wondering why people were faster, and maybe that is the reason...

Nailed it!

Seriously now, people will beat you on the track, LFS is 10 % natural skill an 90 % learning. If you're slower, I can guarantee you it's not because of other racers using this kind of "cheat". Force view is a fully legitimate and justifiable feature people use to create and tweak setups, unless you have I better idea, I don't see why should it be removed...

So... the guys has driven slightly over 1000 kms online, probably got his ass kicked and now he's looking for an excuse why? This kind of threads is always a smile on the face of my day

I'd certainly like to be sure there's nothing wrong in with the InSim communication before I suggest any sort of experiments. It'd be great to have some better feedback than just yours...

The less invasive method would be for you to download Wireshark and log all communication on port 29999 to see if all the packets are getting through.

This is something I wouldn't expect to fail as it's just a DirectInput call handled by DirectX. It worked for me with Logitech devices, perhaps some other manufacturers' drivers might have a problem with "CooperativeLevel.Background | CooperativeLevel.Exclusive" which IIRC is somewhat out of DX specs (although it works for me:shrug

Quote from e2mustang :

Anyway,i have 4 memory sticks,what should i do?

If possible, get a completely different memory stick that's 100 % known to work elsewhere and put it in instead of your 4 sticks. Even though I doubt it's the RAM, it's something you can test pretty easily so I guess it's worth a try.

MB is way too complex piece of electronics to either just work or don't work. For instance, operating system doesn't do direct BIOS calls to handle device communications, so when Windows loads, the messed up pathways might not be in use. I'm just guessing here, but when your MB has problems booting and complains about incorrect voltages and stuff, it's its way to tell you it's about to give in for good.
Other likely possibility is of course a faulty RAM which you can test very easily by borrowing a stick from someone, but my bet is still on the MB.

LFS sends a keep-alive packet each 30 seconds to check if an InSim guest is still there. It's been my understanding that LFS always wants a reply to this packet regardless of any other communication. I kept Winamper running for about 40 minutes and it was working fine. Your networking stack appears to be seriously messed up.

Seriously man, I suggest you stop driving yourself crazy over this and get a new MoBo. The kind of errors you're getting point to a fried MoBo more and more...

Are the drivers installed correctly? Can you access the wheel's properties like FFB strength and range via Control Panel? Your wheel is apparently not being initialized properly by the Logitech drivers, I've never figured out why this happens, but usually a reboot and clean driver reinstallation worked for me. If you still can't get it working, it would be a good idea to try the wheel in another PC as there's a slim possibility of the wheel being faulty.

From the top:
r0: y = kx + q
y = tg(beta)x + q
q = - distance from camera (DFC)

x = DFC / tg(beta) (windscreen is on the X-axis, so Y is 0).

I hope you get where I was going with this. I suppose it should work as long as you're working only with points in 2D space. (You could do the same for height to move the button up and down on the windscreen)

Thinking only in 2D and assuming that you want to project a position of an object on the windscreen (a sort of a HUD if you will), what you need to do is something like this. (the green line is the windscreen width, the "+" is the object's real position and the diamond is where the object has to be projected). I didn't have time to fire up LaTeX and GNUPlot, so my terrible handwriting will have to do for this time (sorry).

Every BIOS is different, you'd better check the motherboard's manual - it's usually possible to google those - some BIOSes don't offer any OC'ing options at all.
More to the point, why do you want to OC it? I used to run W2K on a 1 GHz Coppermine and although the user experience wasn't that of a blazingly snappy system, I used it as a IM chatter, music player and web browser quite happily. That CPU and MB is going to be pretty worn out anyway so the chances you'll be able to get it running reasonably faster are kinda slim anyway. 833 P3 should handle the music server workload just fine if you strip it off any unnecessary services.