[SirKnightly]

Here is the nightly for Windows on 20 Aug 2009 - Revision 5524

fso-WIN-20090820_r5524.7z
MD5Sum

Code: [Select]

------------------------------------------------------------------------
r5524 | Wanderer | 2009-08-19 12:19:37 -0500 (Wed, 19 Aug 2009) | 1 line
Changed paths:
   M /trunk/fs2_open/code/ship/ship.cpp

fix for shield armor issue reported by Qent
------------------------------------------------------------------------



[Macfie]

I just noticed a problem.  I was playing an FSPort campaign and noticed that the GTSC Faustus #medical, GTT Elysium #medical, GTFR Chronos #medical and the TAC 1#medical do not have the proper textures.  They use the standard texture rather than the medical white and blue.  If I go back to using the 3.6.10 build everything is normal.

Went back and checked different builds.  The windows 5207 build works but the windows 5219 build doesn't.  I believe 3.6.10 is built off the 5209 build.  So something changed in the 5219 build caused the problem.

[portej05]

hmm, curious.
I've had a cursory look through the commits in question, and there's nothing obvious that jumps out.
Will keep my eyes peeled.

Thanks for the report!

3.6.10 is based on the 5209 commit (5210 is the final tag).

[JGZinv]

Perhaps this will help:

Code: [Select]

Assert: (bm_bitmaps[n].handle == bitmapnum)
File: bmpman.cpp
Line: 1978
bitmapnum = 475271, n = 271, bm_bitmaps[n].handle = 750771

gß^¹P‘|üß^! KiFastSystemCallRet
gß^¹P‘|üß^! WaitForSingleObject + 18 bytes
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! <no symbol>
gß^¹P‘|üß^! RegisterWaitForInputIdle + 73 bytes
I've hit it twice. Once in the F3 viewer looking at a model, and once going into a mod mission
that didn't have anything to do with that model.

Don't know nor am acquainted with error reporting.. but there it be if it helps.

[Wanderer]

Basically what it is stating is that one of your bitmaps does not match with the one in memory.. usually reason for this is that the bitmap failed to load. If you can identify the model which cause the issue then it perhaps could be fixed.

As for the stack... Without PDBs the whole stack is useless (if the build you were using had those, make sure to extract them to the same directory as where the exe file is)

[Macfie]

I also found that the medical ship problem also effects all of the nameplated orion destroyers in the FSPort.  Instead of using the fsport model for the destroyer it just uses the standard orion model.

In looking at the models affected it appears that anything beyond the basic model is being ignored.  The models affected all have additional information.
I.E. capital01a.pof or capital01-Soyakaze.pof in both cases it defaults to capital01.pof
The same thing with the medical ships the GTSC Faustis#medical uses model science01-medical.pof but it defaults to science01.pof

Put in Mantis #1979

[Echelon9]

JGZinv, we had that same issue with an internal Diaspora model during development. Without saying too much, check to ensure the model in question doesn't load textures twice or have glow points with 0 radius and no info. Hope that helps tracking the cause down.