| From: | streu |
|---|---|
| Thread: | Phost experience |
| Forum: | Planets |
| In reply to: | Re: Phost experience |
| Date: | Wed, 2018-03-21 20:15 GMT |
You know what they use to say
The problem is between the keyboard and the chair
The warp was nota zero
Nonzero warp does not prevent training - training prevents nonzero warp ![]()
If training fails, you get an information in util.dat. PCC1 and EchoView can show that file. For example, training in free space will generate this:
Type 44, Length 14 -- Failed Action
Action: 10000
Ship Id: 78
Planet Id: 0
Cause: no matching target (19)
Mission: 38
Intercept: 400
Tow: 0
("no matching target" is the error code for "I didn't find the planet I need to get supplies from")
A little-known feature of PHost is that can also write a special log file (trace.log) intended for debugging. Unfortunately, that file is currently lacking the mission failure reasons. Successful training shows up as
Training:ship8: 300 supplies
in that file (invoke PHost as "phost -Lship8" to receive all information that applies to ship 8).
--Stefan
Note to self: add a util.dat viewer to PCC2 and PlanetsCentral