Author Topic: Enter the Dragon dock path bug  (Read 1247 times)

0 Members and 1 Guest are viewing this topic.

Offline Arpit

  • 27
Enter the Dragon dock path bug


 :sigh:

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

 

Offline Yarn

  • Moderator
  • 210
Re: Enter the Dragon dock path bug
That happens in FS1 too (at least it does in FRED).
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Re: Enter the Dragon dock path bug
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?

 

Offline Arpit

  • 27
Re: Enter the Dragon dock path bug
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]

 

Offline mjn.mixael

  • Cutscene Master
  • 212
  • Anims: 420, Cutscenes: 10, Mainhalls: 7, Logos: 52
    • Steam
    • Twitter
    • Mix-Hai Productions
Re: Enter the Dragon dock path bug
Checked the data. It is not fixed in MediaVPs 3.6.12. It is fixed in MediaVPs Next.
Cutscene Upgrade Project - Mainhall Remakes - MixaelANITools - Between the Ashes - MjnMixael's Render Boutique - Mix-Hai Productions
Youtube Channel - P3D Model Box - Photobucket Albums - Model Releases - Downloads
Between the Ashes is looking for committed testers, PM me for details.
Report MediaVP issues, now on the MediaVP Mantis! Read all about it Here!

 

Offline Arpit

  • 27
Re: Enter the Dragon dock path bug
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)

 

Offline Yarn

  • Moderator
  • 210
Re: Enter the Dragon dock path bug
It's probably this bug, just in a different mission. Disable -fb_explosions (Enable Framebuffer Shockwaves) to avoid the crash.
"Your fighter is running out of oil.  Please check under the hood and add more if necessary"
--strings.tbl, entry 177

"Freespace is very tired.  It is shutting down to get some rest."
--strings.tbl, entry 178

 

Offline Arpit

  • 27
Re: Enter the Dragon dock path bug
It's probably this bug, just in a different mission. Disable -fb_explosions (Enable Framebuffer Shockwaves) to avoid the crash.

Thanks for the info.  :)