•     Please make sure you check the Support FAQ and relevant Guides before you create a new thread in this section!

Technical Issue Windows 10 MB2 Problem

Posts
4
Likes
0
So I recently upgraded to Windows 10, and now I'm having issues running MB2. I tried playing shortly after the upgrade, and while joining a server at some point when the bar on the loading screen reached 2/3 full, my game crashed and I encountered this error:

139292 files in pk3 files
glGetError() = 0x500
Loading dll file ui.
UI: Initializing Unhandled Exception Filter
Loading dll file cgame.
CGAME: Initializing Unhandled Exception Filter
Z_Malloc(): Failed to alloc 1764000 bytes (TAG_TEMP_WORKSPACE) !!!!!
---------------------------------------------------------------------------
Zone Tag Bytes
-------- -----
BOTLIB 7196 ( 0.00MB) in 2 blocks ( 3598 average)
GENERAL 2152 ( 0.00MB) in 269 blocks ( 8 average)
SND_MP3STREAMHDR 612628 ( 0.58MB) in 23 blocks ( 26636 average)
HUNK_MARK1 32372831 (30.87MB) in 40824 blocks ( 792 average)
EVENT 300732 ( 0.28MB) in 247 blocks ( 1217 average)
FILESYS 4436086 ( 4.23MB) in 261 blocks ( 16996 average)
AMBIENTSET 980 ( 0.00MB) in 7 blocks ( 140 average)
SMALL 24771 ( 0.02MB) in 1999 blocks ( 12 average)
MODEL_MD3 971278 ( 0.92MB) in 102 blocks ( 9522 average)
MODEL_GLM 2770620 ( 2.64MB) in 24 blocks ( 115442 average)
MODEL_GLA 12896827 (12.29MB) in 6 blocks ( 2149471 average)
SHADERTEXT 3970352 ( 3.78MB) in 1 blocks ( 3970352 average)
SND_RAWDATA 26647759 (25.41MB) in 486 blocks ( 54830 average)
TEXTPOOL 10240 ( 0.00MB) in 1 blocks ( 10240 average)
IMAGE_T 107096 ( 0.10MB) in 1217 blocks ( 88 average)
---------------------------------------------------------------------------

The zone is using 85131548 bytes (81.19MB) in 45469 memory blocks
The zone peaked at 103901908 bytes (99.09MB)
Shutting down OpenGL subsystem
(Repeat): Z_Malloc(): Failed to alloc 1764000 bytes (TAG_TEMP_WORKSPACE) !!!!!

After I couldn't figure out what the issue was I decided to just reinstall MB2 entirely, but after restoring all my settings in the main menu before joining a server, I experienced the same crash. I then tried returning all my settings to default, and was able to join a server as long as I didn't mess with my video settings, so currently I can play but not at the highest settings. Also just recently updated graphics drivers to try to remedy the situation, but to no avail.

Any help would be greatly appreciated.
 
Posts
133
Likes
156
Try going into your launcher settings and launch MBII through "MBII Client"

After upgrading to Win10 this is the only way my game will run without crashing
 
Posts
296
Likes
216
Not sure if related but something you can try: [SOLVED] - Windows 10 - Sliding mouse. I know you didn't mention anything about a sliding mouse, but if you look at thread, I was also have weird display issues on windows 10 at the start.

Also, does this issue only happen when you use a custom resolution or if you change it to anything other than the default?
 
Posts
4
Likes
0
I tried changing that setting in jamp.exe from the thread you linked, however it did not seem to solve the issue of crashing when using the video settings I used to use.

I joined a server after setting back to default settings and changed each one of the settings one by one to see which one caused the crash, and it seemed to be that when I set texture quality from 16-bit to 32-bit, the crash occurred. So for now I can play with texture quality set as 16-bit and the rest of my video settings at what I'm accustomed to.
 
Posts
296
Likes
216
I am unable to replicate this issue. I am on Windows 10, using the steam version of JA, and I am launching JAMP. If you are sure that it is the texture quality setting and it doesn't cause problems after you a join server, you could probably save it as a config. Then copy the config and put it into your base folder under the name autoexec.cfg so it always loads that setting without having to manually apply it.
 
Posts
133
Likes
156
The issue is related to your video/graphic drivers getting an update with Windows 10. It's a common issue when it comes to old games. Your crash is something involving OpenGL according to your crash log. I don't really know too much about it just that it is something to do with graphics. I've had OpenGL errors a number of times and it's always been relating to my graphic drivers. After updating to Windows 10 I get an OpenGL crash within two seconds if I try to launch Jedi Knight without OpenJK.

You could try rolling back to your previous version of Windows, pretty sure that's something you can do. Either that or continue to mess around with graphic settings and try things like launching through OpenJK. Not sure of too many ways to fix this without rolling back your drivers. Then again I am just throwing out my opinion, I don't really know much about OpenGL errors other than from my own experiences with them.
 
Top