Page 3 of 3 FirstFirst 123
Results 21 to 29 of 29

Thread: CoD2MP_s.exe Slow Start

  1. #21
    Global Mossaderator Mitch's Avatar
    Join Date
    Nov 2012
    Posts
    654
    Thanks
    204
    Thanked 450 Times in 305 Posts
    i just set com_hunkMegs to 512 and it increases the load time of cod2 a lot. So keep com_hunkMegs on the default 160.

  2. #22
    Private
    Join Date
    Feb 2014
    Posts
    10
    Thanks
    2
    Thanked 2 Times in 2 Posts
    Quote Originally Posted by kung foo man View Post
    Well, final solution was -> .exe -> Properties -> Run XP Compatibility mode, as IzNoGod figured out, but r_gamma isn't working then

    (Just saw some guest in here searching obviously for solution)
    Same problem here with Windows 8.1. (DirectX7 and ATI HD4850)
    Call of Duty 2 in running compatibility mode caused noticeable lags in mouse movements, and the r_gamma isn't working too
    Solution for me: Come back to Win7 x64

  3. #23
    Assadministrator IzNoGoD's Avatar
    Join Date
    Aug 2012
    Posts
    1,718
    Thanks
    17
    Thanked 1,068 Times in 674 Posts
    Heres a fix for cod2 on win8+

    Use cod2fix.reg and one of the items in the winfixes folder (choose your appropriate scaling percentage)

    Fix based on:
    http://donewmouseaccel.blogspot.nl/2...ation-fix.html
    and
    http://support.microsoft.com/kb/2908279

    Good luck

    Edit: after applying the registry fix, execute the following command:
    Code:
    Rundll32 apphelp.dll,ShimFlushCache
    Then, reboot your pc
    Attached Files Attached Files
    Last edited by IzNoGoD; 25th December 2014 at 22:47.
    "Does not work" is an error report for a bug between keyboard and chair.

    All hail Artie Effem

  4. The Following 2 Users Say Thank You to IzNoGoD For This Useful Post:

    kung foo man (26th December 2014),Mitch (26th December 2014)

  5. #24
    Global Mossaderator Mitch's Avatar
    Join Date
    Nov 2012
    Posts
    654
    Thanks
    204
    Thanked 450 Times in 305 Posts
    The problem lies somewhere in the DirectDraw emulation in Windows 8(.1).

    http://answers.microsoft.com/en-us/w...dd38825?page=1

  6. The Following User Says Thank You to Mitch For This Useful Post:

    kung foo man (26th January 2015)

  7. #25
    Private
    Join Date
    Nov 2018
    Posts
    24
    Thanks
    1
    Thanked 8 Times in 7 Posts
    For me fix was simple. I just connect my headphones through jack or USB and then i just enabled mix stereo.

  8. The Following User Says Thank You to Prawy For This Useful Post:

    kung foo man (19th January 2021)

  9. #26
    Private
    Join Date
    Apr 2020
    Posts
    66
    Thanks
    28
    Thanked 14 Times in 13 Posts
    I had the same issue with windows 10. It got solved when i set the compatibility settings as shown below. No problem with fps draw either.
    MmYDtxMQkn.png

  10. #27
    Global Mossaderator Mitch's Avatar
    Join Date
    Nov 2012
    Posts
    654
    Thanks
    204
    Thanked 450 Times in 305 Posts
    There is a patched version of 1.3 that solves the black screen issue: https://cdn.discordapp.com/attachmen...-LuKeStorm.rar
    I haven't had any issues with this patch and i'm able to run it without compatibility settings on Windows 11.

    https://steamcommunity.com/app/2630/...8242389390014/

  11. The Following User Says Thank You to Mitch For This Useful Post:

    raphael (30th July 2023)

  12. #28
    Assadministrator kung foo man's Avatar
    Join Date
    Jun 2012
    Location
    trailerpark
    Posts
    2,010
    Thanks
    2,102
    Thanked 1,084 Times in 753 Posts
    Quote Originally Posted by Mitch View Post
    There is a patched version of 1.3 that solves the black screen issue: https://cdn.discordapp.com/attachmen...-LuKeStorm.rar
    I haven't had any issues with this patch and i'm able to run it without compatibility settings on Windows 11.

    https://steamcommunity.com/app/2630/...8242389390014/

    Nice, seems legit, byte compare for 1.3:
    Code:
      arr[0x33ee0] = 0xc3; // was 0x51
      arr[0x33fc2] = 0x90; // was 0xe8
      arr[0x33fc3] = 0x90; // was 0x09
      arr[0x33fc4] = 0x90; // was 0xcb
      arr[0x33fc5] = 0x90; // was 0xfe
      arr[0x33fc6] = 0x90; // was 0xff
      arr[0x65190] = 0xc3; // was 0x6a
      arr[0x65191] = 0x90; // was 0x00
      arr[0x65209] = 0x90; // was 0x74
      arr[0x6520a] = 0x90; // was 0x66
      arr[0x664cd] = 0xeb; // was 0x75
      arr[0x664ce] = 0x2d; // was 0x06
      arr[0xb3b7c] = 0x90; // was 0x75
      arr[0xb3b7d] = 0x90; // was 0x09
      arr[0xb8dd0] = 0xc3; // was 0x55
      arr[0xb9569] = 0x74; // was 0x90
      arr[0xb956a] = 0x0b; // was 0x90
    timescale 0.01

  13. The Following User Says Thank You to kung foo man For This Useful Post:

    raphael (30th July 2023)

  14. #29
    Private
    Join Date
    Jun 2013
    Posts
    70
    Thanks
    20
    Thanked 32 Times in 26 Posts
    to fix the problem all you have to do is to enable stereomix in the record setting in windows sound settings
    Last edited by vanfreddy; 4th August 2023 at 22:20.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •