Hard Light Productions Forums

Hosted Projects - FS2 Required => FreeSpace Conversion => Topic started by: Arpit on May 26, 2013, 05:59:14 am

Title: Enter the Dragon dock path bug
Post by: Arpit on May 26, 2013, 05:59:14 am

(http://imageshack.us/a/img547/3061/dockpointbug.jpg)

 :sigh:

Am I the only the one with this bug or does it happen on other computers too ?

Title: Re: Enter the Dragon dock path bug
Post by: Yarn on May 26, 2013, 03:39:46 pm

That happens in FS1 too (at least it does in FRED).

Title: Re: Enter the Dragon dock path bug
Post by: Goober5000 on May 27, 2013, 02:12:09 am

This was noticed a while ago, and fixed in the FSPort models, but then those fixed models were removed in order to avoid conflicting with the mediavps.  I was assured that the mediavp models had been fixed though. :sigh:

Are you playing with the most up-to-date downloads?  Can you post your fs2_open.log?

Title: Re: Enter the Dragon dock path bug
Post by: Arpit on May 27, 2013, 03:40:49 am

Here is the debug log attached below.

Also when I played it on debug the following error came up and then .... crash.

Assert: num == bm_bitmaps[n].handle
File: bmpman.cpp
Line: 2556

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes


[attachment deleted by ninja]

Title: Re: Enter the Dragon dock path bug
Post by: mjn.mixael on May 27, 2013, 08:08:58 am

Checked the data. It is not fixed in MediaVPs 3.6.12. It is fixed in MediaVPs Next.

Title: Re: Enter the Dragon dock path bug
Post by: Arpit on May 27, 2013, 01:48:42 pm

Well that explains it.

Quote from: Me

Assert: num == bm_bitmaps[n].handle
File: bmpman.cpp
Line: 2556

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
fs2_open_3_6_19-DEBUG-20130512_r9677.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

However I still don't understand how this error came up. :doubt: (it only happens in debug)

Title: Re: Enter the Dragon dock path bug
Post by: Yarn on May 27, 2013, 02:14:22 pm

It's probably this bug (http://scp.indiegames.us/mantis/view.php?id=2865), just in a different mission. Disable -fb_explosions (Enable Framebuffer Shockwaves) to avoid the crash.

Title: Re: Enter the Dragon dock path bug
Post by: Arpit on May 27, 2013, 02:28:55 pm

Quote from: Yarn on May 27, 2013, 02:14:22 pm

It's probably this bug (http://scp.indiegames.us/mantis/view.php?id=2865), just in a different mission. Disable -fb_explosions (Enable Framebuffer Shockwaves) to avoid the crash.

Thanks for the info.  :)