It's been a long while since I touched Java, but the basic principles should be universal. LFS indeed can and will send multiple packets in one burst, you just have to deal with that
In my C(++) tools I something of this sort
char buffer[SIZE];
ssize_t bytes = 0;
while {
bytes = recv(sock, buffer + bytes, SIZE - bytes, 0);
while (buffer[0] <= bytes) {
handle_packet(buffer);
bytes -= buffer[0];
memmove(buffer, buffer + buffer[0], bytes);
}
}
I wrote the code off the top of my head so do check if it's correct
It can also be further optimized by doing memmove() only when all complete packets are handled.This is an easy fix. Just turn your wheel from lock to lock and LFS will calibrate the steering properly. Same goes for pedals.
That should have no effect unless you put LFS on a different drive, than it might make a difference in certain cases, particularly when you're very low on RAM and your system is forced to hit swap a lot.
@General Lee
This might be related to some process triggering a resource-heavy action. You might want to go through the background tasks and check if kililng any of them fixes the problem. Is there any HDD activity when this happens? How long does it take until the framerate returns to normal?
What? Did he use his ImperialDroidNet as a packet generator? Or does the first D in DDoS stand for "Darkside"?
On a more serious note:
It looks like the websites are back online, nice job! I think that most server admins would appreciate a technical report about this incident and what actions were taken to get it sorted. If there is anything interesting about it, would you mind, Victor?
Are you aware that although DDoS is technically a crime, it is next to impossible to prosecute anyone for DDoSing? The attacker himself doesn't even have to take part in the packet flood generation. DDoS attacks are done through botnets that usually consist of compromised computers - if you were to prosecute owners of the attacking machines, you'd go after innocent people who just happened to be stupid enough to click on a bad link they got through Facebook or something. Being stupid is bad, but not illegal. There is also no law that would oblige you to secure you computer so in couldn't be abused by hackers - frankly, that should be the responsibility of software vendors to at least some extent.
The only way how to prevent or at least reduce the damage done be DDoS is by using correctly configured machines both on part of ISPs and service providers.
This is exactly what emulators do, but they do it on the fly. The problem with this is that there is no direct 1:1 translation between x86 instruction set and the instruction sets used by console CPUs. The process is somewhat similar to translating texts from one human language to another - you don't translate word by word, you rather extract the meaning and express it in a different language. This is one of the reasons why you need a top-notch PC to nicely emulate ancient PS2. There is also a problem with graphics acceleration, sound and input interfaces which you have to simulate via DirectX on Windows...
I'm sorry mate, but are you talking about the same show? Spartacus is a lot of gore and tits on the surface, especially in S1 and the prequel, but it's not like it's the only thing it has to offer. Have you not noticed the very well written characters? Spartacus is one of the few shows where I actually like and feel for the villains just as much as I do for the heroes - from their perspectives they're all doing the right thing and the story captures this very well IMHO. Battle and sex scenes don't drive the series, it's the storytelling and various subplots that does. If it wasn't for all the sex and brutality, it would have probably been a bit boring to watch sometimes, I'll give you that. However, if it wasn't for the characters and the rather new take on the whole Spartacus story, I wouldn't even bother finishing S1.
Special points for anybody who cracks the password and finds out whatever crap he put in there
Have you tried anything to resolve the problem since you last posted in that thread? As it's been explained the that thread, it's most likely your ISP blocking certain UDP communication - you should take it up with them.
Last edited by MadCatX, .
Vista and XP have a totally different installer. It wouldn't hurt if you told us what exactly are you and how.
Either you have selected a wrong boot device or the device you're trying to boot from is faulty. Whatever the problem is, it is NOT in ANY way caused by Windows 7.
Just create a WinXP installation CD from an image, that will work as long as your CD drive is OK.
Step 1) Make a Windows XP installation medium (most likely a CD)
Step 2) Backup all valuable data you have on your system disk (the one with Windows, most likely C
Step 3) Boot from the Windows XP installation medium
Step 4) Tell the installer to format the system disk
Step 5) Proceed with the installation
Step 6) Realize that Windows 7 can be almost as fast as Windows XP if you turn all the unnecessary bells and whistles off
Step 7) ... (profit usually goes here) ...
Step 2) Backup all valuable data you have on your system disk (the one with Windows, most likely C
Step 3) Boot from the Windows XP installation medium
Step 4) Tell the installer to format the system disk
Step 5) Proceed with the installation
Step 6) Realize that Windows 7 can be almost as fast as Windows XP if you turn all the unnecessary bells and whistles off
Step 7) ... (profit usually goes here) ...
There appears to be a bit of a confusion about what HW you need to run LFS. The short answer is - ANY today's hardware will run LFS just fine. A Sandy Bridge i5 laptop with Intel HD3000 GPU runs LFS at 1600x1200 32bit, 4xAA, 8xAF and with 11 AIs on track at 20+ FPS at all times. You have got to realize that LFS does not use any of the advanced rendering technologies that stress modern GPUs. There is no realtime lighting, no volumetric shadows, no pixel shaders nor tessellation. Really, there is nothing for the GPU to do. Cranking up AA and AF might push some low-end GPUs but that's about it.
LFS used to be CPU limited back in the days of single core P4s & co. Physics of all visible cars is calculated on the CPU (obviously). AI cars are even more taxing because their physics has to be calculated even when they are not visible plus there is all the AI logic processing.
If you are having performance problems with LFS on a gaming grade PC with current hardware, there is something wrong with your machine. CPU might be overheating due to clogged fan, worn off thermal grease or incorrectly installed heatsink. Overheating CPU will throttle itself down by lowering its speed or executing "empty" cycles. The drop in performance can be quite huge, easily over 50 %. Bad drivers are another common issue; I once had a dodgy sound card driver that apparently used so much CPU time that my framerate in games took like a 500% dive. Some laptops use more aggressive power saving settings that trade off performance to save every single milliwatt of battery capacity. Passive cooling policy is a nice example: when it's enabled, CPU will clock itself down under load so that fans don't have to kick in to cool it.
I hope this busts some myths about LFS and its hardware demands.
LFS used to be CPU limited back in the days of single core P4s & co. Physics of all visible cars is calculated on the CPU (obviously). AI cars are even more taxing because their physics has to be calculated even when they are not visible plus there is all the AI logic processing.
If you are having performance problems with LFS on a gaming grade PC with current hardware, there is something wrong with your machine. CPU might be overheating due to clogged fan, worn off thermal grease or incorrectly installed heatsink. Overheating CPU will throttle itself down by lowering its speed or executing "empty" cycles. The drop in performance can be quite huge, easily over 50 %. Bad drivers are another common issue; I once had a dodgy sound card driver that apparently used so much CPU time that my framerate in games took like a 500% dive. Some laptops use more aggressive power saving settings that trade off performance to save every single milliwatt of battery capacity. Passive cooling policy is a nice example: when it's enabled, CPU will clock itself down under load so that fans don't have to kick in to cool it.
I hope this busts some myths about LFS and its hardware demands.
There is no Linux specific cruise mod. LFS_External based mods might run through Mono though, WINE is another possibility if you won't have any luck with Mono.
LFS generates sounds by writing into a memory buffer which is read by your sound card. Sound card loops over the buffer and plays its contents. LFS has to write into the buffer slightly ahead of the position the sound card is reading. Sound Lag sets how much ahead of that position LFS writes.
This is at least how it used to be before the big Vista compatibility patch. LFS has been using DirectSound instead of waveOut since then, but the basic principle probably hasn't changed.
This is at least how it used to be before the big Vista compatibility patch. LFS has been using DirectSound instead of waveOut since then, but the basic principle probably hasn't changed.
This should be fairly easy to do unless the application's code is an utter mess. I might be able to give you a hand with that...
I believe that we've tracked this problem down to a bug in Logitech drivers. I'll include a workaround in a next version.
Great, thank you for the test. Do I understand correctly that when the LED commands are being sent faster than 16 msecs apart, FFB dies? Does this happen regardless of which LEDs are on/off? This is however obviously a driver bug. I guess it has something to do with the way Logitech drivers queue hardware commands that are sent to the wheel because people were experiencing some odd FFB behavior even with the 1.0x series. It might be interesting to capture the USB traffic and see what is the wheel actually told do to.
Anyway, I'll reintroduce the command rate limit and make it configurable which would hopefully resolve this.
As you have a G27, you might want to consider reporting this to Logitech. I'm pretty sure this is something the have to either fix or at least make developers aware of.
It's good that you made people aware of an alternative, I guess not many players would figure out that Fanaleds has extended its support to G27.
My mod is aimed specifically at LFS and it's much simpler it its nature. It requires no actual installation and I believe it's as configurable and easy to use as Fanaleds.
Fanaleds is a great choice for people who play a lot of racing games and want to get as much out of their hardware as possible. There is also a technical difference between my mod and Fanaleds. Although my mod proxies dinput8.dll, it uses official method of controlling the LEDs. Fanaleds hacks around the necessity of proxying DirectInput calls by using HID API - you basically have two drivers fighting over the wheel. I'm sure you have tested this to make sure it doesn't cause any trouble, but I believe your users should be aware of this. If an incorrect hardware command is sent to a device, it can in extreme cases cause hardware damage.
Because the previous attempt to get to the bottom of this has been unsuccessful, I uploaded a modified version of the testing tool.
- It is now possible to set the delay as low as 1 msec
- The tool can now use DirectInput as well as raw access. DirectInput accesses the wheel in the same manner as the G27LEDs mod.
See the original post for download link.
- It is now possible to set the delay as low as 1 msec
- The tool can now use DirectInput as well as raw access. DirectInput accesses the wheel in the same manner as the G27LEDs mod.
See the original post for download link.
I believe that both the server and the clients must run the tweak with the same settings.
Is the server's LAN IP actually 192.168.0.1? Did you assign in a static address?
This is how it's done on a Netgear DGN1000. Note that people will be connecting to your server, therefore there will be incoming connections, but you set the rule for outgoing connections. This is incorrect as your router's firewall allows all outgoing connections by default, but blocks all incoming connections (which is pretty standard and secure behavior BTW).
It's impossible to give you any specific information when we don't know anything about your Internet connection; I assume the machine you want to host the server on is connected via a router which has a web interface for administration?
Some routers might not forward ports to machines which have a dynamic IP. If possible, adjust DHCP settings on the router and the server to assign the server a static IP. Also, port forwading requires you to input the destination machine's IP address. The screenshot you posted doesn't show the address, are you sure you changed the right setting?
Some routers might not forward ports to machines which have a dynamic IP. If possible, adjust DHCP settings on the router and the server to assign the server a static IP. Also, port forwading requires you to input the destination machine's IP address. The screenshot you posted doesn't show the address, are you sure you changed the right setting?
When you say server space, you mean a storage on a server where you can upload your web presentations? This is not enough to run a LFS server. You need at least a VPS to run LFS Dedi.
FGED GREDG RDFGDR GSFDG