Couldn't find image for shader 0


Recommended Posts

Hello everyone.

I have searched the Internet and searched Neowin for help, but did not find anything. I purchased MOHAAB today for $5, brand new at Electronic Boutique (yes, I know the game is old, but I bought it for my nephew) anyway, the game installed fine, and I pass the first level (of course I'm gonna play it :D), when the game starts the second level, the console opens automatically with the following error message:

Couldn't find image shader 0

The game does not work anymore. Please look at the picture. What is that? Could someone help me?

Computer specs:

P4 2.8GHz w/HT

Asus mobo P4S533

Running XP with 1GB DDR RAM

64MB nVidia card & like 11GB free HD space.

TIA

/EZ

P.S.

The first time I installed the game, ran it without the patch 1.11 and it did the same thing, so I went ahead and installed the patch thinking it would fix it, but no luck.

post-40930-1104640030_thumb.jpg

Edited by EZRecovery
Link to comment
https://www.neowin.net/forum/topic/265470-couldnt-find-image-for-shader-0/
Share on other sites

I'm gonna answer my own question :D

Found the information on EAGames website.

Question

Why does the game crash with an error about not finding an image for shader 0?

Answer

The error ERROR - Level::AllocEdict: no free edicts or Couldn't find image for shader 0 is caused by three things.

* The wuss cheat code entered in the console. The weapons spawned by this code will cause the error, and result in a crash to the main menu when loading the next mission. We recommend that you not use this code when playing the game to minimize any further issues.

* This could also happen if you have installed any game mods, using other cheats or additions to the game that are not supported by Electronic Arts.

* If this is not the case, it's may be because the install files were corrupted.

In these cases a clean install will be desired. This will clear the game entirely off your system, allowing you to reinstall the game without corruption.

Source

:angry:

I couldnt edit my last post, but it did not work. I did have the cheat codes in there, but removing it, did not do anything. Started level 2 and the same thing happened, the console open automatically with the error message. I'm gonna remove the game like EAGames says (step by step).

No one has received this error message using the cheat codes provided on different places on the Internet?

TIA

Ok. This is the final answer. I had to manually delete the whole game like it said in EAGames, and now the game works fine. I guess once I added the cheat codes to the shortcut executable I had created, it corrupted the whole game.

Thanks

/EZ

  EZRecovery said:
Ok. This is the final answer. I had to manually delete the whole game like it said in EAGames, and now the game works fine. I guess once I added the cheat codes to the shortcut executable I had created, it corrupted the whole game.

Thanks

/EZ

585259301[/snapback]

the cheats added to the shorcut dont corrupt the game , they just make the console available for entering commands & cheats .......but anyways you will need to reinstall & remove the shortcut with the cheats in it .

  Rahul said:
the cheats added to the shorcut dont corrupt the game , they just make the console available for entering commands & cheats .......but anyways you will need to reinstall & remove the shortcut with the cheats in it .

585260988[/snapback]

Whatever happened, it did corrupt the files, because once I removed the shortcut.exe, the original icon was not working either, it would come up with the same error.

That's what I did. Removed the whole game manually, including registry keys. Did a fresh installation, and its been working after that. :p

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Building 100 hospitals around the world would have spent his fortune easily. But that would not keep him at the table with the elites in the world for the rest of his life. Or keep him from chanting about how good he is to the poor people around the globe to the media.
    • Exactly. that's what I use when I do use Windows 10 on my Linux through QEMU/KVM VM (the 'activation' is tied to the UUID of the VM) and, like you said, that Jan 2032 version of Win10, even if decent program/game support ends earlier than Jan 2032, I suspect, for a conservative figure, that we got at least 2-3 years from now (so call it 2027-2028) before Win10 may start to become more of a legitimate issue. but for general usage I suspect we got a 'easy' 2-3+ years. because like you say, as long as browsers don't start to become a issue, all the more reason to continue using Win10 for many, probably most, people. even when it comes to browsers, you mentioned Firefox supports Win7 until end of August etc... but I think it's just ESR releases which, while I get it technically works, are when browser support is getting a bit long-in-the-tooth. but as long as the standard Firefox release is still supported, then one is still easily well within the 'good support range', which my comment basically plays inline with what Werct said, which I suspect comes back to my 2027-2028 estimate before Win10 'starts' to legitimately fade off into the sunset
    • Intel's new GPU driver adds support for FBC: Firebreak, Stellar Blade, and more by Taras Buria Intel has released a new non-WHQL driver under version 32.0.101.6876. The update brings support and optimizations for four games and a single fix for visual artifacts that appear in certain situations. Here is the list of newly-supported games in driver 32.0.101.6876 on systems with Intel Arc B-Series, A-Series, and Intel Core Ultra with built-in Arc graphics: FBC: Firebreak Rematch Stellar Blade Tom Clancy's Rainbow Six Siege X There is also a single bug fixed in today's release: Intermittent visual artifacts may appear in certain usage scenarios. Known issues remain the same as in the latest WHQL release, except for a new bug that causes audio glitches on handheld devices: Certain handheld devices may experience audio glitches and lower-than-expected performance while audio is playing. You can mitigate the problem by following a guide that Intel published on the official forum. It requires reinstalling the graphics and NPU drivers on the affected systems. A proper fix will be available in a future driver update. You can install Intel 32.0.101.6876 non-WHQL driver on PCs with 64-bit Windows 10 and Windows 11 with the following graphics products from Intel: Discrete GPUs Integrated GPUs Intel Arc A-Series (Alchemist) Intel Arc B-Series (Battlemage) Intel Iris Xe Discrete Graphics (DG1) Intel Core Ultra Series 2 (Lunar Lake and Arrow Lake) Intel Core Ultra (Meteor Lake) Intel Core 14th Gen (Raptor Lake Refresh) Intel Core 13th Gen (Raptor Lake) Intel Core 12th Gen (Alder Lake) Intel Core 11th Gen (Tiger Lake) You can download the driver from the official website here. Full release notes are available here (PDF). Keep in mind that this is a non-WHQL driver, which means it could be less stable than certified WHQL drivers.
    • He did give it away in 2008, well actually he gave away half of his fortune. He was open at the time that part of the reason he was doing it was that he was accumulating wealth faster than he could conceive of spending it
    • ooof! made me wince when i saw where the stand connected!
  • Recent Achievements

    • Dedicated
      jbatch earned a badge
      Dedicated
    • Week One Done
      Leonard grant earned a badge
      Week One Done
    • One Month Later
      portacnb1 earned a badge
      One Month Later
    • Week One Done
      portacnb1 earned a badge
      Week One Done
    • First Post
      m10d earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      266
    2. 2
      snowy owl
      158
    3. 3
      +FloatingFatMan
      145
    4. 4
      ATLien_0
      140
    5. 5
      Xenon
      131
  • Tell a friend

    Love Neowin? Tell a friend!