Hard Light Productions Forums

Community Projects => The FreeSpace Upgrade Project => Topic started by: General Battuta on August 10, 2010, 03:13:05 pm

Title: GVFR Bes & faulty subsystem paths
Post by: General Battuta on August 10, 2010, 03:13:05 pm: 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?
Title: Re: 3.6.13 causes crashes with retail assets
Post by: pecenipicek on August 10, 2010, 03:19:54 pm: that particular one stinks of a borked pof. i mean its not like you see a bes being attacked very often.
Title: Re: 3.6.13 causes crashes with retail assets
Post by: General Battuta on August 10, 2010, 03:43:41 pm: 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.
Title: Re: 3.6.13 causes crashes with retail assets
Post by: chief1983 on August 10, 2010, 03:44:26 pm: More broken retail data? No one would have noticed this whole time?

How is it only 3.6.13?
Title: Re: 3.6.13 causes crashes with retail assets
Post by: pecenipicek on August 10, 2010, 03:46:26 pm: a bes was never attacked in the retail data
Title: Re: 3.6.13 causes crashes with retail assets
Post by: General Battuta on August 10, 2010, 03:47:21 pm: Quote from: pecenipicek on August 10, 2010, 03:46:26 pm
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. :lol:

Still, Procyon Insurgency?
Title: Re: 3.6.13 causes crashes with retail assets
Post by: Timerlane on August 10, 2010, 07:57:04 pm: Warzone had you escorting Beses a couple of times, too, IIRC.
Title: Re: 3.6.13 causes crashes with retail assets
Post by: The E on August 10, 2010, 08:38:01 pm: 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.
Title: Re: 3.6.13 causes crashes with retail assets
Post by: pecenipicek on August 10, 2010, 09:17:22 pm: and its caused by some bad chunks in the pof data, relating to subys paths?
Title: Re: 3.6.13 causes crashes with retail assets
Post by: chief1983 on August 10, 2010, 10:25:58 pm: 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.
Title: Re: BVFR Bes & faulty subsystem paths
Post by: Fury on August 10, 2010, 11:08:25 pm: Was this path problem identified to be in mediavps freighter2v-01.pof, or in retail freighter2v-01.pof, or in both?
Title: Re: BVFR Bes & faulty subsystem paths
Post by: chief1983 on August 10, 2010, 11:35:31 pm: First post _did_ say with retail assets, so I hope it's not MediaVPs.
Title: Re: BVFR Bes & faulty subsystem paths
Post by: General Battuta on August 11, 2010, 12:08:46 am: Quote from: chief1983 on August 10, 2010, 11:35:31 pm
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.
Title: Re: BVFR Bes & faulty subsystem paths
Post by: blowfish on August 11, 2010, 12:23:15 am: Quote from: General Battuta on August 11, 2010, 12:08:46 am
Quote from: chief1983 on August 10, 2010, 11:35:31 pm
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.
Title: Re: BVFR Bes & faulty subsystem paths
Post by: The E on August 11, 2010, 07:48:18 pm: Yes, it was a problem with both the retail and the mediavps model. The model in the FSU svn has been fixed, though.