[ShivanSpS]

This is quite strange i remember to have play with the HD3000 before, year or two.

Now the game starts, i can move the mouse, but whaverer i go to a button or just press enter, i hear the "button press" sound, and them a crash with malloc failed.

Code: [Select]

Malloc Failed!

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_0_RC2.exe! <no symbol>
fs2_open_3_7_0_RC2.exe! <no symbol>
ig4icd32.dll! <no symbol>
fs2_open_3_7_0_RC2.exe! <no symbol>
fs2_open_3_7_0_RC2.exe! <no symbol>
fs2_open_3_7_0_RC2.exe! <no symbol>
fs2_open_3_7_0_RC2.exe! <no symbol>

It maybe releated to Intel drivers, as the driver now forces EVERYTHING intro DVT memory, fixed memory is never used.

[MatthTheGeek]

Please post your fs2_open.log file.  Instructions on how to do this can be found in this post.

[ShivanSpS]

There is not much there.



[attachment deleted by ninja]

[Yarn]

Code: [Select]

  -mipmap
  -spec
  -glow
  -env
Try removing these (especially -mipmap).

[ShivanSpS]

That did it... i wonder where those flags come from, i dont remember putting those intro the launcher as custom.

Thanks.

BTW, those flags work using a Nvidia or ATI card, why?

[Yarn]

The problem was most likely the -mipmap flag. Another person with Intel graphics reported crashes with the flag here. As for why that was enabled, it's probably because it used to be listed under Graphics instead of Troubleshoot, and anyone who wants the best visual quality would turn on anything that says "Enable [xxxx]," even though this particular flag (in FS2 Open at least) should be disabled. There's hardly any reason to use it anyway; most textures included with SCP mods and the MediaVPs include mipmaps, and those get used regardless of your settings.

The other three flags were supported in FSO versions 3.6.14 and earlier, and you probably enabled those flags back then by some means. Those features are now enabled by default and can be disabled with -nospec, -noglow, and -noenv.

[ShivanSpS]

Ok thanks, its definately the Intel drivers causing problem with that flag, as GT520 and HD5850 can play with those.

[MatthTheGeek]

That they can doesn't mean they should. Why is this flag not deprecated yet ?

[chief1983]

Well, it was almost forced _on_ recently, until I talked The_E into reverting that commit.  I'm also more in favor of removing the mipmap support altogether, although I don't know why it would be getting enabled when it's under troubleshooting unless you needed it for something specific.

[MatthTheGeek]

I think there might be one or two outdated articles on the wiki that recommend it. Someone should check.

[Fury]

Well, it was almost forced _on_ recently, until I talked The_E into reverting that commit.

wat

What was the reason behind that?

[niffiwan]

Wasn't that -img2dds that was forced on, not -mipmap?

[chief1983]

Wait nm, got them confused.  Mipmap can break drivers too?

[niffiwan]

yeah, looks like there are at least two reported cases with Intel cards/drivers, this thread and this mantis:
http://scp.indiegames.us/mantis/view.php?id=2803

[ShivanSpS]

Well i have a GT520, a HD5850 and the Intel HD3000, i use all 3 for diferent tasks.

The -mipmap crash the game with malloc failed ONLY when using the Intel HD3000, nvidia and amd are ok.