Game Development Community

Demo: Error reading PNG file

by Noby Nobriga · in Torque Game Engine · 03/20/2005 (2:58 pm) · 4 replies

After a fresh checkout of torque 1.2.1 and fixing various compiler errors in VC6 (mostly "gui" files in different directories than the projects were expecting), I get this error when compiling and then running the demo. "Overview" works. But, I crash when the mission begins loading for "Feature Walkthrough," "Example: FPS," and "Example: Racing." Here's a snippit of my log:


[cropped]
*** Sending mission load to client: demo/data/missions/features.mis
Mapping string: ServerMessage to index: 0
Mapping string: MsgConnectionError to index: 1
Mapping string: MsgLoadInfo to index: 2
Mapping string: MsgLoadDescripition to index: 3
Mapping string: MsgLoadInfoDone to index: 4
Mapping string: MsgClientJoin to index: 5
Mapping string: Welcome to the Torque demo app %1. to index: 6
Mapping string: Visitor to index: 7
Mapping string: MissionStartPhase1 to index: 8
*** New Mission: demo/data/missions/features.mis
*** Phase 1: Download Datablocks & Targets
Mapping string: MissionStartPhase1Ack to index: 0
Fatal-ISV: ([cropped]\engine\dgl\bitmapPng.cc @ 80) Error reading PNG file:
[end of log]

The error dialog that appears reads:
Fatal-ISV: ([cropped]\engine\dgl\bitmapPng.cc @ 80)
Error Reading PNG file:
IHDR: CRC error

I noticed that there is no filename mentioned after "file:" Should there be one listed?
I haven't modified anything.

Any suggestions as to what may be causing the problem?

Thanks.

#1
03/20/2005 (6:45 pm)
I found the problem. The following files appear to be corrupt.

torque\example\demo\data\environment\lightning1frame1.png
torque\example\demo\data\environment\lightning1frame2.png
torque\example\demo\data\environment\lightning1frame3.png

Do these files work for anyone else, or is it just mine?
#2
03/25/2005 (1:10 am)
Yeah, thanks Noby. It's working now. Really great thanks to you.
#3
03/26/2005 (7:07 am)
@Noby:

Yep they are corrupt. Probably added as text files to cvs vs binary... (svn deals with it automagically while cvs requires you to do it manually)
#4
03/27/2005 (11:03 am)
Looking back, I'm not sure what version of the code I was checking out to begin with... But, at anyrate, it appears that version 2.2 of these files (which is the HEAD as of the time of this post) is corrupt. It does look like they were committed as text instead of bin. Can't tell you how many times I've done that same thing. Anyway. Until this is corrected in the repository, checkout revision 2.1 of those files and everything should be fine.