SiMPLE | Forum

Sorry, I meant everyone will understand what it was you meant! Wow, it's working already!

If you want spaces, try using quotes.

game.addPlayerToBuddyListByName "Danny Devito"

I think rememberExcessInput is just for mice. It allows the control surface to remain at full deflection while the mouse is picked up and moved back.

The amount of time it takes to swing a joystick can definitely be significant. If we look at the spitfire's roll controls:

There's a rotation range of the control surface of 60°. The maximum rate you can deflect it is 120°/s. So It can be deflected from full roll right to full roll left in 0.5s. If it takes you longer than 0.5s to move your joystick from full right deflection to full left deflection, a smaller joystick would help. Larger flight sim joysticks/yokes and rudder pedals fit into this category. I'm pretty sure setMaxSpeed is in degrees/sec, but it wouldn't hurt to check that in game.

You are certifiably insane. The client is merely sending movement packets to the server. So long as the server receives the movement packets, all will be fine. If more than 3 are dropped in a row, you'll start to lose throttle and your plane will slow down. Dropping 3 movement packets in a row is a sign of a really shitty connection, a shitty overloaded system, or both. You can turn netstats on to see how you are doing in this area. All the stuff you are seeing is placebo.

The plane control surfaces have a maximum response speed. It's pretty "slow". You can check it out by using the external view. So long as your control, whether it be keyboard, mouse, or joystick, can outpace the maximum response speed, you're fine.

See:

http://bfmods.com/mdt/scripting/ObjectT … Speed.html
http://bfmods.com/mdt/scripting/ObjectT … ation.html

And again, if you're on a shitty connection and drop movement packets, you won't be able to deflect as quickly.

game.packetDropRatio is only for debug. It randomly drops a percentage of outgoing packets which is almost never what you want.

You need an AC line splitter to use a power clamp, since total current through neutral and hot is zero. At that point it's much easier just to get a plug-in watt meter (such as Kill-A-Watt).

Get off my lawn

https://www.youtube.com/watch?v=dfZ_OhwHGhY

bfsmd is linked with a super ancient version of libproc, and it uses it rather poorly. That's where the "Internal Error!" comes from. I don't think it effects the functionality though.

2.01 is a late (2007) release that was sponsored by clan MOW to fix a few issues. There were a bunch of 2.0beta releases so the last 2.0 release (2005) is titled 2.0final.

Here's a detailed paper that describes the BF1942 networking model: https://archive.org/details/tribes-networking-model

The only major difference is that the Datablock manager is replaced by static data that is verified to match on the client and server.

BTW, the new server must be at a really good hosting center, connection is rock solid:

--- 163.172.13.221 ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14018ms
rtt min/avg/max/mdev = 142.085/142.671/143.661/0.646 ms

These binaries have symbols, neat!

Codename Eagle, duh

https://www.youtube.com/watch?v=uYNbTC5EPv8

Your original ban still stands as discussed.