ok i would like to ask how far does it let you go before giving the error do most of you get past the versus screen then it gives the error or is it sooner, so that i know were to see if i can make any changes and make it load for you
It give me the error after a 15 second white screen. Which is wierd because my other 1.0 screenpacks take about 30+ seconds to load sometimes and they still work fine. So i'm not sure if it's a loading issue or an OpenGL PNG issue with 1.1. Maybe this could be fixed in the future because i've seen the videos of the screenpack in action and It doesn't look that hungry when it comes to resources.
But I have an i3 laptop with no video card. I still find it wierd that it won't even start.
I am going to build a gaming pc soon because I need this screenpack and others that will come out to be 1.1 in the future.
ok is that just loading up mugen it gives you the error not even getting to the logo and press start screen bit
when i first started work on this screenpack i only had 3 gig of ram and no graphics card on xp and i could load it up, but soon as i started adding stuff in 32bit png it started to slow and it got to a point were it would crash with that error straight after the versus screen so i updated my machine to win7 with 10gig of ram and added a HD radeon 6670 and it now runs fine and loads and plays at 70fps.
so what i might do is work backwords and go back to were it loaded ok for me with 3 gig of ram and no card and see if that helps with people loading it up