Announcement

Collapse
No announcement yet.

The game Couldn't start

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • The game Couldn't start

    when i open the game i get it brings me back to the desktop and gives me this error



    ----- Client Initialization Complete -----
    Attempting 44 kHz 16 bit [Windows default] sound
    ----- R_Init -----
    Getting Direct3D 9 interface...
    Pixel shader version is 3.0
    Vertex shader version is 3.0
    Shader model 2.0 code path is available.
    Shader model 3.0 code path is available.
    Using Shader model 3.0 code path because it is the best available path on this hardware.
    Attempting 800 x 600 fullscreen with 32 bpp at 60 hz
    Game window successfully created.
    Using 2x anti-aliasing
    Creating Direct3D device...
    Com_TouchMemory: 0 msec. Using sum: 0
    Loading fastfile code_post_gfx
    Loading fastfile ui
    Loading fastfile common
    Initializing render targets...
    Requested frame buffer to be 24-bit color with 8-bit alpha
    DirectX returned a frame buffer that is 24-bit color with 8-bit alpha
    Initializing static model cache...
    Initializing dynamic buffers...
    Initializing particle cloud buffer...
    Creating Direct3D queries...
    Setting initial state...
    DirectX reports 256 MB of video memory and 567 MB of available texture memory.
    Using video memory size to cap used texture memory at 240 MB.
    Texture detail is set automatically.
    Using picmip 0 on most textures, 1 on normal maps, and 3 on specular maps
    Waited 16 msec for asset '$default' of type 'material'.
    Waited 4 msec for asset '$additive' of type 'material'.
    Waited 2 msec for asset 'clear_alpha_stencil' of type 'material'.
    Waited 2 msec for asset 'depthprepass' of type 'material'.
    Waited 2 msec for asset 'shadowcookieoverlay' of type 'material'.
    Waited 9 msec for asset 'shadowcookieblur' of type 'material'.
    Waited 12 msec for asset 'shadowcaster' of type 'material'.
    Waited 2 msec for asset 'shadowoverlay' of type 'material'.
    Waited 2 msec for asset 'cinematic' of type 'material'.
    Loaded zone 'code_post_gfx'

    ------- sound system initialization -------
    ------- sound system successfully initialized -------
    end $init 980 ms
    --- Common Initialization Complete ---
    Waited 105 msec for asset 'ui/menus.txt' of type 'menufile'.
    Loaded zone 'ui'
    Working directory: F:\SG\call
    ERROR: image 'images/~weapon_saw_spc-r65g65b65&wea~fbd00e22.iwi' is missing


    Couldn't load image '~weapon_saw_spc-r65g65b65&wea~fbd00e22'

    plezzzzzzzzz helppp

  • #2
    have you tried uninstalling and reinstalling the game? Be sure to back up any saved multiplayer data before you do this.

    Comment


    • #3
      i tried to uninstalling and reinstalling the game many times

      note:- the game never started on my pc.

      Comment


      • #4
        When a file like that doesn't load, that's often the sign of a corrupt install.

        If you've tried a few times and it has never worked, then there's a chance your disc could have a scratch on it or something that's preventing it from reading that sector when installing.

        You could try to have someone send you that specific file through email, and try to plug it into that directory yourself to see if that's all it is.

        Comment


        • #5
          The problem is i have already searched for the file in the game but i didn't find it .

          File name: weapon_saw_spc-r65g65b65&wea~fbd00e22.iwi
          Or : fbd00e22.iwi

          If any one found it plz send it for me.

          Comment


          • #6
            Found it. Here is where it is supposed to be located:

            Call of Duty 4 - Modern Warfare\main\iw_06.iwd

            Comment


            • #7
              Thanks but is there any programe that i could open with it this file.



              Thanks for your interest.

              Comment


              • #8
                Yes. The .iwd file is just a compressed file...if you change the extension to .zip, you can open it in WinZip, add/remove files, then simply rename it back to .iwd and put it back into the game directory, and it should work.

                Comment


                • #9
                  Nice idea Thanksssss.

                  Could you plz upload to me this file ~weapon_saw_spc-r65g65b65&wea~fbd00e22.iwi

                  Comment


                  • #10
                    I have no where I can upload it to...but PM me your email and I can send it to you that way. It's less than 700K in size.

                    Comment


                    • #11
                      I changed the extension into .zip then i try to repair the file as a zip then renamed the repair file from .zip to .iwd then i try to open the game it works:yay:.
                      thanxxxxxxxxxxxxxxxxxxxxxxxxxxx fo you helping

                      Comment


                      • #12
                        Awesome! It's a Festivus Miracle!

                        Glad it worked! Enjoy this awesome game!

                        ps. Save that file somewhere...you'll need it again if you ever have to uninstall/re-install the game.

                        Comment


                        • #13
                          ok thanxxxx.

                          oops there is another problem the game started well and the main menu appears then i click on New game the game closed and tells me that the file killhouse.ff is corrupted.
                          any ideas

                          Comment


                          • #14
                            Well, I'm not sure... BUT

                            even if you do fix it, you're probably going to get another problem. When I had a problem with my MOHA I contacted the company and was able to receive a new disc. Also, sometimes if you know somebody that works at a store like Gamestop, they will normally give you another disc (without a new cd code of course)

                            I'd try that.

                            Comment


                            • #15
                              Out of interest, has your disc drive ever given a "CRC (cyclic Redundancy check) error)"?

                              I think it might be of greater importance to find the cause of the problem instead of makeshift solutions.

                              Comment

                              Working...
                              X