HLP Network

News:

HLP Donations Page has been reworked for supporting the site.
Please note that the previous "Tiers" are currently not operational (but will be worked on).
You can still cancel any previous re-occurring donations to make new ones which will go to the new Treasurer Admin (Zacam).

 
« Previous Thread Next Thread »
Print
Pages: [1]   Go Down

Author Topic: AoA crash  (Read 3189 times)

0 Members and 1 Guest are viewing this topic.

Offline hkmp57

  • 23
AoA crash
on: June 21, 2014, 09:31:23 am
I have a problem after i engaged subspace drive in first mission to get to earth the game crashes and this appear

For asteroid 'Terran Debris 1', detail level
mismatch (POF needs 3)
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

I m using 3.6.17 debug sse2 bp.exe to open mod
 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: AoA crash
Reply #1 on: June 21, 2014, 09:37:10 am
Quote from: hkmp57 on June 21, 2014, 09:31:23 am
I have a problem after i engaged subspace drive in first mission to get to earth the game crashes and this appear

For asteroid 'Terran Debris 1', detail level
mismatch (POF needs 3)
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
fs2_open_3_6_17_DEBUG_SSE2_BP.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

I m using 3.6.17 debug sse2 bp.exe to open mod
First off, don't use the 3.6.17 build; it has a known pilot corruption issue.

Secondly, that is a warning, not an error; you can just hit "no" and continue playing. You really shouldn't be using a debug build to play the mod anyway; your framerate is going to take quite the hit.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.
 

Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: AoA crash
Reply #2 on: June 21, 2014, 09:45:53 am
That's a harmless warning caused by using debug builds to play. Don't use debug builds to play - switch to the normal build.
 

Offline hkmp57

  • 23
Re: AoA crash
Reply #3 on: June 22, 2014, 01:39:32 am
Yes, i just have to click "no" in that window few times, thanks for that. Second thing how to switch to normal build? If you mean to chose build 3.16.17 sse2 bp instead debug, i have a "progam stopped working" issue. Because framerate really sucks.
 

Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: AoA crash
Reply #4 on: June 22, 2014, 10:50:49 am
We just released a new version of BP via the FSO Installer. I suggest deleting your current install and grabbing that. You will want to get FSO 3.7.2 RC3 as well.
 

Offline hkmp57

  • 23
Re: AoA crash
Reply #5 on: July 01, 2014, 08:14:31 am
I've downloaded new release of bp, and fso 3.7.2 RC3 and now i'can't play it at all when i try debug version this appear

 bp-shp.tbm(line 222):
Error: Required token = [#End], [$Subsystem:], [$Name], or [$Template], found [$Glowpoint overrides: ( "red_glow_10:1,2" "blue_glow4_small_15:].

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! SCP_DumpStack + 354 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! Error + 229 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! error_display + 369 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! required_string_4 + 388 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! parse_ship_values + 23642 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! parse_ship + 935 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! parse_shiptbl + 374 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! parse_modular_table + 267 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! ship_init + 578 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! game_init + 1746 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! game_main + 519 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! WinMain + 330 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_7_2_RC3-DEBUG.exe! WinMainCRTStartup + 15 bytes
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes

or this version without debug

bp-shp.tbm(line 222):
Error: Required token = [#End], [$Subsystem:], [$Name], or [$Template], found [$Glowpoint overrides: ( "red_glow_10:1,2" "blue_glow4_small_15:].

ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_2_RC3_SSE.exe! <no symbol>
fs2_open_3_7_2_RC3_SSE.exe! <no symbol>
fs2_open_3_7_2_RC3_SSE.exe! <no symbol>
fs2_open_3_7_2_RC3_SSE.exe! <no symbol>
 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: AoA crash
Reply #6 on: July 01, 2014, 08:33:48 am
Quote from: hkmp57 on July 01, 2014, 08:14:31 am
I've downloaded new release of bp
Are you sure about that? Did you download it through the FSO Installer? Because the error you're getting is what happens if you used the previous release of Blue Planet without the compatibility package.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.
 

Offline Klaustrophobia

  • 210
  • the REAL Nuke of HLP
    • North Carolina Tigers
Re: AoA crash
Reply #7 on: July 02, 2014, 08:12:59 am
Quote from: General Battuta on June 22, 2014, 10:50:49 am
We just released a new version of BP via the FSO Installer. I suggest deleting your current install and grabbing that. You will want to get FSO 3.7.2 RC3 as well.

i ran the installer (a few times before everything succeeded) without deleting the old folders.  is that going to be a problem?
I like to stare at the sun.
 

Offline General Battuta

  • Poe's Law In Action
  • 214
  • i wonder when my postcount will exceed my iq
Re: AoA crash
Reply #8 on: July 02, 2014, 10:28:06 am
I don't know enough about how the Installer works to answer that with confidence.
 

Offline Axem

  • 211
Re: AoA crash
Reply #9 on: July 02, 2014, 05:27:08 pm
The installer should replace the core vps that have those tbm files. Do you have some others files hiding in /data/tables maybe? Or try deleting bp-core.vp and bp2-core.vp and rerun the installer.
 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: AoA crash
Reply #10 on: July 02, 2014, 05:40:11 pm
Quote from: Axem on July 02, 2014, 05:27:08 pm
The installer should replace the core vps that have those tbm files. Do you have some others files hiding in /data/tables maybe? Or try deleting bp-core.vp and bp2-core.vp and rerun the installer.
Klaustrophobia is not hkmp57.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.
 

Offline Axem

  • 211
Re: AoA crash
Reply #11 on: July 02, 2014, 07:22:24 pm
Right, I can't read.
 

Offline hkmp57

  • 23
Re: AoA crash
Reply #12 on: July 05, 2014, 09:34:46 am
Everything work's fine thanks for that. I've downloaded it from page not from fso installer (i don't like it), and that was the problem. Now i have only problem with fps when big ships appears but that's probably my hardware problem or you have some solution for that?
Print
Pages: [1]   Go Up
« Previous Thread Next Thread »