Author Topic: AI Path Issues - GVC Mekhet  (Read 1784 times)

0 Members and 1 Guest are viewing this topic.

Offline NeonShivan

  • Previously known as BTA
  • 29
  • By the Omnisiah's grace.
AI Path Issues - GVC Mekhet
So I was play testing one of my missions that involve the capture of a [Zod] cruiser, the Mekhet, all was going well when the transport arrive and FSOpen collectively shat itself and gave me this error:

Code: [Select]
ai_find_path tring to find a path (1) that doesn't exist, on ship ANC Horus
KERNELBASE.dll! IsNLSDefinedString + 3228 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 139 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
fs2_open_3_7_2_RC3.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes


I've never seen such an error before and I have no real knowledge, as a result, to fix it. If anyone could help that would be greatly appreciated.
In German even the most beautiful love letter sounds like an execution order -Mito

(•_•)
 <)  )/
 /  \ All the Single Ladies

( •_•)
\(  (>
  /  \ All the Single Ladies

(•_•)
 <)  )/
 /  \  Oh Oh Oh

Author of Dusk Wars - A modification for Freespace 2.

 

Offline zookeeper

  • *knock knock* Who's there? Poe. Poe who?
  • 210
Re: AI Path Issues - GVC Mekhet
Well, probably the transport is arriving from a fighterbay, with the name of the path being one that doesn't actually exist in the anchor ship's model. Or, possibly, the paths might be named wrong somehow in said model. Pasting the relevant arrival anchor code from the mission file and a PCS2 screenshot of the paths list should reveal if anything's amiss.

 

Offline NeonShivan

  • Previously known as BTA
  • 29
  • By the Omnisiah's grace.
Re: AI Path Issues - GVC Mekhet
The transport is arrive via warp, not from a fighterbay.

Here's the POF screenshot

In German even the most beautiful love letter sounds like an execution order -Mito

(•_•)
 <)  )/
 /  \ All the Single Ladies

( •_•)
\(  (>
  /  \ All the Single Ladies

(•_•)
 <)  )/
 /  \  Oh Oh Oh

Author of Dusk Wars - A modification for Freespace 2.

  

Offline zookeeper

  • *knock knock* Who's there? Poe. Poe who?
  • 210
Re: AI Path Issues - GVC Mekhet
The transport is arrive via warp, not from a fighterbay.

Oh, right, well in that case it's something else. Maybe a ship trying to dock or undock with another when the latter doesn't have a proper path for it, or something. I'd guess the problem to be with the model of whatever class ANC Horus is.

A debug build ought to give a better stacktrace and/or something interesting in the log.