Automated Trade Lane builder - anyone want to try it?
I have a complete tool now, but I don't have much experience with making trade lanes and I'd be interested in getting feedback on it from people who want to try it out. I want to make sure it gets stress-tested before I submit it as a download. If you're interested and preferably have done trade lanes before, let me know and I can get you a copy; I just need feedback on how it behaves.
Unfortunately I don't have an easy spot to put up a screenshot right now, but here's a quick word picture. It's a simple graphical app (actually an HTA like aFLDirectIP and MyFLAccountID from Freelancer) for convenience.
At top there are 2 spots for you to put in the start and end ring positions - obviously you need to know where you're coming from and where you're going to even start a ring. There's a box for maximum distance between rings (default is 7500), and another one for a "base" name for your trade rings. The default is "TLR".
If you leave the defaults and then just plug in the start ring pos -29000, 0, -29000 and the end ring pos -20000, 0, -17000, the following is all automatically generated in a box at bottom. You can then copy and paste the entire thing into the system ini file where the trade lane is going to be.
A couple of comments on what I have...
+ I wanted to make it as generic as possible so that simple use wouldn't produce weird things. So I used an empty ids_info spot and there is no faction orientation for the rings created this way.
+ The example data would give you a short lane in li01.ini pointing vaguely from Trenton towards the sun.
+ The angles are automatically generated and worked ok for minor variations around the Trenton-to-sun orientation. The calculation will blow up for some angles, and does NOT work vertically yet. It's a standard but complex transformation based on the direction of the lane relative to the system axes, and I need to figure out details. Also, I get the impression that there may be a problem with near-vertical lanes from prior posts, so there may be an actual limitation for purely vertical lanes.
<pre><font size=1 face=Courier>
;; Autogenerated trade lane ring data follows.
;; vector: 9000,0,12000
;; lane length: 15000
;; Ring count: 2
;; ring spacing: 7500
;; unit vector: 0.6,0,0.8
[Object
nickname = TLR_Trade_Lane_Ring_0
ids_name = 260616
pos = -29000, 0, -29000
rotate = 0, -143, 0
Archetype = Trade_Lane_Ring
ids_info = 66170
next_ring = TLR_Trade_Lane_Ring_1
behavior = NOTHING
difficulty_level = 2
loadout = trade_lane_ring
pilot = pilot_solar_easy
[Object
nickname = TLR_Trade_Lane_Ring_1
ids_name = 260616
pos = -24500, 0, -23000
rotate = 0, -143, 0
Archetype = Trade_Lane_Ring
ids_info = 66170
prev_ring = TLR_Trade_Lane_Ring_0
next_ring = TLR_Trade_Lane_Ring_2
behavior = NOTHING
difficulty_level = 2
loadout = trade_lane_ring
pilot = pilot_solar_easy
[Object
nickname = TLR_Trade_Lane_Ring_2
ids_name = 260616
pos = -20000, 0, -17000
rotate = 0, -143, 0
Archetype = Trade_Lane_Ring
ids_info = 66170
prev_ring = TLR_Trade_Lane_Ring_1
behavior = NOTHING
difficulty_level = 2
loadout = trade_lane_ring
pilot = pilot_solar_easy
</font></pre>