[Goober5000]

Not necessarily.

[Legate Damar]

So what do I do then?

[Goober5000]

If the problem still exists, then open a Mantis bug, mark it as private, attach the mission, and assign it to me.  I'll take a look at it.

[Legate Damar]

I've never used the Mantis thing before... sorry to sound like a noob but how do I do that

[Goober5000]

http://www.hard-light.net/forums/index.php?topic=74840.0

[Legate Damar]

What do I write for Platform, OS, and OS Version? I'm guessing Windows and Windows Vista for the latter two, but I don't know what the first one means.

Also if you want a copy of the mission to try to run it and get the bug, you won't be able to because the mission has a lot of unreleased assets that you would need in order to play it. Is that a problem?

[Goober5000]

Platform is a vague term that could mean either operating system or processor type (brand, 32 vs. 64-bit, etc.)  You can leave that blank.

And yes, the unreleased assets would be a problem.  Save a copy of the mission, and then change the ship and weapon classes to retail types.

[Legate Damar]

Okay, while I'm at it I'll also censor the spoilers and stuff.

[Legate Damar]

I tried changing it in FRED to use only retail stuff but I keep getting this error now:

Unable to find WEAPON_LIST_TYPE string "ÿÿÿÿ" in stuff_int_list

Many possible sources for this error.  Get a programmer!

ntdll.dll! KiFastSystemCallRet
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! SCP_DumpStack + 354 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! Warning + 430 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! stuff_int_list + 596 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! parse_common_object_data + 949 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! parse_object + 1481 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! parse_objects + 192 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! parse_mission + 500 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! parse_main + 449 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! mission_load + 215 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! game_start_mission + 184 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! game_enter_state + 462 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! gameseq_set_state + 310 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! game_process_event + 242 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! gameseq_process_events + 152 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! game_main + 782 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! WinMain + 330 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_6_14_RC6_DEBUG_NO-SSE.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

[Goober5000]

Okay, while I'm at it I'll also censor the spoilers and stuff.

As I said before, you can mark the bug as private.  This ensures that only you and the SCP staff will be able to view it.

I tried changing it in FRED to use only retail stuff but I keep getting this error now:

Unable to find WEAPON_LIST_TYPE string "ÿÿÿÿ" in stuff_int_list

Well, for the time being, open your mission in Notepad and replace ÿÿÿÿ with a retail weapon.

[Legate Damar]

Okay, I'm no longer getting the error, but now the game is just crashing whenever I try to run the mission.

Log attached.


[attachment deleted by a ninja]

[Goober5000]

For future reference, this is how you report a bug.

Please follow directions next time; we could have gotten it fixed 12 days faster.

[mjn.mixael]

Now I feel like my life meant something!

MjnMixael gives self a pat on the back.

[Legate Damar]

I said I tried to submit it but my version of the mission using non-modded assets kept crashing and I couldn't figure out how to fix it. Is the bug fix going to be in a new build or something?

[Goober5000]

Well, if you can't reproduce the bug with non-modded assets, then we often won't be able to.  Fortunately, mjn.mixael stepped in and provided a mission.

The bug fix will be in 3.6.14 and any new trunk builds.

[Legate Damar]

It's not that I couldn't reproduce the bug, it's that the non-modded version of the mission wouldn't run at all, it just crashed