Hosted Projects - Standalone > The Babylon Project

Many model warnings with latest FSO build

(1/3) > >>

wesp5:
So I was checking the latest FSO build with TBP 3.7.9 and Run Fast Debug and got over 20 model warnings, most of them looking like this: "Warning: On model 'BI_Falkosi.pof', the path for dockpoint 'rearm dock' does not have the same parent submodel as the dockpoint itself!" Any ideas on how to fix these? I took a look using pof-tools, but I can't see a difference between models that give the warning, e. g. CR_Sekundus and those that don't, e. g. CR_Primus, their parameters and the models look the same. Another less common error is "Warning: On model 'DF_Sky_Serpent.pof', path 0 for dockpoint 'dock point 2' is not valid!  The index is 9 but the total number of paths is 9." Sometimes models even give both warnings!

wesp5:
P.S.: I tried assigning detail0 as parent submodel and this seems to fix the first warning, although many models have no parent set there and still work fine. Maybe the docking point is outside of the model in the cases that give warnings? Anyway, I will fix all of these tomorrow and then will take a look at the second problem. Once I am finished I will upload the fixed models here, so somebody with Knossos access, Admiral Nelson?, can integrate them and maybe release a TBP 3.8.0 :)!

Goober5000:

--- Quote ---"Warning: On model 'BI_Falkosi.pof', the path for dockpoint 'rearm dock' does not have the same parent submodel as the dockpoint itself!"
--- End quote ---

I will have to tweak that message: most of the time the problem here is not the submodel but the actual path.  In other words the ship's path for that dockpoint could be wrong, and the dockpoint might need to be assigned a different path.

For the second problem, somehow the dockpoint does not have a valid path at all.

wesp5:

--- Quote from: Goober5000 on September 30, 2023, 06:14:13 pm ---I will have to tweak that message: most of the time the problem here is not the submodel but the actual path.

--- End quote ---

Pof-Tools lists $dock-01-01 for most of these paths and when I assign a parent the warning goes away. What is this path anyway? And what is the docking point? Especially with fighter which don't have a docking bay.


--- Quote ---For the second problem, somehow the dockpoint does not have a valid path at all.

--- End quote ---

Any way to fix that? Because Pof-Tools just crashes giving back a long error list...

wesp5:
P.S.: I tried using path01 instead of dock-01-01 and the warning went away for the two ships I tested too. So which solution is the correct one? Also there is at least one ship, NR_Cargo_Pod1 with no other path at all!

Navigation

[0] Message Index

[#] Next page