[General Battuta]

While ships were attacking a Bes (freighter2v-01.pof) I crashed out on a release 3.6.13 build with the following error.

Code: [Select]

ai_find_path tring to find a path (9) that doesn't exist, on ship Upsilon 2
ntdll.dll! KiFastSystemCallRet
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_3_6_13r_INF_SSE2-20100804_r6348.exe! <no symbol>
Mantis?

[pecenipicek]

that particular one stinks of a borked pof. i mean its not like you see a bes being attacked very often.

[General Battuta]

Apparently so.

We've got a fixed model in Blue Planet SVN now, but people running without the MediaVPs under 3.6.13 are gonna be screwed.

[chief1983]

More broken retail data?  No one would have noticed this whole time?

How is it only 3.6.13?

[pecenipicek]

a bes was never attacked in the retail data

[General Battuta]

a bes was never attacked in the retail data

I don't know if this is true or not it but it cracked me up. 

Still, Procyon Insurgency?

[Timerlane]

Warzone had you escorting Beses a couple of times, too, IIRC.

[The E]

Quick note: This issue isn't specific to 3.6.13. It will pop up every time the AI tries to attack a specific subsystem using that system's path. This is a bug that is almost always caused by faulty pofs, and a great deal of (bad) luck.

[pecenipicek]

and its caused by some bad chunks in the pof data, relating to subys paths?

[chief1983]

I just want to make sure that whatever the issue is, that it's not _only_ presenting itself in 3.6.13, unless that's because 3.6.13 added some sort of error checking, but it sounds like the latter is not the case.

[Fury]

Was this path problem identified to be in mediavps freighter2v-01.pof, or in retail freighter2v-01.pof, or in both?

[chief1983]

First post _did_ say with retail assets, so I hope it's not MediaVPs.

[General Battuta]

First post _did_ say with retail assets, so I hope it's not MediaVPs.

Mediavps were in fact on but I was told the Bes hadn't been touched.

[blowfish]

First post _did_ say with retail assets, so I hope it's not MediaVPs.

Mediavps were in fact on but I was told the Bes hadn't been touched.

The model will have been modified to remove the a b c etc from the texture names, but I don't know why it would have been modified other than that.  Might wanna check the retail Bes just to be sure though.

[The E]

Yes, it was a problem with both the retail and the mediavps model. The model in the FSU svn has been fixed, though.