iboomboom

Ah, I misread. You hacker.

You know, I have done something and if that fixes it. Then enjoy. Your ping should come back to what it was too.

You use a software crosshair overlay? And you get stutter when the overlay is active? Press Enter to select a class.

Thank you for giving me the contact info for some of the CoD4x devs, I will reach out to them once I get some breathing room.

But why are you the only Dutch person having this issue. Why not other people from the same or nearby region? I am wondering what are the differences. Cod4x client version, ISP, PC, Rotuer? Queenie has issues too, on both servers.

COD4x Server Address 74.91.119.86:28960 I want to thank everyone for their patience in playing on the CoD4x server and suffering thru the crashes and reboots. I care deeply about our clan and everyone I play with, hence, my motivation to dedicate my time and put in the effort to make this happen. Retrospect When we first launched the CoD4x server it was on a managed NFO server, meaning all the server controls are with NFO, just put the mod files in there. The server was crashing due to fundamental changes in how the CoD4x code is re-written and how our mod handles player data. We had no way of figuring out what was wrong since we had no control over the server's internal behavior. I decided to launch the CoD4x server on a dedicated machine where I had absolute control over the server process. I recompiled the CoD4x server code and launch binary after binary. Each iteration informed by the logs collected when the server crashed. On the Linux machine I was able to capture the exact behavior of the server and put guard rails against crashing, but didn't address the root-cause. Until now. I have strong confidence in the latest deployment that I have addressed the root-cause of the crashes. A bug in memory handling that becomes bigger and bigger as people join and leave the server. When a map changes it causes corruption and crashes the server. It took all of this to get to the bottom of this problem. The work arounds I put in, would delay the inevitable and one of the work arounds had a sever-side side effect. People with lossy connections @Icequeen@Dukoo @P1nh3ad or well high ping, would experience stuttering, this was real, caused by the bug, but made worse by the work around I put in to keep the server from crashing right away. I am confident that you will not experience this anymore. If you know programming, I had to patch the disassembly of the stock COD4 server and recompile the CoD4x server code. Our mod does a double free of player data. This happens on the stock server too but the stock server is single threaded so while it never crashes it starts becoming laggy the longer it stays on. We change rotations every Friday so a server restart would clean the slate. The CoD4x server launches multiple threads, and does things in parallel, when the mod's code would try to delete player data upon disconnect, it would do that more than once in CoD4x, this would poison the memory heap. The only solution was to block the call in the server code. CoD4x automatically deletes all the pertinent player data on disconnect, the mod doesn't need to send that command in the script. This is in essence a two-part fix, put a check in the server code to don't let the memory get poisoned then remove all the player data delete from the mod's scripts/code. At the moment, I don't have the mod's source code so I did the only and the best thing I could. I hope the server's clock-work like crashes are behind us and all my hard work and sleeplessness has paid off. There will still be small things here and there but we will address them as we go. Thank you for reading and happy gaming.

Cod4x client replaces your binary and places some dlls in your games folder. It's a community driven open source project. It was created by people who love COD4MW and wanted to address its short comings. They disassembled the original binaries and then recompiled with the re-worked network stack, bringing modern updates to an old game. Hope this helps.

CoD4x client behaves differently. It communicates with the server securely and are handled in a bit more standardized way. The original doesn't support ultra wide monitors. The image is just stretched. This may or may not be desirable. A stretched image also changes the hit markers perception.

Hit enter, this was happening to me on my wqhd monitor with the wqhd resolution. Lower it to 2569x1440 and then ESC key works fine.

This is a stock map, also, which server are you trying to connect to?

Bert_987 @Bori @JOMAMA @Nemesis @snakepliskin @Sourtap If you guys can try this server 74.91.119.86:28960 that would be great, your clients were sending the error prone packets.

If you are having issues or still do not have COD4x Client installed visit this server. It will prompt you to download the files. While I sort out the issues with the managed COD4x server on NFO. We have an alternative COD4x with the same mod here. 74.91.119.86:28960 This is running on a dedicated server, and I am hoping it doesn't have the same crash issue. This is NOT the official new server. If you would like to help us please Favorite this server and play when you can.

Folks, While I sort out the issues with the managed COD4x server on NFO. We have an alternative COD4x with the same mod here. 74.91.119.86:28960 This is running on a dedicated server, and I am hoping it doesn't have the same crash issue. This is NOT the official new server. If you would like to help us please Favorite this server and play when you can.

This crash produced the log that has helped me figure out the root cause. It's connection attempts from people with improperly installed clients that are causing the server to allocate obscene amounts of memory and NFO kills the server because its spiking CPU usage. I have applied optimizations to the server to guard against it. Once we have people successfully rolled over to COD4x client, the crashes will go away. I will be talking to our host as well.

Bori why are you trying to launch a server? I think you downloaded the server not the client. Please launch the multiplayer game.

I'll play around with my other monitors to see what I get. I do recall I had to set my ratio to 1:1 on my 16:9 4k monitor. On WQHD I had the same having to press enter issue I'll try to recreate and then recall what I did to fix it.

Such a drama queen.

Ah, try hitting ENTER key. I have run in to this in the past. I uninstalled and re-installed C4x for this to work.

This is what I would expect, and yes it supports WQHD monitors properly.

No admins online? I will look in to what's causing this.

For those who have older PCs with Windows 7 please do the following: Install https://aka.ms/vc14/vc_redist.x86.exe Download the attached zip file Decompress it inside the game installation folder and run install.cmd cod4-client-manualinstall_21.1.zip

@JOMAMA I added you to a PM, please read the last few messages. Also, can you install all of these? https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Your monitor has an OSD, go to picture settings and make sure the ratio is 1:1. If you tell me the model, I can look up the manual for you.

Can you elaborate a little bit on this. What happens? Also, try joining without the patches just uninstall them using the manual uninstaller here: http://74.91.119.86/cod4xclient/cod4xclient.zip Unzip the directory in your game's installation folder and then run the uninstall.cmd. Then just join the server and see if you can connect. If not, try the install.cmd file. The automated installer may not be working well for older OSes. Also, did you install all the redistributables?

I think you are referring to the restart that I announced on the server, perhaps a few moments before you joined.