Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Kaz]

Hi

I have been working on the previous version of WME with no crashing problems but having downloaded version 1.8, it has started crashing and giving the following error report "Microsoft Visual C++ Runtime Library, Runtime Error! This application has required the Runtime to terminate it in an unusual way. Please contact the application support team for more information".

All I'm trying to do when it crashes is load a sprite in SceneEdit which I've already saved in the a file in the game I'm creating. I'm using Vista. Is it me, or has anyone else had this problem?

Thanks

[Mnemonic]

So you're getting the error in SceneEdit only?

[Mnemonic]

Also, what WME version were you using before upgrading to 1.8? The 1.7.x series or 1.8 beta?

Could you please describe step-by-step what you did to get the error? Also, does it crash always or randomly, does it crash for one particluar sprite/image, or any of them?

[Kaz]

Hi

Thanks for your very prompt reply - I didn't expect to hear from you so soon so I'm afraid I didn't check the forum until now.

I've discovered the problem which was that the graphic that I was trying to import into the scene was not a png but another type of file that sometimes accompanies pngs that my brother sends me for the game (he uses a Mac and I think they are some sort of thumbnail of the graphic). I had somehow managed to save the thumbnail rather than the proper png. For some reason though, WME didn't like the file type so much that it crashed the program rather than just refusing to load the graphic.

Just in case you are still interested though, the previous version I was using was 1.7.003 but I assume it could be a universal reaction to the type of file I was attempting to load. I've now loaded the png successfully and have no further problems.

Thanks again for your speedy response.

[Mnemonic]

Ah, good, thanks for the info After doing some research I was suspecting it would be caused either by the png or jpg loading code.

Bottom line, just for the record, if anyone's interested (perhaps finding this thread via google), the above message is displayed when the application calls the abort() C function. libjpeg and libpng can call the abort() function when encountering a fatal error, caused perhaps by a corrupted or other malformed image.