Author Topic: Strange error, possibly a bug in code.  (Read 1450 times)

0 Members and 1 Guest are viewing this topic.

Offline Dragon

  • Citation needed
  • 212
  • The sky is the limit.
Strange error, possibly a bug in code.
I made a mission using few retextured OTT ships (Aegis, Gaia and Chiron), retabled Chronos, retextured Trashman's Valkyrie MK2 and Scooby Doo's Foxbat, all of them working in lab and  individual tests. This mission however, crashes both in regular and debug builds, after loading Corvette.pof (Aegis).
There is no error message in debug build, just standard error report message.
The log ends with this:
Code: [Select]
Found bitmap doctile6.dds -- number 2621
Found bitmap doctile6-glow.dds -- number 2622
Found bitmap doctile6-shine.dds -- number 2623
For "Frigate.pof" I couldn't find doctile6-normal.ani
Ship Frigate.pof with engine wash associated with subsys engine01
Ship Frigate.pof with engine wash associated with subsys engine02
Ship Frigate.pof with engine wash associated with subsys engine03
Loading model 'Corvette.pof'
IBX: Found a good IBX/TSB to read for 'Corvette.pof'.
IBX-DEBUG => POF checksum: 0xc5b7530c, IBX checksum: 0x53bb7b43 -- "Corvette.pof"
Found bitmap ntdt04.pcx -- number 2614
Found bitmap ntdt04-glow.pcx -- number 2615
For "Corvette.pof" I couldn't find ntdt04-shine.ani
For "Corvette.pof" I couldn't find ntdt04-normal.ani
Found bitmap beam3.dds -- number 2611
For "Corvette.pof" I couldn't find beam3-glow.ani
Found bitmap beam3-shine.dds -- number 2612
Found bitmap beam3-normal.dds -- number 2613
For "Corvette.pof" I couldn't find beam3-height.ani
Found bitmap fedtex.dds -- number 2606
For "Corvette.pof" I couldn't find fedtex-glow.ani
For "Corvette.pof" I couldn't find fedtex-shine.ani
Found bitmap fedtex-normal.dds -- number 2607
For "Corvette.pof" I couldn't find fedtex-height.ani
Found bitmap fedlights.dds -- number 2608
Found bitmap fedlights-glow.dds -- number 2609
For "Corvette.pof" I couldn't find fedlights-shine.ani
Found bitmap fedlights-normal.dds -- number 2610
For "Corvette.pof" I couldn't find fedlights-height.ani
Found bitmap turretfed.pcx -- number 2624
Found bitmap turretfed-glow.pcx -- number 2625
For "Corvette.pof" I couldn't find turretfed-shine.ani
For "Corvette.pof" I couldn't find turretfed-normal.ani
Found bitmap bsmall.pcx -- number 2626
Found bitmap bsmall-glow.pcx -- number 2627
For "Corvette.pof" I couldn't find bsmall-shine.ani
For "Corvette.pof" I couldn't find bsmall-normal.ani
Found bitmap msmall.pcx -- number 2636
For "Corvette.pof" I couldn't find msmall-glow.ani
For "Corvette.pof" I couldn't find msmall-shine.ani
For "Corvette.pof" I couldn't find msmall-normal.ani
Found bitmap doctile6.dds -- number 2621
Found bitmap doctile6-glow.dds -- number 2622
Found bitmap doctile6-shine.dds -- number 2623
For "Corvette.pof" I couldn't find doctile6-normal.ani
Ship Corvette.pof with engine wash associated with subsys engines
Allocating space for at least 25 new ship subsystems ...  a total of 400 is now available (203 in-use).
I'm using latest 3.6.11 Inferno build with SSE (5615).
Strangely, at first, only debug build crashed, the regular had no problems unless I modified mission specs, so I'm posting first lines of a mission, just in case.
Code: [Select]
#Mission Info

$Version: 0.10
$Name:  XSTR("The Enemy", -1)
$Author: Dragon
$Created: 08/01/09 at 11:34:38
$Modified: 10/02/09 at 06:25:59
$Notes:
This is a FRED2_OPEN created mission.
$End Notes:

$Mission Desc:
 XSTR("Put mission description here
", -1)
$end_multi_text

+Game Type Flags: 1

+Flags: 128

+Disallow Support: 1

+Hull Repair Ceiling: 0.000000

+Subsystem Repair Ceiling: 100.000000

+Viewer pos: -16.390530, 4.355962, -11.078446
+Viewer orient:
0.999979, 0.000003, 0.006506,
-0.001246, 0.981575, 0.191072,
-0.006386, -0.191076, 0.981554

$Starting wing names: ( "Alpha A" "Alpha B" "Beta B" )
$Squadron wing names: ( "Alpha A" "Alpha B" "Gamma" "Delta" "Epsilon" )
$Team-versus-team wing names: ( "Alpha A" "Zeta" )

$Skybox Model: StarField.pof

$AI Profile: Smart

#Command Briefing
FRED debugger doesn't report any problems with this mission.
Does anyone know what can cause such behaviour?

 

Offline The E

  • He's Ebeneezer Goode
  • 213
  • Nothing personal, just tech support.
    • Steam
    • Twitter
Re: Strange error, possibly a bug in code.
Now, unless someone else has a brilliant idea, I would recommend getting Visual Studio 2008 Express from here: http://msdn.microsoft.com/en-us/visualc/aa336402.aspx

Then use the instructions in this thread to get a copy of the source code. Open the VS 2008 project, use the configuration selector to select "Debug", and build your own debug build. Copy that to your FS2 folder (without changing the name of the build), select it in the Launcher, and let it crash. Windows should then give you the option to debug it. At that stage, consult #scp for online help.
If I'm just aching this can't go on
I came from chasing dreams to feel alone
There must be changes, miss to feel strong
I really need lifе to touch me
--Evergrey, Where August Mourns

 

Offline Aardwolf

  • 211
  • Posts: 16,384
Re: Strange error, possibly a bug in code.
I see you modified the wing names, was that intentional? Do the wing names in your mission match?

 

Offline Dragon

  • Citation needed
  • 212
  • The sky is the limit.
Re: Strange error, possibly a bug in code.
Yes, as I said, FRED doesn't report any issues with the mission.
There is no "Beta B" wing in this mission, but I would be suprised if that was the cause.