Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: ARSPR on November 15, 2006, 02:13:06 pm

Title: "Warning: Couldn't fix up turret ..." inside mission
Post by: ARSPR on November 15, 2006, 02:13:06 pm
While testing Derelict's "The Stars are Right" with debug builds I get "Warning: Couldn't fix up turret indices in spline path" in several ships.

On three of them (capital02.pof, cruiser01x.pof and science01.pof) I get the message during mission loading. All these kinds of ships are present in the mission from the begining.

With the last one (corvette2s-01.pof), I get the error just when it jumps in from subspace.

Is this a normal behaviour? Or should corvette2s-01.pof warning have appeared during mission loading?. (I mean, is this a small bug?).
Title: Re: "Warning: Couldn't fix up turret ..." inside mission
Post by: Vasudan Admiral on November 15, 2006, 05:39:32 pm
It's a tiny error present in the original [v] models, which is why it's been missed a lot when doing HTL versions.

(Just copied my reply from this thread: http://www.hard-light.net/forums/index.php/topic,43126.0.html)
Quote
This should be fixed in the next media VP set.

In the meantime: http://sectorfiles.net/ti-file-dump/VasudanAdmiral/FixedPofs.zip and http://sectorfiles.net/ti-file-dump/VasudanAdmiral/FixedPofsIBX.zip

Stick the contents of both those zips in your models and cache folders respectively. They will fix that error (and all the other ships the same error will occur on), and the ones I've HTLed in there should run faster too. :)
Title: Re: "Warning: Couldn't fix up turret ..." inside mission
Post by: ARSPR on November 16, 2006, 08:43:30 am
Sorry about my English ...

I know the "Warning" is caused by small errors in pofs. What I was asking about is if the error of warp-in ships should appear during mission loading or when they're just going to jump in.
Title: Re: "Warning: Couldn't fix up turret ..." inside mission
Post by: Trivial Psychic on November 16, 2006, 07:47:25 pm
First of all, it sounds like you're using a debug build, since AFAIK a release build wouldn't complain about something like that.  Secondly, I've noticed that in debug FRED, an error such as this wouldn't come up until I'd placed the ship on the grid, so its possible that it waits for the ship to enter the playing field before it complains about the debug anomalies.