Fatal-ISV (..\..\source\dgl\bitmapPng.cc @ 85

#1 Isaac Barbosa and I went the rounds with this problem a short while back. Often times you will get that message if your PNG headers are munged. Running optiPNG cleans the headers and they work fine. The problem was that Isaac hadn't done anything with PNG's to cause the problem. Something had just gone wonky.

Here is the thread where he fixed it (and I was helping him with OptiPNG info that actually wasn't related to his particular issue.

If you are loading a PNG image, you might want to make sure the headers aren't munged. If it is closer to his issue, try what he did in the last post.

#2 Ok, I downloaded optiPNG, and ran it on every .png file in my torque project - no change, I still get the exact same error. Also, I can't do the fix that Isaac Barbosa did because I can't open my project in the first place (ie: he clicked on an image map in the image editor, but I can't even get to the image editor).

So... my problem persists. Any other ideas?

edit: Oh, I wanted to mention that I have TGB set to "open most recently worked on project" whenever I load it up. so at this point, I can't even open up TGB (since my most recently worked on project is the one generating the error message).

#3 I uninstalled TBG from my computer, then redownloaded it and reinstalled it, but I'm still getting the exact same error message every time I open TGB. This is getting downright scary - is Torque an inherently buggy engine? Did I waste my money? How can I fix this?

If anyone has ANY ideas on how to fix this, I'll be in their debt.

#4 Rrrrrr - now I went into the defaultPrefs.cs file inside of C:\Program Files\GarageGames\TorqueGameBuilder-1.7.4\tgb\common\preferences and edited it to NOT load the most recent project when I open TGB, and to NOT load the most recent scene - but the exact same error message still comes up every time I open up TGB. It seems that TGB has lost the ability to open up in the first place. This is extremely disheartening - If I can't get this fixed, then I'll never be able to use TGB again.

#5 I don't own TGB so this may be way off, but perhaps a .dll that TGB depends on is corrupted? Perhaps you need to re-install a dll? I'm not sure what TGB uses, like if it uses opengl, DX, or what, but maybe that's where the problem lies? If you've re-installed, it would seem that it would have to be something outside of TGB.

#6 If this is a problem in TGB without opening any project then reinstalling seems like the right thing to do...

Try reinstall to a different directory, or run the uninstaller first and then go delete all folders that remain in program files, also might want to delete the garagegames folder in the appdata folder.

You can delete the t2dImageMapDatablock's for your project outside-of the editor by going to game/managed/datablock.cs.

#7 Zip up your project and I'll see if it breaks my TGB install. Then maybe I can get a hold on fixing it. I've seen this happen to two people, and Isaac's ended up fixing itself somehow.

#8 The version of libpng included in TGB 1.7.4 is ancient [1.0.12]. I would recommend updating it to the latest version [1.2.31] and recompiling TGB.

Edit: While you're at it, zlib is also quite old [1.1.3 - 1998!] and known to have security and performance issues. That may not be a concern for your game, but you can get the latest version [1.2.3] here.

#9 Good call, Andy. Hopefully we can get this rolled into the newest builds for those with binary licenses if it solves the issue.

#10 Yeah - I think they should be updated regardless.

I updated all the support libs when I was doing the TGE and TGEA releases last year, but they should be checked again and updated as necessary. I believe it should be SOP when working on a release.

#11 This may be completely off-beam and not in any way applicable to the cause of your error, but I had problems with TGEA misreading PNGs and crashing out due to a fatal ISV error when I started. My fix was to pull 2 GB from my computer (I had 4 GB installed, all matching 1 GB chips from the same maker) and I haven't seen the error since.

-------------------------------------

On launch... selecting the non-Atlas terrain missions yield this error about 75% of the time: a dialog with text reading "Fatal ISV: ..\..\..\..\..\engine\source\gfx\bitmapPng.cpp@84. Error reading PNG file. IDAT: CRC error."

Once this pops up, I have to restart the computer... the game demo will freeze, and although the window will vanish if you click on the compiler window behind it, the game cannot be launched until the machine is rebooted.

-------------------------------------

Reference thread is here http://garagegames.com/mg/forums/result.thread.php?qt=76822

#12 Hi all I see this error when I use a texture out the standard range as [256x256], [1024x1024] but I don't know if is your case.

#13 Thanks for your help everyone - After wrestling with this one for a few days, I finally managed to get it fixed. What I finally ended up doing was uninstalling TGB, deleting the Garage Games directory, deleting the Garage Games directory in the appdata folder, and reinstalling the whole thing to another directory.

I was hoping to figure out what caused the problem in the first place, but at this point, I'll settle for being able to get back to work.

#14 I don´t know what is wrong. But it seems to work if you delete the garage games directory in the appdata folder.

#15 i've just stumbled upon this issue (bug?), and your solution, Isaac, worked like a charm, so, thank you m8 for the tip... i really needed it.

i hope the guys at GG find what the problem is, cuz its such an annoying problem whenever it pops up.

#16 I know it's not nice to bump ancient threads, but this one just helped me. In my case, the bug happened because one of the imagemaps used a 2048x2048 png image. Removing/shrinking it fixed the problem.