Beta Fleet Carriers at Sag A: The Fram Test

Status
Thread Closed: Not open for further replies.
To coincide with Obsidian's video, I've some remarks on taking the Fram to Sag A and details concerning its use while doing so. First, however, it must be addressed some responses to the fact this was done at all.


--
1. The goal was to be the first.
Answer: The goal was not to be the first, though I did wonder if that were the case and did have suspicions at least 1-3 others may have attempted the same. Congratulations to CMDR SpaceMeLater and the Spear of Bitter Mercy (B92-P2Q) for not only preceding the Fram's arrival by mere hours, but sharing in the achievement! Thanks, also, to Obsidian Ant and CMDR Valorin for making the Fram their passage to Sag A.

2. It is in Beta, therefore does not count, and there's no achievement for doing so in Beta.
Answer: The Beta is the primary reason for this undertaking. There's nothing to count except the gathering of information for the greater community and Frontier.
--

The Fram Test was conceived roughly 2 weeks preceding Beta 2, with purpose to examine long-distance use for Fleet Carriers (hereafter FCs). Its execution was inspired by the DSSA, and plans made for utilizing FCs by communities such as the Fuel Rats, Hull Seals, and others. While there are several contradictions in Beta 2 vs. what is intended for Live, all information regarding the fueling, usage, and finalize results for the Fram have been recorded to the best of my ability in a 24 hour period without sleep. They are sourced entirely from the UI. The Fram Test also includes my observations from initial purchase to arrival at Sag A.

Success: Zero lag, no disconnect, no stalling--mostly applies to hyperspace log.

Blue: Suggestion.
--

Beta 2 Log: The Fram Test

First load of Beta 2 - Could not resolve connection to Beta Server.
Close. Reload - Success.
Personal Ship: Ceryneian Hind (hereafter the Hind)
Jump into Carrier Service System Diso - Success.
Docking at Shifnalport, Diso - Success.
FC purchase - Success.

Carrier designated FRAM (K08-P6H).

Diso System Map - No icon for the Fram among large gathering of FCs.
Diso System Map - Fram not present.
Left Panel, Scroll - Fram located in listings. Indicator for the Fram is Yellow vs. Amber of default UI; they are too similar.
Supercruise - Waypoint targeting switched from the Fram to star system Mauradi. Cause unknown.
Supercruise - Exit to Fram. She drifted AWAY from the Hind. Ahead Full, impossible to reach.
Supercruise - Re-enter, exit to Fram in Normal Space with no prompt for safe exit. Fram continued to drift. 3 attempts failed.
Relog - Problem with Fram drift persisted.
Carrier Command - Issued jump order Diso > Orrere.
Jump - To Orrere, ahead of Fram.
Notificaion Received - Fram has entered Orrere.
Orrere System Map - Fram did not appear.
Left Panel, Scroll - Fram appeared.
Relog - Success.
Orrere System Map - Fram appeared. Icon indicating ownership atop FC icon.
Supercruise - Exit to Fram successful.
Fram - Docking succesful.
Fleet Transfer - Success.
Deposit into Fram Account - Success.
Carrier Command - Issued jump order Orrere > Diso for Carrier Servicing.

Fram outfitted with Shipyard for visitors, Repair, Refuel, and Universal Cartographics.

Personal Ship Change - Hind to Deer of Nine Colors (hereafter DNC) for Tritium allocation.
Carrier Command - Issued jump order Diso > Beronii.

The search for Tritium involved roughly 4-6 system checks before a proper source. All Tritium for the Fram Test was purchased from Libby Horizons, Oresqu (53,700 ls) via the DNC, with a total tonnage of 696. The first haul was shipped back to the Fram in Beronii; following logset occurred as the Fram was provisioned.

Carrier Command - Issued jump order Boronii > Oresqu, specifically targeting an orbit near Libby Horizons.
Supercruise - 1 incident. Exit to Fram, total crash.
Carrier OS - Entering and exiting Commodities Market temporarily greyed out Carrier Management.
Carrier OS - Above issue resolved by exiting, re-entering Carrier OS.
Jump - First live ride on the Fram, successful.
Supercruise - Fram's waypoint behaved as a star system waypoint upon departure of Libby Horizons, behind B2 from the port. Prep for supercruise acted as if making a full jump, with alert that target destination is obscured despite existing in the same system.
Right Panel, Inventory - Transfer to Carrier may temporarily White Out (text).
Right Panel, Inventory - Max transfer only operates Ship > Carrier, and not in reverse.
Right Panel, Inventory - Fix above issue by entering filter, selecting and de-selecting Damaging box.
Criminal Activity: Multiple 250cr fine alerts (erroneous) for dumping cargo at Libby Horizons. Cause unknown.
Right Panel: 1 incident glitched, permanently stuck on Transfer screen. Cause unknown.
Relog: Above issue fixed.

Fram fully supplied with Tritium. Joined by CMDR Valorin and Obsidian Ant prior to journey to Sag A. As some information is contained within the video attached below, I will only provide specific information in this post. From start to finish, every jump has been logged. Oresque to Sag A required nearly 17 hours of mostly non-stop activity, the majorly of jumps initiated within 10 seconds of the cooldown's end.

No indicator for traveling between Galactic Sectors was found to appear during FC jumps. This was checked with sharp attention to the Codex.


Jump Range & Fuel Use Record

1st max jump: 498.81ly; 264t - Success.
2nd max jump: 493.13ly; 262t - Success.
3rd max jump: 492.52ly; 261t - Success.
4th max jump: 498.02ly; 263t - Success.
5th max jump: 493.38ly; 260t - Success.
6th max jump: 494.10ly; 259t - Success.
7th max jump: 499.84ly; 258t - Success.
8th max jump: 494.10ly; 253t - Success.
9th max jump: 497.03ly; 256t - Success.
10th max jump: 492.38ly; 250t - Success.
11th max jump: 496.90ly; 251t - Success.
12th max jump: 499.44ly; 251t - Success.
13th max jump: 498.27ly; 249t - Success.
14th max jump: 497.37ly; 247t - Success.
15th max jump: 498.22ly; 246t - Success.
16th max jump: 499.03ly; 245t - Success.
17th max jump: 498.73ly; 244t - Success.
18th max jump: 499.51ly; 243t - Success.

INNER ORION SPUR > INNER SCUTUM-CENTAURUS ARM

19th max jump: 498.39ly; 241t - Success.
20th max jump: 498.53ly; 240t - Success.
21st max jump: 497.75ly; 239t - Success.
22nd max jump: 497.61ly; 238t - Success.
23rd max jump: 499.31ly; 237t - Success.
24th max jump: 498.11ly; 235t - Success.

INNER SCUTUM-CENTAURUS ARM > NORMA EXPANSE

25th max jump: 499.79ly; 235t - Success.
26th max jump: 499.93ly; 234t - Success.
27th max jump: 498.02ly; 232t - Success.

HALFWAY

28th max jump: 499.50ly; 321t - Success.

NORMA EXPANSE > NORMA ARM

29th max jump: 497.88ly; 229t - Success.
30th max jump: 498.33ly; 229t - Success.
31st max jump: 498.16ly; 227t - Success.
32nd max jump: 499.04ly; 227t - Success.
33rd max jump: 499.16ly; 225t - Success.
34th max jump: 499.13ly; 224t - Success.
35th max jump: 498.83ly; 223t - Success.
36th max jump: 499.33ly; 222t - Success.
37th max jump: 499.16ly; 221t - Success.
38th max jump: 498.48ly; 220t - Success.
39th max jump: 499.85ly; 219t - Success.

NORMA ARM > EMPYREAN STRAITS

40th max jump: 498.65ly; 218t - Success.
41st max jump: 499.24ly; 217t - Success.
42nd max jump: 498.97ly; 215t - Success.
43rd max jump: 499.76ly; 215t - Success.
44th max jump: 499.08ly; 213t - Success.
45th max jump: 498.95ly; 212t - Success.
46th max jump: 498.51ly; 211t - Success.
47th max jump: 498.53ly; 210t - Success.
48th max jump: 498.69ly; 209t - Success.

EMPYREAN STRAITS > GALACTIC CENTRE

49th max jump: 499.64ly; 208t - Success.
50th max jump: 499.70ly; 207t - Success.
51st max jump: 499.98ly; 206t - Success.
52nd max jump: 499.70ly; 205t - Success.
53rd jump: 64.34ly; 35t - Success.


At no time during the Fram Test did the process of jumping feel tedious or repetitive despite its intensely repetitive nature. During these wait times, I made every effort to not be sedentary and listened to music the entire 17 hours. The 15/5 ratio for spool-n-cool felt balanced and sensible, regardless how much time it added to the journey. DNC acted as a fuel transfer station between Fram's Cargo and Fuel Tank. The efficiency of mining is up to question, as the Fram Test sought to remove it entirely from the equation. With total load, it is estimated the Fram would have been capable of covering 41,000 lightyears before needing Tritium. The consecutive multi-jump have proven manually viable, flawless. However, a data point of 1 isn't enough.

The conclusion for fueling FCs is to make mining an option, but not the primary option. If anything, a last resort. Searching for Tritium has proven tedious for many, and perhaps should be available directly from Carrier Contacts in Carrier Service Systems. The ability to plot multiple jumps and automatically transfer Tritium into the Fuel Tank is recommended. Per the necessity of high amounts fuel to move considerable distance, it is also recommended the total space within the FCs be increased beyond 25,000 and/or resize the Fuel Tank to accommodate a mass quantity of fuel.

As for other statistics, given Beta 2's numbers are not final and may have errors, I'll defer to those with more knowledge.


 
Last edited:
To coincide with Obsidian's video, I've some remarks on taking the Fram to Sag A and details concerning its use while doing so. First, however, it must be addressed some responses to the fact this was done at all.


--
1. The goal was to be the first.
Answer: The goal was not to be the first, though I did wonder if that were the case and did have suspicions at least 1-3 others may have attempted the same. Congratulations to CMDR SpaceMeLater and the Spear of Bitter Mercy (B92-P2Q) for not only preceding the Fram's arrival by mere hours, but sharing in the achievement! Thanks, also, to Obsidian Ant and CMDR Valorin for making the Fram their passage to Sag A.

2. It is in Beta, therefore does not count, and there's no achievement for doing so in Beta.
Answer: The Beta is the primary reason for this undertaking. There's nothing to count except the gathering of information for the greater community and Frontier.
--

The Fram Test was conceived roughly 2 weeks preceding Beta 2, with purpose to examine long-distance use for Fleet Carriers (hereafter FCs). Its execution was inspired by the DSSA, and plans made for utilizing FCs by communities such as the Fuel Rats, Hull Seals, and others. While there are several contradictions in Beta 2 vs. what is intended for Live, all information regarding the fueling, usage, and finalize results for the Fram have been recorded to the best of my ability in a 24 hour period without sleep. They are sourced entirely from the UI. The Fram Test also includes my observations from initial purchase to arrival at Sag A.

Success: Zero lag, no disconnect, no stalling--mostly applies to hyperspace log.

Blue: Suggestion.
--

Beta 2 Log: The Fram Test

First load of Beta 2 - Could not resolve connection to Beta Server.
Close. Reload - Success.
Personal Ship: Ceryneian Hind (hereafter the Hind)
Jump into Carrier Service System Diso - Success.
Docking at Shifnalport, Diso - Success.
FC purchase - Success.

Carrier designated FRAM (K08-P6H).

Diso System Map - No icon for the Fram among large gathering of FCs.
Diso System Map - Fram not present.
Left Panel, Scroll - Fram located in listings. Indicator for the Fram is Yellow vs. Amber of default UI; they are too similar.
Supercruise - Waypoint targeting switched from the Fram to star system Mauradi. Cause unknown.
Supercruise - Exit to Fram. She drifts AWAY from the Hind. Ahead Full, impossible to reach.
Supercruise - Re-enter, exit to Fram in Normal Space with no prompt for safe exit. Fram continues to drift. 3 attempts failed.
Relog - Problem with Fram drift persists.
Carrier Command - Issued jump order Diso > Orrere.
Jump - To Orrere, ahead of Fram.
Notificaion Received - Fram has entered Orrere.
Orrere System Map - Fram does not appear.
Left Panel, Scroll - Fram appears.
Relog - Success.
Orrere System Map - Fram appears. Icon indicating ownership atop FC icon.
Supercruise - Exit to Fram successful.
Fram - Docking succesful.
Fleet Transfer - Success.
Deposit into Fram Account - Success.
Carrier Command - Issued jump order Orrere > Diso for Carrier Servicing.

Fram outfitted with Shipyard for visitors, Repair, Refuel, and Universal Cartographics.

Personal Ship Change - Hind to Deer of Nine Colors (hereafter DNC) for Tritium allocation.
Carrier Command - Issued jump order Diso > Beronii.

The search for Tritium involved roughly 4-6 system checks before a proper source. All Tritium for the Fram Test was purchased from Libby Horizons, Oresqu (53,700 ls) via the DNC, with a total tonnage of 696. The first haul was shipped back to the Fram in Beronii; following logset occurred as the Fram was provisioned.

Carrier Command - Issued jump order Boronii > Oresqu, specifically targeting an orbit near Libby Horizons.
Supercruise - 1 incident. Exit to Fram, total crash.
Carrier OS - Entering and exiting Commodities Market temporarily greyed out Carrier Management.
Carrier OS - Above issue resolved by exiting, re-entering Carrier OS.
Jump - First live ride on the Fram, successful.
Supercruise - Fram's waypoint behaved as a star system waypoint upon departure of Libby Horizons, behind B2 from the port. Prep for supercruise acted as if making a full jump, with alert that target destination is obscured despite existing in the same system.
Right Panel, Inventory - Transfer to Carrier may temporarily White Out (text).
Right Panel, Inventory - Max transfer only operates Ship > Carrier, and not in reverse.
Right Panel, Inventory - Fix above issue by entering filter, selecting and de-selecting Damaging box.
Criminal Activity: Multiple 250cr fine alerts (erroneous) for dumping cargo at Libby Horizons. Cause unknown.
Right Panel: 1 incident glitched, permanently stuck on Transfer screen. Cause unknown.
Relog: Above issue fixed.

Fram fully supplied with Tritium. Joined by CMDR Valorin and Obsidian Ant prior to journey to Sag A. As some information is contained within the video attached below, I will only provide specific information in this post. From start to finish, every jump has been logged. Oresque to Sag A required nearly 17 hours of mostly non-stop activity, the majorly of jumps initiated within 10 seconds of the cooldown's end.

No indicator for traveling between Galactic Sectors was found to appear during FC jumps. This was checked with sharp attention to the Codex.

1st max jump: 498.81ly; 264t - Success.
2nd max jump: 493.13ly; 262t - Success.
3rd max jump: 492.52ly; 261t - Success.
4th max jump: 498.02ly; 263t - Success.
5th max jump: 493.38ly; 260t - Success.
6th max jump: 494.10ly; 259t - Success.
7th max jump: 499.84ly; 258t - Success.
8th max jump: 494.10ly; 253t - Success.
9th max jump: 497.03ly; 256t - Success.
10th max jump: 492.38ly; 250t - Success.
11th max jump: 496.90ly; 251t - Success.
12th max jump: 499.44ly; 251t - Success.
13th max jump: 498.27ly; 249t - Success.
14th max jump: 497.37ly; 247t - Success.
15th max jump: 498.22ly; 246t - Success.
16th max jump: 499.03ly; 245t - Success.
17th max jump: 498.73ly; 244t - Success.
18th max jump: 499.51ly; 243t - Success.

INNER ORION SPUR > INNER SCUTUM-CENTAURUS ARM

19th max jump: 498.39ly; 241t - Success.
20th max jump: 498.53ly; 240t - Success.
21st max jump: 497.75ly; 239t - Success.
22nd max jump: 497.61ly; 238t - Success.
23rd max jump: 499.31ly; 237t - Success.
24th max jump: 498.11ly; 235t - Success.

INNER SCUTUM-CENTAURUS ARM > NORMA EXPANSE

25th max jump: 499.79ly; 235t - Success.
26th max jump: 499.93ly; 234t - Success.
27th max jump: 498.02ly; 232t - Success.

HALFWAY

28th max jump: 499.50ly; 321t - Success.

NORMA EXPANSE > NORMA ARM

29th max jump: 497.88ly; 229t - Success.
30th max jump: 498.33ly; 229t - Success.
31st max jump: 498.16ly; 227t - Success.
32nd max jump: 499.04ly; 227t - Success.
33rd max jump: 499.16ly; 225t - Success.
34th max jump: 499.13ly; 224t - Success.
35th max jump: 498.83ly; 223t - Success.
36th max jump: 499.33ly; 222t - Success.
37th max jump: 499.16ly; 221t - Success.
38th max jump: 498.48ly; 220t - Success.
39th max jump: 499.85ly; 219t - Success.

NORMA ARM > EMPYREAN STRAITS

40th max jump: 498.65ly; 218t - Success.
41st max jump: 499.24ly; 217t - Success.
42nd max jump: 498.97ly; 215t - Success.
43rd max jump: 499.76ly; 215t - Success.
44th max jump: 499.08ly; 213t - Success.
45th max jump: 498.95ly; 212t - Success.
46th max jump: 498.51ly; 211t - Success.
47th max jump: 498.53ly; 210t - Success.
48th max jump: 498.69ly; 209t - Success.

EMPYREAN STRAITS > GALACTIC CENTRE

49th max jump: 499.64ly; 208t - Success.
50th max jump: 499.70ly; 207t - Success.
51st max jump: 499.98ly; 206t - Success.
52nd max jump: 499.70ly; 205t - Success.
53rd max jump: 64.34ly; - Fuel not recorded - Success.


At no time during the Fram Test did the process of jumping feel tedious or repetitive despite its intensely repetitive nature. During these wait times, I made every effort to not be sedentary and listened to music the entire 17 hours. The 15/5 ratio for spool-n-cool felt balanced and sensible, regardless how much time it added to the journey. DNC acted as a fuel transfer station between Fram's Cargo and Fuel Tank. The efficiency of mining is up to question, as the Fram Test sought to remove it entirely from the equation. With total load, it is estimated the Fram would have been capable of covering 41,000 lightyears before needing Tritium. The consecutive multi-jump have proven manually viable, flawless. However, a data point of 1 isn't enough.

The Fram will remain at Sag A to the end of Beta 2. It is open for all CMDRs* with Universal Cartographics, Refuel, and Repair.
*Closed to Notorious CMDRs.

The conclusion for fueling FCs is to make mining an option, but not the primary option. If anything, a last resort. Searching for Tritium has proven tedious for many, and perhaps should be available directly from Carrier Contacts in Carrier Service Systems. The ability to plot multiple jumps and automatically transfer Tritium into the Fuel Tank is recommended. Per the necessity of high amounts fuel to move considerable distance, it is also recommended the total space within the FCs be increased beyond 25,000 and/or resize the Fuel Tank to accommodate a mass quantity of fuel.

As for other statistics, given Beta 2's numbers are not final and may have errors, I'll defer to those with more knowledge.


This insanely elaborate and well worded data!

Also: Thank's for the ride!

2020-05-12 18_14_13-Greenshot.jpg
 
Nice. How many ships did you have on your FC and how many "guests".
I had 4 ships in total, with 2 guests. Most jumps were made with only myself being live, given the time zone difference between the three of us. A several were done with two live. We also tested what happens when a guest on board attempts to log-in while the carrier is in lockdown. They receive a timer on the mode select screen, explaining the carrier on which they are situated is entering hyperspace.
 
I had 4 ships in total, with 2 guests. Most jumps were made with only myself being live, given the time zone difference between the three of us. A several were done with two live. We also tested what happens when a guest on board attempts to log-in while the carrier is in lockdown. They receive a timer on the mode select screen, explaining the carrier on which they are situated is entering hyperspace.
I also had two ships on the carrier. The T10 I docked with and a transfered Krait Phantom.
 
If you're still out at Sag A*, could you pop into Explorer's Anchorage and see if there's still Tritium available? There was in the first beta, but that may well have changed.
I can do that later. Wanted to take a look anyway. Last time I saw it, it hasn't finished building. :D
 
Excellent write up, I experienced a few of the same bugs as well, most notably the switching of waypoint from carrier to star system. There is a lot of useful information I can use as I am planning a trip to an explorer account I have.
 
This is great data! I'm currently on the way out there with my FC and am 2/3 of the way there. I don't have the ability to babysit the jumping so it is taking me awhile. Not to mention that gathering the initial tritium took forever on my own. Multi jump scheduling would be awesome for long hauls but, tbh, when I do this on live I will probably be taking more time to explore along the way anyway.
 
This is great data! I'm currently on the way out there with my FC and am 2/3 of the way there. I don't have the ability to babysit the jumping so it is taking me awhile. Not to mention that gathering the initial tritium took forever on my own. Multi jump scheduling would be awesome for long hauls but, tbh, when I do this on live I will probably be taking more time to explore along the way anyway.
The FC feels better suited to GPE (Gradual Process Exploration; just made up this term now for convenience) as opposed to making long distance trips at a fast pace. A definite mothership feel. It used to be that exploration required leaving the Bubble (or Colonia), and this being the fact bestowing a sense of isolation. With an FC, the sense of isolation is still present despite having a small city in relative close proximity. The farther one travels, the more the FC will feel like home, and in those most remote systems that have been so far beyond the reach of any normal ship, that FC becomes a lifeline back to humanity. Someone is bound to specialize in those types of systems, taking the risk of the FC running out of fuel, possibly in a system with no ice rings, that only another FC can reach.
 
Status
Thread Closed: Not open for further replies.
Top Bottom