MegaGlest Forum
MegaGlest => Bug reports => Closed bug reports => Topic started by: praveensvsrk on 11 October 2013, 14:09:05
-
Hello!
Mega glest 3.8.0(beta) do not work in my computer, i have 2 computers and it doesn't work on both of them.
i have the game to my friends and they said it didnt work for them too!
i switched on the game, i click "new game" and then, after loading it crashes automatically, some thing like unknown error|unknown function
i have uploaded 4 crash dump files, please do something!!!
thanks... !
uploaded files: (i dont know other alternative, sorry :/)
http://www.2shared.com/file/Gevd2w9S/2b606eef-376c-442f-ae18-c7bd26.html (http://www.2shared.com/file/Gevd2w9S/2b606eef-376c-442f-ae18-c7bd26.html)
http://www.2shared.com/file/FWJcHkTN/a8c672d8-e03f-4ab0-9aa0-55e2d8.html (http://www.2shared.com/file/FWJcHkTN/a8c672d8-e03f-4ab0-9aa0-55e2d8.html)
http://www.2shared.com/file/fw7BACZf/dc09503c-5de3-45aa-83b9-eeb09c.html (http://www.2shared.com/file/fw7BACZf/dc09503c-5de3-45aa-83b9-eeb09c.html)
http://www.2shared.com/file/WxC2Qe6j/e2529044-9798-4fb2-bb74-082b7a.html (http://www.2shared.com/file/WxC2Qe6j/e2529044-9798-4fb2-bb74-082b7a.html)
-
Hi praveensvsrk, and thanks for your feedback. Please read READ THIS FIRST: How to report bugs (https://forum.megaglest.org/index.php?topic=5332.0) and add more details about your environment. For example, we're lacking information on your operating system (there are Linux and Windows buiilds, 32 and 64-bit), its patchlevel (when did you last install all available system updates), and your hardware (total installed physical memory, available memory before you start MegaGlest, CPU, graphics card). Also, where did you download it and what is the exact filename and exact filesize (in bytes, not kilobytes or Megabytes) of the installer?
-
Any update on this?
-
sorry for late reply, was busy, and i am always busy so i have almost no time to even post on forums :( luckily i got some time today.
ok, size of the beta (MegaGlest-Installer-3.8.0-beta1_i386_win32)installer: (228,135,678 bytes), downloaded on 5 October 2013
OS: Windows XP SP 3
1.5 GB RAM, 1.66 GHz
Open GL version 1.1 (I know 1.3 is required but how to get it?? i went to intel update website but there was no difference)
I never updated my system for 6- 8 months because i have ultra slow internet of about 128 kbps, its ridiculous i know...
-
and one more update!
I have another XP system with almost same specs but 2.0 GB ram
there it told me i have OpenGL version 1.1 but OpenGL 1.3 is required.
i tried to update but failed....installing OpenGL is too hard! OMG what to do??
-
OpenGL 1.1 means software rendering, meaning that hardware acceleration is not working. You need to get a current Intel graphics driver which works for your Intel graphics chipset and your operating system (and it's version). 1.5 GB total system RAM is not much either. Windows will eat 500 MB, leaving only 1.0 GB for MegaGlest. This will work for small games but you will get into trouble on any medium or large game, much more so because the Intel hardware is not meant to be used for this type of game, but for office computers, 2D graphics and simple videos.
So my short term suggestion is: Try to get a working driver which gives you proper OpenGL support for the (yet unknown) Intel hardware you have there.
And the mid term suggestion is: Buy a new computer with a dedicated (ATI or NVidia) graphics chip or a current Intel (latest generation, GMA 3500 or 4000 - those are both affordable and provide just enough performance). And get a fully supported operating system, too (mainstream support for XP ended in 2009, extended support for XP SP3 ends on April 8, 2014).
Edit: This is not a bug since you are trying to run MegaGlest on a system which does not meet the system requirements. I'll move it to the main forums. Please don't file support requests in the bug forum.
-
Thinking about this more, I think this actually still is a bug in that the game should still detect the lack of proper OpenGL support and exit cleanly, not crash. But it does exit uncleanly, since it writes those DMP files (which it would not do otherwise).
-
This should be fixed in svn now (a clean shutdown after warning the user)